Why: include the current integration baseline before verification.
Evidence: fetched origin/main=ec0169cad19c9525ce6ee4d7e26632351a5e5dbc.
Impact: integrate upstream changes without rewriting task history.
Refs: task-sync
Why: card and PR description are one document; record the PR link before merge.
Evidence: Dev PR #333 created via Gitea API.
Impact: task metadata only.
Refs: PR #333.
Why: stage review needs results, stage verdicts and the three evidence segments in the card before the PR.
Evidence: make test / test-backend-pg (real services) / make build all exit 0 via the evidence tool.
Impact: task metadata 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: 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: The close automation filled the card header (PR #329, merge
bfcdeef) but the merge-record and cleanup-record lines still said
NOT_RUN.
Evidence: CI ci/test passed on final head 7f58e6e (run 1767) after a
pre-merge task-sync to 90c07a5; task-finish recycled the worktree and
deleted the task branch at 7f58e6e on 2026-10-11.
Impact: Archived task-card text only.
Refs: PR #329; PR #332
Why: branches merged into main had left their task cards open; backfill status and archive to prevent bookkeeping debt.
Evidence: feature-generative-ui-u1.md(PR#329) — 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: establish the authorized task workspace and its initial baseline.
Evidence: preserved precheck receipt in .task/feature-collab-storage-u3-budget-authz.md; R0=90c07a5b4fb75251ea72b492ccb6714e5e699fe5.
Impact: task metadata only; the feature workspace starts at 90c07a5b4f.
Refs: .task/feature-collab-storage-u3-budget-authz.md
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: branches merged into main had left their task cards open; backfill status and archive to prevent bookkeeping debt.
Evidence: feature-collab-storage-u3-atomicity.md(PR#328) — 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=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: card and PR description are one document; record the PR link on the branch before merge.
Evidence: Dev PR #328 created via Gitea API.
Impact: task metadata only.
Refs: PR #328.
Why: stage review needs the results, stage verdicts and three evidence segments in the card before the PR.
Evidence: make test / test-backend-pg (real services) / make build all exit 0 via the evidence tool.
Impact: task metadata only.
Refs: backend PR #140.
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: establish the authorized task workspace and its initial baseline.
Evidence: preserved precheck receipt in .task/feature-collab-storage-u3-atomicity.md; R0=6479eb5c38636e758b7e44a36fdc7ce6883ad1c9.
Impact: task metadata only; the feature workspace starts at 6479eb5c38.
Refs: .task/feature-collab-storage-u3-atomicity.md
Why: branches merged into main had left their task cards open; backfill status and archive to prevent bookkeeping debt.
Evidence: feature-collab-storage-pg-tier.md(PR#325) — 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: 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: include the current integration baseline before verification.
Evidence: fetched origin/main=5771d4f1e5b692bce95eb64cc30dc9931079ad12.
Impact: integrate upstream changes without rewriting task history.
Refs: task-sync
Why: the job runs the full backend suite against real services; internal/runtime lint tests require python-docx (job 2290: ModuleNotFoundError 'docx') which the plain test job already installs.
Evidence: job 2290 log; all PG/Redis-dependent packages green in the same run (store 2.6s, pgbus, runmgr, ratelimit, server).
Impact: test-pg job setup only.
Refs: Dev 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: establish the authorized task workspace and its initial baseline.
Evidence: preserved precheck receipt in .task/feature-generative-ui-u1.md; R0=5771d4f1e5b692bce95eb64cc30dc9931079ad12.
Impact: task metadata only; the feature workspace starts at 5771d4f1e5.
Refs: .task/feature-generative-ui-u1.md
Why: the runner container executes as root without sudo; the previous $SUDO -u postgres expanded to a bare '-u' and failed with exit 127 on the first test-pg run (job 2280 log).
Evidence: job 2280 log lines '/var/run/act/workflow/3: line 6: -u: command not found', exitcode 127; postgresql service itself started fine as root.
Impact: test-pg job setup steps only; also prints pinned pgvector/pg_trgm extension versions for acceptance records.
Refs: PR #325; docs/guides/team-storage.md section 5.
Why: The close automation filled the card header (PR #324, merge
0d92b9e) but the merge-record and cleanup-record lines still described
the in-progress state.
Evidence: CI ci/test passed on PR HEAD 6b96967 (run 1738); task-finish
recycled the worktree and deleted the local/remote task branch at
6b96967 on 2026-10-11.
Impact: Archived task-card text only.
Refs: PR #324; PR #326
Why: branches merged into main had left their task cards open; backfill status and archive to prevent bookkeeping debt.
Evidence: feature-generative-ui-research.md(PR#324) — 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: card and PR description are one document; the PR link and the user's authorization basis must be on the branch before merge.
Evidence: Dev PR #325 created via Gitea API; user directive 2026-10-11 quoted in the card.
Impact: task metadata only.
Refs: PR #325.
Why: the card is the single record for stage review; results, stage verdicts and the three evidence runs must be in it before the PR.
Evidence: make test / test-backend-pg (real PG+Redis) / make build all exit 0, written by the evidence tool.
Impact: task metadata 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
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 collaboration plan U2 requires CI to run the backend suite against real PostgreSQL+pgvector and Redis and fail when the services are missing, instead of silently skipping the tier.
Evidence: local gate green twice against PostgreSQL 18.6+pgvector and Redis 8.10.2 (isolated svc.sh instance); the target fails fast when AGENT_PG_TEST_DSN/AGENT_REDIS_TEST_ADDR are unset.
Impact: new make target test-backend-pg (env-guarded) and a required test-pg job (apt postgresql-16-pgvector + redis-server, ephemeral per-run services); existing test job unchanged.
Refs: proposals/2026-10-11-collaboration-storage-and-distribution.md U2; docs/guides/team-storage.md section 5.
weichen