Why: task-sync advanced the base; key checks re-run at the merged head per the evidence gate.
Evidence: make evidence appended the post-sync make test-governance run (146/146 OK); sync row recorded by task-sync.
Impact: task metadata only.
Refs: .task/feature-svc-autorecover.md
Why: include the current integration baseline before verification.
Evidence: fetched origin/main=acc8bf124c04b89ed05093467ebce865934bdddc.
Impact: integrate upstream changes without rewriting task history.
Refs: task-sync
Why: the completion claim needs tool-written evidence per the evidence gate.
Evidence: make evidence wrote the make test-governance run (146/146 OK) into the card.
Impact: task metadata only.
Refs: .task/feature-svc-autorecover.md
Why: svc services are bare nohup'd processes with persisted registration
but no supervision -- a crash, an OOM kill, or a reboot left them dead
until manual restart (2026-10-11 outage: dev service lost, runtime/ also
wiped by hand, nothing brought services back).
Evidence: tests/test_svc_recover.py 10 cases green (start records
autostart, stop clears it incl. dead-process stop, SIGKILL then recover
revives with persisted exec=, lock-held skips, port-stolen fails with
recover fail event, watchdog unit text via --print); make test-governance
146/146 OK locally; real-machine watchdog install + kill -9 revival to be
recorded on the task card.
Impact: svc.sh gains autostart key in svc.env, `recover [name]
[--quiet]` (postgres-first, per-service .start.lock, recover history
events), `watchdog install|remove|status` (systemd user timer, cron
fallback hint), lifecycle lock across start/stop/restart/deploy/update;
spawned services no longer inherit the lock fd (9>&-), and lock release
no longer clobbers script stderr. Makefile adds svc-recover/svc-watchdog;
docs/svc.md documents semantics and boundaries.
Refs: task card .task/feature-svc-autorecover.md; docs/svc.md 6.5/6.6;
parallel planning card feature/service-restart-recovery-plan (same
problem space, plan-stage).
Why: branches merged into main had left their task cards open; backfill status and archive to prevent bookkeeping debt.
Evidence: feature-rdm-e2e-acceptance.md(PR#393) — merges verified via git log --merges against origin/main.
Impact: .task/*.md moved to .task/archive/ with status backfilled; no code or submodule change.
Refs: task.sh close (card-autoclose-r1)
Why: include the current integration baseline before verification.
Evidence: fetched origin/main=660f581d81bb54c9868920df07e0b8fdbec8e036.
Impact: integrate upstream changes without rewriting task history.
Refs: task-sync
Why: task-sync advanced the Dev backend gitlink past the RDM pin; a newer-schema user-create CLI migrates the fresh store beyond what the RDM binary (schema ceiling of its pin) can open.
Evidence: reproduce on 20261011-180439 run (v25 store vs v24 binary); rerun green recorded after this change.
Impact: scripts/e2e.sh only; seeding and serving now share one base version.
Why: include the current integration baseline before verification.
Evidence: fetched origin/main=aa1f87602471cc567afd5756326e994315984fc8.
Impact: integrate upstream changes without rewriting task history.
Refs: task-sync
Why: git submodule clone over the flaky Gitea SSH endpoint hangs the whole run; local archive + pinned-checkout snapshot removes the network dependency and cuts the build stage to seconds.
Evidence: this exact tree ran scripts/e2e.sh to green (4 passed) twice, recorded in the task card.
Impact: scripts/e2e.sh only; behavior unchanged when the network is healthy.
Why: branches merged into main had left their task cards open; backfill status and archive to prevent bookkeeping debt.
Evidence: feature-material-intake-flow.md(PR#391) — merges verified via git log --merges against origin/main.
Impact: .task/*.md moved to .task/archive/ with status backfilled; no code or submodule change.
Refs: task.sh close (card-autoclose-r1)
Why: U4 acceptance needs a reproducible real-browser run: build the
RDM binary from its origin/main, seed projects/ingest via the command
API, serve with auth on, and drive Playwright against vite preview.
Evidence: scripts/e2e.sh --seed-only smoke (in progress this task);
frontend pin points at the Playwright harness commit.
Impact: dev tooling only (.tmp artifacts ignored; no runtime changes).
Refs: task feature/rdm-e2e-acceptance; frontend feature branch of
the same name.
Why: include the current integration baseline before verification.
Evidence: fetched origin/main=cef97ce34e0c77c83d24c9b4f39b94fb7a19ee2c.
Impact: integrate upstream changes without rewriting task history.
Refs: task-sync
Why: card closure requires the real PR link and completion backfill before archiving.
Evidence: links to merged PRs #48/#161/#390 and CI commit statuses (GATE).
Impact: task card only.
Why: include the current integration baseline before verification.
Evidence: fetched origin/main=94314361563d12271913eb5dabd4c42d03e69c19.
Impact: integrate upstream changes without rewriting task history.
Refs: task-sync
# Conflicts:
# modules/backend
Why: stage-7 products must be recorded before review.
Evidence: summaries reference the tool-written receipt rows above (SELF).
Impact: task card only.
Why: acceptance requires browser-level verification of the full loop.
Evidence: receipt mat-browser-e2e exit=0 (headless Chromium against the isolated AFTER instance, real MiniMax; SELF); screenshots under /tmp/mat-e2e/shots.
Impact: task card only.
Why: Branches #387/#388 merged but the close automation did not
recognize the hand-written card headers, leaving bookkeeping debt
(precheck would flag it).
Evidence: Both PRs merged with CI green (Dev #387, #388); E2E receipt
in the e2e-record card.
Impact: Cards moved to .task/archive/ with backfilled status.
Refs: PR #387; PR #388
Why: The children-repair card promised a post-deploy E2E rerun; it
now exists with a before/after contrast.
Evidence: Real MiniMax-M3 run on dev@0f61271 - present succeeded
(ok=true revision=1) where the pre-fix run fell back to a file
artifact; surfaces API returns the saved page. Receipt imported via
make evidence (SELF, key redacted).
Impact: Task card only.
Refs: PR #387
Why: The children-repair fix needs its card and evidence on the Dev
branch before publication.
Evidence: Receipts imported via make evidence (SELF); combined make
test exit 0 after clearing orphan test-server processes left by a
parallel session (earlier runs' port-collision failures retained in
/tmp receipts and noted in the card).
Impact: Task card only.
Refs: Backend PR #160
Why: honest evidence - full suite red on one svc.sh test that also fails on clean main (live dev service port collision).
Evidence: imported receipt exit=2 (SELF); main reproduction noted.
Impact: task card only.
Why: combined validation and review must run on the exact component versions of this task.
Evidence: gitlink updates only; make test to follow in the task card via make evidence.
Impact: modules/backend -> 16ed7b2 (I1-I3), modules/ui -> bfecf8b (pending-filter fix).
Refs: .task/feature-material-intake-flow.md I3.
Why: establish the authorized task workspace and its initial baseline.
Evidence: preserved precheck receipt in .task/feature-rdm-e2e-acceptance.md; R0=a884b5b4553ba070a4a08cbe4227718cbce856cf.
Impact: task metadata only; the feature workspace starts at a884b5b455.
Refs: .task/feature-rdm-e2e-acceptance.md
Why: branches merged into main had left their task cards open; backfill status and archive to prevent bookkeeping debt.
Evidence: feature-base-ext-admin-project.md(PR#385) — merges verified via git log --merges against origin/main.
Impact: .task/*.md moved to .task/archive/ with status backfilled; no code or submodule change.
Refs: task.sh close (card-autoclose-r1)
Why: policy/delivery.md requires staged review records; the user approved the plan and four scope rulings on 2026-10-11.
Evidence: card sections filled from the approved session plan (SELF); no command outputs transcribed.
Impact: task card only; no code changes.
Refs: .task/feature-material-intake-flow.md
Why: establish the authorized task workspace and its initial baseline.
Evidence: preserved precheck receipt in .task/feature-material-intake-flow.md; R0=555fb2162fe47e13835c592013bc3a69e46239e2.
Impact: task metadata only; the feature workspace starts at 555fb2162f.
Refs: .task/feature-material-intake-flow.md
weichen