| Filename | Latest commit message | Latest commit date |
|---|---|---|
|
Some checks failed
wasm-build.yml / cmms-embed: ai-bridge apply — carry newly-placed symbols' (lib_symbols) defs (push) Failing after 0s
wasm-build.yml / cmms-embed: ai-bridge apply — carry newly-placed symbols' (lib_symbols) defs (release) Failing after 0s
release / meta (push) Has been cancelled
release / build (push) Has been cancelled
release / publish-wasm (push) Has been cancelled
release / deploy-demo (push) Has been cancelled
release / deploy-editor (push) Has been cancelled
release / Build all tools + KiCad e2e (Ubicloud) (push) Has been cancelled
The cmms-ai-editor-apply handler diffed the proposed sheet with docDelta and pushed the item delta through applyDeltaToY. docDelta only diffs uuid-bearing items; a (lib_symbols ...) definition has no uuid, so an AI proposal that places a part the sheet has never carried landed the instance with no library definition — KiCad drew an instance pointing at an undefined symbol (nothing). applyToActiveBuffer now upserts the proposal's lib defs into kdoc_libsymbols (upsert by lib id, never deletes — the CMMS's kicad_splice_elements always splices into the existing block, so the proposal is existing ∪ additions) before the item delta, mirroring kicad-binding.ts's own DOWN path (upsertLibSymbolsToY(doc, defs, ORIGIN)). Deliberately not syncLayoutToY, which would also LWW-reconcile non-item layout heads (root uuid, sheet_instances, paper) from the proposal. New ai-bridge.test.ts covers it (fails without the upsert: the placed symbol's definition never reaches kdoc_libsymbols). Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> |
||
| .. | ||
| public | ||
| scripts | ||
| src | ||
| .env.example | ||
| .env.production | ||
| index.html | ||
| package.json | ||
| postcss.config.js | ||
| tailwind.config.js | ||
| tsconfig.json | ||
| vite.config.ts | ||
| vitest.config.ts | ||
| wrangler.staging.jsonc | ||