4 Commits

Include renames

Author	SHA1	Message	Date
weichenandCursor	10bff94a6a	Pin the D1 heads and cover the adapter modules ... Why: Dev has to test the split modules and refuse a core import of a sibling library. Evidence: bash scripts/lint-boundaries.sh printed boundaries ok. Full make test follows on this pin. Impact: test-libs runs the intent, native, sqlite, and command modules. The sibling allowlist is empty. Refs: D1 Co-authored-by: Cursor <cursoragent@cursor.com>	2026-10-03 13:47:02 +00:00
weichenandCursor	88d5787f29	Compare pin trees offline and archive finished task cards ... Why: Merge commits share a tree with the pinned feature commit, the import ratchet downloaded modules during CI, and task sync wrote the checkpoint onto the wrong card. Evidence: check-pins accepts 6c0f1e8 (same tree as Backend squad 8e987bf) and rejects empty-tree 8db069d; both objects stayed local. An empty GOMODCACHE run of lint-boundaries matches the cached go list, 14 pairs. bash -n scripts/task.sh. Impact: make pin no longer checks out Backend nested core or agent-command, and a failing pin check does not fail the target. task sync writes the branch card or warns. precheck reports completed-but-unarchived cards and card-close branches older than 24 hours. Refs: feature/agent-stack-r0-r1 Co-authored-by: Cursor <cursoragent@cursor.com>	2026-10-03 10:19:06 +00:00
weichenandCursor	978bf8bdae	Check nested library pins and test the three agent libraries ... Why: Dev could ship a combination whose nested gitlinks differed from the top-level pins, and make test never ran the three agent libraries. Evidence: A go.work was measured and not adopted: workspace MVS selected newer golang.org/x crypto, exp, net, term, and text than backend with GOWORK=off. check-pins passes on the new pins and fails when backend's squad pin is 5cbac00. Impact: make test adds pin checks and GOWORK=off vet/test for intent, native, and squad. make build still compiles inside backend; the pin check requires those gitlinks to match Dev. Refs: R0 Co-authored-by: Cursor <cursoragent@cursor.com>	2026-10-03 02:10:00 +00:00
weichenandCursor	09964e522b	Pin the extension roadmap and downstream spike ... Why: Downstream products need a published extension surface, contract checks, and a sample plugin that does not modify the base. Evidence: scripts/lint-boundaries.sh printed boundaries ok. examples/downstream-rdm go test passed. Submodule pointers record the core, documents, backend, ui, and frontend commits for this roadmap. Impact: make test runs the boundary lint first. make plugin-new scaffolds a declaration plugin. Version tags and remote downstream repositories are not created. Refs: .task/feature-base-extension-roadmap.md Co-authored-by: Cursor <cursoragent@cursor.com>	2026-10-01 10:35:15 +00:00