Why: include the current integration baseline before verification.
Evidence: fetched origin/main=d53efd5f14bb339dfe908c5d8850ed0eedec024e.
Impact: integrate upstream changes without rewriting task history.
Refs: task-sync
Why: The proposal 2026-10-10-agent-delegation-routing-sandbox.md merged
into Documents main (#53) and needs a Dev-side pin plus its task card so
the research, the F1-F5 defect findings, and the E1-E5/S0 increment plan
have a tracked record with evidence receipts.
Evidence: Task card feature-agent-exec-routing-sandbox-plan carries five
SELF receipts (sandbox latency benchmarks, model-endpoint probes) and the
make-test/task-sync runs are appended before the PR; Documents #53 merged
at 0f6d697.
Impact: Gitlink-only bump for modules/documents (3e43193 -> 0f6d697) plus
the task card; no product code changes.
Refs: Documents PR #53; proposals/2026-10-10-agent-delegation-routing-sandbox.md.
Why: Backend #125 (background subagent inbox card lifecycle, delegate/base-method
dual-speed guidance, #background mock demo) merged into component main; the Dev
gitlink must move to the merged head for the combo to build with it.
Evidence: Backend PR #125 CI green (ci/vet-and-test on 43087a7); Dev-level make
test to be rerun on the committed pin (previous run failed only the drift check
that expects exactly this commit).
Impact: modules/backend gitlink 421fee8 -> d2bb936; no other component moves.
Refs: Backend PR #125; task card feature/dual-speed-tasks.
Why: the Dev pin sat at e03d3ac while backend main moved to 421fee8
(#124: pluginRegistry now fills the shared EXT-8 authz slot instead of
rejecting in-proc registrations — the fix that restored rdm.* command
availability in the served RDM process). The umbrella must carry it
before v0.3.0 is tagged so the release combination includes the fix.
Evidence: Backend #124 head 72b2098 CI success, merged as 421fee8;
RDM consumed it as pins 421fee8 in RDM #173 with the full MS1
re-acceptance green. Umbrella make test follows via evidence.
Impact: umbrella gitlink only.
Refs: Backend #124; RDM #173; plan G1-8.
Why: The Dev combination must test the gate narrowing, fact checks and lazy
search registration.
Evidence: SELF - gitlink equals backend feature/agent-quality-phase05 head.
Impact: Pointer only.
Why: The Dev combination must test the working-method prompt set and the
compose demotion.
Evidence: SELF - gitlink equals backend feature/agent-quality-phase04 head.
Impact: Pointer only.
Why: The Dev combination must test the workspace-tool opening and the build
pipeline.
Evidence: SELF - gitlink equals backend feature/agent-quality-phase03 head.
Impact: Pointer only.
Why: Backend #115 (transcript-authoritative switch) and #118 (squad pin
alignment) merged; the Dev combination tests the merged head.
Evidence: SELF - gitlink equals backend origin/main head; make test recorded
on the task card after this commit.
Impact: Pointer only.
Why: include the current integration baseline before verification.
Evidence: fetched origin/main=6c763cc1cf4b3e980835de0ad864220f97f3c93c.
Impact: integrate upstream changes without rewriting task history.
Refs: task-sync
Why: Backend #115 merged the transcript-authoritative switch; the Dev
combination must test the merged head (with main's concurrent EXT-14).
Evidence: SELF - gitlink equals backend origin/main head.
Impact: Pointer only.
Why: RDM G1 sequence-4 needs the base to share retrieval inside runs and
open project listing/conversations to adapter-authorized members; the
implementation is merged on Backend main and the Dev gitlink is the
delivery vehicle.
Evidence: SELF - Backend PR #113 CI success at the merge head 9fa1787
(run rerun green after an unrelated ordering flake; the full suite passed
locally 32/32 first); Dev composite CI on this PR is the GATE.
Impact: modules/backend gitlink 449d8a6 -> 9fa1787. No other pin changes.
Refs: Backend #113; proposal 2026-10-09-ext-g1-b1-b3-exec-backend (EXT-13/15)
Why: I2 switches the direct path to the kernel transcript as the authoritative
context; the backend head carries that switch plus the nested kernel pin.
Evidence: SELF - gitlinks equal the pushed branch heads; combined make test
recorded on the task card after this commit.
Impact: Pointer only.
Why: EXT-13..EXT-16 (shared in-run retrieval, commands-as-tools, shared
project list, exec backend seam) are the base-side prerequisites RDM G1/G2
depend on; the application must live on the base Documents main before
implementation tasks can be opened against it.
Evidence: SELF - Documents #52 merged (3e43193); proposal cites code
locations verified at Dev main; Dev composite CI on this PR is the GATE.
Impact: modules/documents gitlink bump only.
Refs: Documents #52; RDM plan V1.1 sections 3.3/3.4/5.3
Why: The gate misfire fix from the live after-run belongs in the same increment.
Evidence: SELF - gitlink equals the backend phase02 head.
Impact: Pointer only.
Why: The Dev combination must test the context-fidelity increment.
Evidence: SELF - gitlink equals backend feature/agent-quality-phase02 head.
Impact: Pointer only.
Why: The backend branch gained the user-scope model capture fix, and the
live eval produced the before-baseline report on remote main (1ebd46e) that
the task card and the improvement-plan record reference as evidence.
Evidence: SELF - report .task/phase01-eval/before-main-1ebd46e.json (model
MiniMax-M2.7-highspeed, 4 golden tasks, 17 min run): reproduces the diagnosed
failure chain on the pre-fix build - readability dead-loop x4 on two tasks,
9 full regens with 0 original-material reads in plan-followup, 8 unverified
percentages, forged-marker false positive, internal check text leaked to the
user.
Impact: Report committed for the after-comparison once this PR merges; gitlink
points at the harness-inclusive backend head.
Why: The lint skills-root injection moved from the app root to the runner,
keeping the architecture ratchet green; the Dev combination must test that head.
Evidence: SELF - gitlink equals backend feature/agent-quality-phase01 head;
make test rerun recorded on the task card.
Impact: Pointer only.
Why: The previous pointer predated the eval/live package commit; the
combination must test the full phase01 backend branch.
Evidence: SELF - gitlink equals backend feature/agent-quality-phase01 head.
Impact: Pointer only.
Why: Backend carries the seven quality-gate repairs with the eval/live
harness; documents carries the improvement-plan main record with the six user
rulings. The Dev combination must test these heads together.
Evidence: SELF - gitlink pointers match the pushed branch heads; make test
recorded on the task card after this commit.
Impact: Combined test surface now includes the phase01 backend and documents
content; no behavior change from the pointers alone.
Refs: feature/agent-quality-phase01 (backend), feature/agent-quality-plan (documents).
Why: v0.2.0 must carry the DOCX tracked-change fix and the exec hard
switch (Backend #110) and the release record (Documents #50); RDM shared
work is blocked until v0.2.0 is tagged.
Evidence: SELF - make test exits 0 on this tree; Backend #110 CI success
on the merge commit; the composite CI on this PR is the GATE source.
Impact: modules/backend 92ede3b -> f1c9cc0, modules/documents 9995552 ->
d3c9b45. core/frontend/ui pins unchanged (a253a40/84b73ab/76d6633).
Refs: Backend #110; Documents #50; docs/records/2026-10-09-base-v0.2.0-release.md
Why: The Dev combination must pin the closure commit; make test validates the fixed combination.
Evidence: modules/backend -> 92ede3b970dd8bc0a40b3359a04a6e35b812a9d1 (Backend PR #109).
Impact: Gitlink only.
Refs: Backend PR #109; task card.
Why: The Dev combination must pin the EXT-11 commit; make test validates the fixed combination.
Evidence: modules/backend -> bbe39b475fc79d4e1fbf211d3d6d55dcad9fac4a (Backend PR #108).
Impact: Gitlink only.
Refs: Backend PR #108; task card.
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
weichen
