IAM U3 Dev composition: pin Frontend main 6db528d (PR #86, U3 account UI) and close the obsolete account help in scripts/svc.sh and docs.
Task card: .task/feature-iam-u3-account-directory-recovery.md (same document as this PR description).
Components: Backend PR #198 (v0.5.0, already in main), Frontend PR #86 -> 6db528d, RDM PR #380 -> 7c968d9.
Acceptance: merge_then_accept (user accepts on a deployment; issues become separate fix tasks).
IAM U3 Dev composition: pin Frontend main 6db528d (PR #86, U3 account UI) and close the obsolete account help in scripts/svc.sh and docs.
Task card: .task/feature-iam-u3-account-directory-recovery.md (same document as this PR description).
Components: Backend PR #198 (v0.5.0, already in main), Frontend PR #86 -> 6db528d, RDM PR #380 -> 7c968d9.
Acceptance: merge_then_accept (user accepts on a deployment; issues become separate fix tasks).
Why: establish the authorized task workspace and its initial baseline.
Evidence: preserved precheck receipt in .task/feature-iam-u3-account-directory-recovery.md; R0=add097d06137c4912a4ed9279e98ca353e4e4cf1.
Impact: task metadata only; the feature workspace starts at add097d061.
Refs: .task/feature-iam-u3-account-directory-recovery.md
Why: preserve the authorized U3 scope and concrete contract for human phase review.
Evidence: SELF startup and document-check receipts; independent document review of fixed drafts.
Impact: task metadata only; no product code, runtime data, production operations or gitlink changes.
Refs: Documents c236d3099dd3e20f7bdd35caf162e0be9a7d52eb; IAM r1 U3
Why: bind the human review checkpoint to the authoritative baseline and fixed contract.
Evidence: SELF task-sync and document-check receipts captured by make evidence.
Impact: evidence metadata only; business tests, CI and runtime delivery remain NOT_RUN.
Refs: Documents c236d3099dd3e20f7bdd35caf162e0be9a7d52eb; IAM U3 phase 4-5
Why: Operators need the approved no-password initialization and owner-confirmed recovery contract, and stage 6 reviewers need an exact component/evidence map.
Evidence: SELF task-card precheck and make test-governance receipts; component receipts listed in the task card with separate source identities.
Impact: svc rejects obsolete credential commands before storage binding, help points to protected delivery and recovery proposals, and the task card records stage 6 scope with formal pin/CI dependencies still pending.
Refs: IAM U3 r1 Documents c236d309; Backend 3e01614; RDM 265d33e; Frontend a961b19
Why: The stage 6 row should point to the committed Dev candidate without leaving a pending-commit placeholder.
Evidence: SELF git diff --cached --check at the task-card follow-up commit.
Impact: Reviewers use this card HEAD for the Dev help/guard diff; component SHAs and the pin limitation remain explicit.
Refs: IAM U3 r1; feature/iam-u3-account-directory-recovery
Why: Stage 6 reviewers need the observed flaky-test replays and the exact order needed to move from local overlay to a fixed RDM pin.
Evidence: SELF receipts named in the task card; this commit changes only review metadata, so the prior exact-head Dev governance result remains applicable to unchanged scripts.
Impact: Keeps formal stage 7/GATE and user-executed version publication explicit; no component source or production state changes.
Refs: IAM U3 r1; policy/delivery.md stage 6
Why: include the current integration baseline before verification.
Evidence: fetched origin/main=4f84c2e1630cd0311643529fae1c3a99f1dd5d64.
Impact: integrate upstream changes without rewriting task history.
Refs: task-sync
Why: Stage-six review needs the current Backend and RDM source identities and a clear boundary between local overlay checks and formal pin validation.
Evidence: SELF task-sync, exact-head Backend SQLite/PostgreSQL tests and build, RDM overlay checks, and Dev governance results are recorded by make evidence.
Impact: Review record only; no production migration, deployment, or formal acceptance.
Refs: IAM U3 r1; U7 PR #185
Why: Approved A1-A4 fixes have a committed Backend candidate, while independent review found that delegated rename still loses the real operator at the Backend write.
Evidence: The task card contains tool-written SELF receipts for exact Backend adcd8fe SQLite full test/build, isolated PostgreSQL suites, and RDM source-overlay full test/build.
Impact: Keeps stage 6 paused and records the pending Documents 5783940 stage 4-5 contract review. No component pin, PR, merge, production migration, deployment, or real-account action.
Refs: Documents U3 r1 c236d30, approved amendment fb3a821, delegated actor proposal 5783940.
Why: include the current integration baseline before verification.
Evidence: fetched origin/main=d23fb4363dcc0a206e71e47f9cd23a644c7e1c70.
Impact: integrate upstream changes without rewriting task history.
Refs: task-sync
Why: The Dev task branch synced new governance code while the U3 delegated projection contract awaits stage 4-5 human review.
Evidence: Tool-written SELF receipts in the task card contain make task-sync and make test-governance on Dev HEAD 05fa140, alongside fixed Backend and RDM source checks.
Impact: Updates only the U3 task record. Stage 6, formal pin, independent replay, CI, PR, merge and deployment remain pending.
Refs: Documents delegated actor proposal 5783940 and Backend candidate adcd8fe.
Why: The approved A1-A4 and delegated-actor repairs now have fixed Backend/RDM source candidates and reviewable local verification.
Evidence: The task card contains tool-written SELF receipts for exact Backend test/build, isolated PostgreSQL, RDM source overlay, Frontend/UI tests/build, browser account flows, and Dev governance.
Impact: Prepares stage 6 human review while preserving separate stage 7, trusted Backend tag, formal RDM pin, CI, PR, merge and production boundaries.
Refs: Documents U3 r1 c236d30, amendments fb3a821 and 5783940, Backend 7492fea, RDM source 98f50be.
Why: include the current integration baseline before verification.
Evidence: fetched origin/main=11aa76a3bc1c5047791f9a2de154e451634b6567.
Impact: integrate upstream changes without rewriting task history.
Refs: task-sync
Why: Backend, RDM, Documents and Dev main advanced while preparing the U3 candidate, requiring exact-source verification and a current review record.
Evidence: Tool-written SELF receipts cover synced Backend full test/build, isolated PostgreSQL serial replay, RDM source overlay full test/build, Frontend/UI checks, fresh isolated browser flow, and task-sync; failed attempts remain recorded.
Impact: Submits only a stage 6 review candidate. Formal RDM pin, independent replay/GATE, stage 7 acceptance, PR, merge, trusted tag and production work remain pending.
Refs: Backend d2f9b16, RDM source 98f50be and task branch 7b3d9eb, Documents amendments fb3a821 and 5783940.
Why: include the current integration baseline before verification.
Evidence: fetched origin/main=7e9ebdea5055a63c713ccc0fb1f938ffe35a6b9d.
Impact: integrate upstream changes without rewriting task history.
Refs: task-sync
Why: The review candidate needed current-main synchronization and a fixed account of the post-sync Backend, RDM, browser and PostgreSQL verification.
Evidence: Tool-written SELF receipts preserve failed parallel PG/SSE and browser setup attempts alongside serial PG, source-overlay, frontend and fresh-browser successes at their exact objects.
Impact: Task card only; stage 6 remains for human judgment, and stage 7, trusted Backend pin, GATE, PR, merge and production operations remain pending.
Refs: Backend d2f9b16, RDM source 98f50be, Documents amendments fb3a821 and 5783940.
Why: include the current integration baseline before verification.
Evidence: fetched origin/main=e1bc2602e18a89e4d75a4bf6cd80bc7f9b4d2164.
Impact: integrate upstream changes without rewriting task history.
Refs: task-sync
Why: Stage-seven recovery initially found a stale branch; after synchronization its own evidence receipt left the task card as the sole dirty path.
Evidence: Tool-written receipts preserve the SYNC_REQUIRED and SHARED_WORKSPACE_BUSY precheck results and the successful make task-sync output at the new Dev head.
Impact: Saves only this task card and restores a clean worktree for strict resume; no formal U3 acceptance or component pin change is claimed.
Refs: U3 task card and policy/governance.md startup and recovery gate.
Why: Stage 6 approval advanced U3 to formal testing and isolated PostgreSQL exposed a migration guard regression.
Evidence: The task card contains tool-written SELF receipts for the failing and corrected Backend candidate, current SQLite and PG suites, Frontend/UI, browser, Dev governance, and an imported independent reviewer log.
Impact: Backend Stage 7 is reviewable on fixed SHA 26305ca; trusted RDM pin, combined CI, and human acceptance remain open.
Refs: IAM U3; docs/proposals/2026-10-14-iam-u3-account-contract-and-plan.md §10
Why: The Stage 7 component review needs a fresh check against the authoritative Dev target without changing the candidate.
Evidence: Tool-written make task-sync receipt records sync_base e1bc260 and changed=0; Backend branch independently contains origin/main.
Impact: Review packet reflects the latest observed base while formal RDM pins and combined CI remain pending.
Refs: IAM U3; policy/delivery.md Stage 7; policy/merge-queue.md
Why: The planning line lagged the final Backend SHA and completed independent replay.
Evidence: The task card now points to the fixed component and preserves the failed dirty-tree sync receipt.
Impact: Stage 7 remains pending human review; no application code or component pin changed.
Refs: IAM U3; policy/delivery.md Stage 7
Why: The final review packet must show a clean current-base sync after the planning-status correction.
Evidence: make task-sync recorded sync_base e1bc260, tested_head b14c431, and changed=0; full output is tool-written in the task card.
Impact: Only task-card evidence changed; Backend candidate and component test objects remain fixed.
Refs: IAM U3; policy/delivery.md Stage 7
Why: The Backend draft PR moved to a new HEAD after CI exposed a time-sensitive SSE test and the corrected candidate now has verified GATE and independent replay.
Evidence: Tool-written receipts include final SQLite and isolated PostgreSQL suites, original reviewer replay, and a Gitea run/job identity check for PR #198 at 121b4d6.
Impact: Human Stage 7 review can use fixed Backend evidence; RDM trusted pin and Dev combined acceptance remain open.
Refs: IAM U3; Backend PR #198; policy/delivery.md Stage 7
Why: Stage 7 review requires a current-base sync after the final Backend evidence was recorded.
Evidence: Tool-written make task-sync receipt reports Dev sync_base e1bc260, tested_head a33cbe0, and changed=0; Backend remains 0 commits behind origin/main.
Impact: This commit adds only task-card evidence; the tested Backend, Frontend, and UI objects are unchanged.
Refs: IAM U3; policy/delivery.md Stage 7
Why: The user explicitly accepted the fixed Backend component test candidate while cross-repository U3 acceptance remains separate.
Evidence: Stage 7 record binds approval to Backend PR #198 head 121b4d6, local SELF, independent replay and Gitea run 3174.
Impact: Backend code review may proceed; trusted tag, RDM pin, Dev combined acceptance and production operations remain pending.
Refs: IAM U3; policy/delivery.md Stage 7
Why: Backend main advanced through new process-event and skills PRs after the original component approval, so the changed candidate needs impact-bound retesting and human review.
Evidence: Tool-written receipts cover red/green auth-off replay, exact-head SQLite and PG suites, independent two-Store PG replay, delta review and Gitea run 3190.
Impact: Backend PR #198 remains draft; affected Stage 7 approval, merge, trusted tag and RDM formal pin remain pending.
Refs: IAM U3; Backend PR #198; policy/delivery.md Stage 7
Why: include the current integration baseline before verification.
Evidence: fetched origin/main=a9fa63f657e0dad1033576fd6783f63ccfabcc4e.
Impact: integrate upstream changes without rewriting task history.
Refs: task-sync
Why: The human review packet must include the latest authoritative Dev base after the vendor-skills main advance.
Evidence: Tool-written make task-sync receipt records new sync_base a9fa63f, tested_head 08a7073, and the changed component/document metadata.
Impact: Dev task branch is current; the Backend U3 PR head and its independent tests remain separate fixed objects.
Refs: IAM U3; policy/delivery.md Stage 7
Why: The user accepted the new fixed Backend candidate after main introduced and U3 fenced the process-event read path.
Evidence: Stage 7 record binds approval to Backend 6dadde4, independent two-Store PostgreSQL replay, impact review and Gitea run 3190.
Impact: Backend PR #198 may enter final merge verification; trusted tag and downstream formal combination remain separate.
Refs: IAM U3; policy/delivery.md Stage 7; Backend PR #198
Why: Backend PR #198 has the required affected Stage 7 approval and needs a final current-target check before merge.
Evidence: Tool-written make task-sync receipt records Dev base a9fa63f, tested_head 4faaeed and changed=0; Backend branch is 0 behind its origin/main.
Impact: Only task-card evidence changed; no Backend source or validated PR head changed.
Refs: IAM U3; Backend PR #198; policy/delivery.md Stage 9
Why: Backend PR #198 has merged, but U3 depends on a user-published trusted Backend tag before RDM can adopt the public contract.
Evidence: Tool-written postmerge receipt verifies PR merged=true, merge 2716b9e with expected base/head parents, current main and Gitea run 3190 at the tested head.
Impact: Backend component is merged; RDM pins, combined acceptance, production work and cleanup remain open.
Refs: IAM U3; Backend PR #198; policy/delivery.md Stage 9
Why: RDM can formally consume the merged Backend public contract only after a trusted release tag, and release publication is an owner-only dual-key operation.
Evidence: The task card records absent proposed v0.5.0 refs, the verified merge commit, current RDM pin and exact readback/creation commands.
Impact: No tag was created or pushed; downstream formal pin and combined acceptance remain pending owner action.
Refs: IAM U3; Backend PR #198; AGENTS.md high-consequence release boundary
Why: The task record must distinguish the owner-published Backend tag, RDM pin, and Frontend Stage 7 candidate from earlier implementation snapshots.
Evidence: Tool-written SELF receipts preserve isolated browser red/green runs, independent REPLAY log import, and current Frontend GATE query for PR #86.
Impact: Reviewers can assess exact component versions and outstanding manual gates without treating historical NOT_RUN states as current.
Refs: IAM U3; Frontend PR #86; RDM PR #380
Why: include the current integration baseline before verification.
Evidence: fetched origin/main=99119a733830bc120cd6747b8b61736ea6da6078.
Impact: integrate upstream changes without rewriting task history.
Refs: task-sync
Why: The Frontend Stage 7 review packet needs an exact Dev synchronization receipt after main advanced.
Evidence: Tool-written make task-sync receipt records sync_base and tested_head; current Frontend PR GATE and independent replay remain tied to their own fixed SHAs.
Impact: Task card preserves the current review boundary without promoting older Dev combination receipts.
Refs: IAM U3; Frontend PR #86
Why: the user approved Frontend PR #86 stage 7 on 2026-10-14; the card still showed it pending.
Evidence: card text only.
Impact: task card only.
Refs: Frontend PR #86
Co-authored-by: Cursor <cursoragent@cursor.com>
Why: include the current integration baseline before verification.
Evidence: fetched origin/main=d9ac28f89159e17781e2a8ef3094965130f29d2f.
Impact: integrate upstream changes without rewriting task history.
Refs: task-sync
Why: the user approved Frontend PR #86 stage 7 on 2026-10-14; the card still showed it pending.
Evidence: card text only.
Impact: task card only.
Refs: Frontend PR #86
Co-authored-by: Cursor <cursoragent@cursor.com>
Why: include the current integration baseline before verification.
Evidence: fetched origin/main=d9ac28f89159e17781e2a8ef3094965130f29d2f.
Impact: integrate upstream changes without rewriting task history.
Refs: task-sync
Why: card must reflect the re-sync, reviews and component merges before closing.
Evidence: card text only; CI and merge records refer to platform runs.
Impact: task card only.
Refs: Dev PR #626, Frontend PR #86, RDM PR #380
Co-authored-by: Cursor <cursoragent@cursor.com>
Why: close the task card inside its own PR so landing it needs no post-merge backfill or separate close PR.
Evidence: .task/feature-iam-u3-account-directory-recovery.md -> .task/archive/feature-iam-u3-account-directory-recovery.md; status 已完成（合入前闭合）; PR #626https://git-home.u1680832.nyat.app:30319/weichen/Agent-System-Dev/pulls/626.
Impact: task metadata only; the card is archived within PR #626 and lands with its merge commit.
Refs: task.sh close --self
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
IAM U3 Dev composition: pin Frontend main 6db528d (PR #86, U3 account UI) and close the obsolete account help in scripts/svc.sh and docs.
Task card: .task/feature-iam-u3-account-directory-recovery.md (same document as this PR description).
Components: Backend PR #198 (v0.5.0, already in main), Frontend PR #86 -> 6db528d, RDM PR #380 -> 7c968d9.
Acceptance: merge_then_accept (user accepts on a deployment; issues become separate fix tasks).