Replace the NOT_RUN note in the deployment acceptance bullet with the
rerun result on dev@5360884: the 10-12 API checklist passes (11 items,
no model calls), run through a temporary genui-accept role and account
that were disabled afterwards. Also record that project.create now comes
only from roles, so admin cannot create projects until a role is assigned.
Why: the upgrade record still listed the GenUI acceptance as NOT_RUN.
Evidence: agent-exec unit documents-genui-prod-acceptance-20261021 (cursor, attempt 1, terminal=success); prod API replay VERDICT PASS on 2026-10-21.
Impact: documentation only.
Refs: Dev task fix/genui-prod-upgrade-followups.
Co-authored-by: Cursor <cursoragent@cursor.com>
Why: prod was upgraded on 2026-10-21 (schema v25 to v51) and both prod and
pg1 are now managed by scripts/svc.sh; the closure doc still described the
manual prodctl.sh layout.
Evidence: agent-exec unit documents-genui-prod-upgrade-docsync (cursor,
attempt 1, terminal=success); one bullet changed.
Impact: Documentation only.
Refs: Dev task feature/genui-prod-upgrade-docsync
Co-authored-by: Cursor <cursoragent@cursor.com>
Why: The closure doc still said prod is managed by `scripts/svc.sh prod`
from dev@c76f2bb; prod actually runs dev@b4649d7 from a preserved runtime
directory with manual prodctl.sh lifecycle, and pg1 moved under svc.
Evidence: Implemented by agent-exec unit documents-genui-prod-ops-docsync
(cursor, attempt 1, terminal=success); diff touches one bullet only.
Impact: Documentation only; no code or runtime change.
Refs: Dev task feature/genui-prod-ops-docsync
Co-authored-by: Cursor <cursoragent@cursor.com>
Why: the card and PR description are one record.
Evidence: PR #115 created via the Gitea API.
Impact: task card only.
Refs: Documents PR #115
Co-authored-by: Cursor <cursoragent@cursor.com>
Why: track preservation and merge of the approved U3 contract documents.
Evidence: SELF blob identity, diff check and ancestry checks recorded in the card.
Impact: task card only.
Refs: Dev PR #626; Documents c236d30, fb3a821, 5783940
Co-authored-by: Cursor <cursoragent@cursor.com>
Why: U4 must sync main before stage 7 acceptance; main carries 21 newer commits (renderer, regulations and two-trees documents). Evidence: git merge-tree reported no conflicts; no content resolved by hand. Impact: U4 documents now sit on main 5bb4877. Refs: Dev card feature-iam-u4-role-authority
Why: Register the U9 public contract proposal.
Evidence: CI success on 3a3904fe (governance).
Impact: Documentation only.
Refs: .task/feature-regulations-kb-ext20-proposal.md
Why: the adoption PR is reviewed and its candidate HEAD passed CI; the card closure is folded into the PR so no separate close PR is needed.
Evidence: CI GATE on 9d4582a47f4f4c887afd2fafb3ad507f20716f8d; independent Review REPLAY (cursor-agent-stable --mode ask 全新只读会话(fresh_session=true,session id not-observable)闭合重审 VERDICT: APPROVE(对象 9d4582a,与 HEAD 仅 .task/ 不同)).
Impact: task card only (moved to .task/archive/).
Refs: https://git-home.u1680832.nyat.app:30319/weichen/Agent-System-Documents/pulls/110
Why: independent Review blocked the adoption; the repair unit ran through the shared executor and was integrated with agent-exec apply.
Evidence: .task/evidence/governance-adoption/ (SELF): governance check and agent-exec validate on the repaired head.
Impact: task card and evidence logs only.
Refs: .task/feature-governance-adoption.md
Why: Phase 6 requires one positive executor run and the negative cases (missing config, bad receipt, out-of-scope path, unknown side effect) before adoption becomes active.
Evidence: .task/evidence/governance-adoption/ (SELF): governance check, agent-exec validate and adoption cases; this commit passed the generated pre-commit hook (admit).
Impact: task card and evidence logs only.
Refs: .task/feature-governance-adoption.md
Why: development-governance-v2 Phase 6 adopts the shared governance kit in every formal repository; the executor needs a valid AGENT-EXECUTION.md before any implementation unit can run.
Evidence: generated by dm-server governance init at Development-Manager bd3a7de57a3a9e1a4495b94c5fa5c08d71e7be8c; dm-server agent-exec validate passes.
Impact: configuration and task card only; no code or CI change yet.
Refs: Agent-System-Dev docs/superpowers/plans/2026-10-16-development-governance-v2-master.md
Why: Task 10 closed four independent review rounds and needs a durable record.
Evidence: Backend a2f4978 SELF suite plus host REPLAY of tools/docgen tests and Dev build.
Impact: Documentation only; no product behavior change.
Refs: docs/records/2026-10-15-unified-document-renderer/09-implementation-plan.md Task 10
Co-authored-by: Cursor <cursoragent@cursor.com>
Why: Task 9 now has a reproducible Renderer dependency, CLI implementation, independent review, one corrective pass and exact local/isolated-PostgreSQL evidence that require human assessment.
Evidence: The report fixes RDM 019d60d4 and Renderer 732e7e7, records all review findings and repairs, focused race, vet, make test/build and disposable PostgreSQL verification.
Impact: Documents the local RDM rendering transaction candidate without publishing profiles, migrating a real database, starting Task 10, pushing, merging or deploying.
Refs: Unified document renderer Task 9
Why: The three blocked Word bases now have safe derivative candidates implemented by CLI, independently reviewed, corrected, and verified without publishing profiles or changing source assets.
Evidence: RDM 48120ed and Renderer 732e7e7 bind a clean 44/44 compatibility receipt; the report records the review findings, one corrective pass, 20 safety tests, generator checks, and full build.
Impact: Replaces the prior 41-pass/3-blocked implementation snapshot with 44 safe-preflight draft bindings while retaining human visual and publication gates.
Refs: Unified document renderer Tasks 7-8
Why: PostgreSQL and authenticated product-matrix runs must remain tied to the exact RDM commit on which they executed.
Evidence: The report now distinguishes final-head SQLite and full-suite replay from the earlier 3f60265 PostgreSQL and 44/44 product runs.
Impact: Documentation-only evidence correction; no implementation or publication state changes.
Refs: Unified document renderer Tasks 7-8