Why: proposal must record the 2026-09-30 decision (avatars, cards,
settings as base capabilities plugins reuse) and where it landed.
Evidence: feature/ui-capability-platform across core (avatar
vocabulary), ui (shared components + full vocabulary renderers),
frontend (consumption); 35+ tests and headless walk green.
Impact: status line only.
Why: the user replaced the stage-2 email self-registration sketch with
admin-issued accounts (2026-09-30): no self registration, admin sets
initial passwords, first login after creation or reset forces a change.
Evidence: R2 landed on feature/auth-admin-accounts (migration v10,
auth/session APIs, CLI user subcommands, login page + forced change
gate + admin user management); store/e2e tests and a full headless
journey on the real binary are green (see that task's PR).
Impact: proposal status line only; section 5.1 sketch superseded.
Why: the backend now registers tavily_search/web_search via
Agent-Native's TavilyProvider, so the guide's not-ported reason no
longer holds.
Evidence: backend PR records the registration and runtime checks.
Impact: table row updated, library count 44 -> 46.
Refs: feature/tavily-search-tool task card.
Why: the user picked option A (task-centric) after reviewing the demos;
the proposal status must reflect the decision and where R1 landed.
Evidence: R1 delivered on feature/task-sidebar-r1 across core/backend/
frontend (contract flags, migration v8, task list APIs, TaskSidebar);
headless walk and test suites green there.
Impact: status line only; no design content change.
Why: deciding what enters the library from an external prompt catalog
needs a stated rule (carrier mechanism or future slot) and an auditable
per-item disposition, otherwise coverage drifts by reviewer taste.
Evidence: table maps every Claude Code catalog entry to a library module
or an explicit not-ported reason.
Impact: guide gains section 9; no code change.
Refs: feature/prompt-catalog-coverage task card.
Why: the prompt system's design rationale (layering, the eight module
patterns, trigger semantics, override chain) needs to live with the
docs so future prompt work follows it instead of re-deriving it.
Evidence: guide content distilled from the implemented library and the
Claude prompt catalog analysis recorded in the task card.
Impact: new docs/guides/prompt-library-design.md; no code change.
Refs: feature/prompt-library task card.
Why: current UI scatters creation entries (project + at sidebar top-left,
new session at bottom-left), has no user/tenant surfaces, and the project
tree forces per-project navigation; the system targets multi-user
multi-tenant operation.
Evidence:
- Studied zai-org/ZCode desktop layout (WorkspaceShellLayout, WorkspaceSidebar,
DESIGN.md) and mapped transferable patterns (single New-Task entry,
organize-by views, sidebar account footer) with repo file citations.
- Three layout proposals (task-centric / activity rail / project portal) with
comparison table and recommendation A; auth stage-2 design (orgs,
memberships, server sessions) with SSE cookie upgrade removing ?key=.
- Five static demos (index + A/B/C + auth) verified headless: DOM layout
assertions (column widths, view switching, screen switching), clipping and
contrast QA clean, zero console errors, light/dark themes render.
Impact: documents only; no code change. Demos double as the R4 design-token
target palette. Implementation proceeds only after direction is approved.
Refs: docs/proposals/2026-09-30-ui-inbox-command-workspace.md (D25-D33),
docs/proposals/2026-09-30-dual-tier-storage-and-multitenancy.md (D17-D24)
Why: T2-T4 changed the interaction foundation (pure-inbox rail, four-entrance command bus, overlay workspaces) and the guide still described the classic tabs; T5 acceptance also requires the verification record with the zero-page walkthrough.
Evidence: zero-page walkthrough 12/12 PASS on a fresh real binary (fresh data dir: empty instance -> project/conversation -> slash commands -> #upload card lifecycle -> card action receipts -> tidy -> HITL block+resolve -> button-entrance dispatch -> plugin workspace declaration -> artifacts -> four-entrance audit); StatusLamp shape+color dual encoding asserted by ui suite; combo make test at pinned heads.
Impact: usage guide sections 4.2-4.7/5/6.2/7 rewritten; new T5 record; no code change.
Refs: docs/proposals/2026-09-30-ui-inbox-command-workspace.md T5; task card feature/polish-r1
Why: T4 acceptance requires a verification record in this repo before the Dev combo pin.
Evidence: backend full sweep green with TestWorkspacesOverlay; ui 23/23 (OverlayHost semantics); frontend tsc+vitest+build; example plugin workspace/command assets JSON-validated; combo make test at pinned heads.
Impact: docs/records only.
Refs: docs/proposals/2026-09-30-ui-inbox-command-workspace.md T4; task card feature/workspaces-r1
Why: T3 acceptance requires a verification record in this repo before the Dev combo pin.
Evidence: backend 15 pkgs ok incl. new cmdbus suite and danger-confirm e2e (dispatch -> confirm card -> action -> committed -> audit query ordered); ui 18/18; frontend 9/9; combo make test at pinned heads.
Impact: docs/records only.
Refs: docs/proposals/2026-09-30-ui-inbox-command-workspace.md T3; task card feature/command-bus-r1
Why: Delivery gate requires a verification record with per-case PASS evidence
for the T1 contract task before requesting review.
Evidence: record covers core/agent-command/frontend/ui suites, combo test and
the additive-compatibility check; contract change list enumerated.
Impact: Documentation only.
Refs: Dev task feature/core-cards-commands-r1
Why: Record the approved design for the interaction foundation phase — inbox/
command-bus/workspace mechanisms sink into the base system, domain views stay
plugin territory (target-system strategy), decisions D25-D33.
Evidence: proposal covers background, five UI principles, dialogue-completeness
P0 constraint, module/repo split (Agent-System-UI, Agent-Command), contract
sketch, task sequence T0-T5 and acceptance criteria.
Impact: Becomes the design baseline for T0-T5 tasks across five repos.
Refs: Agent-System-Dev feature/ui-foundation-r0
Why: the backend startup layer had only defaults and CLI flags; the
configuration standard's baseline (file, env, CLI layers, read-only explain,
instance isolation) requires the full pipe for dev/test/prod operation.
Evidence: fields and categories mapped one-to-one onto the existing app
Options; runtime settings API kept as the separate business-policy layer.
Impact: design record only; implementation follows in the backend repo.
Refs: standards/configuration.md; backend feature/config-surface
Why: the migration safety net (archive refs, bundles, SHA maps) had never
been exercised; verification rules treat untested recovery as a claim.
Evidence: 15/15 drill checks in a remote-only fresh environment (fsck, tip
and count matches, go test passing on the restored pre-rewrite tip, parent
gitlink reachability); the found gap — chain SHAs only in local bundles —
fixed by pushing refs/rewrite-backup/pre-2026-09-30-chain.
Impact: record-only; backend full-chain restore noted as a known, accepted
limitation.
Refs: 2026-09-30-history-migration.md; 2026-09-30-history-migration-sha-map.md
Why: the migration recovery data lived only on the migration workstation;
before the local backup bundles are retired, the maps belong in the
process repo per the single-source rule.
Evidence: combined from backups-2026-09-30/mapping-*.txt (10 repos + parent
+ restored chains); migration record pointer updated.
Impact: record-only; enables the scheduled local backup cleanup while
remote archive refs remain the full safety net.
Refs: 2026-09-30-history-migration.md
Why: both 2026-09-30 incidents produced reusable causal knowledge (nil-slice
JSON null vs .map; shared-checkout conflicts and gitlinks pinning unpushed
commits) that meets the lesson bar of trigger, mechanism, checks, and
verified guards.
Evidence: incident records and fix PRs referenced inline; guards validated
in policy/adoption.md and the tool-adaptation matrices.
Impact: record-only; documents no product code.
Refs: Agent-System-Dev 8f7cf2d; Agent-System-Backend fix/empty-list-json
Why: the composition-wide message normalization rewrote ten repos; the
governed-migration rule requires bundle backups, archive refs, SHA maps, and
a recovery record in the process repo.
Evidence: per-repo commit counts and empty tree diffs captured during
execution; remote mains verified against local after force-push.
Impact: record-only; documents no product code. Also records the
multitenancy delivery defect (gitlinks pinning unpushed commits) and its
remediation.
Refs: Development-Guidelines 0.1.0-draft.7 multi-repo.md; Agent-System-Dev ef89fc8
Why: the composition adopted the delivery gate (Dev repo ef89fc8); resident
entry rules must carry the gate so agents load them without reading the
guidelines submodule first.
Evidence: text-only entry change; gate mechanics validated in the Dev repo
scratch-repo suite (19/19) and merged as PR weichen/Agent-System-Dev#1.
Impact: entry doc only; no code, contract, or build change in this repo.
Refs: Development-Guidelines 0.1.0-draft.7; Agent-System-Dev ef89fc8
Details (original message):
R2: defer domain plugins to the future roadmap (fresh design, no legacy compat) and expand the skeleton extensibility and customizability design.
weichen
weichen