Why: the parent must pin the merged component SHAs so the combined build and CI gate run against the delivered U2 code and U1 runbook.
Evidence: backend origin-main merge commit of #137 and documents origin-main merge commit of #61 (fetched post-merge, replacing a stale pre-merge pin attempt).
Impact: gitlink updates only.
Refs: backend PR #137; documents PR #61.
Why: the approved plan r1 landed on documents main via PR #59; the Dev parent must pin it for the combined build.
Evidence: documents origin/main=95e5c9d307626727db2d1df3b42d74873bc8bbe4 containing proposal r1, index entry, review record, audit receipt.
Impact: gitlink only; no code or runtime change.
Refs: documents PR #59.
Why: include the current integration baseline before verification.
Evidence: fetched origin/main=4c8ad93892e5c8a88d7160220288720c40805251.
Impact: integrate upstream changes without rewriting task history.
Refs: task-sync
Why: include the current integration baseline before verification.
Evidence: fetched origin/main=5fa6cfbd8c8995c4267d0a76390f652b62d953dc.
Impact: integrate upstream changes without rewriting task history.
Refs: task-sync
Why: Frontend PR #49 merged; the pin must point at component main so the
merged content is actually contained (branch-head pins drop unmerged diff).
Evidence: vitest 85/85 and browser replay recorded earlier cover the branch
head; make test rerun on this pin before the Dev PR.
Impact: modules/frontend gitlink 84b73ab -> 339a9eb.
Refs: Frontend PR #49; task card feature/empty-state-preview-fix.
Why: include the current integration baseline before verification.
Evidence: fetched origin/main=412c8742a6db4baea83839d24dca32bdbecffb32.
Impact: integrate upstream changes without rewriting task history.
Refs: task-sync
Why: include the current integration baseline before verification.
Evidence: fetched origin/main=bf2a8f073079eb6b49910142151345e87da03ae1.
Impact: integrate upstream changes without rewriting task history.
Refs: task-sync
Why: the frontend fix branch carries the preview key unification, orphan-tab
adoption, conversation restore, and missing-artifact toast; the Dev gitlink
records the tested head ahead of the Frontend PR merge.
Evidence: vitest 85/85; fresh-profile browser replay in the task card.
Impact: modules/frontend gitlink 84b73ab -> 475fd3a only.
Refs: Frontend PR #49; task card feature/empty-state-preview-fix.
Why: Backend #126 (fact-check demotes the standing summary, verifier skip and
cap notices become process checks instead of final text) merged into component
main; the Dev gitlink moves with it.
Evidence: Backend PR #126 ci/vet-and-test success; Dev-level make test to be
recorded on this pin.
Impact: modules/backend gitlink d2bb936 -> c6912b6 only.
Refs: Backend PR #126; task card feature/final-reply-pollution-fix.
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.
weichen