root/moteva
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: record reference anchor placement and generating label notes

Browse Source 
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This commit is contained in:
liangxu
2026-07-17 09:08:04 +08:00
parent 9da13d2814
commit fe4b08f548
3 changed files with 29 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
progress.md
+10
View File
@@ -198,6 +198,16 @@
- Benchmarked the maximum fully connected 640 x 480 color analysis at about 22ms and confirmed the updated single preview server responds at `http://127.0.0.1:5175`.
- The configured in-app browser backend remained unavailable, so final interactive visual inspection is left to the running local preview; source-level interaction coverage and HTTP verification pass.
### Phase 34: Reference-Anchored Generation Placement
- **Status:** complete
- Started tracing ordered image capsules through prompt serialization, agent submission, streamed project updates, and generated-node reconciliation.
- Confirmed the capsule retains its canvas node ID before submission, while the current generation update path has no reference anchor for result placement.
- Added ordered canvas-reference resolution and a hidden per-turn anchor directive; the visible optimistic Agent message still contains only the user's original capsules and prompt.
- Positioned generation placeholders plus final incremental/non-incremental outputs to the right of the last canvas-backed capsule, with multiple outputs ordered horizontally and no-match behavior unchanged.
- Added frontend and Go regressions for last-capsule selection, URL fallback, unmatched external capsules, directive parsing, immutable anchors, multi-output ordering, and default placement.
- Verification passes: 36 frontend tests, strict TypeScript compilation, Next/Vite production builds, `go mod tidy`, full Go tests, Go build, focused final regressions, and `git diff --check`.
- Restarted the updated preview at `http://127.0.0.1:5175` with the rebuilt backend on `http://127.0.0.1:8889`; frontend, backend auth options, and the frontend API proxy all return HTTP 200.
### Phase 30: Native-Resolution Vector Crop Fidelity
- **Status:** in_progress
- Reproduced the user-visible symptom from the supplied comparison: the cropped transparent WebP has substantially thicker CAD strokes and degraded text/detail than the source SVG.