Why: The Dev combination must pin the slice-2 commit; make test validates the fixed combination.
Evidence: modules/backend -> 1de663a8d3302eddbd35d8a1906e4234e17c28e8 (Backend PR #107).
Impact: Gitlink only.
Refs: Backend PR #107; task card.
Why: The Dev combination must pin the EXT-9 commit; make test validates the fixed combination.
Evidence: modules/backend -> fbc924c24045f8a9e22fc4047982c23d09bcebf3 (Backend PR #106).
Impact: Gitlink only.
Refs: Backend PR #106; task card.
Why: The Dev combination must pin the EXT-8 commit; make test validates the fixed combination (which also carries the audit fix via stacking).
Evidence: modules/backend -> a4783d18e7156e4f48188e6816be865ed82380f6 (Backend PR #105, stacked on #104).
Impact: Gitlink only; other pins unchanged.
Refs: Backend PR #105; task card.
Why: The Dev combination must pin the proposal commit; make test validates the fixed combination (adopting Documents main 4e57196 plus the new proposal and INDEX row).
Evidence: modules/documents -> 9995552152616bfaf6473cd9249e55a28a1685b4 (Documents PR #49); make test row follows.
Impact: Gitlink only; other pins unchanged.
Refs: Documents PR #49; task card.
Why: The planning index registered the stale RDM snapshot as an open
reconciliation item; the review re-verdicts the baseline and audits the
seven MS1 acceptance clauses so P1 scheduling rests on evidence.
Evidence: Documents PR #47 merged as 9505c7e (plan SS2.3 review, MS1
audit, six registered gaps, index sync, seven SELF receipts under
docs/records); replays run in an isolated clone at RDM 4feb2f0 with
pins=v0.1.0; the private minutes receipt stays local by decision.
Impact: documents gitlink -> 9505c7e; task card records authorization,
requirements R1-R5, increments, and next-task candidates; no code
changes; review is not milestone acceptance.
Refs: Documents #47; task feature/rdm-status-review.
Why: The planning index named stage-record reconciliation as the
preferred next task; N1 WP6b/6c, the Q1 platform-task boundary, I1
reserved command consumption, and the I2 dangling reference all feed
N2/Q3 and RDM dependency judgments.
Evidence: Documents PR #46 merged as d630a04 (backfill sections in the
N1/Q1/I1 plan, stack completion plan I2 note, INDEX navigation); Dev
merge SHAs #230/#231/#234/#235/#237/#240 verified via git log --merges
on 2026-10-08; PR #242 body checked (0 wrong references, fixes confined
to the archived card).
Impact: modules/documents gitlink -> d630a04; archived I2 card now
points at stack completion plan SS5 I2 with a dated correction note;
task card records authorization, requirements, and increments.
Refs: Documents #46; task feature/agent-stack-stage-records.
Why: include the current integration baseline before verification.
Evidence: origin/main=7f1d87dbb976ebe02ceb632d5a657a416ffb50bc. The documents gitlink is resolved to documents main c39efdc5015c57b18e18cc99ecf7f4c4f2e499ee, which contains the planning index.
Impact: integrate upstream changes and point documents at the merged index.
Refs: task-sync; Documents #45
Co-authored-by: Cursor <cursoragent@cursor.com>
Why: check-pins requires nested and Dev-level pins to agree; squad main
advanced to 819b0c5 (nested agent-native pin #48) and backend main to
fe7c245 (nested agent-squad pin #103) after the Q3 WP1-WP5 merges.
Evidence: both component PRs CI green (GATE); make test recorded via
make evidence in the follow-up commit on this branch.
Impact: deps/agent-squad 663e89e -> 819b0c5; modules/backend 4791b2e ->
fe7c245; deps/agent-native stays 37c5e6f.
Refs: Q3 plan WP6; task card .task/feature-agent-stack-q3.md
Why: Q3 (convergence and interop) completed across agent-native (#40),
agent-squad (#46/#47) and backend (#99-#102); Dev gitlinks must track the
merged component mains and the task card records the outcome before the
completion declaration.
Evidence: card increment table rows WP1a-WP6 with merged PR/SHA references;
component CI statuses recorded as GATE in the card verification section;
three-segment outputs (precheck/task-sync/test) appended via make evidence
in follow-up commits on this branch.
Impact: deps/agent-squad bcc8d08 -> 663e89e, deps/agent-native 1ac21c6 ->
37c5e6f, modules/backend 06934bc -> 4791b2e; task card filled.
Refs: .task/feature-agent-stack-q3.md; Q3 plan 2026-10-07-agent-stack-q2q3-plans.md
Why: Q2 (topology library) completed in Agent-Squad across WP1-4 (PRs
#42-#45, main bcc8d08) and the backend nested pin followed (PR #98, main
06934bc); Dev gitlinks must track the merged component mains and the task
card records the outcome before the completion declaration.
Evidence: card increment table rows WP1-4 with merged PR/SHA references;
component CI statuses recorded as GATE in the card's verification section;
three-segment outputs (precheck/task-sync/test) appended via make evidence
in follow-up commits on this branch.
Impact: deps/agent-squad c462bc4 -> bcc8d08, modules/backend 6e02a1f ->
06934bc; task card filled (results/verification/increments).
Refs: .task/feature-agent-stack-q2.md; Q2 plan 2026-10-07-agent-stack-q2q3-plans.md
Why: Documents #44 merged the Q2/Q3 plans; the Dev documents pin
follows and the Q2 card opens with its requirement rows (Q3 gets its
own task after Q2 closes).
Evidence: R1-R4 map to the plan's Q2-WP1..WP4 with verified gap citations.
Impact: documentation pin + task card.
Refs: Agent-System-Documents#44
Why: backend main carries the nested core pin at a253a40b plus the
rewind-test settle-window fix; the combination check now passes across
all nested copies.
Evidence: check-pins pins ok; backend CI green on 26bd9286 (GATE).
Impact: none beyond the pin.
Refs: Agent-System-Backend#97
Why: the TypeScript contract authority gained the usage split fields
(Core a253a40b) and the ui mirror was regenerated (UI 76d66337); the
Dev build step regenerates contracts.ts from the authority, so the
pins must carry this combination for the worktree check to pass.
Evidence: make contracts on this combination produces byte-identical
files (verified locally).
Impact: none beyond the pins.
Refs: Agent-System-Core#24, Agent-System-UI#39
Why: Backend#96 merged the usage split and default retry; the core
Usage fields, Frontend#48, and the native/squad cascades landed; Dev
pins and the increment record follow.
Evidence: check-pins pins ok; WP6 chain CI green on every merge head;
audit N20 closes (split flows into run records on every path).
Impact: usage accounting is uniform end to end; stream retry is a
library default.
Refs: Agent-Native#35-#39, Agent-Squad#41, Agent-System-Backend#96,
Agent-System-Frontend#48
Why: Backend#95 merged the memory port wiring; Native#34 and Squad#38
carried the port; Dev pins and the increment record follow.
Evidence: check-pins pins ok; WP5 chain CI green on every merge head;
the migration parity test GATE on backend 766a96e8.
Impact: the memory port exists end to end with write-back.
Refs: Agent-Native#34, Agent-Squad#38, Agent-System-Backend#95
Why: Backend#94 merged the checkpoint closure wiring; Native#33 and
Squad#37 carried the library work; Dev pins and the increment record
follow.
Evidence: check-pins pins ok; WP3 chain CI green on every merge head;
acceptance clause 2's tests GATE across layers.
Impact: rollback evidence complete (eligibility, symlink guard,
partial restore, retention, HTTP).
Refs: Agent-Native#33, Agent-Squad#37, Agent-System-Backend#94
Why: Backend#93 merged the GenAI telemetry wiring; Native#32 and
Squad#36 carried the convention work; Dev pins and the increment
record follow.
Evidence: check-pins pins ok; WP4 chain CI green on every merge head;
acceptance clause 3's tests GATE on native fe0c4a9f.
Impact: spans follow the OTel GenAI convention end to end.
Refs: Agent-Native#32, Agent-Squad#36, Agent-System-Backend#93
Why: Backend#92 merged the JournalOnly conversation wiring; Native#31
and Squad#35 carried the library mode; Dev pins and the increment
record follow, including the design adjustment (journal-only instead
of transcript-authoritative, with the freeze rationale).
Evidence: check-pins pins ok; WP2 chain CI green on every merge head;
acceptance clause 1's product tests GATE on backend 9f3fdb26.
Impact: conversation runs are durable mid-turn without freezing the
context pipeline.
Refs: Agent-Native#31, Agent-Squad#35, Agent-System-Backend#92
Why: Backend#91 merged the graceful-resume split; Native#30 and
Squad#34 carried the tail repair and N6 fix; Dev pins and the
increment record follow.
Evidence: check-pins pins ok; WP1 chain CI green on every merge head;
acceptance clause 1's library tests GATE on native cb21ec4e.
Impact: every Run now pairs orphan tails before the first request;
gracefully-interrupted subagents resume exactly once.
Refs: Agent-Native#30, Agent-Squad#34, Agent-System-Backend#91
Why: Documents #43 merged the N3 plan; the Dev documents pin follows
and the card opens with its requirement rows.
Evidence: R1-R6 map to the plan's WP1-WP6 with verified gap citations.
Impact: documentation pin + task card.
Refs: Agent-System-Documents#43
Why: Backend#90 merged the subagent transcript/resume/notice work;
Native#29 and Squad#33 carried the Background field; Dev pins and the
increment record follow.
Evidence: check-pins pins ok; WP5 chain CI green on every merge head;
the three WP5 acceptance tests are GATE on backend main 7980a8a2.
Impact: subagents are resumable with per-run transcripts and durable
notices.
Refs: Agent-Native#29, Agent-Squad#33, Agent-System-Backend#90
Why: present a complete local index candidate without inferring missing plan owners.
Evidence: source facts, independent review and follow-up, all 19 source blobs, links and final make test output are preserved as SELF records.
Impact: Documents candidate and task metadata only; original plans and other tasks remain unchanged.
Refs: .task/feature-planning-index.md; Documents f8cc211
Why: Backend#89 merged the plugin/bundled skill validation; Native#28
and Squad#32 carried the validator; Dev pins, the plugins→skills edge,
and the increment record follow.
Evidence: check-pins pins ok; WP4 chain CI green on every merge head;
TestV2InvalidSkillRejected GATE on backend main b44f78b0.
Impact: skills now validated against the open Agent Skills spec.
Refs: Agent-Native#28, Agent-Squad#32, Agent-System-Backend#89
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#27 merged the MCP 2026-07-28 alignment; Squad#31 and
Backend#88 carried the cascade; Dev pins and the increment record follow.
Evidence: check-pins pins ok; WP3 chain CI green on every merge head;
TestStdioSlowCancelThenEcho (acceptance 3) passes unchanged.
Impact: MCP client negotiates versions and recognizes resultType.
Refs: Agent-Native#27, Agent-Squad#31, Agent-System-Backend#88
Why: Native#26 merged the native Anthropic client (acceptance clause 1,
audit N4 closed); Squad#30 and Backend#87 carried the cascade; Dev pins
and the increment record follow.
Evidence: check-pins pins ok; WP2 chain CI green on every merge head;
TestAnthropicPresetToolRound GATE on native main d6053baf.
Impact: acceptance clause 1 is closed.
Refs: Agent-Native#26, Agent-Squad#30, Agent-System-Backend#87
Why: Backend #86 merged the tool-group-aligned trimming; native #25 and
squad #29 carry the spill and cache contract work; the Dev pins and the
increment record follow.
Evidence: check-pins pins ok; WP1 chain CI green on every merge head.
Impact: acceptance clause 2's product side is closed
(TestTrimOldestKeepsToolPairs GATE).
Refs: Agent-Native#25, Agent-Squad#29, Agent-System-Backend#86
Why: Documents #42 merged the N2 plan (six work packages with the
current-state survey); the Dev pin follows.
Evidence: plan cites pinned baselines agent-native ead690b, backend
68addfd; implementation proceeds per its WP order.
Impact: documentation pin only.
Refs: Agent-System-Documents#42
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
weichen
