Why: make existing directions, milestones and tasks discoverable with their evidence boundaries.
Evidence: all 19 proposals are covered, 55 PR records were checked, and make test passed on the staged combination; original SELF receipts are preserved.
Impact: local documentation candidate only; the Documents candidate includes the N2 proposal already on Documents main, with Dev PR 244 coordination still recorded.
Refs: .task/feature-planning-index.md; Documents b87b929; PROJECT.md
Why: native ead690be (Agent-Native#24) stops workspace-less requests
from writing session state into the process CWD; squad 029edc08
(Agent-Squad#28) and backend 68addfda (Backend#85) carry it. Without
this the CI build step fails the worktree check after make test.
Evidence: check-pins pins ok; combination re-verified by make test
before push (see card).
Impact: none beyond pins; the I2 slow-lane stack is unchanged.
Refs: Agent-Native#24, Agent-Squad#28, Agent-System-Backend#85, Dev#242
Why: backend #83 merged the slow-lane wiring (intentsem scorer/
generator, gate SetSemantic/SetGenerator, settings flags default off);
the Dev pins and boundary rules must move with it.
Evidence: backend CI green on 9d29371; check-pins consistent
(agent-intent 343b1e6 across Dev and the backend nested copy);
lint-boundaries registers intentsem as an agent-intent adapter and the
architecture baseline gains backend/app->backend/intentsem.
Impact: product behavior unchanged by default; the two
runtime.intent* flags opt into the slow lane.
Refs: Agent-System-Backend#83, I2 increment 3
Why: Agent-Squad PR #26 and Backend PR #82 landed; Dev pins must
point at those merged component main heads.
Evidence: check-pins exit=0.
Impact: Two gitlinks.
Refs: Agent-Squad PR #26; Agent-System-Backend PR #82
Why: Agent-Squad PR #25 and Backend PR #81 landed; Dev pins must
point at those merged component main heads.
Evidence: check-pins exit=0.
Impact: Two gitlinks.
Refs: Agent-Squad PR #25; Agent-System-Backend PR #81
Why: Agent-Squad PR #24 and Backend PR #80 landed; Dev pins must
point at those merged component main heads.
Evidence: check-pins exit=0.
Impact: Two gitlinks.
Refs: Agent-Squad PR #24; Agent-System-Backend PR #80
Why: Agent-Squad PR #23 and Backend PR #79 landed; Dev pins must
point at those merged component main heads.
Evidence: check-pins exit=0.
Impact: Two gitlinks.
Refs: Agent-Squad PR #23; Agent-System-Backend PR #79
Why: The I1 eval increments landed across the chain (intent #8,
squad #21/#22, native #22, backend #77/#78); Dev pins must point at
those merged component main heads.
Evidence: check-pins exit=0 after full matrix propagation.
Impact: Four gitlinks.
Refs: Agent-Intent PR #8; Agent-Squad PR #21/#22; Agent-Native PR #22; Agent-System-Backend PR #77/#78
Why: Backend PR #76 fixed the boundary violation by projecting the
command types through intentgate; the Dev pin must carry it for
lint-boundaries to pass.
Evidence: backend CI success on #76; check-pins ok.
Impact: One gitlink plus the card receipt.
Why: The I1 intent/router increments landed across the chain (intent
#6/#7, squad #19/#20, native #21, backend #74/#75); Dev pins must
point at those merged component main heads.
Evidence: check-pins exit=0 after the full cascade.
Impact: Four gitlinks.
Refs: Agent-Intent PR #6/#7; Agent-Squad PR #19/#20; Agent-Native PR #21; Agent-System-Backend PR #74/#75
Why: Increment four landed across the chain (native #19/#20, backend
#72, squad #18, backend #73); Dev pins must point at those merged
component main heads.
Evidence: check-pins exit=0; native c9c2f23, squad 7ecc04e and
backend 303983bd are direct merge commits on their component mains.
Impact: Three gitlinks.
Refs: Agent-Native PR #19/#20; Agent-Squad PR #18; Agent-System-Backend PR #72/#73
Why: Increment three landed across the chain (native #18, squad #17,
backend #71); Dev pins must point at those merged component main
heads so the tested combination is the released one.
Evidence: check-pins exit=0; native c5b9dca, squad fc9620e and
backend f0b0db9 are direct merge commits on their component mains.
Impact: Three gitlinks.
Refs: Agent-Native PR #18; Agent-Squad PR #17; Agent-System-Backend PR #71
Why: Squad PR #16 and Backend PR #70 completed the pin cascade;
Dev's squad and backend pins must point at those merged heads for
check-pins to verify the tested combination.
Evidence: a75d359 is the #16 merge on squad main; backend main head
is the #70 merge; backend CI passed before each merge.
Impact: Two gitlinks.
Refs: Agent-Squad PR #16; Agent-System-Backend PR #70
Why: include the current integration baseline before verification.
Evidence: fetched origin/main=9c9483ac54ff5355c86824ac94097e65e59dcb5d.
Impact: integrate upstream changes without rewriting task history.
Refs: task-sync
Why: Library PR #17 and Backend PR #69 are merged; the Dev pins must
point at the merged component main heads (native c2befaf, backend
fe0c5a4) so the tested combination is the released one.
Evidence: both pins are direct merge commits on their component
mains; backend CI passed at 4075cc6 before its merge.
Impact: Two gitlinks plus the task card evidence records.
Refs: Agent-Native PR #17; Agent-System-Backend PR #69
Why: Register the docs-only planning task and point the documents
gitlink at the phase-plan commit on its feature branch.
Evidence: task card carries the precheck receipt; documents commit
b8eaa16 holds the proposal.
Impact: Task card plus documents gitlink; no code changes.
Refs: docs/proposals/2026-10-07-rdm-phase-plan.md
Why: Register the docs-only planning task and point the documents
gitlink at the proposal commit on its feature branch.
Evidence: task card carries the precheck receipt; documents commit
e935713 holds the proposal.
Impact: Task card plus documents gitlink; no code changes.
Refs: docs/proposals/2026-10-07-agent-stack-n1q1i1-plans.md
Why: backend e7fb276 fixes the EXT-5 review findings; pin it and keep the verification row with it.
Evidence: SELF receipt exit=0 (full make test green); backend PR #68 CI pending as GATE.
Impact: modules/backend gitlink 727f370 -> e7fb276; task card row.
Refs: .task/fix-ext-5-wide-cols.md
Why: completion claims require tool-written evidence (AGENTS.md).
Evidence: SELF receipt appended by make evidence; full suite green incl. ui 103 tests and agent-command.
Impact: task metadata only.
Refs: .task/feature-ext-5-host-parse.md
Why: the umbrella pinned 2cb1496, a commit on ui's feature/governance-docs
branch rather than main history, so the material-12 check (Dev gitlink equals
the ui tag commit) would fail the moment the owner tags v0.1.0.
Evidence: make test on the re-pinned combination (recorded via make evidence
on the task card).
Impact: modules/ui gitlink 2cb1496 -> 27d5adb (ui main tip, an ancestor);
all four sub-repo pins now sit on their repos' main history.
Refs: .task/feature-ui-pin-align.md
Why: cleanup, component synchronization, receipt recording and credential handling could contradict the documented development boundaries.
Evidence: SELF 75 isolated governance tests and source checks are captured in .task/feature-governance-reliability.md; combination and CI verification follow.
Impact: hardens local task and CI tooling, aligns policy and component documentation, and adds continuous regression tests without changing product behavior.
Refs: .task/feature-governance-reliability.md; policy/governance.md; policy/platform-admission.md
Why: Expanding the preview left the conversation column in the row because .main { display: flex } overrode the UA [hidden] rule. Frontend PR #47 restores that hide and centers a wide docx page.
Evidence: Frontend vitest previewfit + design-guard 10 passed. Headless Chromium 1512x900 shows expanded .main display:none, preview slot 1184px, page center delta 0; at 420px and 640px the wrapper stays column-width and the page stays left-aligned.
Impact: modules/frontend 0a0b556 -> 50c7244. Narrow-column fit scaling is unchanged. previewfit still returns 1 when available width is <= 0.
Refs: .task/fix-preview-expanded-hidden.md; https://git-home.u1680832.nyat.app:30319/weichen/Agent-System-Frontend/pulls/47
Co-authored-by: Cursor <cursoragent@cursor.com>
Why: Backend PR #62 merged as 3f438b9 (superseded by #64/#65); task card
requires re-pinning the gitlink to the backend merge commit before the
Dev PR can merge.
Evidence: backend go vet + go test ./... -count=1 all ok (29 packages);
merged tree content-identical to backend main.
Impact: modules/backend 685bd0d -> 3f438b9.
Refs: .task/fix-pg-boolean-columns.md
Why: The right-hand preview clipped docx instead of scrolling, and a second overlay viewer duplicated FilePreview. Both fixes are already on the module mains.
Evidence: make test passed in the task worktree (boundaries, pins, libs, core, backend, frontend 82 tests, ui 103 tests, agent-command).
Impact: modules/ui moves to 27d5adb (icons #36 and contrast #37). modules/frontend moves to 0a0b556 (preview scroll #46, including contrast #45).
Refs: Agent-System-UI#36, Agent-System-Frontend#46, Agent-System-Dev#196
Co-authored-by: Cursor <cursoragent@cursor.com>
Why: The frontend branch gained two follow-up commits that stop a typecheck artifact from dirtying the submodule.
Evidence: modules/frontend HEAD is 9badbb1 and git status in that repo is clean.
Impact: The Dev branch records the frontend tip that includes page scaling and the tsbuildinfo ignore. No other gitlinks move.
Refs: feature/docx-paper-preview
Co-authored-by: Cursor <cursoragent@cursor.com>
Why: The preview painted docx pages with the theme background, so black document text was unreadable in dark mode and the page overflowed the narrow column.
Evidence: UI vitest 84 passed and tsc clean at b14c9c0; frontend vitest 81 passed and tsc -b clean at cf6f24e.
Impact: DESIGN.md documents --paper and --paper-ink. Gitlinks pick up the UI and frontend paper-preview commits. Mammoth and fake-docx text fallbacks stay theme-styled.
Refs: feature/docx-paper-preview
Co-authored-by: Cursor <cursoragent@cursor.com>
Why: the default unarchived task list still compared a BOOLEAN column
to the integer literal 0, so GET /api/conversations returned 500 on
the postgres tier after the previous dialect fix.
Evidence: backend PR #65 (8d82408). Before the fix, TestConversationFlagsAndTaskList
on pg1 failed with SQLSTATE 42883; after, go test ./internal/store -count=1
passed on pg1. Dev make test passed on this pin.
Impact: modules/backend gitlink moves to 8d82408. No other surface changes.
Refs: Agent-System-Backend#65
Co-authored-by: Cursor <cursoragent@cursor.com>
Why: the backend fix unblocks account management, login and conversation
flags on the postgres tier (1/0 literals and int scans rejected with 42804).
Evidence: backend PR #64 merged; live pg1 CLI verified (reset-password +
user list OK); combined make test green.
Impact: dev pins move to the fixed backend; no other surface changes.
Refs: Agent-System-Backend#64
Why: The incremental build info commit has to be the gitlink Dev records.
Evidence: modules/frontend is eb6502f. make build produced bin/agent-system.
Impact: The parent branch names the same frontend commit the worktree built.
Refs: .task/feature-sillytavern-review.md
Co-authored-by: Cursor <cursoragent@cursor.com>
Why: The shared types dropped a spare export so the knip ratchet stays at its baseline, and every container must name those commits.
Evidence: core 0b5c774, ui 6b2589c, frontend 13a1c63, backend c05832d. UI knip 55 and frontend knip 43.
Impact: Gitlinks move together. JSON field names are unchanged.
Refs: .task/feature-sillytavern-review.md
Co-authored-by: Cursor <cursoragent@cursor.com>
Why: Dev's agent-native moved for message shaping, so squad and backend have to follow or check-pins fails.
Evidence: Squad 5a57636 and backend include that pin. make test previously stopped at test-pins on this mismatch.
Impact: The parent, backend, and squad all resolve agent-native 3a110a7.
Refs: .task/feature-sillytavern-review.md
Co-authored-by: Cursor <cursoragent@cursor.com>
Why: Empty innerHTML clears were flagged because the space matcher could backtrack past the quotes. The child tests now keep that whitespace inside the lookahead.
Evidence: Frontend vitest 78 passed. UI html-sinks passed. Child commits are ui 5f8308a and frontend 02cebc0.
Impact: The parent pins match the ratchet that allows clearing a node before appending sanitized children.
Refs: .task/feature-sillytavern-review.md
Co-authored-by: Cursor <cursoragent@cursor.com>
Why: The research record, HTML cleaning, listen guard, secret store, and context controls land together, and the parent pointers have to name those commits.
Evidence: Child commits are core bd63223, agent-native 3a110a7, ui d76a8e6, frontend 36b92ed, documents f3f823e, backend 42cca8f. svc.sh forwards the listen switches and info prints them.
Impact: A reverse proxy or a LAN hostname needs allowedHosts or an unauthenticated host check returns 403. Startup moves raw API keys into the secret table after a settings snapshot.
Refs: .task/feature-sillytavern-review.md
Co-authored-by: Cursor <cursoragent@cursor.com>
Why: advance the backend gitlink to the boolean-column fix so the dev
runtime's PostgreSQL tier stops failing every conversations endpoint.
Evidence: backend branch pushed (685bd0d); make test run recorded in
the task card.
Impact: gitlink-only change in Dev; combined verification via make test.
Refs: .task/fix-pg-boolean-columns.md
Why: the Dev branch must record the Backend main commit that contains the settings fix, not the unmerged feature tip.
Evidence: Backend #61 merged as fd17011.
Impact: modules/backend gitlink moves from d90b9c0 to fd17011. Behavior is the merged fix.
Refs: fix/settings-dotted-keys
Co-authored-by: Cursor <cursoragent@cursor.com>
Why: dotted setting writes were stored as unread keys, and secret pools were returned in clear text.
Evidence: Backend go test ./... at d90b9c0. Dev make test follows this pin.
Impact: the dev branch tracks Backend fix/settings-dotted-keys until that PR merges, then the pin moves to main.
Refs: fix/settings-dotted-keys
Co-authored-by: Cursor <cursoragent@cursor.com>
Why: the shared Python host and the MCP connect change landed in the libraries the product already calls.
Evidence: native, squad, and backend feature commits are recorded on the task card.
Impact: gitlinks move to those commits. Code orchestration stays off unless the setting is turned on.
Refs: feature/code-orchestration
Co-authored-by: Cursor <cursoragent@cursor.com>
Why: tool intent, file checkpoints, fallback, and span names landed in the libraries and the product shell.
Evidence: native, squad, core, backend, frontend, and ui feature commits are recorded in the task card.
Impact: gitlinks move to those commits. Default fallback stays empty and replay stays never.
Refs: feature/durable-rewind
Co-authored-by: Cursor <cursoragent@cursor.com>
Why: Session mode, confirmation detail, and the shared tool gate now exist in the libraries the product builds.
Evidence: make test passed. Plan mode rejects write_artifact while the default mode still runs it. Hook adapters match the old stop, reminder, and deny counts.
Impact: Empty permission mode keeps today's profile policy. There is no mode that skips every confirmation.
Refs: feature/permission-hooks
Co-authored-by: Cursor <cursoragent@cursor.com>
Why: The conversation screen has to import the phase type so the unused-export ratchet stays at the baseline.
Evidence: frontend 5961b6e, knip 43.
Impact: No other pin moves.
Refs: feature/runstate-shell
Co-authored-by: Cursor <cursoragent@cursor.com>
Why: The composer phase and the SSE retry interval have to land together so a reconnect shows 重连中 and still receives the missed events.
Evidence: frontend dcf9b6b, backend 7bef7a4.
Impact: No change to permissions, models, or the already merged live-bubble fix.
Refs: feature/runstate-shell
Co-authored-by: Cursor <cursoragent@cursor.com>
Why: Tool-result clearing, folded reminders, and character truncation land in the native loop and the product path together.
Evidence: agent-native 6fd1d44, agent-squad 4d53450, backend b2dc9a7.
Impact: Default context window stays 32000 characters. Empty tool selection still exposes the profile's tools.
Refs: feature/context-engineering
Co-authored-by: Cursor <cursoragent@cursor.com>
Why: New cross-layer imports and unused exports could land unnoticed, and confirm-waiting reused the success color.
Evidence: bash scripts/lint-boundaries.sh passed, including a probe that a new edge fails. Both design-guard tests passed. Knip counts stay at the baselines.
Impact: make test-boundaries now checks architecture edges. Frontend and ui test targets also run the knip ratchet.
Refs: feature/architecture-baseline
Co-authored-by: Cursor <cursoragent@cursor.com>
Why: The direct path's default retry only works once every repo builds the same model stream.
Evidence: native 9f5751c, squad 9efce79, backend 93adb93.
Impact: Three gitlinks move. No product UI change.
Refs: feature/llm-robustness
Co-authored-by: Cursor <cursoragent@cursor.com>
Why: The stack proposal and the durable note need the v1.0.1 correction before later batches change code.
Evidence: Documents 847f681 adds the second-pass record, the durable correction, and proposal section 2.4.
Impact: Only the documents gitlink moves. No library or product code.
Refs: feature/pi-zcode-second-pass
Co-authored-by: Cursor <cursoragent@cursor.com>
Why: The submodule pull requests landed as merge commits, and the parent pin must include those tips so the composed tree keeps both this fix and the commits that arrived on submodule main.
Evidence: Frontend main is 8be98b4 (contains e4ca2ac); Backend main is 28ccb74 (contains 51b1ff6).
Impact: Dev #161 now pins the commits that are already on each submodule main.
Refs: Frontend #38, Backend #54, Dev #161
Why: Sending a message left the composer on 发送 and hid the live process, because the user message now carries the run id and a refresh had no cursor to replay an open run.
Evidence: make test passed in the worktree. A mock server showed the stop and queue buttons within 250ms, the reply growing before it settled, and the in-progress turn restored after switching away and after reload.
Impact: Frontend and backend gitlinks only, plus this task card. No core contract change.
Refs: Frontend fix/live-run-visibility, Backend fix/live-run-visibility
Co-authored-by: Cursor <cursoragent@cursor.com>
Why: The review and the four recovery fixes live in the documents, backend, and frontend repositories. The Dev pin is what the combined test runs.
Evidence: Documents 6340900, backend 44aa764, frontend 763c4b4. Each submodule branch is feature/pi-durable-borrow, based on that repository's origin/main.
Impact: Gitlinks only. The pins also move documents, backend, and frontend forward to the main commits that landed after the previous Dev pin.
Refs: feature/pi-durable-borrow
Co-authored-by: Cursor <cursoragent@cursor.com>
weichen
