Why: Land phase 3 of the UI redesign in the parent repo.
Evidence: frontend submodule commit on feature/ui-tokens-v3; tsc -b and
38 vitest tests pass; task card records the runs.
Impact: modules/frontend gitlink moves; no API changes.
Refs: task feature/ui-tokens-v3.
Why: Land phase 2 of the UI redesign in the parent repo: admin-only
full-screen system management, conversation-first sidebar, role-aware
workspace shortcuts.
Evidence: frontend submodule commit on feature/ui-tokens-v3; tsc -b and
38 vitest tests pass in the submodule; combined make test re-run recorded
at phase boundaries in the task card.
Impact: modules/frontend gitlink moves; no API or contract changes.
Refs: task feature/ui-tokens-v3.
Why: The approved frontend redesign requires a durable design constitution
so future UI work stays consistent (user directive: make this project's
standing design guidance, four principles: beautiful/modern/concise/usable).
DESIGN.md encodes the Zai-calibrated rules (surface ladder, type scale,
radius nesting, MotionKit recipes, ToolBlock contract, IA principles) and
AGENTS.md adds a mandatory UI gate; submodules land phase 1 (tokens v3,
MotionKit, Collapsible, panel layout, mono primary buttons).
Evidence: make test in this worktree -> frontend 38 passed (incl. new
host design-guard ratchet), ui 61 passed (incl. collapsible + design-guard),
go core/backend/agent-command ok. precheck READY at R0 0be23f9a4d.
Impact: gitlinks advance to Agent-System-UI/Agent-System-Frontend
feature/ui-tokens-v3 heads; AGENTS.md gains a UI section; no backend or
contract changes.
Refs: session-approved redesign plan v2 (8 decisions recorded in task card).
Why: branches merged into main had left their task cards open; backfill status and archive to prevent bookkeeping debt.
Evidence: feature-artifact-unify-r1.md(PR#103) — 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: CF-A lands in backend (ctxasm backfill + facade cards) and documents.
Evidence: backend commit recorded in module log; combination make test in
task card.
Impact: gitlink-only.
Why: svc.sh update skipped services with a local@<sha> source whenever the
main checkout was dirty, and bare deploy built the current workspace. The
owner requires updates/deploys to be independent of the working tree
state, defaulting to the latest remote commit built outside the checkout.
Evidence: bash -n passes; commits dev lists from the source clone; bare
deploy --dry-run plans dev@<origin/main>; end-to-end "svc.sh update
svc-selftest" with a dirty tree updated a local@d64742c service to
dev@0be23f9 (built in runtime/.worktrees from
~/.cache/agent-system-svc/src, started healthy), then stopped and purged.
Full make test output recorded on the task card.
Impact: deploy now defaults to dev@<origin/main> resolved in the
script-owned clone (SVC_SRC_DIR, default ~/.cache/agent-system-svc/src);
--from local stays the only workspace-dependent source; update no longer
pulls the main checkout - local@/dev@ services redeploy from remote
latest, ahead/diverged/missing-on-remote still decline to act.
docs/svc.md and in-script help updated to match.
Refs: .task/svc-remote-source.md
Why: branches merged into main had left their task cards open; backfill status and archive to prevent bookkeeping debt.
Evidence: feature-card-stream-r1.md(PR#100) — 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: module PRs #28 merged (backend a067d08, documents f5aa687); final
combination make test exit 0 on f96c55df.
Evidence: task-sync rows in card.
Impact: card-only.
Why: CF-S (D44/D45) implementation lands in backend and documents; Dev
tracks the tested combination.
Evidence: backend 24a2873 (tools+cardsvc+runmgr+mock+tests), documents
3d2da4e (usage guide); combination make test recorded in task card.
Impact: gitlink-only on Dev.
Refs: documents 2026-09-30-card-stream-artifact-unify-project-inbox.md (D44/D45).
Why: branch merged into main via PR #97; card must move to archive to
prevent bookkeeping debt (status already backfilled to 已完成).
Evidence: merge of PR #97 present in origin/main.
Impact: .task file move only.
Why: track 2 of the fake-docx remediation — read-only preview fallback for
stock text-masquerading docx artifacts; also ignore the Mimosa plugin's
per-session .mimosa state dir that kept dirtying the tree and blocking precheck.
Evidence: modules/ui 83367f7 (doc->binary dispatch + readable Office error),
modules/frontend cd77340 (PK magic sniff + markdown fallback); make test-ui
49/49, make test-frontend 33/33, frontend tsc --noEmit clean.
Impact: parent pins move to the two submodule branches; .gitignore gains
.mimosa/; no code outside those modules.
Refs: .task/feature-preview-sniff-fallback.md
Why: proposal approved and merged (Documents PR #27, merge 437af31);
card must carry sync and test evidence before close.
Evidence: task-sync d64742c/464f302; make test exit 0.
Impact: card-only.
Why: proposal D44-D52 approved and merged in Documents main; Dev must
track the authoritative combination.
Evidence: documents main tip 437af31.
Impact: gitlink-only.
Why: proposal PR (Documents #27) is the task master record pending
approval; task card tracks baseline and handoff.
Evidence: R0=d64742c; documents 67cf52b on feature/cardflow-future-plan.
Impact: docs-only on Dev branch; no runtime change.
Why: branches merged into main had left their task cards open; backfill status and archive to prevent bookkeeping debt.
Evidence: feature-file-preview-caps.md(PR#94) — 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)