Why: The task card is the review record, and it still pointed at a placeholder after the pull request existed.
Evidence: Dev pull request 147 is open.
Impact: The card status stays in progress until merge.
Refs: feature/stream-display-overhaul
Co-authored-by: Cursor <cursoragent@cursor.com>
Why: Tool calls stayed invisible while arguments streamed, and a failed run hid the only reply inside the collapsed process block.
Evidence: make test in the worktree passed: boundaries, core, backend, frontend vitest 66, ui vitest 79, agent-command. Mock browser check showed the Chinese process summary, the reply outside the fold, a humanized error with 继续执行, and the back-to-bottom button.
Impact: Dev gitlinks move to the feature commits for core, agent-native, backend, ui, and frontend. DESIGN.md §9.6 describes individual tool blocks for exec, write, and delegate.
Refs: feature/stream-display-overhaul
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-p4.md(PR#144) feature-s4-shell-overhaul.md(PR#145) — 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: P4 is on main, and the shell pull request has to record UI and frontend commits that contain both the workflow contracts and the shell.
Evidence: submodule trees match the merged mains for core, backend, documents, ui, and frontend.
Impact: the shell branch now contains P4's example workflows and the combined pins.
Refs: feature/s4-shell-overhaul
Co-authored-by: Cursor <cursoragent@cursor.com>
Why: The confirm card only folds after the client refetches the decision, so the parent pin has to include that frontend commit.
Evidence: make test passed; mock browser checked the shell, the pending filter, the blocked card, the folded row, and the molv theme.
Impact: task card records the result; modules/frontend moves to the refetch commit.
Refs: feature/s4-shell-overhaul
Co-authored-by: Cursor <cursoragent@cursor.com>
Why: The molv theme and the rebuilt shell land together, so the design doc and the submodule pins stay in one change.
Evidence: UI npm test 79 passed; frontend tsc -b and npm test 61 passed.
Impact: DESIGN.md records the molv token table; modules/ui and modules/frontend point at the shell branches.
Refs: feature/s4-shell-overhaul
Co-authored-by: Cursor <cursoragent@cursor.com>
Why: Acceptance needs the precheck, task-sync, and make test evidence on the card, plus what the three live conversations actually did.
Evidence: make test passed at 5f872f3. The sync row is in the table. The p4 service produced the slot question, one critic rejection, a confirmed plan, and the plugin script artifact.
Impact: Documentation only. The six pull requests stay unmerged.
Refs: feature/agent-harness-p4
Co-authored-by: Cursor <cursoragent@cursor.com>
Why: Dev should record the backend commit that runs a registered script from the launch of that call.
Evidence: go test ./internal/runtime/ -run TestRegisteredWorkflowUsesItsOwnScriptCopy passed.
Impact: Only the backend pointer moves.
Refs: feature/agent-harness-p4
Co-authored-by: Cursor <cursoragent@cursor.com>
Why: Dev should record the backend commit that makes planning return JSON and makes the critic reject a missing line.
Evidence: go test ./internal/runtime/ ./internal/prompts/ passed on that commit.
Impact: Only the backend pointer moves.
Refs: feature/agent-harness-p4
Co-authored-by: Cursor <cursoragent@cursor.com>
Why: The step critic has to call the configured model, and Dev should record that backend commit.
Evidence: go test ./internal/runtime/ -run TestJudgeUsesConfiguredModel passed in the backend repo.
Impact: Only the backend pointer moves.
Refs: feature/agent-harness-p4
Co-authored-by: Cursor <cursoragent@cursor.com>
Why: The live check needs the first draft to miss a line the critic can name, then the retry can add it.
Evidence: The prompt does not mention the marker. maxRetries stays 1.
Impact: demo.brief drafts are rejected until they contain 核对标记：P4.
Refs: feature/agent-harness-p4
Co-authored-by: Cursor <cursoragent@cursor.com>
Why: Dev has to record the Core, Backend, Frontend, UI, and Documents commits that implement intent-to-workflow.
Evidence: make test passed, including boundary lint, core, backend, frontend vitest, UI tsc and vitest, and agent-command.
Impact: agent-native stays at a34689c. The example plugin is already on this branch.
Refs: feature/agent-harness-p4
Co-authored-by: Cursor <cursoragent@cursor.com>
Why: The example plugin needs a bound intent and a plugin-shipped script so the three P4 paths can be checked against a real plugin.
Evidence: TestRepoExamplePluginLoads accepts the plugin, asks 主题是什么？, and keeps the topic slot.
Impact: demo.brief starts the five-step workflow. demo.script stays unbound and needs runtime.workflowScripts.
Refs: feature/agent-harness-p4
Co-authored-by: Cursor <cursoragent@cursor.com>
Why: The task card is the authorization record for intent-to-workflow work, and the routing, retry, and script rulings have to be fixed before code changes.
Evidence: precheck READY at 959179f88f; core/baseline.md and workflows/delivery.md section 1 were read.
Impact: No product code. Six pull requests are the delivery end, and merging them is not authorized.
Refs: feature/agent-harness-p4
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-p3b.md(PR#142) — 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: task-sync appends the checkpoint after the results section, and the card keeps those rows in the sync table.
Evidence: The row is the 2026-10-01T15:51:28Z checkpoint for d05a73872c.
Impact: No code change.
Refs: feature/agent-harness-p3b
Co-authored-by: Cursor <cursoragent@cursor.com>
Why: The card and the Dev pull request should name the five open requests and state that none are merged.
Evidence: Core #15, Backend #46, Frontend #32, UI #26, Dev #142.
Impact: No code change. Main is unchanged.
Refs: feature/agent-harness-p3b
Co-authored-by: Cursor <cursoragent@cursor.com>
Why: task-sync appends the checkpoint after the results section, and the card keeps those rows in the sync table.
Evidence: The row is the 2026-10-01T15:39:25Z checkpoint for 1bc9954e40.
Impact: No code change.
Refs: feature/agent-harness-p3b
Co-authored-by: Cursor <cursoragent@cursor.com>
Why: The task card has to show the combination test and the two live conversations before the pull requests open.
Evidence: make test passed at 6430738. p3b on 127.0.0.1:8841 showed a queued notice turn and a review pipeline.
Impact: No code change.
Refs: feature/agent-harness-p3b
Co-authored-by: Cursor <cursoragent@cursor.com>
Why: The combination has to move together so background subagents, review, and the notice row are the same build.
Evidence: Each module's own tests passed on its feature branch. agent-native stays at a34689c.
Impact: Dev does not merge this pin. The four module pull requests stay open until review.
Refs: feature/agent-harness-p3b
Co-authored-by: Cursor <cursoragent@cursor.com>
Why: Background subagents, review, squad role mapping, and prompt overrides need an explicit write scope and the three rulings before code edits.
Evidence: make precheck verdict READY at fdd311c8c0. Required reading baseline.md and delivery.md section 1.
Impact: No code change. Kernel and squad contracts stay as on main.
Refs: feature/agent-harness-p3b
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-p3.md(PR#140) — 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: task-sync appended the checkpoint after the test block. The card keeps sync rows in one table.
Evidence: sync_base bc8fef76bb, tested_head 53f8a05, checked_at 2026-10-01T14:50:18Z.
Impact: Task card only.
Refs: feature/agent-harness-p3
Co-authored-by: Cursor <cursoragent@cursor.com>
Why: The confirm card on a child run and the history split were only covered by tests. A real conversation had to show they hold before merge.
Evidence: p3a at dev@f823118. explore hid tool names from the next turn, writer pinned artifacts, the inbox showed the child confirm card, and the squad leader wrote output.md.
Impact: Task card only. No code change.
Refs: feature/agent-harness-p3
Co-authored-by: Cursor <cursoragent@cursor.com>
Why: The card is the pull request body, so it has to name the open Backend and Dev requests.
Evidence: Backend pull 45 and Dev pull 140 are open and unmerged.
Impact: Task card only. Neither request is merged.
Refs: feature/agent-harness-p3
Co-authored-by: Cursor <cursoragent@cursor.com>
Why: Acceptance needs the precheck, task-sync, and test evidence on the same card that will become the pull request.
Evidence: make task-sync at 5ed3649; make test exited 0 (boundaries, core, backend, frontend 51, ui 71, agent-command).
Impact: Task card only. No code or submodule change.
Refs: feature/agent-harness-p3
Co-authored-by: Cursor <cursoragent@cursor.com>
Why: Subagents now run a profile-scoped tool loop and stay out of the parent history. The Dev checkout has to build that backend.
Evidence: Backend 5051a06; go test ./... and make test passed in this checkout. The three agent-native gitlinks stay a34689c.
Impact: Only modules/backend moves. Squad, core, and the three agent-native pins stay put.
Refs: feature/agent-harness-p3
Co-authored-by: Cursor <cursoragent@cursor.com>
Why: The subagent runtime task needs an explicit write scope and the two rulings before backend edits.
Evidence: make precheck verdict READY at bc8fef76bb. Required reading baseline.md and delivery.md section 1.
Impact: No code change. Kernel, squad, and core contracts stay as on main.
Refs: feature/agent-harness-p3
Co-authored-by: Cursor <cursoragent@cursor.com>
weichen
