Why: retain the clarified shared-project and private-document design with complete requirements coverage.
Evidence: SELF source receipt, 112-row requirements matrix, plan review and documentation checks in the task card.
Impact: local planning candidate only; no business implementation, push, merge to main or deployment.
Refs: modules/documents/docs/proposals/2026-10-11-rdm-final-target-completion.md
Why: save this task owned pending documentation before resuming the broader system plan.
Evidence: user confirmation and SELF documentation check receipt are retained in the task card.
Impact: local documentation snapshot only; no push or implementation.
Refs: .task/feature-rdm-template-dialog-plan.md
Why: include the current integration baseline before verification.
Evidence: fetched origin/main=80a518628c526fd6ddece4abeb707ab4bb0b5618.
Impact: integrate upstream changes without rewriting task history.
Refs: task-sync
Why: retain the requested template audit and proposed delivery design in the project entrypoints.
Evidence: SELF precheck, source inventory and documentation checks are preserved in the task card; business and combination tests NOT_RUN.
Impact: local documentation candidate only; no push, merge, migration or deployment.
Refs: .task/feature-rdm-template-dialog-plan.md
Why: the real-PG CI gate on PR #333 exposed the stack overflow; PR #142 fixes it with a regression test.
Evidence: backend origin-main merge of #142 fetched post-merge and checked out.
Impact: gitlink only.
Refs: backend PR #142; Dev PR #333.
Why: the parent must pin the merged component SHAs for the combined build and CI gates.
Evidence: both origin-main merge commits fetched post-merge and checked out.
Impact: gitlink updates only.
Refs: backend PR #141; documents PR #64.
Why: include the current integration baseline before verification.
Evidence: fetched origin/main=bfcdeef9aa335ca605c5794de9fc3889eeb1c2ab.
Impact: integrate upstream changes without rewriting task history.
Refs: task-sync
Why: include the current integration baseline before verification.
Evidence: fetched origin/main=90c07a5b4fb75251ea72b492ccb6714e5e699fe5.
Impact: integrate upstream changes without rewriting task history.
Refs: task-sync
Why: the plan was approved and merged in Documents (PR #63); the Dev pin and planning entry must follow the approved master record.
Evidence: modules/documents gitlink d3e40c783d1a092b67d025303f28384a564548f4 (Documents PR #63 merge, SELF API query); task card backfilled with the user rulings and merge record.
Impact: documents gitlink, PROJECT.md planning entry, and task-card metadata only; no code change.
Refs: Documents PR #63; .task/feature-rdm-two-trees-audit-plan.md
Why: include the current integration baseline before verification.
Evidence: fetched origin/main=6479eb5c38636e758b7e44a36fdc7ce6883ad1c9.
Impact: integrate upstream changes without rewriting task history.
Refs: task-sync
Why: The U1 controlled trial finished; its fixtures, validator, runner,
per-run results, report, and renderer spike must be reviewable from the
task branch, and the task card needs the final PASS/FAIL record.
Evidence: results/summary.json + report.md (SELF, MiniMax official
channel, CNY 3 of 200 cap); make evidence receipts for precheck,
task-sync, and make test follow in this branch.
Impact: Task-scoped experiment artifacts only (.task/genui-u1/); no
production code changes.
Refs: Documents PR #62 (proposal r2); task card feature/generative-ui-u1
Why: the parent must pin the merged component SHA for the combined build and CI gates.
Evidence: backend origin-main merge of #140 fetched and checked out.
Impact: gitlink only.
Refs: backend PR #140.
Why: the racing-migrator test failed deterministically on slow CI disks from the connection-open phase; PR #139 adds a bounded Begin retry and pre-materializes the racing test database.
Evidence: backend PR #139 merged (CI logs jobs 2285/2293 cited there); local store suite green.
Impact: gitlink only.
Refs: PR #325.
Why: the runner-container guard had a doubled '[[' from a string replacement (exit '[: too many arguments'), and pgvector's extension is named 'vector' (control file vector.control) - CREATE EXTENSION pgvector failed with 'extension not available' (jobs 2285/2286 logs).
Evidence: job 2286 log 'ERROR: extension pgvector is not available ... pgvector.control: No such file'; package postgresql-16-pgvector 0.6.0 installed fine.
Impact: test-pg job only; repins backend to the #138 merge (30s SQLite busy timeout for serialized migrators).
Refs: backend PR #138; Dev PR #325.
Why: include the current integration baseline before verification.
Evidence: fetched origin/main=2afcfd5d6db29e76ae89b34798b8f34f030a3a69.
Impact: integrate upstream changes without rewriting task history.
Refs: task-sync
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: include the current integration baseline before verification.
Evidence: fetched origin/main=2afcfd5d6db29e76ae89b34798b8f34f030a3a69.
Impact: integrate upstream changes without rewriting task history.
Refs: task-sync
# Conflicts:
# PROJECT.md
Why: The user ruled the three open choices on 2026-10-11 (first pilot =
in-conversation analysis page; trusted compiled-plugin delivery for
enable/disable; U1 trial limited to MiniMax M3 + M2.7-highspeed,
sanitized materials, CNY 200 cap), converting the research draft into a
publishable direction record.
Evidence: Precheck and evidence receipts live in the task card;
Documents PR #60 (merged at 3304efe) carries the proposal and index
entry that this gitlink pins.
Impact: Dev-side PROJECT.md entry, documents gitlink, and the task card
only; no code or contract changes.
Refs: modules/documents/docs/proposals/2026-10-10-generative-ui-plugin.md
Why: include the current integration baseline before verification.
Evidence: fetched origin/main=7743f53c5dfe9ed8dfd0663d05e3be15544d8942.
Impact: integrate upstream changes without rewriting task history.
Refs: task-sync
Why: The approved three-column redesign converges entries and hierarchy:
preview merges into a Work/Files third column, the left rail moves
project switching to the top and sinks files/workspaces/account to the
bottom, stop control consolidates into the input area with a light
fast/slow-lane status hint, and the top bar stops repeating project
identity. DESIGN.md 6 and 9.3 are revised in the same changeset per the
design gate (no token changes; 12.2 records the revision).
Evidence: Frontend npx vitest run 85/85 and npm run build passed in this
worktree (SELF receipts below); full make test to follow before review.
Impact: bumps modules/frontend to 3ed10e1 (two commits: layout rework +
workspace builtin expectations); DESIGN.md 6/9.3/12.2; task card records
requirements R1-R6 and the authorized-continuous scope.
Refs: three-column workbench proposal (2026-10-11).
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.
weichen