Why: the U4 design and acceptance mapping must land with the code.
Evidence: clean merge of main 5bb4877; documents only.
Impact: documentation only.
Refs: Dev .task/feature-iam-u4-role-authority.md（任务卡即 PR 描述；阶段 7 候选清单与 DR1–DR15 映射）
Why: the U4 design and acceptance mapping must land with the code.
Evidence: clean merge of main 5bb4877; documents only.
Impact: documentation only.
Refs: Dev `.task/feature-iam-u4-role-authority.md`（任务卡即 PR 描述；阶段 7 候选清单与 DR1–DR15 映射）
Why: The implementation scope must match the requested single-role position model and three permission layers without carrying unrelated IAM work.
Evidence: The spec was checked for placeholders, internal contradictions, and whitespace errors.
Impact: Backend becomes the role authority while RDM retains project permissions and document duties.
Refs: IAM role and permission system
Why: The approved scope spans Backend authority, RDM project enforcement, and Frontend configuration and needs exact contracts and verification boundaries.
Evidence: The plan was checked against every specification section, fixed interface names, failure cases, and placeholder rules.
Impact: Implementation is limited to one effective role, system and project authorization, and the requested configuration views.
Refs: Focused role and permission system spec
Why: base the IAM delivery plan on the current Documents main.
Evidence: fetched origin/main=87b88018b9236434b97ff6781655d625901d4090.
Impact: integrates documentation-only upstream changes before adding the U4 delivery plan.
Refs: feature/iam-u4-role-authority
Why: The approved role and permission implementation needs a focused, reviewable path through browser acceptance, component delivery, and guarded closure.
Evidence: Structural audit confirms DR1-DR21, U1-U9, and KTD1-KTD6; git diff --check passes; six-lens document review findings are incorporated.
Impact: Adds the stage 7-10 plan, records the focused specification approval, and indexes the plan without authorizing production migration or deployment.
Refs: feature/iam-u4-role-authority
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
weichen
merged commit 1e036e981e into main2026-10-18 14:20:30 +00:00
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.
Why: the U4 design and acceptance mapping must land with the code.
Evidence: clean merge of main 5bb4877; documents only.
Impact: documentation only.
Refs: Dev
.task/feature-iam-u4-role-authority.md（任务卡即 PR 描述；阶段 7 候选清单与 DR1–DR15 映射）