Why: the isolated-source deploy change was finished but never merged, and
the task card had no PR link.
Evidence: the only content conflict was the shared sync-log card; both
rows kept. scripts/svc.sh merged cleanly. PR link recorded as Dev #102.
Impact: branch now contains origin/main. Deploy semantics unchanged.
Refs: https://git-home.u1680832.nyat.app:30319/weichen/Agent-System-Dev/pulls/102
Co-authored-by: Cursor <cursoragent@cursor.com>
Why: the card was folded into PR #109 already marked complete, so
task-close skipped it; archive it manually per the no-open-cards rule
and advance the frontend gitlink past the mimosa-ignore chore (#26).
Evidence: .task has no deliverable-docx-r1.md left; precheck [cards]
to be re-run after merge; frontend -> de38791 (chore #26 merged).
Impact: housekeeping only; no code paths touched.
Refs: task feature/deliverable-docx-r1 (PR #109), frontend PR #26
Why: users received plain-text .docx files and had to dig through the
process collapse or workspace panel to find deliverables; deliverables
must appear directly in the conversation and open with real formatting.
Evidence: module PRs merged — Agent-System-Backend#31 (docgen Markdown
to styled OOXML, write_docx tool, artifact_ref pinned as content after
final text, prompt routing, mock #doc dogfood) and
Agent-System-Frontend#25 (deliverable card renderer, live projection
pinned tail). Combination `make test` green in this worktree: backend
go test 19 pkgs, frontend vitest 40/40 + tsc clean, ui tsc + vitest
68/68 incl design-guard, agent-command ok. Task card records scope,
sync nodes and leftovers.
Impact: gitlinks backend -> 8550bb0, frontend -> b048d90; core/ui
unchanged.
Refs: task feature/deliverable-docx-r1
Why: branches merged into main had left their task cards open; backfill status and archive to prevent bookkeeping debt.
Evidence: feature-ui-tokens-v3.md(PR#107) — 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 requires the PR link as its master record once the
PR exists (delivery workflow); sub-PR numbers recorded for merge order.
Evidence: PRs created via Gitea API — UI #23, Frontend #24, Dev #107.
Impact: task card only.
Refs: task feature/ui-tokens-v3.
Why: Submodule branches merged their origin/main (CF3) and were pushed;
record the new heads so the parent sync merges cleanly.
Evidence: submodules green post-merge (ui 68 / frontend 39 tests, tsc
clean); parent task-sync re-run follows this commit.
Impact: gitlinks only.
Refs: task feature/ui-tokens-v3.
Why: Land phase 4 of the UI redesign in the parent repo: ToolBlock chat
contract, Collapsible migration of all folds, live sweep with worked-time,
and the honest in-progress input hint. Completes the four-phase plan on
this branch (deviation recorded in the task card).
Evidence: combined make test -> go core/backend/agent-command ok, frontend
39 vitest passed, ui 66 vitest passed; tsc clean in both submodules.
Impact: modules/ui and modules/frontend gitlinks move to their
feature/ui-tokens-v3 heads; task card records results and remaining items.
Refs: task feature/ui-tokens-v3.
Why: branches merged into main had left their task cards open; backfill status and archive to prevent bookkeeping debt.
Evidence: feature-project-inbox-r1.md(PR#105) — 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: 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)
weichenandCursor