Why: U3 requires the fixed Dev combination (gitlinks at the candidate) to test and build locally before requesting review.
Evidence: receipt in card; make test and make build exit 0 at the task branch HEAD.
Impact: card only.
Refs: feature/iam-u4-role-authority
Why: AE7 requires the same migration oracle to hold on the PG dialect.
Evidence: receipt in card; six migration/authority tests pass on isolated PostgreSQL.
Impact: card only.
Refs: feature/iam-u4-role-authority
Why: AE7 requires freeze/stage/compare/activate migration rehearsal evidence on the real store path.
Evidence: receipt in card; six migration/authority tests pass on SQLite.
Impact: card only.
Refs: feature/iam-u4-role-authority
Why: U3 replays the RDM development-contract suite against the fixed U4 backend overlay.
Evidence: receipt in card; all packages ok, exit 0 at rdm 0181982 x backend c8c49a6.
Impact: card only.
Refs: feature/iam-u4-role-authority
Why: U2's live layer must be recorded at its real evidence level (SELF, local harness run on frozen candidates).
Evidence: receipt in card; 18/18 (16 deterministic + 2 live) against backend@c8c49a6 rdm@0181982 frontend@05609ff ui@e295cae on a fresh SQLite root.
Impact: card only.
Refs: feature/iam-u4-role-authority
Why: U2 verification binds the frontend suites to the acceptance slice commit.
Evidence: receipt in card; 283 unit tests, build and knip baseline green at 05609ff.
Impact: card only.
Refs: feature/iam-u4-role-authority
Why: U2 verification requires the repeatable browser gate recorded by the evidence tool.
Evidence: receipt in card; 16/16 scenarios on the isolated preview at frontend 05609ff.
Impact: card only.
Refs: feature/iam-u4-role-authority
Why: U2 landed the browser acceptance slice and the live harness; DR21 requires the manifest to track the tested component heads.
Evidence: frontend 05609ff (e2e slice + admin draft guards), RDM 0181982 (live isolation harness); harness run green at these heads.
Impact: manifest rows only.
Refs: feature/iam-u4-role-authority
Why: U1 records the user's approved stage 7-10 delivery plan and fixes one synchronized candidate per DR1 before formal acceptance evidence.
Evidence: green task-sync receipt recorded via make evidence (sync_base ff3a562e, exit 0). Note: commit b2c2581's message called the prior receipt green; that receipt was a dirty-tree refusal — the honest record is its receipt content, superseded by this green run.
Impact: candidate manifest frozen at Backend c8c49a6, Frontend 20c20b7, UI e295cae, RDM 1537f3d, Documents c061181, Dev 1660515e; component branches all synced with their authoritative mains (RDM absorbed 83 commits, Frontend 2, Documents 1).
Refs: feature/iam-u4-role-authority
Why: include the current integration baseline before verification.
Evidence: fetched origin/main=ff3a562e50375ed592126c36ed2c76327517688a.
Impact: integrate upstream changes without rewriting task history.
Refs: task-sync
Why: U1 requires each task branch synchronized with origin/main before stage 7 evidence; the re-verification confirms the resolved sync.
Evidence: receipt in card, exit 0.
Impact: none.
Refs: feature/iam-u4-role-authority
Why: the plugin compose task card stayed open after its feature merged.
Evidence: Actions run 3300 jobs 5075 test, 5076 test-pg, 5077 svc-realcombo success on 4542cd7d37.
Impact: archive the card as completed. No product code change.
Refs: #562#558
Why: the first make task-sync hit the documents gitlink conflict; the evidence tool recorded the failure honestly before resolution.
Evidence: receipt in card, exit 1 on modules/documents conflict; resolution commit e913bc7.
Impact: none beyond the record.
Refs: feature/iam-u4-role-authority
Why: precheck reported SYNC_REQUIRED (17 commits behind); main advanced backend gitlink and card archives. The documents gitlink conflicted because neither side contains the other; resolved by syncing the Documents task branch with its main (d668a3e) first, giving c061181 which contains both the approved U4 plan (bcdb30c) and main's svc-compose proposal.
Evidence: resolved during make task-sync; green re-verification follows in the task card.
Impact: task branch is synchronized; documents pin is provisional until U6/U8 fix authoritative pins.
Refs: feature/iam-u4-role-authority
Why: branches merged into main had left their task cards open; backfill status and archive to prevent bookkeeping debt.
Evidence: feature-svc-plugin-compose.md(PR#558) — merges verified via git log --merges plus Gitea API squash lookup 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: deploy can compile selected plugins into one service binary.
Evidence: Actions run 3288 jobs 5053 test, 5054 test-pg, and 5055 svc-realcombo success on 77f7975cac. Head contains origin/main 63e70d8.
Impact: default remains no plugins; --with selects the catalog. Lifecycle suite stays NOT_RUN.
Refs: #558
Why: The stage 7-10 plan must be reviewed against the current authoritative Dev baseline.
Evidence: make task-sync completed at Dev f4ae91a with sync base 63e70d8 and recursive component checks passing.
Impact: Records the SELF sync receipt after resolving the Backend gitlink conflict; no additional product behavior is introduced.
Refs: feature/iam-u4-role-authority
Why: include the current integration baseline before verification.
Evidence: fetched origin/main=63e70d8b91ccb1691ce9b78a373e4e8bc9da24a2.
Impact: integrate upstream changes without rewriting task history.
Refs: task-sync
# Conflicts:
# modules/backend
Why: branches merged into main had left their task cards open; backfill status and archive to prevent bookkeeping debt.
Evidence: feature-pptx-gate-reference-integrity.md(PR#559) feature-workbench-visual-redesign.md(PR#556) — merges verified via git log --merges plus Gitea API squash lookup 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: Stage 6 is approved and the focused role-permission task needs a precise acceptance and protected-delivery contract.
Evidence: Documents bcdb30c passes git show --check and its SELF receipt is recorded in the task card.
Impact: Pins the reviewed stage 7-10 plan and records the approval state; no runtime code, production data, or deployment changes.
Refs: feature/iam-u4-role-authority
Why: include the current integration baseline before verification.
Evidence: fetched origin/main. The multi-instance account bootstrap conflict keeps main's identity ensure and activation flow.
Impact: integrate upstream changes without rewriting task history. Backend gitlink stays 80bb123.
Refs: task-sync
Co-authored-by: Cursor <cursoragent@cursor.com>
Why: Dev CI must build the backend head that contains current main and the child-event assertion fix.
Evidence: Agent-System-Backend feature/svc-plugin-host-options is 80bb123.
Impact: modules/backend gitlink only.
Refs: Agent-System-Backend 80bb123c874cd9eb0e25f12ccd41e888f727a7e1
Co-authored-by: Cursor <cursoragent@cursor.com>
Why: include the current integration baseline before verification.
Evidence: fetched origin/main=59cbf1109634b66c88f5b1702f330cd738aa75ef.
Impact: integrate upstream changes without rewriting task history.
Refs: task-sync
Why: The multi-instance acceptance test still created alice with a literal
password; backend U3 replaced local password-bearing creation with trusted
pending-account activation, so the first pin bump past U3 failed test-pg
with RECOVERY_CONTRACT_REPLACED. The seam was left pending by the U3 task
and this PR is the first to cross it.
Evidence: Full TestTwoInstancesOverSharedPG passes against a disposable
PostgreSQL 16 container (identity ensure -> bootstrap-admin -> pending
create with activation key -> key redemption -> grant-setup password ->
api key -> all cross-instance scenarios, 15s).
Impact: Test-only bootstrap rewrite (deployment-level identity ensured once
per pair, admin bootstrapped first, alice activated through the key
redemption and grant-setup password flow); no product code changes.
Refs: Dev task feature/pptx-gate-reference-integrity; backend U3 #198
Why: the current heads are not green, so the merge chain stops before any repository is merged.
Evidence: SELF query of the open pull requests and their current-head Actions runs.
Impact: task card only. This commit stays local so the open Dev pull request head does not move.
Refs: Agent-System-Dev pulls/558
Co-authored-by: Cursor <cursoragent@cursor.com>
Why: Stage 6 review must reference the post-sync Dev HEAD and its fresh exact-combination evidence.
Evidence: task-sync receipt 475cbbb4109b4486; make test receipt ead7146e2e2ffb5d; RDM overlay receipt 5c02b23e2348c4d.
Impact: Updates only the U4 task record after merging current origin/main; component SHAs remain unchanged.
Refs: feature/iam-u4-role-authority
Why: include the current integration baseline before verification.
Evidence: fetched origin/main=59cbf1109634b66c88f5b1702f330cd738aa75ef.
Impact: integrate upstream changes without rewriting task history.
Refs: task-sync
Why: the backend branch moved forward to include the OOXML gate fix, and this checkout should name that commit.
Evidence: Agent-System-Backend feature/svc-plugin-host-options is bffd37c.
Impact: modules/backend gitlink only.
Refs: Agent-System-Backend bffd37c42f809332499d3227ba1377c8d40c9459
Co-authored-by: Cursor <cursoragent@cursor.com>
Why: The review candidate needs reproducible evidence bound to the exact Dev and Frontend commits.
Evidence: SELF receipts record 272 unit tests, the production build, and 16 browser scenarios on Dev 49ef24b.
Impact: Updates only the task record; product behavior is unchanged.
Refs: feature/workbench-visual-redesign
Why: bootstrap-admin now refuses a database that has no agent_system_identity row, and serve does not insert one.
Evidence: Dev CI run 3266 job 5008 failed with system identity missing on 7eef723.
Impact: test setup only.
Refs: Agent-System-Dev pulls/558
Co-authored-by: Cursor <cursoragent@cursor.com>
Why: Final U4 combination must include the independently reviewed authorization and administration fixes.
Evidence: Backend SQLite and isolated PostgreSQL suites, RDM overlay full suite, Frontend tests/build, and independent final review passed.
Impact: Advances only Backend and Frontend gitlinks and records SELF evidence; RDM remains separately overlaid pending a trusted Backend release.
Refs: feature/iam-u4-role-authority
Why: the synced backend rejects password-bearing user create, so the shared-PG acceptance could not open its first account.
Evidence: Backend CI run 3261 succeeded on 8c60ed0; Dev test-pg run 3263 failed in TestTwoInstancesOverSharedPG before this change.
Impact: test setup only. Alice remains a non-admin account and still receives an API key after setting a password.
Refs: Agent-System-Dev pulls/558
Co-authored-by: Cursor <cursoragent@cursor.com>
Why: The review candidate needs reproducible evidence bound to the exact Dev and Frontend commits.
Evidence: SELF receipts record 272 unit tests, the production build, and 16 browser scenarios on Dev 49ef24b.
Impact: Updates only the task record; product behavior is unchanged.
Refs: feature/workbench-visual-redesign
Why: include the current integration baseline before verification.
Evidence: fetched origin/main=cc40e10f3b4b6e41cb3a7aa0826e08dd3b8b7270.
Impact: integrate upstream changes without rewriting task history.
Refs: task-sync
Why: The review candidate needs reproducible evidence bound to the exact Dev and Frontend commits.
Evidence: SELF receipts record 272 unit tests, the production build, and 16 browser scenarios on Dev 49ef24b.
Impact: Updates only the task record; product behavior is unchanged.
Refs: feature/workbench-visual-redesign
weichen
