Why: include the current integration baseline before verification.
Evidence: fetched origin/main=efa8f2b3322490c8c1a49707ed3f7a3970927cf8.
Impact: integrate upstream changes without rewriting task history.
Refs: task-sync
Why: merging origin/main changed governance tests, so the combo had to be run again.
Evidence: SELF make test and make build exited 0 on 87a4559e0f after unsetting a local telemetry variable that corrupted one receipt.
Impact: the task card stores the pass and the earlier failure; duty pins are unchanged.
Refs: .task/feature-rdm-duty-matrix.md
Co-authored-by: Cursor <cursoragent@cursor.com>
Why: PR #567 is merged and its task card must be backfilled and archived without touching other pending cards.
Evidence: Exact HEAD 3ffd641 passed test, test-pg, and svc-realcombo; merge d51828a has the same tree as the candidate; task-finish recycled the task worktree and branches.
Impact: Moves only feature-goal-first-delivery.md to .task/archive and records final delivery evidence.
Refs: #567, #518
Why: origin/main moved and the duty branch has to contain it before merge.
Evidence: SELF make task-sync exit 0, sync_base=d51828a73aaebd15a52da7dc5f6b63ad7188ad9a, changed=1.
Impact: the branch includes the goal-first delivery scripts; duty pins are unchanged.
Refs: .task/feature-rdm-duty-matrix.md
Co-authored-by: Cursor <cursoragent@cursor.com>
Why: include the current integration baseline before verification.
Evidence: fetched origin/main=d51828a73aaebd15a52da7dc5f6b63ad7188ad9a.
Impact: integrate upstream changes without rewriting task history.
Refs: task-sync
Why: the combo test has to cover the frontend and documents commits that contain origin/main.
Evidence: SELF make test and make build exited 0 on 92e809c6dd.
Impact: the task card stores those receipts; product pins are unchanged.
Refs: .task/feature-rdm-duty-matrix.md
Co-authored-by: Cursor <cursoragent@cursor.com>
Why: frontend and documents were updated so their heads contain origin/main before merge.
Evidence: SELF frontend vitest 293 passed on 04269ee; both pull requests merged.
Impact: modules/frontend is 04269ee and modules/documents is 5f41149.
Refs: .task/feature-rdm-duty-matrix.md
Why: the branch must contain origin/main before it can be merged.
Evidence: SELF make task-sync exit 0, sync_base=919f75cf7b39ca357e212a08a0ba5ba3d9a79b51, tested_head=ba1bdfb3c7a8a7ddf042c5915ec4f2db685a3e95, changed=0.
Impact: the task card stores the sync receipt; product pins are unchanged.
Refs: .task/feature-rdm-duty-matrix.md
Co-authored-by: Cursor <cursoragent@cursor.com>
Why: the pin for the duty draft recovery needs evidence written by the evidence tool.
Evidence: SELF make test and make build both exited 0 on 692b7a0239.
Impact: the task card stores those receipts; product pins are unchanged.
Refs: .task/feature-rdm-duty-matrix.md
Co-authored-by: Cursor <cursoragent@cursor.com>
Why: Gitea containers may leave SIGKILLed children as zombies until PID 1 reaps them, while kill -0 still reports success.
Evidence: Both timeout tests and the full AgentExecControllerTests suite pass; git diff --check passes.
Impact: Changes test liveness detection only; genuinely running child processes still fail the assertions.
Refs: #567
Why: the combo has to build the frontend that drops a dirty duty draft when a save result is unknown.
Evidence: SELF frontend vitest, tsc, knip, and Playwright passed on 985fc0f.
Impact: modules/frontend moves from 6093beb to 985fc0f.
Refs: .task/feature-rdm-duty-matrix.md
Co-authored-by: Cursor <cursoragent@cursor.com>
Why: PR #567 CI runs without a global Git user identity, causing every successful agent transport commit to fail with exit 128.
Evidence: The focused no-identity regression plus AgentExecControllerTests and AgentExecHistoryTests pass (30 executions total); git diff --check passes.
Impact: Supplies a deterministic non-secret identity only to git commit-tree; routing, receipts, and transport validation are unchanged.
Refs: #567
Why: acceptance evidence has to be produced by the evidence tool after the branch contains origin/main.
Evidence: SELF make test, make build, RDM package tests, a fresh PostgreSQL legacy migration, and three Playwright duty flows all exited 0.
Impact: the task card stores those receipts; product code is unchanged.
Refs: .task/feature-rdm-duty-matrix.md
Co-authored-by: Cursor <cursoragent@cursor.com>
Why: Record the fixed-candidate validation and independent fresh-session review before opening the delivery PR.
Evidence: PI MiniMax-M3 session 01a13eb4-5e25-70e9-95ae-2342ec525fac reported NO_FINDINGS for fec42e0320c458a8aa060ce9295f332a3ec6d58d; make test and make build passed.
Impact: Updates only delivery metadata; implementation behavior is unchanged.
Refs: feature/goal-first-delivery
Why: acceptance needs a task-sync receipt taken after origin/main is contained.
Evidence: SELF make task-sync exit 0, sync_base=919f75cf7b39ca357e212a08a0ba5ba3d9a79b51, tested_head=4163e2291818b5689afdf9ce651542e9680d973d, changed=0.
Impact: the task card stores the sync receipt; product pins are unchanged.
Refs: .task/feature-rdm-duty-matrix.md
Co-authored-by: Cursor <cursoragent@cursor.com>
Why: acceptance has to include the current main, including newer backend, core, and UI pins, while the duties page stays assignment-only.
Evidence: SELF frontend vitest 292 passed after merging the duties conflict; the earlier task-sync receipt records the submodule conflict that this commit resolves.
Impact: frontend pin is 6093beb; backend, core, and UI follow origin/main.
Refs: .task/feature-rdm-duty-matrix.md
Co-authored-by: Cursor <cursoragent@cursor.com>
Why: execution history intentionally adds one source-external Git metadata path after every run
Evidence: focused fallback and history tests
Impact: preserves the no-canonical-implementation assertion while accepting the history record
Refs: feature/goal-first-delivery
Why: include the current integration baseline before verification.
Evidence: fetched origin/main=919f75cf7b39ca357e212a08a0ba5ba3d9a79b51.
Impact: integrate upstream changes without rewriting task history.
Refs: task-sync
Why: Keep the final PR, component references and operational acceptance boundaries in the authoritative task record.
Evidence: Existing fixed-product review and local verification receipts are linked without relabeling their provenance.
Impact: Task-record metadata only; the reviewed product combination is unchanged.
Refs: Dev #565
Why: Deliver the completed conversation and work-card experience to 8788 after exact-head gates.
Evidence: Independent review and both focused addenda are complete; local test, build and environment-conflict records are retained honestly.
Impact: Pin the final frontend ownership guard and record delivery boundaries; no further product scope is added.
Refs: feature/workbench-flow-completion
Why: include the current integration baseline before verification.
Evidence: fetched origin/main=37a8791cb9f736a7f58e87a88389a55095f06e0d.
Impact: integrate upstream changes without rewriting task history.
Refs: task-sync
Why: Complete execution history must retain outputs beyond one API event page.
Evidence: Independent replay passed both pagination-boundary and stalled-cursor tests; production frontend source is unchanged.
Impact: Pin a test-only frontend follow-up to the reviewed workbench combination.
Refs: feature/workbench-flow-completion review pagination addendum
Why: align the task card with the completed three-CLI routing and execution-history scope
Evidence: source-external probe receipts and git diff --check
Impact: marks implementation complete and final delivery gates pending
Refs: #518
Why: retain which CLI handled each task so routing can improve from real outcomes over time
Evidence: AgentExecHistoryTests and git diff --check
Impact: appends sanitized source-external JSONL records without changing run outcomes
Refs: feature/goal-first-delivery
Why: Track background execution before starting it and preserve generated content and ordinary questions across failure paths.
Evidence: Local full combination test passed before this bounded closure; new fault and race regressions pass, with independent closure and final gates pending.
Impact: Update only the reviewed Backend/UI closure and saved local verification output.
Refs: feature/workbench-flow-completion
Why: the duties draft must stay within the frontend unused-export baseline before combination tests.
Evidence: SELF knip 43 <= 43 on the frontend commit.
Impact: Dev follows the duties page without new unused exports.
Refs: modules/frontend
Why: New questions, rejected messages and delayed result projection must remain recoverable.
Evidence: Focused review regressions, frontend/UI suites and browser mixed-input checks pass locally; full combination retest and independent closure follow.
Impact: Preserve user intent, repair saved result projections and keep archived work read-only.
Refs: feature/workbench-flow-completion
Why: the duties browser scenarios changed after the first frontend pin.
Evidence: SELF playwright 3 passed; frontend commit follows 1b7ba77.
Impact: Dev follows the frontend duties page that records preview before batch save.
Refs: modules/frontend
Why: the task card, proposal index, and frontend gitlink need to name the document-duty rework instead of the superseded duties tab.
Evidence: SELF commits 034faa4 in documents and 1b7ba77 in frontend. RDM f16287f is a sibling repository, not a Dev gitlink.
Impact: the duties settings entry now comes from the three-view frontend. Deployment and live-account acceptance remain unauthorized.
Refs: modules/documents/docs/proposals/2026-10-15-rdm-duty-matrix-rework.md
Co-authored-by: Cursor <cursoragent@cursor.com>
Why: include the current integration baseline before verification.
Evidence: fetched origin/main=37a8791cb9f736a7f58e87a88389a55095f06e0d.
Impact: integrate upstream changes without rewriting task history.
Refs: task-sync
Why: Complete the approved conversation and background-work experience without changing the accepted visual theme.
Evidence: Component regressions and 23 local browser journeys pass; review and final exact-head gates remain pending.
Impact: Combine full results, optional decisions, saved process and independent chronology with compatible optional contracts.
Refs: feature/workbench-flow-completion
Why: Archive the merged four-model vision task card onto main.
Evidence: CI run 3307 attempt 2 jobs 5093, 5094, and 5095 succeeded on 5726fb6.
Impact: Task card moves to .task/archive; product tree is unchanged.
Refs: #564
Why: make the three approved CLIs the only active implementation and test routes
Evidence: adapter unit tests, configuration validation, diff check, and real marker probes for all three profiles
Impact: narrows project routing and fixes agy prompt binding for noninteractive execution
Refs: feature/goal-first-delivery
Why: Freeze a shared contract for independent implementation units.
Evidence: make contracts generated both TypeScript consumers.
Impact: Component-only baseline for parallel scoped work.
Refs: feature/workbench-flow-completion
Why: Preserve fixes already merged by parallel work.
Evidence: Component branches were created from freshly fetched origin/main.
Impact: Record the actual shared baseline before generating contracts.
Refs: feature/workbench-flow-completion
Why: Complete the uploaded-material work flow and preserve current backend fixes.
Evidence: Imported READY startup receipt is attached to the task card.
Impact: Establish isolated implementation scope and component baseline.
Refs: feature/workbench-flow-completion
Why: establish the authorized task workspace and its initial baseline.
Evidence: preserved precheck receipt in .task/feature-rdm-duty-matrix.md; R0=4ba5c40a609dc07deb34d05761b00c29b44f2355.
Impact: task metadata only; the feature workspace starts at 4ba5c40a60.
Refs: .task/feature-rdm-duty-matrix.md
Why: establish the authorized task workspace and its initial baseline.
Evidence: preserved precheck receipt in .task/feature-workbench-flow-completion.md; R0=4ba5c40a609dc07deb34d05761b00c29b44f2355.
Impact: task metadata only; the feature workspace starts at 4ba5c40a60.
Refs: .task/feature-workbench-flow-completion.md
Why: branches merged into main had left their task cards open; backfill status and archive to prevent bookkeeping debt.
Evidence: feature-four-model-vision.md(PR#563) — merges verified via git log --merges plus Gitea API squash lookup 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)
weichen
