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: 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: 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.
Why: branches merged into main had left their task cards open; backfill status and archive to prevent bookkeeping debt.
Evidence: feature-ui-three-column-workbench.md(PR#322) — 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: task-sync merged authoritative main (documents pin and card
archives); receipts recorded before the merge are stale per the
evidence gate, so the key checks were rerun on the synced head.
Evidence: make test and make build rerun on 4c89175 with receipts
appended (SELF); task-sync receipt follows on the committed card.
Impact: task card only.
Why: establish the authorized task workspace and its initial baseline.
Evidence: preserved precheck receipt in .task/feature-collab-storage-pg-tier.md; R0=7743f53c5dfe9ed8dfd0663d05e3be15544d8942.
Impact: task metadata only; the feature workspace starts at 7743f53c5d.
Refs: .task/feature-collab-storage-pg-tier.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 evidence gate requires the three completion segments to be
written by the evidence tool into the task card rather than transcribed.
Evidence: make test and make build receipts appended (SELF); task-sync
to follow on a clean tree.
Impact: task card only.
Why: branches merged into main had left their task cards open; backfill status and archive to prevent bookkeeping debt.
Evidence: feature-collaboration-storage-plan.md(PR#320) — 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 card and PR description are one document; the PR link must be recorded on the branch before merge.
Evidence: Dev PR #320 and documents PR #59 created via Gitea API.
Impact: task metadata only.
Refs: PR #320.
Why: cross-repo gitlink changes require combined make test evidence before the Dev PR.
Evidence: make test exit 0 recorded by the evidence tool (governance, pins, libs, modules all green).
Impact: task card evidence table only.
Refs: documents PR #59; gitlink pin 45e08b9.
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=d9cd5c7dbe8bc62a8abd02f9f8f9014730be88af.
Impact: integrate upstream changes without rewriting task history.
Refs: task-sync
Why: the user approved plan r1 on 2026-10-11 (instruction to start the transformation per the plan); the card must carry the authorization basis and stage-review verdicts before publication.
Evidence: user instruction quoted verbatim in the card; resume precheck receipt imported (receipt_sha256 e8e77e87fc5990b9...).
Impact: task metadata and PROJECT.md entry only; plan content lives in the documents component PR #59.
Refs: documents PR #59; plan section 5 first increment U1+U2.
Why: branches merged into main had left their task cards open; backfill status and archive to prevent bookkeeping debt.
Evidence: feature-agent-s0-workspace-overlay.md(PR#318) — 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-ui-three-column-workbench.md; R0=73c901fa341a3653d6e0826d0da3497507995482.
Impact: task metadata only; the feature workspace starts at 73c901fa34.
Refs: .task/feature-ui-three-column-workbench.md
Why: establish the authorized task workspace and its initial baseline.
Evidence: preserved precheck receipt in .task/feature-collaboration-storage-plan.md; R0=73c901fa341a3653d6e0826d0da3497507995482.
Impact: task metadata only; the feature workspace starts at 73c901fa34.
Refs: .task/feature-collaboration-storage-plan.md
Why: establish the authorized task workspace and its initial baseline.
Evidence: preserved precheck receipt in .task/feature-agent-s0-workspace-overlay.md; R0=73c901fa341a3653d6e0826d0da3497507995482.
Impact: task metadata only; the feature workspace starts at 73c901fa34.
Refs: .task/feature-agent-s0-workspace-overlay.md
Why: branches merged into main had left their task cards open; backfill status and archive to prevent bookkeeping debt.
Evidence: feature-agent-e4-escalation-ledger.md(PR#315) — 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)
weichen