Why: Joined members must see one globally named project and keep private conversations and source documents.\n\nEvidence: Proposal links the fixed implementation plan, explicit authorization and task evidence without claiming deployment or CI success.\n\nImpact: Define optional lifecycle extension, identity recovery, private reads and published knowledge for U2/U3/U5.\n\nRefs: Dev feature/project-member-access
Why: Legacy upload events and synced duty flows need the same private-data and current-state guarantees as new member work.
Evidence: Real legacy SSE leakage and independent duty replay findings; correction evidence remains in the canonical task record.
Impact: Describe trusted per-event sharing and durable duty versions without new mandatory downstream interfaces or runtime changes.
Refs: system-project-membership r1.1; Dev feature/project-member-access
weichen
merged commit 047d362c72 into main2026-10-13 11:52:28 +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: 成员添加已保存却无法看到项目，是宿主项目与领域根未统一造成的入口缺口。本提案记录已获用户授权的统一项目与私域协作修复契约。
Evidence: 提案核对本次只读诊断、公开扩展申请及实施计划。正式命令输出、组件 SHA、独立 Review 和组合验收由 Dev 任务卡维护；本文没有预写 CI 或部署通过。
Impact: 明确全局名称、可信一对一投影、成员个人会话、每项目两树一网及发布知识/受控正文边界，更新总案 U2/U3/U5 的增量链接。8788 部署、运行库收养和发布 tag 另有授权边界。
Refs: 系统项目协作 r1；Dev feature/project-member-access 任务卡及实施计划 r1。