Why: The task card is the PR description, and it needs the Backend and Dev pull request links.
Evidence: Backend pull request 44 and Dev pull request 138 are open. Neither is merged.
Impact: Documentation only.
Refs: feature/agent-harness-p2
Co-authored-by: Cursor <cursoragent@cursor.com>
Why: Acceptance needs the precheck, task-sync, and make test output on the task card before the pull requests.
Evidence: task-sync sync_base=d02fa9c20a tested_head=f9d7bbe9f2. make test exited 0.
Impact: Documentation only. No further code change.
Refs: feature/agent-harness-p2
Co-authored-by: Cursor <cursoragent@cursor.com>
Why: Direct runs now check artifacts and run a fail-closed verifier before they stop. The Dev checkout has to build that backend.
Evidence: Backend a3ae1b9; go test ./... passed in that checkout. agent-native gitlinks stay a34689c.
Impact: Only modules/backend moves. Squad and the three agent-native pins stay put.
Refs: feature/agent-harness-p2
Co-authored-by: Cursor <cursoragent@cursor.com>
Why: The harness P2 task needs an explicit write scope before backend edits: direct-path checks and a fail-closed verifier, with PRs as the endpoint.
Evidence: make precheck verdict READY at d02fa9c20a; required reading baseline.md and delivery.md section 1.
Impact: No code change. Backend, squad, and kernel behavior stay as on main until the implementation commits.
Refs: feature/agent-harness-p2
Co-authored-by: Cursor <cursoragent@cursor.com>
Why: branches merged into main had left their task cards open; backfill status and archive to prevent bookkeeping debt.
Evidence: feature-agent-harness-p1.md(PR#136) — merges verified via git log --merges against origin/main.
Impact: .task/*.md moved to .task/archive/ with status backfilled; no code or submodule change.
Refs: task.sh close (card-autoclose-r1)
Why: the task card is the main record, and review needs the Dev pull request link.
Evidence: Dev pull request 136 is open against main.
Impact: task card only.
Refs: feature/agent-harness-p1
Co-authored-by: Cursor <cursoragent@cursor.com>
Why: acceptance needs the precheck, task-sync, and test evidence on the task card before review.
Evidence: task-sync reported already up to date at 701d4ab1e3; make test had already passed on b7631c7.
Impact: task card only.
Refs: feature/agent-harness-p1
Co-authored-by: Cursor <cursoragent@cursor.com>
Why: the direct chat path and both consumers must compile the same agent-native commit, or the new loop fields exist in only one replace target.
Evidence: make test passed (boundaries, core, backend, frontend 51, ui 71, agent-command). The three agent-native gitlinks are a34689c.
Impact: Dev pins deps/agent-native, deps/agent-squad, and modules/backend. Squad behavior stays on the zero-value kernel switches.
Refs: feature/agent-harness-p1
Co-authored-by: Cursor <cursoragent@cursor.com>
Why: branches merged into main had left their task cards open; backfill status and archive to prevent bookkeeping debt.
Evidence: feature-agent-harness-p0.md(PR#134) — merges verified via git log --merges against origin/main.
Impact: .task/*.md moved to .task/archive/ with status backfilled; no code or submodule change.
Refs: task.sh close (card-autoclose-r1)
Why: The task card is the main record, and it still said the Dev pull request was pending after the request was opened.
Evidence: Dev pull request 134 is open against main.
Impact: Task card text only. No code or gitlink change.
Refs: feature/agent-harness-p0
Co-authored-by: Cursor <cursoragent@cursor.com>
Why: The model imitated flattened tool-call text and invented artifact ids. P0 stops that replay, and the proposal records the harness work that still sits in later phases.
Evidence: Documents PR 32 and Backend PR 42. Backend go test ./... passed. Dev make test passed (boundaries, core, backend, frontend 51, ui 71, agent-command).
Impact: Gitlinks move to feature/agent-harness-p0 on documents (a3f0b80) and backend (188c633). No other submodule changes. P1-P4 are not implemented.
Refs: feature/agent-harness-p0
Co-authored-by: Cursor <cursoragent@cursor.com>
Why: Downstream products need a published extension surface, contract checks, and a sample plugin that does not modify the base.
Evidence: Boundary lint passed. examples/downstream-rdm go test passed. Submodule pointers record the core, documents, backend, ui, and frontend commits.
Impact: Merge order is Core, Documents, UI, and Frontend, then Backend, then this PR. Do not squash the submodule PRs. make test runs the boundary lint first. Version tags and the remote downstream repository are not created.
Refs: .task/feature-base-extension-roadmap.md
Why: The task card needs the Dev PR and the submodule merge order once the branches are published.
Evidence: Pull requests Core 14, Documents 31, UI 25, Frontend 31, Backend 41, and Dev 132 are open.
Impact: Submodule pulls must be merged without squash before Dev, so the gitlinks stay reachable.
Refs: .task/feature-base-extension-roadmap.md
Co-authored-by: Cursor <cursoragent@cursor.com>
Why: task-sync appends its checkpoint to the first file in .task, which was another task's card.
Evidence: The 2026-10-01T10:39:24Z row now sits in feature-base-extension-roadmap.md. The other card matches its previous content.
Impact: The recorded sync base is origin/main 26dfea7ed6 and the tested head is the merge 6d496139b4.
Refs: .task/feature-base-extension-roadmap.md
Co-authored-by: Cursor <cursoragent@cursor.com>
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>
Why: The merge subject did not match the auto-close pattern, so the card stayed open after the work landed.
Evidence: PR 130 merge 26dfea7ed6 is on origin/main
Impact: The card moves to .task/archive and is marked complete.
Refs: feature/card-close-native-squad-full-upgrade
Co-authored-by: Cursor <cursoragent@cursor.com>
Why: Dev has to record the library commits the product now builds against.
Evidence: make test
Impact: runtime.entry stays direct. This commit only moves gitlinks.
Refs: feature/native-squad-full-upgrade
Co-authored-by: Cursor <cursoragent@cursor.com>
Why: The branch is already on main, and the card still said the work was in progress.
Evidence: PR 128 merged as f8fefa0f88.
Impact: The card is archived as completed. No product behavior changes.
Refs: deliverable-quality-system
Co-authored-by: Cursor <cursoragent@cursor.com>
Why: The product needs the new content rules and the optional squad entry, while the library pins must match the kernel and router those paths compile against.
Evidence: Backend go test ./... -count=1 passed on 268f4a9. runtime.entry stays direct because no paired live scores exist.
Impact: Dev now points at the quality and squad-entry backend, agent-native cfc840c, and agent-squad d38f838. make eval-deliverables runs the scorecard tests.
Refs: deliverable-quality-system
Co-authored-by: Cursor <cursoragent@cursor.com>
Why: branches merged into main had left their task cards open; backfill status and archive to prevent bookkeeping debt.
Evidence: feature-agent-professional-deliverables.md(PR#126) — merges verified via git log --merges against origin/main.
Impact: .task/*.md moved to .task/archive/ with status backfilled; no code or submodule change.
Refs: task.sh close (card-autoclose-r1)
Why: The card still named only the backend pull request after the Dev
pin PR was opened.
Evidence: Dev PR #126 and backend PR #38 are both linked from the card.
Impact: Bookkeeping only.
Refs: feature/agent-professional-deliverables
https: //git-home.u1680832.nyat.app:30319/weichen/Agent-System-Dev/pulls/126
Co-authored-by: Cursor <cursoragent@cursor.com>
Why: The deliverable standards landed in Agent-System-Backend and were
merged, so the Dev pin has to move to that commit before this branch
can be reviewed.
Evidence: Backend PR #38 merged as 2079b2dfa851bd4cbe8f399a015126c842c441ec.
make test passed on this worktree before the pin move; the pin itself
does not change Dev source.
Impact: modules/backend now points at the merged standards. No other
submodule moved.
Refs: feature/agent-professional-deliverables
https: //git-home.u1680832.nyat.app:30319/weichen/Agent-System-Backend/pulls/38
Co-authored-by: Cursor <cursoragent@cursor.com>
Why: The task card still had empty goal and evidence fields after the
backend implementation landed in its own pull request.
Evidence: Backend PR #38 is open. go test ./... and the house-style
lint of the sample minutes are recorded on the card.
Impact: Bookkeeping only. The Dev gitlink stays on the previous backend
commit until that pull request merges.
Refs: feature/agent-professional-deliverables
https: //git-home.u1680832.nyat.app:30319/weichen/Agent-System-Backend/pulls/38
Co-authored-by: Cursor <cursoragent@cursor.com>
weichen
