Mark/Kimi_Agent_Brother_10_Digitizing_App
1
0
Fork 0
Code Issues 14 Pull requests Projects Releases Packages Wiki Activity Actions

Decompose: Implement real auto-digitize engine — Phase 3: Satin Column Stitch Generation #8

New issue
Closed
opened 2026-06-22 15:28:15 +00:00 by Mark · 2 comments
Mark commented 2026-06-22 15:28:15 +00:00
Owner
Copy link

⚠️ Re-scoped — blocked on #11

This work was originally framed as "implement from scratch." After auditing the
existing ~/Projects/easystitch/ project (a complete Python embroidery CAM with
5-stage pipeline, satin/fill/running generation, ΔE color matching, and PES/DST/
EXP/JEF output), the right shape is call the EasyStitch service rather than
re-implement the algorithms.

Blocked on #11 ("Stand up EasyStitch as an HTTP service for ThreadCraft").
Until that service exists, this work has no backend to call.

Donor code in EasyStitch (do not port — call it):

  • ~/Projects/easystitch/src/embroidery_converter/satin_stitch_generator.py
  • ~/Projects/easystitch/src/embroidery_converter/underlay_generator.py

New scope (post #11)

Satin stitch generation runs in the Python service. The TypeScript
side only renders the result.

  1. Receive stitchObjects[].type == 'satin' from the /v1/digitize
    response (introduced in #6).
  2. Render each satin object as a series of short line segments along
    the stitches[] point list. Color from threadColor.
  3. Add a src/lib/canvas/satinRenderer.ts that draws the segments to
    a Fabric.js Path or Polyline.
  4. Do not port the medial-axis / perpendicular-walk algorithm.
  5. Do not duplicate the underlay generation — that's also in the
    service response (separate stitch object type or a flag on the
    satin object).

Acceptance: a satin column in a test image renders on the canvas as
parallel stitch pairs that visually correspond to the source region,
and the rendering survives a canvas zoom to 400% without aliasing
into invisibility.

## ⚠️ Re-scoped — blocked on #11 > This work was originally framed as "implement from scratch." After auditing the > existing `~/Projects/easystitch/` project (a complete Python embroidery CAM with > 5-stage pipeline, satin/fill/running generation, ΔE color matching, and PES/DST/ > EXP/JEF output), the right shape is **call the EasyStitch service** rather than > re-implement the algorithms. > > **Blocked on #11** ("Stand up EasyStitch as an HTTP service for ThreadCraft"). > Until that service exists, this work has no backend to call. > > Donor code in EasyStitch (do not port — call it): - `~/Projects/easystitch/src/embroidery_converter/satin_stitch_generator.py` - `~/Projects/easystitch/src/embroidery_converter/underlay_generator.py` ## New scope (post #11) Satin stitch generation runs in the Python service. The TypeScript side only renders the result. 1. Receive `stitchObjects[].type == 'satin'` from the `/v1/digitize` response (introduced in #6). 2. Render each satin object as a series of short line segments along the `stitches[]` point list. Color from `threadColor`. 3. Add a `src/lib/canvas/satinRenderer.ts` that draws the segments to a Fabric.js `Path` or `Polyline`. 4. Do not port the medial-axis / perpendicular-walk algorithm. 5. Do not duplicate the underlay generation — that's also in the service response (separate stitch object type or a flag on the satin object). Acceptance: a satin column in a test image renders on the canvas as parallel stitch pairs that visually correspond to the source region, and the rendering survives a canvas zoom to 400% without aliasing into invisibility.
Mark commented 2026-06-22 16:02:41 +00:00
Author
Owner
Copy link

Blocked on #11 (Stand up EasyStitch as an HTTP service for ThreadCraft).

This work has been re-scoped — see the updated body. The reframe replaces
"implement from scratch" with "call the EasyStitch service and render the
result." #11 must complete first; once the service exposes /v1/digitize and
/v1/export, this work becomes a thin client + canvas rendering job.

cc: #11

**Blocked on #11** (Stand up EasyStitch as an HTTP service for ThreadCraft). This work has been re-scoped — see the updated body. The reframe replaces "implement from scratch" with "call the EasyStitch service and render the result." #11 must complete first; once the service exposes `/v1/digitize` and `/v1/export`, this work becomes a thin client + canvas rendering job. cc: #11
Mark commented 2026-06-23 22:05:23 +00:00
Author
Owner
Copy link

Blocked-on update

This issue is blocked on easystitch-service#1 ("FastAPI wrapper exposing easystitch pipeline as HTTP service").

Why: satin stitch generation runs in the service; rendering the response is the TS-side work.

The parent ticket [Kimi_Agent_Brother_10_Digitizing_App#11] is the integration contract. The actual implementation lives in Mark/easystitch-service. When easystitch-service#1 closes, this issue can move forward.

There is also a frontend-side wiring issue: [Mark/easystitch-service#3] ("TypeScript client wrapper + vite dev proxy") — that one will be mirrored into the ThreadCraft repo as a frontend sub-issue when it's ready to dispatch.

## Blocked-on update This issue is blocked on **easystitch-service#1** ("FastAPI wrapper exposing easystitch pipeline as HTTP service"). **Why:** satin stitch generation runs in the service; rendering the response is the TS-side work. The parent ticket [Kimi_Agent_Brother_10_Digitizing_App#11] is the integration contract. The actual implementation lives in [Mark/easystitch-service](https://forgejo.tail018ac4.ts.net/Mark/easystitch-service). When easystitch-service#1 closes, this issue can move forward. There is also a frontend-side wiring issue: [Mark/easystitch-service#3] ("TypeScript client wrapper + vite dev proxy") — that one will be mirrored into the ThreadCraft repo as a frontend sub-issue when it's ready to dispatch.
Mark 2026-06-27 08:48:46 +00:00
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
No results found.
Labels
Clear labels   
blocked:commit-ready-failed

   
blocked:gate-fetch

   
blocked:gate-lint

   
blocked:gate-plan

   
blocked:gate-research

   
blocked:needs-attention

Worker halted; needs human/janitor inspection

  
blocked:needs-decision

   
blocked:needs-human

   
blocked:no-changes

   
blocked:verify-failed

   
bug

   
deferred

   
feature-request

   
in-progress

   
needs-decompose

   
needs-triage

   
quickfix

   
security/medium

   
triage-approved
No labels
blocked:commit-ready-failed
blocked:gate-fetch
blocked:gate-lint
blocked:gate-plan
blocked:gate-research
blocked:needs-attention
blocked:needs-decision
blocked:needs-human
blocked:no-changes
blocked:verify-failed
bug
deferred
feature-request
in-progress
needs-decompose
needs-triage
quickfix
security/medium
triage-approved
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
Mark/Kimi_Agent_Brother_10_Digitizing_App#8
No description provided.