- composer: contenteditable input where viewport picks and operation tips
land as atomic colored chips ([face:6](face:6) / [fillet](op:fillet)),
peers of free text; IME-safe Enter (composition never submits);
atomic chip backspace; plain-text paste
- operation tips are markdown content, not code: viewer/server/operations/
<op_id>.md (frontmatter label/category/api/reads/doc_refs + hint body),
loaded by a stdlib frontmatter parser with mtime cache; broken files are
named in payload errors, never silently skipped
- five categories per the human's classification (sketch / solid / modify /
surface / pattern); palette rendered from GET /api/operations
- compose_submission embeds operation_context for every referenced op
- SOURCE tab: read-only CodeMirror python view (PythonEditor extracted from
SourceDock, shared extensions) with file tabs and line-range reveal
- FEATURE TREE: viewer's DAG algorithm extracted as FeatureTreeView
(apply_tag hidden, REF/USED/IN badges); clicking a feature switches to
SOURCE and highlights its source span; FTC-header fallback before the
first captured package
- tests: registry load + broken-file naming + operation context (9 pass)
Interactive re-mode (re.html) plus a local case server implementing the
ppt-master handshake: the human selects faces / draws regions / labels intent
on the original STEP, the browser composes a submission with server-side
entity context, and a waiting agent reconstructs per the existing
reconstruction contract and writes artifacts the UI polls back.
- viewer/server (stdlib-only): STEP -> synthesized Scene 2.0 projection
(GLB + entity sidecars, same shape as package scenes), region resolve
(centroid projection + front-facing filter), entity descriptors,
atomic submissions, ndjson side recording, --daemon/--wait/--wait-only/
--shutdown CLI with lockfile and 590s budget
- viewer/src: extract shared cad-three/entity-facts modules (main.ts now
consumes them), new SceneView class (assembly/picking/highlight) reused
by both studio viewports
- re-mode UI: annotation canvas (circle/lasso), intent palette, context
preview, submit flow, rebuilt v3 package loading, comparison image,
feature tree, evaluation tab
- governance: only the browser writes submission.json; UI never edits
geometry — code stays the single source of truth
- tests: 6 server tests (scene contract, region math, submission context
+ named failures, wait handshake exit codes, HTTP endpoints)