Why: The review candidate needs reproducible evidence bound to the exact Dev and Frontend commits.
Evidence: SELF receipts record 272 unit tests, the production build, and 16 browser scenarios on Dev 49ef24b.
Impact: Updates only the task record; product behavior is unchanged.
Refs: feature/workbench-visual-redesign
Why: Long-history task tests could finish while Git background maintenance still rewrote a disposable clone, racing TemporaryDirectory cleanup and failing CI with a non-empty .git directory.
Evidence: The failing test passes 25/25 and all 344 governance tests pass locally.
Impact: Test fixture only; product, governance commands, and runtime behavior are unchanged.
Refs: Dev run 3237 jobs 4951 and 4965
Why: The task record must point to the concrete Dev combination under review.
Evidence: Dev PR #556 targets current main and pins the merged Frontend and UI trees.
Impact: Updates only delivery metadata.
Refs: Dev #556
Why: The review candidate needs reproducible evidence bound to the exact Dev and Frontend commits.
Evidence: SELF receipts record 272 unit tests, the production build, and 16 browser scenarios on Dev 49ef24b.
Impact: Updates only the task record; product behavior is unchanged.
Refs: feature/workbench-visual-redesign
Why: include the current integration baseline before verification.
Evidence: fetched origin/main=b8edf13dc7b818d6e61b829f6e88202ec553f2fc.
Impact: integrate upstream changes without rewriting task history.
Refs: task-sync
Why: The review candidate needs reproducible evidence bound to the exact Dev and Frontend commits.
Evidence: SELF receipts record 272 unit tests, the production build, and 16 browser scenarios on Dev 49ef24b.
Impact: Updates only the task record; product behavior is unchanged.
Refs: feature/workbench-visual-redesign
Why: The Dev composition must consume the reviewed Frontend and UI changes from their authoritative main branches.
Evidence: Frontend and UI merge trees equal the locally verified candidate trees; UI exact-head CI passed.
Impact: Advances only the Frontend and UI pins and records the component merge results.
Refs: Frontend #87; UI #56
Why: The review candidate needs reproducible evidence bound to the exact Dev and Frontend commits.
Evidence: SELF receipts record 272 unit tests, the production build, and 16 browser scenarios on Dev 49ef24b.
Impact: Updates only the task record; product behavior is unchanged.
Refs: feature/workbench-visual-redesign
Why: Independent review found that the visual frame bypassed token and motion ownership and lacked dark/molv proof.
Evidence: UI 4cae1c4 passes 163 tests; Frontend 9b9f24b passes its design guard and 19 browser scenarios across all themes.
Impact: Pairs the new UI tokens with their Frontend consumer and documents the governing design rule.
Refs: Frontend #87; UI #56
Why: make PR #553 the durable task record before final CI and merge.
Evidence: the Gitea API reports PR #553 open and mergeable at head 3138221.
Impact: task metadata only; the next push creates the final PR candidate.
Refs: .task/fix-8788-message-permission.md; PR #553
Why: preserve the exact pre-PR baseline and complete local regression output.
Evidence: task-sync fixed origin/main at 3326192; make test passed all required local checks.
Impact: task evidence only; no source, component pin, or runtime configuration change.
Refs: .task/fix-8788-message-permission.md
Why: include the current integration baseline before verification.
Evidence: fetched origin/main=33261925a10c4eee40d1b6175b3895e78a47ef02.
Impact: integrate upstream changes without rewriting task history.
Refs: task-sync
Why: The review candidate needs reproducible evidence bound to the exact Dev and Frontend commits.
Evidence: SELF receipts record 272 unit tests, the production build, and 16 browser scenarios on Dev 49ef24b.
Impact: Updates only the task record; product behavior is unchanged.
Refs: feature/workbench-visual-redesign
Why: the user confirmed normal conversation behavior and authorized task closeout.
Evidence: user acceptance on 2026-10-15 supplements the preserved SELF runtime checks.
Impact: advances the task record to integration preparation; no production code change.
Refs: .task/fix-8788-message-permission.md
Why: The inverse create control needed its divider and hover state adapted to the new dark navigation surface.
Evidence: Frontend 8dc68fd passes the focused browser layout test and production build locally.
Impact: Advances the Frontend pin and records the final local candidate.
Refs: feature/workbench-visual-redesign
Why: The review candidate needs reproducible evidence bound to the exact Dev and Frontend commits.
Evidence: SELF receipts record 272 unit tests, the production build, and 16 browser scenarios on Dev 49ef24b.
Impact: Updates only the task record; product behavior is unchanged.
Refs: feature/workbench-visual-redesign
Why: The first spacing-focused candidate still resembled the flat gray workspace and did not meet the user's visual target.
Evidence: Frontend ddf3135 passes 272 unit tests, 16 browser scenarios across 320-1920px, and a production build locally.
Impact: Advances the Frontend pin to the visibly differentiated navigation, conversation, and work surfaces.
Refs: feature/workbench-visual-redesign
Why: bind the active runtime repair, rollback point, and review state to the synchronized task record.
Evidence: SELF runtime checks passed for message delivery, completed run, privacy, cleanup, credential revocation, and final database state.
Impact: task metadata only; user browser acceptance and task cleanup remain pending.
Refs: .task/fix-8788-message-permission.md
Why: The deployed workbench needs a clear visual hierarchy across context, conversation, and work without adding new product concepts.
Evidence: Frontend b04f4de passes 272 unit tests, 16 browser scenarios across 320-1920px, and a production build locally.
Impact: Advances only the Frontend pin and records the approved visual increment; runtime adoption remains separately verified.
Refs: feature/workbench-visual-redesign
Why: include the current integration baseline before verification.
Evidence: fetched origin/main=33261925a10c4eee40d1b6175b3895e78a47ef02.
Impact: integrate upstream changes without rewriting task history.
Refs: task-sync
Why: preserve the authorized runtime role repair and its exact local evidence.
Evidence: recorded the pre-fix 404, role commands, completed test run, privacy check, backup, and revoked temporary credentials.
Impact: task metadata only; the live 8788 role configuration is documented without source changes.
Refs: .task/fix-8788-message-permission.md
Why: establish the authorized task workspace and its initial baseline.
Evidence: preserved precheck receipt in .task/fix-8788-message-permission.md; R0=99119a733830bc120cd6747b8b61736ea6da6078.
Impact: task metadata only; the feature workspace starts at 99119a7338.
Refs: .task/fix-8788-message-permission.md
Why: establish the authorized task workspace and its initial baseline.
Evidence: preserved precheck receipt in .task/feature-workbench-visual-redesign.md; R0=99119a733830bc120cd6747b8b61736ea6da6078.
Impact: task metadata only; the feature workspace starts at 99119a7338.
Refs: .task/feature-workbench-visual-redesign.md
Why: the close commit still said the live 8788 check had not run, which contradicts the user acceptance already recorded in the same card.
Evidence: user confirmation on 2026-10-15 of conversation order, pane deduplication, and folded process review; cutover notes already in the card. Local checks stay SELF.
Impact: task-card text only. No code, schema, or runtime change.
Refs: Dev PR #550, close PR #552
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-work-companion-visibility.md(PR#550) — 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)
Why: include the current integration baseline before verification.
Evidence: fetched origin/main=bc76b68cd075379122430acb24fa080b0a38ff5e.
Impact: integrate upstream changes without rewriting task history.
Refs: task-sync
Why: Main advanced during UI delivery and task metadata must identify the new combined candidate.
Evidence: task-sync source-out receipt 6122ca6; Backend ead5ade includes both reviewed run history and concurrent vendor skills.
Impact: Fill the task PR link and mark the new Backend combination and final checks pending.
Refs: Agent-System-Dev #550; Agent-System-Backend #199 and #200
Why: Dev main advanced with a vendor skills task while this UI combination was being verified.
Evidence: Backend main ead5ade contains both Backend #199 and #200; the component merge affects recipes, not run-history handlers.
Impact: Preserve the new main task card and pin the Backend merge containing both changes; combination checks follow on this head.
Refs: Agent-System-Dev #550; Agent-System-Backend #199 and #200
Why: branches merged into main had left their task cards open; backfill status and archive to prevent bookkeeping debt.
Evidence: feature-vendor-popular-skills.md(PR#549) — 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)
Why: The fast and slow channel UI duplicated work cards and hid intermediate output after the final reply.
Evidence: SELF isolated-network make test and make build; 15 browser scenarios; independent component review; component PRs #55, #199, #85.
Impact: Pin merged Backend, Frontend and UI revisions and update DESIGN.md for one detail location and durable folded history.
Refs: .task/feature-work-companion-visibility.md; Agent-System-UI #55; Agent-System-Backend #199; Agent-System-Frontend #85
Why: establish the authorized task workspace and its initial baseline.
Evidence: preserved precheck receipt in .task/feature-vendor-popular-skills.md; R0=e1bc2602e18a89e4d75a4bf6cd80bc7f9b4d2164.
Impact: task metadata only; the feature workspace starts at e1bc2602e1.
Refs: .task/feature-vendor-popular-skills.md
Why: establish the authorized task workspace and its initial baseline.
Evidence: preserved precheck receipt in .task/feature-work-companion-visibility.md; R0=e1bc2602e18a89e4d75a4bf6cd80bc7f9b4d2164.
Impact: task metadata only; the feature workspace starts at e1bc2602e1.
Refs: .task/feature-work-companion-visibility.md
Why: branches merged into main had left their task cards open; backfill status and archive to prevent bookkeeping debt.
Evidence: feature-dhf-plan-progress-note.md(PR#547) — 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
