refactor(gov): 重构强制除名机制并拆分即时除名与裁决除名

[Mikuoso]

Summary by Sourcery

通过将之前单一的强制移除流程拆分为两种分级流程（即时移除和基于裁决的移除），细化维护者移除治理策略，并在变更日志中记录这些更改。

Enhancements:

• 在项目变更日志中记录重构后的两级强制移除机制及其保障措施。

Documentation:

• 更新维护者治理文档，区分针对恶性违规行为的即时移除和针对其他严重不当行为的基于裁决的移除，并说明相关流程、时间线以及申诉/观察机制。

Original summary in English

Summary by Sourcery

Refine the maintainer removal governance policy by splitting the previous single forced-removal flow into two graded processes for immediate and ruling-based removal, and document these changes in the changelog.

Enhancements:

• Record the refactored two-tier forced-removal mechanism and its safeguards in the project changelog.

Documentation:

• Update maintainer governance documentation to distinguish between immediate removal for egregious violations and ruling-based removal for other serious misconduct, including procedures, timelines, and appeal/observation mechanisms.

由 Sourcery 提供的总结

通过将原先单一的强制移除流程拆分为独立的“立即移除”和“裁决式移除”路径，细化维护者治理机制，并文档化新的分级流程和状态。

增强内容：

• 通过将自愿辞任、自动休眠和强制移除拆分成独立的治理章节，澄清维护者退出与休眠部分。
• 引入两级强制移除体系，将针对不可挽回或违法事件的“立即移除”和针对其他严重不当行为的“裁决式移除”区分开来，并包含详细的状态转换、时间线和保障措施。

文档：

• 更新治理文档，描述新的“立即移除”和“裁决式移除”维护者处理流程，包括申诉与观察机制。
• 在项目变更日志中记录重构后的强制移除政策及其分级工作流。
• 新增 CLAUDE.md 指南，说明仓库背景、文档规范以及面向 AI 助手的贡献流程。

Original summary in English

Summary by Sourcery

重构维护者退出和移除治理机制，通过将休眠/退出与强制移除分离，并统一访问控制语义。

Enhancements:

• 将维护者治理拆分为独立的退出/休眠和强制移除两个部分，引入统一且有文档记录的「因故移除」流程，明确定义降级、决策和申诉阶段。
• 简化访问控制的状态/权限矩阵，并新增「状态到权限」映射表，将先前的中间状态合并为单一的 Removal 状态。

Documentation:

• 记录新的强制移除流程，包括降级、决策和申诉时间线，并阐明其与维护者角色及休眠状态之间的关系。
• 在项目更新日志中记录重构后的移除机制以及访问控制的简化。

Original summary in English

Summary by Sourcery

Refactor maintainer exit and removal governance by separating dormancy/exit from forced removal and aligning access-control semantics.

Enhancements:

• Split maintainer governance into separate exit/dormancy and forced-removal sections, introducing a unified, documented removal-for-cause flow with explicit downgrade, decision, and appeal stages.
• Simplify the access-control state/permission matrix and add a status-to-permission mapping table that consolidates prior intermediate states into a single Removal status.

Documentation:

• Document the new forced-removal process, including downgrade, decision, and appeal timelines, and clarify how it interacts with maintainer roles and dormancy.
• Record the refactored removal mechanism and access-control simplification in the project changelog.

Original summary in English

Summary by Sourcery

重构维护者退出和移除治理机制，通过将休眠/退出与强制移除分离，并统一访问控制语义。

Enhancements:

• 将维护者治理拆分为独立的退出/休眠和强制移除两个部分，引入统一且有文档记录的「因故移除」流程，明确定义降级、决策和申诉阶段。
• 简化访问控制的状态/权限矩阵，并新增「状态到权限」映射表，将先前的中间状态合并为单一的 Removal 状态。

Documentation:

• 记录新的强制移除流程，包括降级、决策和申诉时间线，并阐明其与维护者角色及休眠状态之间的关系。
• 在项目更新日志中记录重构后的移除机制以及访问控制的简化。

Original summary in English

Summary by Sourcery

Refactor maintainer exit and removal governance by separating dormancy/exit from forced removal and aligning access-control semantics.

Enhancements:

• Split maintainer governance into separate exit/dormancy and forced-removal sections, introducing a unified, documented removal-for-cause flow with explicit downgrade, decision, and appeal stages.
• Simplify the access-control state/permission matrix and add a status-to-permission mapping table that consolidates prior intermediate states into a single Removal status.

Documentation:

• Document the new forced-removal process, including downgrade, decision, and appeal timelines, and clarify how it interacts with maintainer roles and dormancy.
• Record the refactored removal mechanism and access-control simplification in the project changelog.

Original summary in English

Summary by Sourcery

重构维护者退出和移除治理机制，通过将休眠/退出与强制移除分离，并统一访问控制语义。

Enhancements:

• 将维护者治理拆分为独立的退出/休眠和强制移除两个部分，引入统一且有文档记录的「因故移除」流程，明确定义降级、决策和申诉阶段。
• 简化访问控制的状态/权限矩阵，并新增「状态到权限」映射表，将先前的中间状态合并为单一的 Removal 状态。

Documentation:

• 记录新的强制移除流程，包括降级、决策和申诉时间线，并阐明其与维护者角色及休眠状态之间的关系。
• 在项目更新日志中记录重构后的移除机制以及访问控制的简化。

Original summary in English

Summary by Sourcery

Refactor maintainer exit and removal governance by separating dormancy/exit from forced removal and aligning access-control semantics.

Enhancements:

• Split maintainer governance into separate exit/dormancy and forced-removal sections, introducing a unified, documented removal-for-cause flow with explicit downgrade, decision, and appeal stages.
• Simplify the access-control state/permission matrix and add a status-to-permission mapping table that consolidates prior intermediate states into a single Removal status.

Documentation:

• Document the new forced-removal process, including downgrade, decision, and appeal timelines, and clarify how it interacts with maintainer roles and dormancy.
• Record the refactored removal mechanism and access-control simplification in the project changelog.

Original summary in English

Summary by Sourcery

重构维护者退出和移除治理机制，通过将休眠/退出与强制移除分离，并统一访问控制语义。

Enhancements:

• 将维护者治理拆分为独立的退出/休眠和强制移除两个部分，引入统一且有文档记录的「因故移除」流程，明确定义降级、决策和申诉阶段。
• 简化访问控制的状态/权限矩阵，并新增「状态到权限」映射表，将先前的中间状态合并为单一的 Removal 状态。

Documentation:

• 记录新的强制移除流程，包括降级、决策和申诉时间线，并阐明其与维护者角色及休眠状态之间的关系。
• 在项目更新日志中记录重构后的移除机制以及访问控制的简化。

Original summary in English

Summary by Sourcery

Refactor maintainer exit and removal governance by separating dormancy/exit from forced removal and aligning access-control semantics.

Enhancements:

• Split maintainer governance into separate exit/dormancy and forced-removal sections, introducing a unified, documented removal-for-cause flow with explicit downgrade, decision, and appeal stages.
• Simplify the access-control state/permission matrix and add a status-to-permission mapping table that consolidates prior intermediate states into a single Removal status.

Documentation:

• Document the new forced-removal process, including downgrade, decision, and appeal timelines, and clarify how it interacts with maintainer roles and dormancy.
• Record the refactored removal mechanism and access-control simplification in the project changelog.

Original summary in English

Summary by Sourcery

重构维护者退出和移除治理机制，通过将休眠/退出与强制移除分离，并统一访问控制语义。

Enhancements:

• 将维护者治理拆分为独立的退出/休眠和强制移除两个部分，引入统一且有文档记录的「因故移除」流程，明确定义降级、决策和申诉阶段。
• 简化访问控制的状态/权限矩阵，并新增「状态到权限」映射表，将先前的中间状态合并为单一的 Removal 状态。

Documentation:

• 记录新的强制移除流程，包括降级、决策和申诉时间线，并阐明其与维护者角色及休眠状态之间的关系。
• 在项目更新日志中记录重构后的移除机制以及访问控制的简化。

Original summary in English

Summary by Sourcery

Refactor maintainer exit and removal governance by separating dormancy/exit from forced removal and aligning access-control semantics.

Enhancements:

• Split maintainer governance into separate exit/dormancy and forced-removal sections, introducing a unified, documented removal-for-cause flow with explicit downgrade, decision, and appeal stages.
• Simplify the access-control state/permission matrix and add a status-to-permission mapping table that consolidates prior intermediate states into a single Removal status.

Documentation:

• Document the new forced-removal process, including downgrade, decision, and appeal timelines, and clarify how it interacts with maintainer roles and dormancy.
• Record the refactored removal mechanism and access-control simplification in the project changelog.

Original summary in English

Summary by Sourcery

重构维护者退出和移除治理机制，通过将休眠/退出与强制移除分离，并统一访问控制语义。

Enhancements:

• 将维护者治理拆分为独立的退出/休眠和强制移除两个部分，引入统一且有文档记录的「因故移除」流程，明确定义降级、决策和申诉阶段。
• 简化访问控制的状态/权限矩阵，并新增「状态到权限」映射表，将先前的中间状态合并为单一的 Removal 状态。

Documentation:

• 记录新的强制移除流程，包括降级、决策和申诉时间线，并阐明其与维护者角色及休眠状态之间的关系。
• 在项目更新日志中记录重构后的移除机制以及访问控制的简化。

Original summary in English

Summary by Sourcery

Refactor maintainer exit and removal governance by separating dormancy/exit from forced removal and aligning access-control semantics.

Enhancements:

• Split maintainer governance into separate exit/dormancy and forced-removal sections, introducing a unified, documented removal-for-cause flow with explicit downgrade, decision, and appeal stages.
• Simplify the access-control state/permission matrix and add a status-to-permission mapping table that consolidates prior intermediate states into a single Removal status.

Documentation:

• Document the new forced-removal process, including downgrade, decision, and appeal timelines, and clarify how it interacts with maintainer roles and dormancy.
• Record the refactored removal mechanism and access-control simplification in the project changelog.

Original summary in English

Summary by Sourcery

重构维护者退出和移除治理机制，通过将休眠/退出与强制移除分离，并统一访问控制语义。

Enhancements:

• 将维护者治理拆分为独立的退出/休眠和强制移除两个部分，引入统一且有文档记录的「因故移除」流程，明确定义降级、决策和申诉阶段。
• 简化访问控制的状态/权限矩阵，并新增「状态到权限」映射表，将先前的中间状态合并为单一的 Removal 状态。

Documentation:

• 记录新的强制移除流程，包括降级、决策和申诉时间线，并阐明其与维护者角色及休眠状态之间的关系。
• 在项目更新日志中记录重构后的移除机制以及访问控制的简化。

Original summary in English

Summary by Sourcery

Refactor maintainer exit and removal governance by separating dormancy/exit from forced removal and aligning access-control semantics.

Enhancements:

• Split maintainer governance into separate exit/dormancy and forced-removal sections, introducing a unified, documented removal-for-cause flow with explicit downgrade, decision, and appeal stages.
• Simplify the access-control state/permission matrix and add a status-to-permission mapping table that consolidates prior intermediate states into a single Removal status.

Documentation:

• Document the new forced-removal process, including downgrade, decision, and appeal timelines, and clarify how it interacts with maintainer roles and dormancy.
• Record the refactored removal mechanism and access-control simplification in the project changelog.

Original summary in English

Summary by Sourcery

重构维护者退出和移除治理机制，通过将休眠/退出与强制移除分离，并统一访问控制语义。

Enhancements:

• 将维护者治理拆分为独立的退出/休眠和强制移除两个部分，引入统一且有文档记录的「因故移除」流程，明确定义降级、决策和申诉阶段。
• 简化访问控制的状态/权限矩阵，并新增「状态到权限」映射表，将先前的中间状态合并为单一的 Removal 状态。

Documentation:

• 记录新的强制移除流程，包括降级、决策和申诉时间线，并阐明其与维护者角色及休眠状态之间的关系。
• 在项目更新日志中记录重构后的移除机制以及访问控制的简化。

Original summary in English

Summary by Sourcery

Refactor maintainer exit and removal governance by separating dormancy/exit from forced removal and aligning access-control semantics.

Enhancements:

• Split maintainer governance into separate exit/dormancy and forced-removal sections, introducing a unified, documented removal-for-cause flow with explicit downgrade, decision, and appeal stages.
• Simplify the access-control state/permission matrix and add a status-to-permission mapping table that consolidates prior intermediate states into a single Removal status.

Documentation:

• Document the new forced-removal process, including downgrade, decision, and appeal timelines, and clarify how it interacts with maintainer roles and dormancy.
• Record the refactored removal mechanism and access-control simplification in the project changelog.

Original summary in English

Summary by Sourcery

重构维护者退出和移除治理机制，通过将休眠/退出与强制移除分离，并统一访问控制语义。

Enhancements:

• 将维护者治理拆分为独立的退出/休眠和强制移除两个部分，引入统一且有文档记录的「因故移除」流程，明确定义降级、决策和申诉阶段。
• 简化访问控制的状态/权限矩阵，并新增「状态到权限」映射表，将先前的中间状态合并为单一的 Removal 状态。

Documentation:

• 记录新的强制移除流程，包括降级、决策和申诉时间线，并阐明其与维护者角色及休眠状态之间的关系。
• 在项目更新日志中记录重构后的移除机制以及访问控制的简化。

Original summary in English

Summary by Sourcery

Refactor maintainer exit and removal governance by separating dormancy/exit from forced removal and aligning access-control semantics.

Enhancements:

• Split maintainer governance into separate exit/dormancy and forced-removal sections, introducing a unified, documented removal-for-cause flow with explicit downgrade, decision, and appeal stages.
• Simplify the access-control state/permission matrix and add a status-to-permission mapping table that consolidates prior intermediate states into a single Removal status.

Documentation:

• Document the new forced-removal process, including downgrade, decision, and appeal timelines, and clarify how it interacts with maintainer roles and dormancy.
• Record the refactored removal mechanism and access-control simplification in the project changelog.

Original summary in English

Summary by Sourcery

重构维护者退出和移除治理机制，通过将休眠/退出与强制移除分离，并统一访问控制语义。

Enhancements:

• 将维护者治理拆分为独立的退出/休眠和强制移除两个部分，引入统一且有文档记录的「因故移除」流程，明确定义降级、决策和申诉阶段。
• 简化访问控制的状态/权限矩阵，并新增「状态到权限」映射表，将先前的中间状态合并为单一的 Removal 状态。

Documentation:

• 记录新的强制移除流程，包括降级、决策和申诉时间线，并阐明其与维护者角色及休眠状态之间的关系。
• 在项目更新日志中记录重构后的移除机制以及访问控制的简化。

Original summary in English

Summary by Sourcery

Refactor maintainer exit and removal governance by separating dormancy/exit from forced removal and aligning access-control semantics.

Enhancements:

• Split maintainer governance into separate exit/dormancy and forced-removal sections, introducing a unified, documented removal-for-cause flow with explicit downgrade, decision, and appeal stages.
• Simplify the access-control state/permission matrix and add a status-to-permission mapping table that consolidates prior intermediate states into a single Removal status.

Documentation:

• Document the new forced-removal process, including downgrade, decision, and appeal timelines, and clarify how it interacts with maintainer roles and dormancy.
• Record the refactored removal mechanism and access-control simplification in the project changelog.

Original summary in English

Summary by Sourcery

重构维护者退出和移除治理机制，通过将休眠/退出与强制移除分离，并统一访问控制语义。

Enhancements:

• 将维护者治理拆分为独立的退出/休眠和强制移除两个部分，引入统一且有文档记录的「因故移除」流程，明确定义降级、决策和申诉阶段。
• 简化访问控制的状态/权限矩阵，并新增「状态到权限」映射表，将先前的中间状态合并为单一的 Removal 状态。

Documentation:

• 记录新的强制移除流程，包括降级、决策和申诉时间线，并阐明其与维护者角色及休眠状态之间的关系。
• 在项目更新日志中记录重构后的移除机制以及访问控制的简化。

Original summary in English

Summary by Sourcery

Refactor maintainer exit and removal governance by separating dormancy/exit from forced removal and aligning access-control semantics.

Enhancements:

• Split maintainer governance into separate exit/dormancy and forced-removal sections, introducing a unified, documented removal-for-cause flow with explicit downgrade, decision, and appeal stages.
• Simplify the access-control state/permission matrix and add a status-to-permission mapping table that consolidates prior intermediate states into a single Removal status.

Documentation:

• Document the new forced-removal process, including downgrade, decision, and appeal timelines, and clarify how it interacts with maintainer roles and dormancy.
• Record the refactored removal mechanism and access-control simplification in the project changelog.

Original summary in English

Summary by Sourcery

重构维护者退出和移除治理机制，通过将休眠/退出与强制移除分离，并统一访问控制语义。

Enhancements:

• 将维护者治理拆分为独立的退出/休眠和强制移除两个部分，引入统一且有文档记录的「因故移除」流程，明确定义降级、决策和申诉阶段。
• 简化访问控制的状态/权限矩阵，并新增「状态到权限」映射表，将先前的中间状态合并为单一的 Removal 状态。

Documentation:

• 记录新的强制移除流程，包括降级、决策和申诉时间线，并阐明其与维护者角色及休眠状态之间的关系。
• 在项目更新日志中记录重构后的移除机制以及访问控制的简化。

Original summary in English

Summary by Sourcery

Refactor maintainer exit and removal governance by separating dormancy/exit from forced removal and aligning access-control semantics.

Enhancements:

• Split maintainer governance into separate exit/dormancy and forced-removal sections, introducing a unified, documented removal-for-cause flow with explicit downgrade, decision, and appeal stages.
• Simplify the access-control state/permission matrix and add a status-to-permission mapping table that consolidates prior intermediate states into a single Removal status.

Documentation:

• Document the new forced-removal process, including downgrade, decision, and appeal timelines, and clarify how it interacts with maintainer roles and dormancy.
• Record the refactored removal mechanism and access-control simplification in the project changelog.

Original summary in English

Summary by Sourcery

重构维护者退出和移除治理机制，通过将休眠/退出与强制移除分离，并统一访问控制语义。

Enhancements:

• 将维护者治理拆分为独立的退出/休眠和强制移除两个部分，引入统一且有文档记录的「因故移除」流程，明确定义降级、决策和申诉阶段。
• 简化访问控制的状态/权限矩阵，并新增「状态到权限」映射表，将先前的中间状态合并为单一的 Removal 状态。

Documentation:

• 记录新的强制移除流程，包括降级、决策和申诉时间线，并阐明其与维护者角色及休眠状态之间的关系。
• 在项目更新日志中记录重构后的移除机制以及访问控制的简化。

Original summary in English

Summary by Sourcery

Refactor maintainer exit and removal governance by separating dormancy/exit from forced removal and aligning access-control semantics.

Enhancements:

• Split maintainer governance into separate exit/dormancy and forced-removal sections, introducing a unified, documented removal-for-cause flow with explicit downgrade, decision, and appeal stages.
• Simplify the access-control state/permission matrix and add a status-to-permission mapping table that consolidates prior intermediate states into a single Removal status.

Documentation:

• Document the new forced-removal process, including downgrade, decision, and appeal timelines, and clarify how it interacts with maintainer roles and dormancy.
• Record the refactored removal mechanism and access-control simplification in the project changelog.

Original summary in English

Summary by Sourcery

重构维护者退出和移除治理机制，通过将休眠/退出与强制移除分离，并统一访问控制语义。

Enhancements:

• 将维护者治理拆分为独立的退出/休眠和强制移除两个部分，引入统一且有文档记录的「因故移除」流程，明确定义降级、决策和申诉阶段。
• 简化访问控制的状态/权限矩阵，并新增「状态到权限」映射表，将先前的中间状态合并为单一的 Removal 状态。

Documentation:

• 记录新的强制移除流程，包括降级、决策和申诉时间线，并阐明其与维护者角色及休眠状态之间的关系。
• 在项目更新日志中记录重构后的移除机制以及访问控制的简化。

Original summary in English

Summary by Sourcery

Refactor maintainer exit and removal governance by separating dormancy/exit from forced removal and aligning access-control semantics.

Enhancements:

• Split maintainer governance into separate exit/dormancy and forced-removal sections, introducing a unified, documented removal-for-cause flow with explicit downgrade, decision, and appeal stages.
• Simplify the access-control state/permission matrix and add a status-to-permission mapping table that consolidates prior intermediate states into a single Removal status.

Documentation:

• Document the new forced-removal process, including downgrade, decision, and appeal timelines, and clarify how it interacts with maintainer roles and dormancy.
• Record the refactored removal mechanism and access-control simplification in the project changelog.

Original summary in English

Summary by Sourcery

重构维护者退出和移除治理机制，通过将休眠/退出与强制移除分离，并统一访问控制语义。

Enhancements:

• 将维护者治理拆分为独立的退出/休眠和强制移除两个部分，引入统一且有文档记录的「因故移除」流程，明确定义降级、决策和申诉阶段。
• 简化访问控制的状态/权限矩阵，并新增「状态到权限」映射表，将先前的中间状态合并为单一的 Removal 状态。

Documentation:

• 记录新的强制移除流程，包括降级、决策和申诉时间线，并阐明其与维护者角色及休眠状态之间的关系。
• 在项目更新日志中记录重构后的移除机制以及访问控制的简化。

Original summary in English

Summary by Sourcery

Refactor maintainer exit and removal governance by separating dormancy/exit from forced removal and aligning access-control semantics.

Enhancements:

• Split maintainer governance into separate exit/dormancy and forced-removal sections, introducing a unified, documented removal-for-cause flow with explicit downgrade, decision, and appeal stages.
• Simplify the access-control state/permission matrix and add a status-to-permission mapping table that consolidates prior intermediate states into a single Removal status.

Documentation:

• Document the new forced-removal process, including downgrade, decision, and appeal timelines, and clarify how it interacts with maintainer roles and dormancy.
• Record the refactored removal mechanism and access-control simplification in the project changelog.

Original summary in English

Summary by Sourcery

重构维护者退出和移除治理机制，通过将休眠/退出与强制移除分离，并统一访问控制语义。

Enhancements:

• 将维护者治理拆分为独立的退出/休眠和强制移除两个部分，引入统一且有文档记录的「因故移除」流程，明确定义降级、决策和申诉阶段。
• 简化访问控制的状态/权限矩阵，并新增「状态到权限」映射表，将先前的中间状态合并为单一的 Removal 状态。

Documentation:

• 记录新的强制移除流程，包括降级、决策和申诉时间线，并阐明其与维护者角色及休眠状态之间的关系。
• 在项目更新日志中记录重构后的移除机制以及访问控制的简化。

Original summary in English

Summary by Sourcery

Refactor maintainer exit and removal governance by separating dormancy/exit from forced removal and aligning access-control semantics.

Enhancements:

• Split maintainer governance into separate exit/dormancy and forced-removal sections, introducing a unified, documented removal-for-cause flow with explicit downgrade, decision, and appeal stages.
• Simplify the access-control state/permission matrix and add a status-to-permission mapping table that consolidates prior intermediate states into a single Removal status.

Documentation:

• Document the new forced-removal process, including downgrade, decision, and appeal timelines, and clarify how it interacts with maintainer roles and dormancy.
• Record the refactored removal mechanism and access-control simplification in the project changelog.

Original summary in English

Summary by Sourcery

重构维护者退出和移除治理机制，通过将休眠/退出与强制移除分离，并统一访问控制语义。

Enhancements:

• 将维护者治理拆分为独立的退出/休眠和强制移除两个部分，引入统一且有文档记录的「因故移除」流程，明确定义降级、决策和申诉阶段。
• 简化访问控制的状态/权限矩阵，并新增「状态到权限」映射表，将先前的中间状态合并为单一的 Removal 状态。

Documentation:

• 记录新的强制移除流程，包括降级、决策和申诉时间线，并阐明其与维护者角色及休眠状态之间的关系。
• 在项目更新日志中记录重构后的移除机制以及访问控制的简化。

Original summary in English

Summary by Sourcery

Refactor maintainer exit and removal governance by separating dormancy/exit from forced removal and aligning access-control semantics.

Enhancements:

• Split maintainer governance into separate exit/dormancy and forced-removal sections, introducing a unified, documented removal-for-cause flow with explicit downgrade, decision, and appeal stages.
• Simplify the access-control state/permission matrix and add a status-to-permission mapping table that consolidates prior intermediate states into a single Removal status.

Documentation:

• Document the new forced-removal process, including downgrade, decision, and appeal timelines, and clarify how it interacts with maintainer roles and dormancy.
• Record the refactored removal mechanism and access-control simplification in the project changelog.

Original summary in English

Summary by Sourcery

重构维护者退出和移除治理机制，通过将休眠/退出与强制移除分离，并统一访问控制语义。

Enhancements:

• 将维护者治理拆分为独立的退出/休眠和强制移除两个部分，引入统一且有文档记录的「因故移除」流程，明确定义降级、决策和申诉阶段。
• 简化访问控制的状态/权限矩阵，并新增「状态到权限」映射表，将先前的中间状态合并为单一的 Removal 状态。

Documentation:

• 记录新的强制移除流程，包括降级、决策和申诉时间线，并阐明其与维护者角色及休眠状态之间的关系。
• 在项目更新日志中记录重构后的移除机制以及访问控制的简化。

Original summary in English

Summary by Sourcery

Refactor maintainer exit and removal governance by separating dormancy/exit from forced removal and aligning access-control semantics.

Enhancements:

• Split maintainer governance into separate exit/dormancy and forced-removal sections, introducing a unified, documented removal-for-cause flow with explicit downgrade, decision, and appeal stages.
• Simplify the access-control state/permission matrix and add a status-to-permission mapping table that consolidates prior intermediate states into a single Removal status.

Documentation:

• Document the new forced-removal process, including downgrade, decision, and appeal timelines, and clarify how it interacts with maintainer roles and dormancy.
• Record the refactored removal mechanism and access-control simplification in the project changelog.

Original summary in English

Summary by Sourcery

重构维护者退出和移除治理机制，通过将休眠/退出与强制移除分离，并统一访问控制语义。

Enhancements:

• 将维护者治理拆分为独立的退出/休眠和强制移除两个部分，引入统一且有文档记录的「因故移除」流程，明确定义降级、决策和申诉阶段。
• 简化访问控制的状态/权限矩阵，并新增「状态到权限」映射表，将先前的中间状态合并为单一的 Removal 状态。

Documentation:

• 记录新的强制移除流程，包括降级、决策和申诉时间线，并阐明其与维护者角色及休眠状态之间的关系。
• 在项目更新日志中记录重构后的移除机制以及访问控制的简化。

Original summary in English

Summary by Sourcery

Refactor maintainer exit and removal governance by separating dormancy/exit from forced removal and aligning access-control semantics.

Enhancements:

• Split maintainer governance into separate exit/dormancy and forced-removal sections, introducing a unified, documented removal-for-cause flow with explicit downgrade, decision, and appeal stages.
• Simplify the access-control state/permission matrix and add a status-to-permission mapping table that consolidates prior intermediate states into a single Removal status.

Documentation:

• Document the new forced-removal process, including downgrade, decision, and appeal timelines, and clarify how it interacts with maintainer roles and dormancy.
• Record the refactored removal mechanism and access-control simplification in the project changelog.

Original summary in English

Summary by Sourcery

重构维护者退出和移除治理机制，通过将休眠/退出与强制移除分离，并统一访问控制语义。

Enhancements:

• 将维护者治理拆分为独立的退出/休眠和强制移除两个部分，引入统一且有文档记录的「因故移除」流程，明确定义降级、决策和申诉阶段。
• 简化访问控制的状态/权限矩阵，并新增「状态到权限」映射表，将先前的中间状态合并为单一的 Removal 状态。

Documentation:

• 记录新的强制移除流程，包括降级、决策和申诉时间线，并阐明其与维护者角色及休眠状态之间的关系。
• 在项目更新日志中记录重构后的移除机制以及访问控制的简化。

Original summary in English

Summary by Sourcery

Refactor maintainer exit and removal governance by separating dormancy/exit from forced removal and aligning access-control semantics.

Enhancements:

• Split maintainer governance into separate exit/dormancy and forced-removal sections, introducing a unified, documented removal-for-cause flow with explicit downgrade, decision, and appeal stages.
• Simplify the access-control state/permission matrix and add a status-to-permission mapping table that consolidates prior intermediate states into a single Removal status.

Documentation:

• Document the new forced-removal process, including downgrade, decision, and appeal timelines, and clarify how it interacts with maintainer roles and dormancy.
• Record the refactored removal mechanism and access-control simplification in the project changelog.

Original summary in English

Summary by Sourcery

重构维护者退出和移除治理机制，通过将休眠/退出与强制移除分离，并统一访问控制语义。

Enhancements:

• 将维护者治理拆分为独立的退出/休眠和强制移除两个部分，引入统一且有文档记录的「因故移除」流程，明确定义降级、决策和申诉阶段。
• 简化访问控制的状态/权限矩阵，并新增「状态到权限」映射表，将先前的中间状态合并为单一的 Removal 状态。

Documentation:

• 记录新的强制移除流程，包括降级、决策和申诉时间线，并阐明其与维护者角色及休眠状态之间的关系。
• 在项目更新日志中记录重构后的移除机制以及访问控制的简化。

Original summary in English

Summary by Sourcery

Refactor maintainer exit and removal governance by separating dormancy/exit from forced removal and aligning access-control semantics.

Enhancements:

• Split maintainer governance into separate exit/dormancy and forced-removal sections, introducing a unified, documented removal-for-cause flow with explicit downgrade, decision, and appeal stages.
• Simplify the access-control state/permission matrix and add a status-to-permission mapping table that consolidates prior intermediate states into a single Removal status.

Documentation:

• Document the new forced-removal process, including downgrade, decision, and appeal timelines, and clarify how it interacts with maintainer roles and dormancy.
• Record the refactored removal mechanism and access-control simplification in the project changelog.

Original summary in English

Summary by Sourcery

重构维护者退出和移除治理机制，通过将休眠/退出与强制移除分离，并统一访问控制语义。

Enhancements:

• 将维护者治理拆分为独立的退出/休眠和强制移除两个部分，引入统一且有文档记录的「因故移除」流程，明确定义降级、决策和申诉阶段。
• 简化访问控制的状态/权限矩阵，并新增「状态到权限」映射表，将先前的中间状态合并为单一的 Removal 状态。

Documentation:

• 记录新的强制移除流程，包括降级、决策和申诉时间线，并阐明其与维护者角色及休眠状态之间的关系。
• 在项目更新日志中记录重构后的移除机制以及访问控制的简化。

Original summary in English

Summary by Sourcery

Refactor maintainer exit and removal governance by separating dormancy/exit from forced removal and aligning access-control semantics.

Enhancements:

• Split maintainer governance into separate exit/dormancy and forced-removal sections, introducing a unified, documented removal-for-cause flow with explicit downgrade, decision, and appeal stages.
• Simplify the access-control state/permission matrix and add a status-to-permission mapping table that consolidates prior intermediate states into a single Removal status.

Documentation:

• Document the new forced-removal process, including downgrade, decision, and appeal timelines, and clarify how it interacts with maintainer roles and dormancy.
• Record the refactored removal mechanism and access-control simplification in the project changelog.

Original summary in English

Summary by Sourcery

重构维护者退出和移除治理机制，通过将休眠/退出与强制移除分离，并统一访问控制语义。

Enhancements:

• 将维护者治理拆分为独立的退出/休眠和强制移除两个部分，引入统一且有文档记录的「因故移除」流程，明确定义降级、决策和申诉阶段。
• 简化访问控制的状态/权限矩阵，并新增「状态到权限」映射表，将先前的中间状态合并为单一的 Removal 状态。

Documentation:

• 记录新的强制移除流程，包括降级、决策和申诉时间线，并阐明其与维护者角色及休眠状态之间的关系。
• 在项目更新日志中记录重构后的移除机制以及访问控制的简化。

Original summary in English

Summary by Sourcery

Refactor maintainer exit and removal governance by separating dormancy/exit from forced removal and aligning access-control semantics.

Enhancements:

• Split maintainer governance into separate exit/dormancy and forced-removal sections, introducing a unified, documented removal-for-cause flow with explicit downgrade, decision, and appeal stages.
• Simplify the access-control state/permission matrix and add a status-to-permission mapping table that consolidates prior intermediate states into a single Removal status.

Documentation:

• Document the new forced-removal process, including downgrade, decision, and appeal timelines, and clarify how it interacts with maintainer roles and dormancy.
• Record the refactored removal mechanism and access-control simplification in the project changelog.

Original summary in English

Summary by Sourcery

重构维护者退出和移除治理机制，通过将休眠/退出与强制移除分离，并统一访问控制语义。

Enhancements:

• 将维护者治理拆分为独立的退出/休眠和强制移除两个部分，引入统一且有文档记录的「因故移除」流程，明确定义降级、决策和申诉阶段。
• 简化访问控制的状态/权限矩阵，并新增「状态到权限」映射表，将先前的中间状态合并为单一的 Removal 状态。

Documentation:

• 记录新的强制移除流程，包括降级、决策和申诉时间线，并阐明其与维护者角色及休眠状态之间的关系。
• 在项目更新日志中记录重构后的移除机制以及访问控制的简化。

Original summary in English

Summary by Sourcery

Refactor maintainer exit and removal governance by separating dormancy/exit from forced removal and aligning access-control semantics.

Enhancements:

• Split maintainer governance into separate exit/dormancy and forced-removal sections, introducing a unified, documented removal-for-cause flow with explicit downgrade, decision, and appeal stages.
• Simplify the access-control state/permission matrix and add a status-to-permission mapping table that consolidates prior intermediate states into a single Removal status.

Documentation:

• Document the new forced-removal process, including downgrade, decision, and appeal timelines, and clarify how it interacts with maintainer roles and dormancy.
• Record the refactored removal mechanism and access-control simplification in the project changelog.

Original summary in English

Summary by Sourcery

重构维护者退出和移除治理机制，通过将休眠/退出与强制移除分离，并统一访问控制语义。

Enhancements:

• 将维护者治理拆分为独立的退出/休眠和强制移除两个部分，引入统一且有文档记录的「因故移除」流程，明确定义降级、决策和申诉阶段。
• 简化访问控制的状态/权限矩阵，并新增「状态到权限」映射表，将先前的中间状态合并为单一的 Removal 状态。

Documentation:

• 记录新的强制移除流程，包括降级、决策和申诉时间线，并阐明其与维护者角色及休眠状态之间的关系。
• 在项目更新日志中记录重构后的移除机制以及访问控制的简化。

Original summary in English

Summary by Sourcery

Refactor maintainer exit and removal governance by separating dormancy/exit from forced removal and aligning access-control semantics.

Enhancements:

• Split maintainer governance into separate exit/dormancy and forced-removal sections, introducing a unified, documented removal-for-cause flow with explicit downgrade, decision, and appeal stages.
• Simplify the access-control state/permission matrix and add a status-to-permission mapping table that consolidates prior intermediate states into a single Removal status.

Documentation:

• Document the new forced-removal process, including downgrade, decision, and appeal timelines, and clarify how it interacts with maintainer roles and dormancy.
• Record the refactored removal mechanism and access-control simplification in the project changelog.

Original summary in English

Summary by Sourcery

重构维护者退出和移除治理机制，通过将休眠/退出与强制移除分离，并统一访问控制语义。

Enhancements:

• 将维护者治理拆分为独立的退出/休眠和强制移除两个部分，引入统一且有文档记录的「因故移除」流程，明确定义降级、决策和申诉阶段。
• 简化访问控制的状态/权限矩阵，并新增「状态到权限」映射表，将先前的中间状态合并为单一的 Removal 状态。

Documentation:

• 记录新的强制移除流程，包括降级、决策和申诉时间线，并阐明其与维护者角色及休眠状态之间的关系。
• 在项目更新日志中记录重构后的移除机制以及访问控制的简化。

Original summary in English

Summary by Sourcery

Refactor maintainer exit and removal governance by separating dormancy/exit from forced removal and aligning access-control semantics.

Enhancements:

• Split maintainer governance into separate exit/dormancy and forced-removal sections, introducing a unified, documented removal-for-cause flow with explicit downgrade, decision, and appeal stages.
• Simplify the access-control state/permission matrix and add a status-to-permission mapping table that consolidates prior intermediate states into a single Removal status.

Documentation:

• Document the new forced-removal process, including downgrade, decision, and appeal timelines, and clarify how it interacts with maintainer roles and dormancy.
• Record the refactored removal mechanism and access-control simplification in the project changelog.

Original summary in English

Summary by Sourcery

重构维护者退出和移除治理机制，通过将休眠/退出与强制移除分离，并统一访问控制语义。

Enhancements:

• 将维护者治理拆分为独立的退出/休眠和强制移除两个部分，引入统一且有文档记录的「因故移除」流程，明确定义降级、决策和申诉阶段。
• 简化访问控制的状态/权限矩阵，并新增「状态到权限」映射表，将先前的中间状态合并为单一的 Removal 状态。

Documentation:

• 记录新的强制移除流程，包括降级、决策和申诉时间线，并阐明其与维护者角色及休眠状态之间的关系。
• 在项目更新日志中记录重构后的移除机制以及访问控制的简化。

Original summary in English

Summary by Sourcery

Refactor maintainer exit and removal governance by separating dormancy/exit from forced removal and aligning access-control semantics.

Enhancements:

• Split maintainer governance into separate exit/dormancy and forced-removal sections, introducing a unified, documented removal-for-cause flow with explicit downgrade, decision, and appeal stages.
• Simplify the access-control state/permission matrix and add a status-to-permission mapping table that consolidates prior intermediate states into a single Removal status.

Documentation:

• Document the new forced-removal process, including downgrade, decision, and appeal timelines, and clarify how it interacts with maintainer roles and dormancy.
• Record the refactored removal mechanism and access-control simplification in the project changelog.

Original summary in English

Summary by Sourcery

重构维护者退出和移除治理机制，通过将休眠/退出与强制移除分离，并统一访问控制语义。

Enhancements:

• 将维护者治理拆分为独立的退出/休眠和强制移除两个部分，引入统一且有文档记录的「因故移除」流程，明确定义降级、决策和申诉阶段。
• 简化访问控制的状态/权限矩阵，并新增「状态到权限」映射表，将先前的中间状态合并为单一的 Removal 状态。

Documentation:

• 记录新的强制移除流程，包括降级、决策和申诉时间线，并阐明其与维护者角色及休眠状态之间的关系。
• 在项目更新日志中记录重构后的移除机制以及访问控制的简化。

Original summary in English

Summary by Sourcery

Refactor maintainer exit and removal governance by separating dormancy/exit from forced removal and aligning access-control semantics.

Enhancements:

• Split maintainer governance into separate exit/dormancy and forced-removal sections, introducing a unified, documented removal-for-cause flow with explicit downgrade, decision, and appeal stages.
• Simplify the access-control state/permission matrix and add a status-to-permission mapping table that consolidates prior intermediate states into a single Removal status.

Documentation:

• Document the new forced-removal process, including downgrade, decision, and appeal timelines, and clarify how it interacts with maintainer roles and dormancy.
• Record the refactored removal mechanism and access-control simplification in the project changelog.

Original summary in English

Summary by Sourcery

重构维护者退出和移除治理机制，通过将休眠/退出与强制移除分离，并统一访问控制语义。

Enhancements:

• 将维护者治理拆分为独立的退出/休眠和强制移除两个部分，引入统一且有文档记录的「因故移除」流程，明确定义降级、决策和申诉阶段。
• 简化访问控制的状态/权限矩阵，并新增「状态到权限」映射表，将先前的中间状态合并为单一的 Removal 状态。

Documentation:

• 记录新的强制移除流程，包括降级、决策和申诉时间线，并阐明其与维护者角色及休眠状态之间的关系。
• 在项目更新日志中记录重构后的移除机制以及访问控制的简化。

Original summary in English

Summary by Sourcery

Refactor maintainer exit and removal governance by separating dormancy/exit from forced removal and aligning access-control semantics.

Enhancements:

• Split maintainer governance into separate exit/dormancy and forced-removal sections, introducing a unified, documented removal-for-cause flow with explicit downgrade, decision, and appeal stages.
• Simplify the access-control state/permission matrix and add a status-to-permission mapping table that consolidates prior intermediate states into a single Removal status.

Documentation:

• Document the new forced-removal process, including downgrade, decision, and appeal timelines, and clarify how it interacts with maintainer roles and dormancy.
• Record the refactored removal mechanism and access-control simplification in the project changelog.

Original summary in English

Summary by Sourcery

重构维护者退出和移除治理机制，通过将休眠/退出与强制移除分离，并统一访问控制语义。

Enhancements:

• 将维护者治理拆分为独立的退出/休眠和强制移除两个部分，引入统一且有文档记录的「因故移除」流程，明确定义降级、决策和申诉阶段。
• 简化访问控制的状态/权限矩阵，并新增「状态到权限」映射表，将先前的中间状态合并为单一的 Removal 状态。

Documentation:

• 记录新的强制移除流程，包括降级、决策和申诉时间线，并阐明其与维护者角色及休眠状态之间的关系。
• 在项目更新日志中记录重构后的移除机制以及访问控制的简化。

Original summary in English

Summary by Sourcery

Refactor maintainer exit and removal governance by separating dormancy/exit from forced removal and aligning access-control semantics.

Enhancements:

• Split maintainer governance into separate exit/dormancy and forced-removal sections, introducing a unified, documented removal-for-cause flow with explicit downgrade, decision, and appeal stages.
• Simplify the access-control state/permission matrix and add a status-to-permission mapping table that consolidates prior intermediate states into a single Removal status.

Documentation:

• Document the new forced-removal process, including downgrade, decision, and appeal timelines, and clarify how it interacts with maintainer roles and dormancy.
• Record the refactored removal mechanism and access-control simplification in the project changelog.

Original summary in English

Summary by Sourcery

重构维护者退出和移除治理机制，通过将休眠/退出与强制移除分离，并统一访问控制语义。

Enhancements:

• 将维护者治理拆分为独立的退出/休眠和强制移除两个部分，引入统一且有文档记录的「因故移除」流程，明确定义降级、决策和申诉阶段。
• 简化访问控制的状态/权限矩阵，并新增「状态到权限」映射表，将先前的中间状态合并为单一的 Removal 状态。

Documentation:

• 记录新的强制移除流程，包括降级、决策和申诉时间线，并阐明其与维护者角色及休眠状态之间的关系。
• 在项目更新日志中记录重构后的移除机制以及访问控制的简化。

Original summary in English

Summary by Sourcery

Refactor maintainer exit and removal governance by separating dormancy/exit from forced removal and aligning access-control semantics.

Enhancements:

• Split maintainer governance into separate exit/dormancy and forced-removal sections, introducing a unified, documented removal-for-cause flow with explicit downgrade, decision, and appeal stages.
• Simplify the access-control state/permission matrix and add a status-to-permission mapping table that consolidates prior intermediate states into a single Removal status.

Documentation:

• Document the new forced-removal process, including downgrade, decision, and appeal timelines, and clarify how it interacts with maintainer roles and dormancy.
• Record the refactored removal mechanism and access-control simplification in the project changelog.

Original summary in English

Summary by Sourcery

重构维护者退出和移除治理机制，通过将休眠/退出与强制移除分离，并统一访问控制语义。

Enhancements:

• 将维护者治理拆分为独立的退出/休眠和强制移除两个部分，引入统一且有文档记录的「因故移除」流程，明确定义降级、决策和申诉阶段。
• 简化访问控制的状态/权限矩阵，并新增「状态到权限」映射表，将先前的中间状态合并为单一的 Removal 状态。

Documentation:

• 记录新的强制移除流程，包括降级、决策和申诉时间线，并阐明其与维护者角色及休眠状态之间的关系。
• 在项目更新日志中记录重构后的移除机制以及访问控制的简化。

Original summary in English

Summary by Sourcery

Refactor maintainer exit and removal governance by separating dormancy/exit from forced removal and aligning access-control semantics.

Enhancements:

• Split maintainer governance into separate exit/dormancy and forced-removal sections, introducing a unified, documented removal-for-cause flow with explicit downgrade, decision, and appeal stages.
• Simplify the access-control state/permission matrix and add a status-to-permission mapping table that consolidates prior intermediate states into a single Removal status.

Documentation:

• Document the new forced-removal process, including downgrade, decision, and appeal timelines, and clarify how it interacts with maintainer roles and dormancy.
• Record the refactored removal mechanism and access-control simplification in the project changelog.

Original summary in English

由 Sourcery 提供的总结

通过将原先单一的强制移除流程拆分为独立的“立即移除”和“裁决式移除”路径，细化维护者治理机制，并文档化新的分级流程和状态。

增强内容：

• 通过将自愿辞任、自动休眠和强制移除拆分成独立的治理章节，澄清维护者退出与休眠部分。
• 引入两级强制移除体系，将针对不可挽回或违法事件的“立即移除”和针对其他严重不当行为的“裁决式移除”区分开来，并包含详细的状态转换、时间线和保障措施。

文档：

• 更新治理文档，描述新的“立即移除”和“裁决式移除”维护者处理流程，包括申诉与观察机制。
• 在项目变更日志中记录重构后的强制移除政策及其分级工作流。
• 新增 CLAUDE.md 指南，说明仓库背景、文档规范以及面向 AI 助手的贡献流程。

Original summary in English

Summary by Sourcery

重构维护者退出和移除治理机制，通过将休眠/退出与强制移除分离，并统一访问控制语义。

Enhancements:

• 将维护者治理拆分为独立的退出/休眠和强制移除两个部分，引入统一且有文档记录的「因故移除」流程，明确定义降级、决策和申诉阶段。
• 简化访问控制的状态/权限矩阵，并新增「状态到权限」映射表，将先前的中间状态合并为单一的 Removal 状态。

Documentation:

• 记录新的强制移除流程，包括降级、决策和申诉时间线，并阐明其与维护者角色及休眠状态之间的关系。
• 在项目更新日志中记录重构后的移除机制以及访问控制的简化。

Original summary in English

Summary by Sourcery

Refactor maintainer exit and removal governance by separating dormancy/exit from forced removal and aligning access-control semantics.

Enhancements:

• Split maintainer governance into separate exit/dormancy and forced-removal sections, introducing a unified, documented removal-for-cause flow with explicit downgrade, decision, and appeal stages.
• Simplify the access-control state/permission matrix and add a status-to-permission mapping table that consolidates prior intermediate states into a single Removal status.

Documentation:

• Document the new forced-removal process, including downgrade, decision, and appeal timelines, and clarify how it interacts with maintainer roles and dormancy.
• Record the refactored removal mechanism and access-control simplification in the project changelog.

Original summary in English

Summary by Sourcery

重构维护者退出和移除治理机制，通过将休眠/退出与强制移除分离，并统一访问控制语义。

Enhancements:

• 将维护者治理拆分为独立的退出/休眠和强制移除两个部分，引入统一且有文档记录的「因故移除」流程，明确定义降级、决策和申诉阶段。
• 简化访问控制的状态/权限矩阵，并新增「状态到权限」映射表，将先前的中间状态合并为单一的 Removal 状态。

Documentation:

• 记录新的强制移除流程，包括降级、决策和申诉时间线，并阐明其与维护者角色及休眠状态之间的关系。
• 在项目更新日志中记录重构后的移除机制以及访问控制的简化。

Original summary in English

Summary by Sourcery

Refactor maintainer exit and removal governance by separating dormancy/exit from forced removal and aligning access-control semantics.

Enhancements:

• Split maintainer governance into separate exit/dormancy and forced-removal sections, introducing a unified, documented removal-for-cause flow with explicit downgrade, decision, and appeal stages.
• Simplify the access-control state/permission matrix and add a status-to-permission mapping table that consolidates prior intermediate states into a single Removal status.

Documentation:

• Document the new forced-removal process, including downgrade, decision, and appeal timelines, and clarify how it interacts with maintainer roles and dormancy.
• Record the refactored removal mechanism and access-control simplification in the project changelog.

Original summary in English

Summary by Sourcery

重构维护者退出和移除治理机制，通过将休眠/退出与强制移除分离，并统一访问控制语义。

Enhancements:

• 将维护者治理拆分为独立的退出/休眠和强制移除两个部分，引入统一且有文档记录的「因故移除」流程，明确定义降级、决策和申诉阶段。
• 简化访问控制的状态/权限矩阵，并新增「状态到权限」映射表，将先前的中间状态合并为单一的 Removal 状态。

Documentation:

• 记录新的强制移除流程，包括降级、决策和申诉时间线，并阐明其与维护者角色及休眠状态之间的关系。
• 在项目更新日志中记录重构后的移除机制以及访问控制的简化。

Original summary in English

Summary by Sourcery

Refactor maintainer exit and removal governance by separating dormancy/exit from forced removal and aligning access-control semantics.

Enhancements:

• Split maintainer governance into separate exit/dormancy and forced-removal sections, introducing a unified, documented removal-for-cause flow with explicit downgrade, decision, and appeal stages.
• Simplify the access-control state/permission matrix and add a status-to-permission mapping table that consolidates prior intermediate states into a single Removal status.

Documentation:

• Document the new forced-removal process, including downgrade, decision, and appeal timelines, and clarify how it interacts with maintainer roles and dormancy.
• Record the refactored removal mechanism and access-control simplification in the project changelog.

Original summary in English

Summary by Sourcery

重构维护者退出和移除治理机制，通过将休眠/退出与强制移除分离，并统一访问控制语义。

Enhancements:

• 将维护者治理拆分为独立的退出/休眠和强制移除两个部分，引入统一且有文档记录的「因故移除」流程，明确定义降级、决策和申诉阶段。
• 简化访问控制的状态/权限矩阵，并新增「状态到权限」映射表，将先前的中间状态合并为单一的 Removal 状态。

Documentation:

• 记录新的强制移除流程，包括降级、决策和申诉时间线，并阐明其与维护者角色及休眠状态之间的关系。
• 在项目更新日志中记录重构后的移除机制以及访问控制的简化。

Original summary in English

Summary by Sourcery

Refactor maintainer exit and removal governance by separating dormancy/exit from forced removal and aligning access-control semantics.

Enhancements:

• Split maintainer governance into separate exit/dormancy and forced-removal sections, introducing a unified, documented removal-for-cause flow with explicit downgrade, decision, and appeal stages.
• Simplify the access-control state/permission matrix and add a status-to-permission mapping table that consolidates prior intermediate states into a single Removal status.

Documentation:

• Document the new forced-removal process, including downgrade, decision, and appeal timelines, and clarify how it interacts with maintainer roles and dormancy.
• Record the refactored removal mechanism and access-control simplification in the project changelog.

Original summary in English

Summary by Sourcery

重构维护者退出和移除治理机制，通过将休眠/退出与强制移除分离，并统一访问控制语义。

Enhancements:

• 将维护者治理拆分为独立的退出/休眠和强制移除两个部分，引入统一且有文档记录的「因故移除」流程，明确定义降级、决策和申诉阶段。
• 简化访问控制的状态/权限矩阵，并新增「状态到权限」映射表，将先前的中间状态合并为单一的 Removal 状态。

Documentation:

• 记录新的强制移除流程，包括降级、决策和申诉时间线，并阐明其与维护者角色及休眠状态之间的关系。
• 在项目更新日志中记录重构后的移除机制以及访问控制的简化。

Original summary in English

Summary by Sourcery

Refactor maintainer exit and removal governance by separating dormancy/exit from forced removal and aligning access-control semantics.

Enhancements:

• Split maintainer governance into separate exit/dormancy and forced-removal sections, introducing a unified, documented removal-for-cause flow with explicit downgrade, decision, and appeal stages.
• Simplify the access-control state/permission matrix and add a status-to-permission mapping table that consolidates prior intermediate states into a single Removal status.

Documentation:

• Document the new forced-removal process, including downgrade, decision, and appeal timelines, and clarify how it interacts with maintainer roles and dormancy.
• Record the refactored removal mechanism and access-control simplification in the project changelog.

Original summary in English

Summary by Sourcery

重构维护者退出和移除治理机制，通过将休眠/退出与强制移除分离，并统一访问控制语义。

Enhancements:

• 将维护者治理拆分为独立的退出/休眠和强制移除两个部分，引入统一且有文档记录的「因故移除」流程，明确定义降级、决策和申诉阶段。
• 简化访问控制的状态/权限矩阵，并新增「状态到权限」映射表，将先前的中间状态合并为单一的 Removal 状态。

Documentation:

• 记录新的强制移除流程，包括降级、决策和申诉时间线，并阐明其与维护者角色及休眠状态之间的关系。
• 在项目更新日志中记录重构后的移除机制以及访问控制的简化。

Original summary in English

Summary by Sourcery

Refactor maintainer exit and removal governance by separating dormancy/exit from forced removal and aligning access-control semantics.

Enhancements:

• Split maintainer governance into separate exit/dormancy and forced-removal sections, introducing a unified, documented removal-for-cause flow with explicit downgrade, decision, and appeal stages.
• Simplify the access-control state/permission matrix and add a status-to-permission mapping table that consolidates prior intermediate states into a single Removal status.

Documentation:

• Document the new forced-removal process, including downgrade, decision, and appeal timelines, and clarify how it interacts with maintainer roles and dormancy.
• Record the refactored removal mechanism and access-control simplification in the project changelog.

Original summary in English

Summary by Sourcery

重构维护者退出和移除治理机制，通过将休眠/退出与强制移除分离，并统一访问控制语义。

Enhancements:

• 将维护者治理拆分为独立的退出/休眠和强制移除两个部分，引入统一且有文档记录的「因故移除」流程，明确定义降级、决策和申诉阶段。
• 简化访问控制的状态/权限矩阵，并新增「状态到权限」映射表，将先前的中间状态合并为单一的 Removal 状态。

Documentation:

• 记录新的强制移除流程，包括降级、决策和申诉时间线，并阐明其与维护者角色及休眠状态之间的关系。
• 在项目更新日志中记录重构后的移除机制以及访问控制的简化。

Original summary in English

Summary by Sourcery

Refactor maintainer exit and removal governance by separating dormancy/exit from forced removal and aligning access-control semantics.

Enhancements:

• Split maintainer governance into separate exit/dormancy and forced-removal sections, introducing a unified, documented removal-for-cause flow with explicit downgrade, decision, and appeal stages.
• Simplify the access-control state/permission matrix and add a status-to-permission mapping table that consolidates prior intermediate states into a single Removal status.

Documentation:

• Document the new forced-removal process, including downgrade, decision, and appeal timelines, and clarify how it interacts with maintainer roles and dormancy.
• Record the refactored removal mechanism and access-control simplification in the project changelog.

Original summary in English

Summary by Sourcery

重构维护者退出和移除治理机制，通过将休眠/退出与强制移除分离，并统一访问控制语义。

Enhancements:

• 将维护者治理拆分为独立的退出/休眠和强制移除两个部分，引入统一且有文档记录的「因故移除」流程，明确定义降级、决策和申诉阶段。
• 简化访问控制的状态/权限矩阵，并新增「状态到权限」映射表，将先前的中间状态合并为单一的 Removal 状态。

Documentation:

• 记录新的强制移除流程，包括降级、决策和申诉时间线，并阐明其与维护者角色及休眠状态之间的关系。
• 在项目更新日志中记录重构后的移除机制以及访问控制的简化。

Original summary in English

Summary by Sourcery

Refactor maintainer exit and removal governance by separating dormancy/exit from forced removal and aligning access-control semantics.

Enhancements:

• Split maintainer governance into separate exit/dormancy and forced-removal sections, introducing a unified, documented removal-for-cause flow with explicit downgrade, decision, and appeal stages.
• Simplify the access-control state/permission matrix and add a status-to-permission mapping table that consolidates prior intermediate states into a single Removal status.

Documentation:

• Document the new forced-removal process, including downgrade, decision, and appeal timelines, and clarify how it interacts with maintainer roles and dormancy.
• Record the refactored removal mechanism and access-control simplification in the project changelog.

Original summary in English

Summary by Sourcery

重构维护者退出和移除治理机制，通过将休眠/退出与强制移除分离，并统一访问控制语义。

Enhancements:

• 将维护者治理拆分为独立的退出/休眠和强制移除两个部分，引入统一且有文档记录的「因故移除」流程，明确定义降级、决策和申诉阶段。
• 简化访问控制的状态/权限矩阵，并新增「状态到权限」映射表，将先前的中间状态合并为单一的 Removal 状态。

Documentation:

• 记录新的强制移除流程，包括降级、决策和申诉时间线，并阐明其与维护者角色及休眠状态之间的关系。
• 在项目更新日志中记录重构后的移除机制以及访问控制的简化。

Original summary in English

Summary by Sourcery

Refactor maintainer exit and removal governance by separating dormancy/exit from forced removal and aligning access-control semantics.

Enhancements:

• Split maintainer governance into separate exit/dormancy and forced-removal sections, introducing a unified, documented removal-for-cause flow with explicit downgrade, decision, and appeal stages.
• Simplify the access-control state/permission matrix and add a status-to-permission mapping table that consolidates prior intermediate states into a single Removal status.

Documentation:

• Document the new forced-removal process, including downgrade, decision, and appeal timelines, and clarify how it interacts with maintainer roles and dormancy.
• Record the refactored removal mechanism and access-control simplification in the project changelog.

Original summary in English

Summary by Sourcery

重构维护者退出和移除治理机制，通过将休眠/退出与强制移除分离，并统一访问控制语义。

Enhancements:

• 将维护者治理拆分为独立的退出/休眠和强制移除两个部分，引入统一且有文档记录的「因故移除」流程，明确定义降级、决策和申诉阶段。
• 简化访问控制的状态/权限矩阵，并新增「状态到权限」映射表，将先前的中间状态合并为单一的 Removal 状态。

Documentation:

• 记录新的强制移除流程，包括降级、决策和申诉时间线，并阐明其与维护者角色及休眠状态之间的关系。
• 在项目更新日志中记录重构后的移除机制以及访问控制的简化。

Original summary in English

Summary by Sourcery

Refactor maintainer exit and removal governance by separating dormancy/exit from forced removal and aligning access-control semantics.

Enhancements:

• Split maintainer governance into separate exit/dormancy and forced-removal sections, introducing a unified, documented removal-for-cause flow with explicit downgrade, decision, and appeal stages.
• Simplify the access-control state/permission matrix and add a status-to-permission mapping table that consolidates prior intermediate states into a single Removal status.

Documentation:

• Document the new forced-removal process, including downgrade, decision, and appeal timelines, and clarify how it interacts with maintainer roles and dormancy.
• Record the refactored removal mechanism and access-control simplification in the project changelog.

Original summary in English

Summary by Sourcery

重构维护者退出和移除治理机制，通过将休眠/退出与强制移除分离，并统一访问控制语义。

Enhancements:

• 将维护者治理拆分为独立的退出/休眠和强制移除两个部分，引入统一且有文档记录的「因故移除」流程，明确定义降级、决策和申诉阶段。
• 简化访问控制的状态/权限矩阵，并新增「状态到权限」映射表，将先前的中间状态合并为单一的 Removal 状态。

Documentation:

• 记录新的强制移除流程，包括降级、决策和申诉时间线，并阐明其与维护者角色及休眠状态之间的关系。
• 在项目更新日志中记录重构后的移除机制以及访问控制的简化。

Original summary in English

Summary by Sourcery

Refactor maintainer exit and removal governance by separating dormancy/exit from forced removal and aligning access-control semantics.

Enhancements:

• Split maintainer governance into separate exit/dormancy and forced-removal sections, introducing a unified, documented removal-for-cause flow with explicit downgrade, decision, and appeal stages.
• Simplify the access-control state/permission matrix and add a status-to-permission mapping table that consolidates prior intermediate states into a single Removal status.

Documentation:

• Document the new forced-removal process, including downgrade, decision, and appeal timelines, and clarify how it interacts with maintainer roles and dormancy.
• Record the refactored removal mechanism and access-control simplification in the project changelog.

Original summary in English

Summary by Sourcery

重构维护者退出和移除治理机制，通过将休眠/退出与强制移除分离，并统一访问控制语义。

Enhancements:

• 将维护者治理拆分为独立的退出/休眠和强制移除两个部分，引入统一且有文档记录的「因故移除」流程，明确定义降级、决策和申诉阶段。
• 简化访问控制的状态/权限矩阵，并新增「状态到权限」映射表，将先前的中间状态合并为单一的 Removal 状态。

Documentation:

• 记录新的强制移除流程，包括降级、决策和申诉时间线，并阐明其与维护者角色及休眠状态之间的关系。
• 在项目更新日志中记录重构后的移除机制以及访问控制的简化。

Original summary in English

Summary by Sourcery

Refactor maintainer exit and removal governance by separating dormancy/exit from forced removal and aligning access-control semantics.

Enhancements:

• Split maintainer governance into separate exit/dormancy and forced-removal sections, introducing a unified, documented removal-for-cause flow with explicit downgrade, decision, and appeal stages.
• Simplify the access-control state/permission matrix and add a status-to-permission mapping table that consolidates prior intermediate states into a single Removal status.

Documentation:

• Document the new forced-removal process, including downgrade, decision, and appeal timelines, and clarify how it interacts with maintainer roles and dormancy.
• Record the refactored removal mechanism and access-control simplification in the project changelog.

Original summary in English

Summary by Sourcery

重构维护者退出和移除治理机制，通过将休眠/退出与强制移除分离，并统一访问控制语义。

Enhancements:

• 将维护者治理拆分为独立的退出/休眠和强制移除两个部分，引入统一且有文档记录的「因故移除」流程，明确定义降级、决策和申诉阶段。
• 简化访问控制的状态/权限矩阵，并新增「状态到权限」映射表，将先前的中间状态合并为单一的 Removal 状态。

Documentation:

• 记录新的强制移除流程，包括降级、决策和申诉时间线，并阐明其与维护者角色及休眠状态之间的关系。
• 在项目更新日志中记录重构后的移除机制以及访问控制的简化。

Original summary in English

Summary by Sourcery

Refactor maintainer exit and removal governance by separating dormancy/exit from forced removal and aligning access-control semantics.

Enhancements:

• Split maintainer governance into separate exit/dormancy and forced-removal sections, introducing a unified, documented removal-for-cause flow with explicit downgrade, decision, and appeal stages.
• Simplify the access-control state/permission matrix and add a status-to-permission mapping table that consolidates prior intermediate states into a single Removal status.

Documentation:

• Document the new forced-removal process, including downgrade, decision, and appeal timelines, and clarify how it interacts with maintainer roles and dormancy.
• Record the refactored removal mechanism and access-control simplification in the project changelog.

Original summary in English

Summary by Sourcery

重构维护者退出和移除治理机制，通过将休眠/退出与强制移除分离，并统一访问控制语义。

Enhancements:

• 将维护者治理拆分为独立的退出/休眠和强制移除两个部分，引入统一且有文档记录的「因故移除」流程，明确定义降级、决策和申诉阶段。
• 简化访问控制的状态/权限矩阵，并新增「状态到权限」映射表，将先前的中间状态合并为单一的 Removal 状态。

Documentation:

• 记录新的强制移除流程，包括降级、决策和申诉时间线，并阐明其与维护者角色及休眠状态之间的关系。
• 在项目更新日志中记录重构后的移除机制以及访问控制的简化。

Original summary in English

Summary by Sourcery

Refactor maintainer exit and removal governance by separating dormancy/exit from forced removal and aligning access-control semantics.

Enhancements:

• Split maintainer governance into separate exit/dormancy and forced-removal sections, introducing a unified, documented removal-for-cause flow with explicit downgrade, decision, and appeal stages.
• Simplify the access-control state/permission matrix and add a status-to-permission mapping table that consolidates prior intermediate states into a single Removal status.

Documentation:

• Document the new forced-removal process, including downgrade, decision, and appeal timelines, and clarify how it interacts with maintainer roles and dormancy.
• Record the refactored removal mechanism and access-control simplification in the project changelog.

Original summary in English

Summary by Sourcery

重构维护者退出和移除治理机制，通过将休眠/退出与强制移除分离，并统一访问控制语义。

Enhancements:

• 将维护者治理拆分为独立的退出/休眠和强制移除两个部分，引入统一且有文档记录的「因故移除」流程，明确定义降级、决策和申诉阶段。
• 简化访问控制的状态/权限矩阵，并新增「状态到权限」映射表，将先前的中间状态合并为单一的 Removal 状态。

Documentation:

• 记录新的强制移除流程，包括降级、决策和申诉时间线，并阐明其与维护者角色及休眠状态之间的关系。
• 在项目更新日志中记录重构后的移除机制以及访问控制的简化。

Original summary in English

Summary by Sourcery

Refactor maintainer exit and removal governance by separating dormancy/exit from forced removal and aligning access-control semantics.

Enhancements:

• Split maintainer governance into separate exit/dormancy and forced-removal sections, introducing a unified, documented removal-for-cause flow with explicit downgrade, decision, and appeal stages.
• Simplify the access-control state/permission matrix and add a status-to-permission mapping table that consolidates prior intermediate states into a single Removal status.

Documentation:

• Document the new forced-removal process, including downgrade, decision, and appeal timelines, and clarify how it interacts with maintainer roles and dormancy.
• Record the refactored removal mechanism and access-control simplification in the project changelog.

Original summary in English

Summary by Sourcery

重构维护者退出和移除治理机制，通过将休眠/退出与强制移除分离，并统一访问控制语义。

Enhancements:

• 将维护者治理拆分为独立的退出/休眠和强制移除两个部分，引入统一且有文档记录的「因故移除」流程，明确定义降级、决策和申诉阶段。
• 简化访问控制的状态/权限矩阵，并新增「状态到权限」映射表，将先前的中间状态合并为单一的 Removal 状态。

Documentation:

• 记录新的强制移除流程，包括降级、决策和申诉时间线，并阐明其与维护者角色及休眠状态之间的关系。
• 在项目更新日志中记录重构后的移除机制以及访问控制的简化。

Original summary in English

Summary by Sourcery

Refactor maintainer exit and removal governance by separating dormancy/exit from forced removal and aligning access-control semantics.

Enhancements:

• Split maintainer governance into separate exit/dormancy and forced-removal sections, introducing a unified, documented removal-for-cause flow with explicit downgrade, decision, and appeal stages.
• Simplify the access-control state/permission matrix and add a status-to-permission mapping table that consolidates prior intermediate states into a single Removal status.

Documentation:

• Document the new forced-removal process, including downgrade, decision, and appeal timelines, and clarify how it interacts with maintainer roles and dormancy.
• Record the refactored removal mechanism and access-control simplification in the project changelog.

Original summary in English

Summary by Sourcery

重构维护者退出和移除治理机制，通过将休眠/退出与强制移除分离，并统一访问控制语义。

Enhancements:

• 将维护者治理拆分为独立的退出/休眠和强制移除两个部分，引入统一且有文档记录的「因故移除」流程，明确定义降级、决策和申诉阶段。
• 简化访问控制的状态/权限矩阵，并新增「状态到权限」映射表，将先前的中间状态合并为单一的 Removal 状态。

Documentation:

• 记录新的强制移除流程，包括降级、决策和申诉时间线，并阐明其与维护者角色及休眠状态之间的关系。
• 在项目更新日志中记录重构后的移除机制以及访问控制的简化。

Original summary in English

Summary by Sourcery

Refactor maintainer exit and removal governance by separating dormancy/exit from forced removal and aligning access-control semantics.

Enhancements:

• Split maintainer governance into separate exit/dormancy and forced-removal sections, introducing a unified, documented removal-for-cause flow with explicit downgrade, decision, and appeal stages.
• Simplify the access-control state/permission matrix and add a status-to-permission mapping table that consolidates prior intermediate states into a single Removal status.

Documentation:

• Document the new forced-removal process, including downgrade, decision, and appeal timelines, and clarify how it interacts with maintainer roles and dormancy.
• Record the refactored removal mechanism and access-control simplification in the project changelog.

Original summary in English

Summary by Sourcery

重构维护者退出和移除治理机制，通过将休眠/退出与强制移除分离，并统一访问控制语义。

Enhancements:

• 将维护者治理拆分为独立的退出/休眠和强制移除两个部分，引入统一且有文档记录的「因故移除」流程，明确定义降级、决策和申诉阶段。
• 简化访问控制的状态/权限矩阵，并新增「状态到权限」映射表，将先前的中间状态合并为单一的 Removal 状态。

Documentation:

• 记录新的强制移除流程，包括降级、决策和申诉时间线，并阐明其与维护者角色及休眠状态之间的关系。
• 在项目更新日志中记录重构后的移除机制以及访问控制的简化。

Original summary in English

Summary by Sourcery

Refactor maintainer exit and removal governance by separating dormancy/exit from forced removal and aligning access-control semantics.

Enhancements:

• Split maintainer governance into separate exit/dormancy and forced-removal sections, introducing a unified, documented removal-for-cause flow with explicit downgrade, decision, and appeal stages.
• Simplify the access-control state/permission matrix and add a status-to-permission mapping table that consolidates prior intermediate states into a single Removal status.

Documentation:

• Document the new forced-removal process, including downgrade, decision, and appeal timelines, and clarify how it interacts with maintainer roles and dormancy.
• Record the refactored removal mechanism and access-control simplification in the project changelog.

Original summary in English

Summary by Sourcery

重构维护者退出和移除治理机制，通过将休眠/退出与强制移除分离，并统一访问控制语义。

Enhancements:

• 将维护者治理拆分为独立的退出/休眠和强制移除两个部分，引入统一且有文档记录的「因故移除」流程，明确定义降级、决策和申诉阶段。
• 简化访问控制的状态/权限矩阵，并新增「状态到权限」映射表，将先前的中间状态合并为单一的 Removal 状态。

Documentation:

• 记录新的强制移除流程，包括降级、决策和申诉时间线，并阐明其与维护者角色及休眠状态之间的关系。
• 在项目更新日志中记录重构后的移除机制以及访问控制的简化。

Original summary in English

Summary by Sourcery

Refactor maintainer exit and removal governance by separating dormancy/exit from forced removal and aligning access-control semantics.

Enhancements:

• Split maintainer governance into separate exit/dormancy and forced-removal sections, introducing a unified, documented removal-for-cause flow with explicit downgrade, decision, and appeal stages.
• Simplify the access-control state/permission matrix and add a status-to-permission mapping table that consolidates prior intermediate states into a single Removal status.

Documentation:

• Document the new forced-removal process, including downgrade, decision, and appeal timelines, and clarify how it interacts with maintainer roles and dormancy.
• Record the refactored removal mechanism and access-control simplification in the project changelog.

Original summary in English

Summary by Sourcery

重构维护者退出和移除治理机制，通过将休眠/退出与强制移除分离，并统一访问控制语义。

Enhancements:

• 将维护者治理拆分为独立的退出/休眠和强制移除两个部分，引入统一且有文档记录的「因故移除」流程，明确定义降级、决策和申诉阶段。
• 简化访问控制的状态/权限矩阵，并新增「状态到权限」映射表，将先前的中间状态合并为单一的 Removal 状态。

Documentation:

• 记录新的强制移除流程，包括降级、决策和申诉时间线，并阐明其与维护者角色及休眠状态之间的关系。
• 在项目更新日志中记录重构后的移除机制以及访问控制的简化。

Original summary in English

Summary by Sourcery

Refactor maintainer exit and removal governance by separating dormancy/exit from forced removal and aligning access-control semantics.

Enhancements:

• Split maintainer governance into separate exit/dormancy and forced-removal sections, introducing a unified, documented removal-for-cause flow with explicit downgrade, decision, and appeal stages.
• Simplify the access-control state/permission matrix and add a status-to-permission mapping table that consolidates prior intermediate states into a single Removal status.

Documentation:

• Document the new forced-removal process, including downgrade, decision, and appeal timelines, and clarify how it interacts with maintainer roles and dormancy.
• Record the refactored removal mechanism and access-control simplification in the project changelog.

Original summary in English

Summary by Sourcery

重构维护者退出和移除治理机制，通过将休眠/退出与强制移除分离，并统一访问控制语义。

Enhancements:

• 将维护者治理拆分为独立的退出/休眠和强制移除两个部分，引入统一且有文档记录的「因故移除」流程，明确定义降级、决策和申诉阶段。
• 简化访问控制的状态/权限矩阵，并新增「状态到权限」映射表，将先前的中间状态合并为单一的 Removal 状态。

Documentation:

• 记录新的强制移除流程，包括降级、决策和申诉时间线，并阐明其与维护者角色及休眠状态之间的关系。
• 在项目更新日志中记录重构后的移除机制以及访问控制的简化。

Original summary in English

Summary by Sourcery

Refactor maintainer exit and removal governance by separating dormancy/exit from forced removal and aligning access-control semantics.

Enhancements:

• Split maintainer governance into separate exit/dormancy and forced-removal sections, introducing a unified, documented removal-for-cause flow with explicit downgrade, decision, and appeal stages.
• Simplify the access-control state/permission matrix and add a status-to-permission mapping table that consolidates prior intermediate states into a single Removal status.

Documentation:

• Document the new forced-removal process, including downgrade, decision, and appeal timelines, and clarify how it interacts with maintainer roles and dormancy.
• Record the refactored removal mechanism and access-control simplification in the project changelog.

Original summary in English

Summary by Sourcery

重构维护者退出和移除治理机制，通过将休眠/退出与强制移除分离，并统一访问控制语义。

Enhancements:

• 将维护者治理拆分为独立的退出/休眠和强制移除两个部分，引入统一且有文档记录的「因故移除」流程，明确定义降级、决策和申诉阶段。
• 简化访问控制的状态/权限矩阵，并新增「状态到权限」映射表，将先前的中间状态合并为单一的 Removal 状态。

Documentation:

• 记录新的强制移除流程，包括降级、决策和申诉时间线，并阐明其与维护者角色及休眠状态之间的关系。
• 在项目更新日志中记录重构后的移除机制以及访问控制的简化。

Original summary in English

Summary by Sourcery

Refactor maintainer exit and removal governance by separating dormancy/exit from forced removal and aligning access-control semantics.

Enhancements:

• Split maintainer governance into separate exit/dormancy and forced-removal sections, introducing a unified, documented removal-for-cause flow with explicit downgrade, decision, and appeal stages.
• Simplify the access-control state/permission matrix and add a status-to-permission mapping table that consolidates prior intermediate states into a single Removal status.

Documentation:

• Document the new forced-removal process, including downgrade, decision, and appeal timelines, and clarify how it interacts with maintainer roles and dormancy.
• Record the refactored removal mechanism and access-control simplification in the project changelog.

Original summary in English

Summary by Sourcery

重构维护者退出和移除治理机制，通过将休眠/退出与强制移除分离，并统一访问控制语义。

Enhancements:

• 将维护者治理拆分为独立的退出/休眠和强制移除两个部分，引入统一且有文档记录的「因故移除」流程，明确定义降级、决策和申诉阶段。
• 简化访问控制的状态/权限矩阵，并新增「状态到权限」映射表，将先前的中间状态合并为单一的 Removal 状态。

Documentation:

• 记录新的强制移除流程，包括降级、决策和申诉时间线，并阐明其与维护者角色及休眠状态之间的关系。
• 在项目更新日志中记录重构后的移除机制以及访问控制的简化。

Original summary in English

Summary by Sourcery

Refactor maintainer exit and removal governance by separating dormancy/exit from forced removal and aligning access-control semantics.

Enhancements:

• Split maintainer governance into separate exit/dormancy and forced-removal sections, introducing a unified, documented removal-for-cause flow with explicit downgrade, decision, and appeal stages.
• Simplify the access-control state/permission matrix and add a status-to-permission mapping table that consolidates prior intermediate states into a single Removal status.

Documentation:

• Document the new forced-removal process, including downgrade, decision, and appeal timelines, and clarify how it interacts with maintainer roles and dormancy.
• Record the refactored removal mechanism and access-control simplification in the project changelog.

Original summary in English

Summary by Sourcery

重构维护者退出和移除治理机制，通过将休眠/退出与强制移除分离，并统一访问控制语义。

Enhancements:

• 将维护者治理拆分为独立的退出/休眠和强制移除两个部分，引入统一且有文档记录的「因故移除」流程，明确定义降级、决策和申诉阶段。
• 简化访问控制的状态/权限矩阵，并新增「状态到权限」映射表，将先前的中间状态合并为单一的 Removal 状态。

Documentation:

• 记录新的强制移除流程，包括降级、决策和申诉时间线，并阐明其与维护者角色及休眠状态之间的关系。
• 在项目更新日志中记录重构后的移除机制以及访问控制的简化。

Original summary in English

Summary by Sourcery

Refactor maintainer exit and removal governance by separating dormancy/exit from forced removal and aligning access-control semantics.

Enhancements:

• Split maintainer governance into separate exit/dormancy and forced-removal sections, introducing a unified, documented removal-for-cause flow with explicit downgrade, decision, and appeal stages.
• Simplify the access-control state/permission matrix and add a status-to-permission mapping table that consolidates prior intermediate states into a single Removal status.

Documentation:

• Document the new forced-removal process, including downgrade, decision, and appeal timelines, and clarify how it interacts with maintainer roles and dormancy.
• Record the refactored removal mechanism and access-control simplification in the project changelog.

Original summary in English

Summary by Sourcery

重构维护者退出和移除治理机制，通过将休眠/退出与强制移除分离，并统一访问控制语义。

Enhancements:

• 将维护者治理拆分为独立的退出/休眠和强制移除两个部分，引入统一且有文档记录的「因故移除」流程，明确定义降级、决策和申诉阶段。
• 简化访问控制的状态/权限矩阵，并新增「状态到权限」映射表，将先前的中间状态合并为单一的 Removal 状态。

Documentation:

• 记录新的强制移除流程，包括降级、决策和申诉时间线，并阐明其与维护者角色及休眠状态之间的关系。
• 在项目更新日志中记录重构后的移除机制以及访问控制的简化。

Original summary in English

Summary by Sourcery

Refactor maintainer exit and removal governance by separating dormancy/exit from forced removal and aligning access-control semantics.

Enhancements:

• Split maintainer governance into separate exit/dormancy and forced-removal sections, introducing a unified, documented removal-for-cause flow with explicit downgrade, decision, and appeal stages.
• Simplify the access-control state/permission matrix and add a status-to-permission mapping table that consolidates prior intermediate states into a single Removal status.

Documentation:

• Document the new forced-removal process, including downgrade, decision, and appeal timelines, and clarify how it interacts with maintainer roles and dormancy.
• Record the refactored removal mechanism and access-control simplification in the project changelog.

Original summary in English

Summary by Sourcery

重构维护者退出和移除治理机制，通过将休眠/退出与强制移除分离，并统一访问控制语义。

Enhancements:

• 将维护者治理拆分为独立的退出/休眠和强制移除两个部分，引入统一且有文档记录的「因故移除」流程，明确定义降级、决策和申诉阶段。
• 简化访问控制的状态/权限矩阵，并新增「状态到权限」映射表，将先前的中间状态合并为单一的 Removal 状态。

Documentation:

• 记录新的强制移除流程，包括降级、决策和申诉时间线，并阐明其与维护者角色及休眠状态之间的关系。
• 在项目更新日志中记录重构后的移除机制以及访问控制的简化。

Original summary in English

Summary by Sourcery

Refactor maintainer exit and removal governance by separating dormancy/exit from forced removal and aligning access-control semantics.

Enhancements:

• Split maintainer governance into separate exit/dormancy and forced-removal sections, introducing a unified, documented removal-for-cause flow with explicit downgrade, decision, and appeal stages.
• Simplify the access-control state/permission matrix and add a status-to-permission mapping table that consolidates prior intermediate states into a single Removal status.

Documentation:

• Document the new forced-removal process, including downgrade, decision, and appeal timelines, and clarify how it interacts with maintainer roles and dormancy.
• Record the refactored removal mechanism and access-control simplification in the project changelog.

Original summary in English

Summary by Sourcery

重构维护者退出和移除治理机制，通过将休眠/退出与强制移除分离，并统一访问控制语义。

Enhancements:

• 将维护者治理拆分为独立的退出/休眠和强制移除两个部分，引入统一且有文档记录的「因故移除」流程，明确定义降级、决策和申诉阶段。
• 简化访问控制的状态/权限矩阵，并新增「状态到权限」映射表，将先前的中间状态合并为单一的 Removal 状态。

Documentation:

• 记录新的强制移除流程，包括降级、决策和申诉时间线，并阐明其与维护者角色及休眠状态之间的关系。
• 在项目更新日志中记录重构后的移除机制以及访问控制的简化。

Original summary in English

Summary by Sourcery

Refactor maintainer exit and removal governance by separating dormancy/exit from forced removal and aligning access-control semantics.

Enhancements:

• Split maintainer governance into separate exit/dormancy and forced-removal sections, introducing a unified, documented removal-for-cause flow with explicit downgrade, decision, and appeal stages.
• Simplify the access-control state/permission matrix and add a status-to-permission mapping table that consolidates prior intermediate states into a single Removal status.

Documentation:

• Document the new forced-removal process, including downgrade, decision, and appeal timelines, and clarify how it interacts with maintainer roles and dormancy.
• Record the refactored removal mechanism and access-control simplification in the project changelog.

Original summary in English

Summary by Sourcery

重构维护者退出和移除治理机制，通过将休眠/退出与强制移除分离，并统一访问控制语义。

Enhancements:

• 将维护者治理拆分为独立的退出/休眠和强制移除两个部分，引入统一且有文档记录的「因故移除」流程，明确定义降级、决策和申诉阶段。
• 简化访问控制的状态/权限矩阵，并新增「状态到权限」映射表，将先前的中间状态合并为单一的 Removal 状态。

Documentation:

• 记录新的强制移除流程，包括降级、决策和申诉时间线，并阐明其与维护者角色及休眠状态之间的关系。
• 在项目更新日志中记录重构后的移除机制以及访问控制的简化。

Original summary in English

Summary by Sourcery

Refactor maintainer exit and removal governance by separating dormancy/exit from forced removal and aligning access-control semantics.

Enhancements:

• Split maintainer governance into separate exit/dormancy and forced-removal sections, introducing a unified, documented removal-for-cause flow with explicit downgrade, decision, and appeal stages.
• Simplify the access-control state/permission matrix and add a status-to-permission mapping table that consolidates prior intermediate states into a single Removal status.

Documentation:

• Document the new forced-removal process, including downgrade, decision, and appeal timelines, and clarify how it interacts with maintainer roles and dormancy.
• Record the refactored removal mechanism and access-control simplification in the project changelog.

Original summary in English

Summary by Sourcery

重构维护者退出和移除治理机制，通过将休眠/退出与强制移除分离，并统一访问控制语义。

Enhancements:

• 将维护者治理拆分为独立的退出/休眠和强制移除两个部分，引入统一且有文档记录的「因故移除」流程，明确定义降级、决策和申诉阶段。
• 简化访问控制的状态/权限矩阵，并新增「状态到权限」映射表，将先前的中间状态合并为单一的 Removal 状态。

Documentation:

• 记录新的强制移除流程，包括降级、决策和申诉时间线，并阐明其与维护者角色及休眠状态之间的关系。
• 在项目更新日志中记录重构后的移除机制以及访问控制的简化。

Original summary in English

Summary by Sourcery

Refactor maintainer exit and removal governance by separating dormancy/exit from forced removal and aligning access-control semantics.

Enhancements:

• Split maintainer governance into separate exit/dormancy and forced-removal sections, introducing a unified, documented removal-for-cause flow with explicit downgrade, decision, and appeal stages.
• Simplify the access-control state/permission matrix and add a status-to-permission mapping table that consolidates prior intermediate states into a single Removal status.

Documentation:

• Document the new forced-removal process, including downgrade, decision, and appeal timelines, and clarify how it interacts with maintainer roles and dormancy.
• Record the refactored removal mechanism and access-control simplification in the project changelog.

Original summary in English

Summary by Sourcery

重构维护者退出和移除治理机制，通过将休眠/退出与强制移除分离，并统一访问控制语义。

Enhancements:

• 将维护者治理拆分为独立的退出/休眠和强制移除两个部分，引入统一且有文档记录的「因故移除」流程，明确定义降级、决策和申诉阶段。
• 简化访问控制的状态/权限矩阵，并新增「状态到权限」映射表，将先前的中间状态合并为单一的 Removal 状态。

Documentation:

• 记录新的强制移除流程，包括降级、决策和申诉时间线，并阐明其与维护者角色及休眠状态之间的关系。
• 在项目更新日志中记录重构后的移除机制以及访问控制的简化。

Original summary in English

Summary by Sourcery

Refactor maintainer exit and removal governance by separating dormancy/exit from forced removal and aligning access-control semantics.

Enhancements:

• Split maintainer governance into separate exit/dormancy and forced-removal sections, introducing a unified, documented removal-for-cause flow with explicit downgrade, decision, and appeal stages.
• Simplify the access-control state/permission matrix and add a status-to-permission mapping table that consolidates prior intermediate states into a single Removal status.

Documentation:

• Document the new forced-removal process, including downgrade, decision, and appeal timelines, and clarify how it interacts with maintainer roles and dormancy.
• Record the refactored removal mechanism and access-control simplification in the project changelog.

Original summary in English

Summary by Sourcery

重构维护者退出和移除治理机制，通过将休眠/退出与强制移除分离，并统一访问控制语义。

Enhancements:

• 将维护者治理拆分为独立的退出/休眠和强制移除两个部分，引入统一且有文档记录的「因故移除」流程，明确定义降级、决策和申诉阶段。
• 简化访问控制的状态/权限矩阵，并新增「状态到权限」映射表，将先前的中间状态合并为单一的 Removal 状态。

Documentation:

• 记录新的强制移除流程，包括降级、决策和申诉时间线，并阐明其与维护者角色及休眠状态之间的关系。
• 在项目更新日志中记录重构后的移除机制以及访问控制的简化。

Original summary in English

Summary by Sourcery

Refactor maintainer exit and removal governance by separating dormancy/exit from forced removal and aligning access-control semantics.

Enhancements:

• Split maintainer governance into separate exit/dormancy and forced-removal sections, introducing a unified, documented removal-for-cause flow with explicit downgrade, decision, and appeal stages.
• Simplify the access-control state/permission matrix and add a status-to-permission mapping table that consolidates prior intermediate states into a single Removal status.

Documentation:

• Document the new forced-removal process, including downgrade, decision, and appeal timelines, and clarify how it interacts with maintainer roles and dormancy.
• Record the refactored removal mechanism and access-control simplification in the project changelog.

Original summary in English

Summary by Sourcery

重构维护者退出和移除治理机制，通过将休眠/退出与强制移除分离，并统一访问控制语义。

Enhancements:

• 将维护者治理拆分为独立的退出/休眠和强制移除两个部分，引入统一且有文档记录的「因故移除」流程，明确定义降级、决策和申诉阶段。
• 简化访问控制的状态/权限矩阵，并新增「状态到权限」映射表，将先前的中间状态合并为单一的 Removal 状态。

Documentation:

• 记录新的强制移除流程，包括降级、决策和申诉时间线，并阐明其与维护者角色及休眠状态之间的关系。
• 在项目更新日志中记录重构后的移除机制以及访问控制的简化。

Original summary in English

Summary by Sourcery

Refactor maintainer exit and removal governance by separating dormancy/exit from forced removal and aligning access-control semantics.

Enhancements:

• Split maintainer governance into separate exit/dormancy and forced-removal sections, introducing a unified, documented removal-for-cause flow with explicit downgrade, decision, and appeal stages.
• Simplify the access-control state/permission matrix and add a status-to-permission mapping table that consolidates prior intermediate states into a single Removal status.

Documentation:

• Document the new forced-removal process, including downgrade, decision, and appeal timelines, and clarify how it interacts with maintainer roles and dormancy.
• Record the refactored removal mechanism and access-control simplification in the project changelog.

[Mikuoso]

@TouhouGleaners/core-maintainers

[Mikuoso]

@sourcery-ai review

[sourcery-ai]

审阅者指南

通过将退出/休眠与强制除名分离，引入独立的三步除名流程（含申诉），使访问控制的状态/权限矩阵与统一的 Removal 状态对齐，并在变更日志中记录这些改动，从而重构维护者治理机制。

维护者状态与统一 Removal 状态的状态图

stateDiagram-v2
    [*] --> NormalMaintainer

    NormalMaintainer --> Dormant: 180 天无协作轨迹
    Dormant --> NormalMaintainer: 提交 PR 或 Issue 留言

    NormalMaintainer --> Emeritus: 主动退出

    NormalMaintainer --> Removal: 裁决除名表决通过
    Removal --> NormalMaintainer: 申诉复核通过

Loading

新的三步“因故除名”流程图

flowchart TD
    A[发现严重违规行为] --> B[降权与归档\n任一核心维护者收回写权限\n24 小时内在 THRD-Protocol 开 Issue 归档]
    B --> C[裁决表决\n归档后 7 天内核心维护者多数表决]

    C -->|多数通过| D[除名生效\n状态记为 Removal]
    C -->|多数未通过| E[恢复原维护者权限]

    D --> F[申诉阶段\n除名后 7 天内被除名者可发起申诉 Issue]
    F --> G[复核表决\n核心维护者 7 天内复核]

    G -->|多数通过维持除名| H[维持 Removal 状态]
    G -->|多数否决恢复| E

Loading

文件级变更

变更	详情	文件
重构维护者角色治理，将一般退出与休眠与专门的强制除名章节拆分开来，并采用统一的三步流程与申诉机制。	将第 6 节从原来的“退出与除名机制”重命名并重构为“退出与休眠”，保留自愿辞任和自动休眠的流程。 将强制除名拆分到新的第 7 节“Removal for Cause”，用三步流程（权限降级与归档、7 日内裁决表决、以及 7 日内申诉复核）替换之前的两步“立即暂停/最终裁决”机制。 明确公告、THRD-Protocol Issue 创建、在归档 Issue 中进行明确多数表决，以及申诉与复核的时间限制等操作性要求。	docs/governance/maintainer-role.md
通过显式的“状态-权限”映射以及统一的 Removal 状态，使访问控制模型与重构后的除名策略保持一致。	保留现有的角色/状态描述（技术维护者、运营维护者、Dormant、Emeritus），并追加新的“状态-权限映射”子章节。 定义一张简明表格，将 Normal、Dormant 和 Removal 状态映射到写/读权限、触发条件以及退出/恢复路径。 在 Removal 状态这一行中链接回新的强制除名章节，并记录只有在 7 天内申诉成功才是恢复权限的唯一路径。	docs/governance/access-control.md
在项目变更日志中记录治理重构以及简化后的权限矩阵。	在 unreleased 小节下增加一个“Changed”子章节，概述重构后的强制除名机制及其新的统一流程。 记录访问控制矩阵已简化为单一的 Removal 状态，并删除了中间观察/立即除名等中间状态。	docs/changelog.md

---

提示与命令

与 Sourcery 交互

• 触发一次新的审阅： 在 pull request 中评论 @sourcery-ai review。
• 继续讨论： 直接回复 Sourcery 的审阅评论。
• 从审阅评论生成 GitHub Issue： 在某条审阅评论下回复，请求 Sourcery 根据该评论创建一个 Issue。你也可以直接在该评论下回复 @sourcery-ai issue 来从评论创建 Issue。
• 生成 pull request 标题： 在 pull request 标题中任意位置写上 @sourcery-ai，即可随时生成标题。你也可以在 pull request 中评论 @sourcery-ai title 来（重新）生成标题。
• 生成 pull request 摘要： 在 pull request 正文的任意位置写上 @sourcery-ai summary，即可在该位置生成 PR 摘要。你也可以在 pull request 中评论 @sourcery-ai summary 来在任意时间（重新）生成摘要。
• 生成审阅者指南： 在 pull request 中评论 @sourcery-ai guide，即可在任意时间（重新）生成审阅者指南。
• 一次性解决所有 Sourcery 评论： 在 pull request 中评论 @sourcery-ai resolve，即可将所有 Sourcery 评论标记为已解决。适用于你已经处理完所有评论且不希望再看到它们的情况。
• 一次性驳回所有 Sourcery 审阅： 在 pull request 中评论 @sourcery-ai dismiss，即可驳回所有现有的 Sourcery 审阅。特别适用于你想从头开始一次新的审阅——记得再评论一次 @sourcery-ai review 来触发新的审阅！

自定义你的体验

访问你的 控制面板 以：

• 启用或禁用审阅特性，例如由 Sourcery 生成的 pull request 摘要、审阅者指南等。
• 更改审阅语言。
• 添加、删除或编辑自定义审阅指令。
• 调整其他审阅设置。

获取帮助

• 通过邮件 联系技术支持团队 以获取帮助或提供反馈。
• 访问我们的文档 获取详细指南和信息。
• 通过在 X/Twitter、LinkedIn 或 GitHub 关注我们，与 Sourcery 团队保持联系。

Original review guide in English

Reviewer's Guide

Refactors maintainer governance by separating exit/休眠 from forced removal, introducing a dedicated three-step除名流程 with appeal, aligning the access-control status/permission matrix with a unified Removal state, and documenting these changes in the changelog.

State diagram for maintainer status and unified Removal state

stateDiagram-v2
    [*] --> NormalMaintainer

    NormalMaintainer --> Dormant: 180 天无协作轨迹
    Dormant --> NormalMaintainer: 提交 PR 或 Issue 留言

    NormalMaintainer --> Emeritus: 主动退出

    NormalMaintainer --> Removal: 裁决除名表决通过
    Removal --> NormalMaintainer: 申诉复核通过

Loading

Flow diagram for new three-step Removal for Cause process

flowchart TD
    A[发现严重违规行为] --> B[降权与归档\n任一核心维护者收回写权限\n24 小时内在 THRD-Protocol 开 Issue 归档]
    B --> C[裁决表决\n归档后 7 天内核心维护者多数表决]

    C -->|多数通过| D[除名生效\n状态记为 Removal]
    C -->|多数未通过| E[恢复原维护者权限]

    D --> F[申诉阶段\n除名后 7 天内被除名者可发起申诉 Issue]
    F --> G[复核表决\n核心维护者 7 天内复核]

    G -->|多数通过维持除名| H[维持 Removal 状态]
    G -->|多数否决恢复| E

Loading

File-Level Changes

Change	Details	Files
Refactor maintainer-role governance to split general exit & dormancy from a dedicated forced-removal section with a unified three-step process and appeal.	Rename and restructure section 6 from a combined '退出与除名机制' into '退出与休眠', keeping voluntary resignation and automatic dormancy flows there. Extract forced removal into a new section 7 'Removal for Cause', replacing the previous two-step immediate suspension/final ruling with a 3-step flow:权限降级与归档、7日内裁决表决、以及7日内申诉复核。 Clarify operational requirements around announcements, THRD-Protocol issue creation, explicit majority voting in the archived issue, and time limits for appeals and review.	docs/governance/maintainer-role.md
Align the access-control model with the refactored removal policy via an explicit status-to-permissions mapping and a unified Removal state.	Keep the existing role/state descriptions (技术维护者、运营维护者、Dormant、Emeritus) and append a new '状态-权限映射' subsection. Define a concise table mapping Normal, Dormant, and Removal states to write/read permissions, triggers, and exit/恢复 paths. Link the Removal state row back to the new forced-removal section and document that successful appeal within 7 days is the only path to restore permissions.	docs/governance/access-control.md
Document the governance refactor and simplified permission matrix in the project changelog.	Add a 'Changed' subsection under the unreleased section to summarize the refactored forced-removal mechanism and its new unified流程。 Record that the access-control matrix was simplified to a single Removal state and that intermediate observation/immediate-removal states were removed.	docs/changelog.md

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

嗨，我在下面提供了一些总体反馈：

• 新增的“超时兜底”条款在 30 天上限后的后续处理缺少说明（例如是否自动恢复、升级为即时除名，或需要强制裁决），建议补充明确 30 天到期时的默认处理行为，以避免执行时产生分歧。
• 在 C-1 即时除名的申诉机制中，目前仅说明由“核心维护者团队复核”，但没有约定处理时限或表决规则（例如是否以多数通过为准、申诉逾期如何处理）。建议在该段中补充复核流程的时间边界和具体决策方式。

面向 AI 代理的提示（Prompt）

Please address the comments from this code review:

## Overall Comments
- 新增的“超时兜底”条款在 30 天上限后的后续处理缺少说明（例如是否自动恢复、升级为即时除名，或需要强制裁决），建议补充明确 30 天到期时的默认处理行为，以避免执行时产生分歧。
- 在 C-1 即时除名的申诉机制中，目前仅说明由“核心维护者团队复核”，但没有约定处理时限或表决规则（例如是否以多数通过为准、申诉逾期如何处理）。建议在该段中补充复核流程的时间边界和具体决策方式。

---

Sourcery 对开源项目免费使用——如果你觉得这份代码审查有帮助，欢迎分享 ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{请帮助我变得更有用！欢迎在每条评论上点击 👍 或 👎，我会根据你的反馈改进后续的代码审查。}

Original comment in English

Hey - I've left some high level feedback:

• The new“超时兜底”条款在 30 天上限后缺少后续处理说明（例如自动恢复、升级为即时除名或需强制裁决），建议补充明确 30 天到期时的默认行为以避免执行分歧。
• 在 C-1 即时除名的申诉机制中，仅说明了“核心维护者团队复核”，但未约定处理时限或表决规则（例如多数通过、申诉过期处理），建议在该段中补充复核流程的时间边界和决策方式。

Prompt for AI Agents

Please address the comments from this code review:

## Overall Comments
- The new“超时兜底”条款在 30 天上限后缺少后续处理说明（例如自动恢复、升级为即时除名或需强制裁决），建议补充明确 30 天到期时的默认行为以避免执行分歧。
- 在 C-1 即时除名的申诉机制中，仅说明了“核心维护者团队复核”，但未约定处理时限或表决规则（例如多数通过、申诉过期处理），建议在该段中补充复核流程的时间边界和决策方式。

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[Mikuoso]

@sourcery-ai review

[sourcery-ai]

Hey - 我在这里给了一些高层面的反馈：

• 在 C-1 中你要求在 THRD-Protocol 开 Issue 归档，但 C-2 只写“在组织内部说明情况”，建议统一明确 C-2 是否也需要在同一渠道归档，以便审计和历史追踪。
• C-2 的“超时兜底”条款写明 7 天内未响应则降权自动延长至最多 30 天，但未明确 7–30 天期间是否仍可发起并完成裁决，建议澄清这一时间窗内允许的裁决行为和结果。
• 观察期结束后当前文本只写“由核心维护者决定是否恢复原权限”，未说明是多数表决还是其他决策机制，建议补充决策方式以减少执行歧义。

面向 AI 代理的提示（Prompt for AI Agents）

Please address the comments from this code review:

## Overall Comments
- 在 C-1 中你要求在 `THRD-Protocol` 开 Issue 归档，但 C-2 只写“在组织内部说明情况”，建议统一明确 C-2 是否也需要在同一渠道归档，以便审计和历史追踪。
- C-2 的“超时兜底”条款写明 7 天内未响应则降权自动延长至最多 30 天，但未明确 7–30 天期间是否仍可发起并完成裁决，建议澄清这一时间窗内允许的裁决行为和结果。
- 观察期结束后当前文本只写“由核心维护者决定是否恢复原权限”，未说明是多数表决还是其他决策机制，建议补充决策方式以减少执行歧义。

---

Sourcery 对开源项目是免费的——如果你觉得我们的评审有帮助，请考虑分享它们 ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{帮我变得更有用！请在每条评论上点击 👍 或 👎，我会根据你的反馈改进后续评审。}

Original comment in English

Hey - I've left some high level feedback:

• In C-1 you要求在 THRD-Protocol 开 Issue 归档，但 C-2 只写“在组织内部说明情况”，建议统一明确 C-2 是否也需要在同一渠道归档以便审计和历史追踪。
• C-2 的“超时兜底”条款写明 7 天内未响应则降权自动延长至最多 30 天，但未明确 7–30 天期间是否仍可发起并完成裁决，建议澄清这一时间窗内允许的裁决行为和结果。
• 观察期结束后当前文本只写“由核心维护者决定是否恢复原权限”，未说明是多数表决还是其他决策机制，建议补充决策方式以减少执行歧义。

Prompt for AI Agents

Please address the comments from this code review:

## Overall Comments
- In C-1 you要求在 `THRD-Protocol` 开 Issue 归档，但 C-2 只写“在组织内部说明情况”，建议统一明确 C-2 是否也需要在同一渠道归档以便审计和历史追踪。
- C-2 的“超时兜底”条款写明 7 天内未响应则降权自动延长至最多 30 天，但未明确 7–30 天期间是否仍可发起并完成裁决，建议澄清这一时间窗内允许的裁决行为和结果。
- 观察期结束后当前文本只写“由核心维护者决定是否恢复原权限”，未说明是多数表决还是其他决策机制，建议补充决策方式以减少执行歧义。

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[Mikuoso]

@sourcery-ai review

[sourcery-ai]

嗨，我这边有一些整体层面的反馈：

• 建议进一步澄清 C-1 和 C-2 之间的边界（例如，什么情形算作“不可逆损害”，什么情形算作“严重但未造成不可逆损害”），以减少在事故分级时的歧义和争议。
• C-2 的超时/兜底逻辑读起来有点复杂；可以考虑增加一个小表格或用项目符号列出状态变迁时间线（降权 → 裁决中 → 观察期 → 恢复/除名）以及对应的最大时长，方便大家在实际操作中保持一致。
• PR 描述里有重复的 “Original summary in English” 段落，建议去重一下，以便让变更历史更精简、同时避免造成混淆。

给 AI Agent 的提示词（Prompt）

Please address the comments from this code review:

## Overall Comments
- Consider clarifying the boundary between C-1 and C-2 (e.g., what counts as “不可逆损害” vs. “严重但未造成不可逆损害”) to reduce ambiguity and disagreements when classifying incidents.
- The timeout/兜底逻辑 for C-2 reads a bit complex; a small table or bullet timeline of states (降权 → 裁决中 → 观察期 → 恢复/除名) and their最大时长 could make it easier to apply consistently.
- The PR description contains duplicated ‘Original summary in English’ sections; you might want to deduplicate those to keep the change history concise and avoid confusion.

---

Sourcery 对开源项目是免费的——如果你觉得这次的评审有帮助，欢迎分享 ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{帮我变得更有用！请在每条评论上点击 👍 或 👎，我会根据你的反馈持续改进评审质量。}

Original comment in English

Hey - I've left some high level feedback:

• Consider clarifying the boundary between C-1 and C-2 (e.g., what counts as “不可逆损害” vs. “严重但未造成不可逆损害”) to reduce ambiguity and disagreements when classifying incidents.
• The timeout/兜底逻辑 for C-2 reads a bit complex; a small table or bullet timeline of states (降权 → 裁决中 → 观察期 → 恢复/除名) and their最大时长 could make it easier to apply consistently.
• The PR description contains duplicated ‘Original summary in English’ sections; you might want to deduplicate those to keep the change history concise and avoid confusion.

Prompt for AI Agents

Please address the comments from this code review:

## Overall Comments
- Consider clarifying the boundary between C-1 and C-2 (e.g., what counts as “不可逆损害” vs. “严重但未造成不可逆损害”) to reduce ambiguity and disagreements when classifying incidents.
- The timeout/兜底逻辑 for C-2 reads a bit complex; a small table or bullet timeline of states (降权 → 裁决中 → 观察期 → 恢复/除名) and their最大时长 could make it easier to apply consistently.
- The PR description contains duplicated ‘Original summary in English’ sections; you might want to deduplicate those to keep the change history concise and avoid confusion.

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[Mikuoso]

@sourcery-ai review

[sourcery-ai]

Hey - 我在下面给出了一些整体性的反馈：

• 在 7-B 小节中，状态流转表和下面的流程/制衡描述对“紧急降权→裁决→观察期→永久除名”的时间线和触发条件略有不同（如 7 天与 30 天的关系、何时进入观察期），建议用完全一致的阶段名称和事件触发描述统一两处文本，避免维护者理解偏差。
• 在 7-A 即时除名中，当前只规定了“被除名者可在 14 天内申诉，核心维护者团队需在 14 天内复核”，建议补充说明若核心维护者在复核时限内未形成决议时的兜底结果（默认维持除名或默认恢复），以避免流程上出现悬而未决的状态。

供 AI Agents 使用的提示词

Please address the comments from this code review:

## Overall Comments
- 在 7-B 小节中，状态流转表和下面的流程/制衡描述对“紧急降权→裁决→观察期→永久除名”的时间线和触发条件略有不同（如 7 天与 30 天的关系、何时进入观察期），建议用完全一致的阶段名称和事件触发描述统一两处文本，避免维护者理解偏差。
- 在 7-A 即时除名中，当前只规定了“被除名者可在 14 天内申诉，核心维护者团队需在 14 天内复核”，建议补充说明若核心维护者在复核时限内未形成决议时的兜底结果（默认维持除名或默认恢复），以避免流程上出现悬而未决的状态。

---

Sourcery 对开源项目免费 —— 如果你觉得我们的评审有帮助，欢迎分享 ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{帮我变得更有用！请在每条评论上点击 👍 或 👎，我会根据你的反馈持续改进评审质量。}

Original comment in English

Hey - I've left some high level feedback:

• In section 7-B, the状态流转表和下面的流程/制衡描述对“紧急降权→裁决→观察期→永久除名”的时间线和触发条件略有不同（如 7 天与 30 天的关系、何时进入观察期），建议用完全一致的阶段名称和事件触发描述统一两处文本，避免维护者理解偏差。
• 在 7-A 即时除名中，当前只规定了“被除名者可在 14 天内申诉，核心维护者团队需在 14 天内复核”，建议补充说明若核心维护者在复核时限内未形成决议时的兜底结果（默认维持除名或默认恢复），以避免流程上出现悬而未决的状态。

Prompt for AI Agents

Please address the comments from this code review:

## Overall Comments
- In section 7-B, the状态流转表和下面的流程/制衡描述对“紧急降权→裁决→观察期→永久除名”的时间线和触发条件略有不同（如 7 天与 30 天的关系、何时进入观察期），建议用完全一致的阶段名称和事件触发描述统一两处文本，避免维护者理解偏差。
- 在 7-A 即时除名中，当前只规定了“被除名者可在 14 天内申诉，核心维护者团队需在 14 天内复核”，建议补充说明若核心维护者在复核时限内未形成决议时的兜底结果（默认维持除名或默认恢复），以避免流程上出现悬而未决的状态。

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[Mikuoso]

@sourcery-ai review

[sourcery-ai]

Hey - 我给出了一些整体层面的反馈：

• 在 7-B 裁决除名流程中多次提到“观察期状态（14 天内仅有只读权限）”，建议在 access-control 权限矩阵中增加明确的观察期状态或映射到现有状态，以避免该状态在不同文档间语义不一致。
• 即时除名与裁决除名的适用边界目前通过示例描述（如“数据不可恢复 / 密钥实质泄露 / 违法”），可考虑补充一两条更边缘的典型情形或判断原则，以减少维护者在实际分流时的主观分歧。

给 AI Agents 的提示词

Please address the comments from this code review:

## Overall Comments
- 在 7-B 裁决除名流程中多次提到“观察期状态（14 天内仅有只读权限）”，建议在 access-control 权限矩阵中增加明确的观察期状态或映射到现有状态，以避免该状态在不同文档间语义不一致。
- 即时除名与裁决除名的适用边界目前通过示例描述（如“数据不可恢复 / 密钥实质泄露 / 违法”），可考虑补充一两条更边缘的典型情形或判断原则，以减少维护者在实际分流时的主观分歧。

---

Sourcery 对开源项目是免费的——如果你觉得我们的评审有帮助，欢迎分享 ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{帮我变得更有用！请在每条评论上点击 👍 或 👎，我会根据这些反馈持续改进你的代码评审体验。}

Original comment in English

Hey - I've left some high level feedback:

• 在 7-B 裁决除名流程中多次提到“观察期状态（14 天内仅有只读权限）”，建议在 access-control 权限矩阵中增加明确的观察期状态或映射到现有状态，以避免该状态在不同文档间语义不一致。
• 即时除名与裁决除名的适用边界目前通过示例描述（如“数据不可恢复 / 密钥实质泄露 / 违法”），可考虑补充一两条更边缘的典型情形或判断原则，以减少维护者在实际分流时的主观分歧。

Prompt for AI Agents

Please address the comments from this code review:

## Overall Comments
- 在 7-B 裁决除名流程中多次提到“观察期状态（14 天内仅有只读权限）”，建议在 access-control 权限矩阵中增加明确的观察期状态或映射到现有状态，以避免该状态在不同文档间语义不一致。
- 即时除名与裁决除名的适用边界目前通过示例描述（如“数据不可恢复 / 密钥实质泄露 / 违法”），可考虑补充一两条更边缘的典型情形或判断原则，以减少维护者在实际分流时的主观分歧。

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[Mikuoso]

@sourcery-ai review

[sourcery-ai]

嗨，我这边有一些整体性的反馈：

• 新的 7-A / 7-B 拆分引入了几个新的状态（即时除名、裁决期、观察期、Probation），但 maintainer-role.md 和 access-control.md 目前只是在零散的位置提到这些状态——建议增加一份小而共享的状态图或表格，把每个命名状态及其对应权限一一列出，以避免和 Dormant/Emeritus 之间的状态切换关系产生歧义。
• 在 7-B 裁决除名流程中，紧急降权、裁决期、超时延长和观察期的触发条件与终止条件一部分写在正文，一部分写在表格里；建议对相关表述进行统一（例如，明确且统一界定什么算作“有人响应”、谁可以发起表决），从而在表格和项目列表中都采用同一套、无歧义的定义，方便维护者理解和执行。

给 AI Agent 的提示（Prompt）

Please address the comments from this code review:

## Overall Comments
- The new 7-A/7-B split introduces several new states (即时除名、裁决期、观察期、Probation)，but `maintainer-role.md` and `access-control.md` only loosely reference them—consider adding a small, shared state diagram or table that maps each named state and its permissions to avoid ambiguity about how transitions interact with Dormant/Emeritus.
- In the 7-B 裁决除名流程，紧急降权、裁决期、超时延长和观察期的触发条件和终止条件 are described partly in prose and partly in the table; it would help maintainers if you normalize the wording (e.g., consistently define what counts as“有人响应”and who can发起表决) so there is a single, unambiguous definition across both the table and the bullet list.

---

Sourcery 对开源项目是免费的——如果你觉得我们的评审有帮助，欢迎分享 ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{帮助我变得更有用！请在每条评论上点击 👍 或 👎，我会根据你的反馈持续改进评审质量。}

Original comment in English

Hey - I've left some high level feedback:

• The new 7-A/7-B split introduces several new states (即时除名、裁决期、观察期、Probation)，but maintainer-role.md and access-control.md only loosely reference them—consider adding a small, shared state diagram or table that maps each named state and its permissions to avoid ambiguity about how transitions interact with Dormant/Emeritus.
• In the 7-B 裁决除名流程，紧急降权、裁决期、超时延长和观察期的触发条件和终止条件 are described partly in prose and partly in the table; it would help maintainers if you normalize the wording (e.g., consistently define what counts as“有人响应”and who can发起表决) so there is a single, unambiguous definition across both the table and the bullet list.

Prompt for AI Agents

Please address the comments from this code review:

## Overall Comments
- The new 7-A/7-B split introduces several new states (即时除名、裁决期、观察期、Probation)，but `maintainer-role.md` and `access-control.md` only loosely reference them—consider adding a small, shared state diagram or table that maps each named state and its permissions to avoid ambiguity about how transitions interact with Dormant/Emeritus.
- In the 7-B 裁决除名流程，紧急降权、裁决期、超时延长和观察期的触发条件和终止条件 are described partly in prose and partly in the table; it would help maintainers if you normalize the wording (e.g., consistently define what counts as“有人响应”and who can发起表决) so there is a single, unambiguous definition across both the table and the bullet list.

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[Mikuoso]

@sourcery-ai review

[sourcery-ai]

你好，我在这里给出一些高层次的反馈：

• 在 maintainer-role.md 和 access-control.md 中，建议显式将 即时除名 和 永久除名 定义为状态名称，并在 7-A/7-B 的文本中引用这些状态名和 观察期 (Probation)，以保持状态流转描述与权限矩阵表中的术语完全一致。
• 在 7-B 的状态流转表中，有人响应后可随时裁决 与 表决 的具体操作主体和位置（例如在归档 Issue 中由哪些角色发起/记录）略显模糊，可以在流程描述中补一句，明确谁在何处触发裁决，以减少执行时的理解歧义。

供 AI Agent 使用的提示词

Please address the comments from this code review:

## Overall Comments
- In `maintainer-role.md` and `access-control.md`, consider explicitly defining `即时除名` 和 `永久除名` 作为状态名称，并在 7-A/7-B 文本中引用这些状态名和 `观察期 (Probation)`，以保持状态流转描述与权限矩阵表中的术语完全一致。
- 在 7-B 的状态流转表中，`有人响应后可随时裁决` 与 `表决` 的具体操作主体和位置（例如在归档 Issue 中由哪些角色发起/记录）略显模糊，可以在流程描述中补一句明确谁在何处触发裁决，以减少执行时的理解歧义。

---

Sourcery 对开源项目免费——如果你觉得我们的评审有帮助，欢迎分享 ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{帮我变得更有用！请在每条评论上点击 👍 或 👎，我会根据你的反馈持续改进评审质量。}

Original comment in English

Hey - I've left some high level feedback:

• In maintainer-role.md and access-control.md, consider explicitly defining 即时除名 和 永久除名 作为状态名称，并在 7-A/7-B 文本中引用这些状态名和 观察期 (Probation)，以保持状态流转描述与权限矩阵表中的术语完全一致。
• 在 7-B 的状态流转表中，有人响应后可随时裁决 与 表决 的具体操作主体和位置（例如在归档 Issue 中由哪些角色发起/记录）略显模糊，可以在流程描述中补一句明确谁在何处触发裁决，以减少执行时的理解歧义。

Prompt for AI Agents

Please address the comments from this code review:

## Overall Comments
- In `maintainer-role.md` and `access-control.md`, consider explicitly defining `即时除名` 和 `永久除名` 作为状态名称，并在 7-A/7-B 文本中引用这些状态名和 `观察期 (Probation)`，以保持状态流转描述与权限矩阵表中的术语完全一致。
- 在 7-B 的状态流转表中，`有人响应后可随时裁决` 与 `表决` 的具体操作主体和位置（例如在归档 Issue 中由哪些角色发起/记录）略显模糊，可以在流程描述中补一句明确谁在何处触发裁决，以减少执行时的理解歧义。

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[Mikuoso]

@sourcery-ai review

[sourcery-ai]

Hey - 我在这里给出一些整体性的反馈：

• 在 maintainer-role.md（7-A/7-B）和 access-control.md 中引入的新状态名称和流程，建议进行交叉核对，确保每一种生命周期状态（例如 Immediate Removal、Permanent Removal、Probation）在两份文档中都只有一个清晰定义的含义和转移路径，避免出现关于临时的 “Immediate Removal” 何时、如何转变为 “Permanent Removal” 的歧义。
• 对于 7-A appeal/复核流程，建议明确写出如何处理逾期或重复申诉（例如在 14 天窗口之后出现的新证据），以及谁有权限重新开启或推翻过去的裁决，这样边缘案例就不需要在书面政策之外临时处理。

Prompt for AI Agents

Please address the comments from this code review:

## Overall Comments
- The new state names and flows introduced in `maintainer-role.md` (7-A/7-B) and `access-control.md` should be cross-checked so that each lifecycle state (e.g., Immediate Removal vs Permanent Removal vs Probation) has a single, clearly defined meaning and transition path across both documents, avoiding any ambiguity about when a temporary 'Immediate Removal' becomes 'Permanent Removal'.
- For the 7-A appeal/复核流程，consider explicitly documenting how to handle late or repeated appeals (e.g., new evidence after the 14 天窗口) and who is allowed to reopen or override a past裁决, so edge cases don’t have to be resolved ad‑hoc outside the written policy.

---

Sourcery 对开源仓库是免费的——如果你觉得我们的代码审查有帮助，欢迎分享 ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{帮我变得更有用！请在每条评论上点击 👍 或 👎，我会根据你的反馈改进后续的审查。}

Original comment in English

Hey - I've left some high level feedback:

• The new state names and flows introduced in maintainer-role.md (7-A/7-B) and access-control.md should be cross-checked so that each lifecycle state (e.g., Immediate Removal vs Permanent Removal vs Probation) has a single, clearly defined meaning and transition path across both documents, avoiding any ambiguity about when a temporary 'Immediate Removal' becomes 'Permanent Removal'.
• For the 7-A appeal/复核流程，consider explicitly documenting how to handle late or repeated appeals (e.g., new evidence after the 14 天窗口) and who is allowed to reopen or override a past裁决, so edge cases don’t have to be resolved ad‑hoc outside the written policy.

Prompt for AI Agents

Please address the comments from this code review:

## Overall Comments
- The new state names and flows introduced in `maintainer-role.md` (7-A/7-B) and `access-control.md` should be cross-checked so that each lifecycle state (e.g., Immediate Removal vs Permanent Removal vs Probation) has a single, clearly defined meaning and transition path across both documents, avoiding any ambiguity about when a temporary 'Immediate Removal' becomes 'Permanent Removal'.
- For the 7-A appeal/复核流程，consider explicitly documenting how to handle late or repeated appeals (e.g., new evidence after the 14 天窗口) and who is allowed to reopen or override a past裁决, so edge cases don’t have to be resolved ad‑hoc outside the written policy.

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[Mikuoso]

@sourcery-ai review

[sourcery-ai]

Hey - 我在这里给出一些高层次的反馈：

• 访问控制矩阵声称涵盖六种状态，但当前表格只列出了五种，并且遗漏了 Emeritus，所以要么把 Emeritus 作为一行补充进去，要么调整措辞以避免造成混淆。
• 在 access-control.md 中，建议让 Immediate Removal 和 Permanent Removal 的状态转换显式引用 7-A/7-B 小节（例如通过锚点），这样读者可以在矩阵和详细流程之间快速跳转。
• 在 CLAUDE.md 中，你引用了 docs/skills/docs-standard.md；请确保该路径是正确且稳定的，或者在文件中添加一条简短说明，指向规范文档标准的权威位置，以避免未来偏移。

给 AI 代理的提示

Please address the comments from this code review:

## Overall Comments
- The access-control matrix claims to cover six states but the table currently only lists five plus omits `Emeritus`, so either add `Emeritus` as a row or adjust the wording to avoid confusion.
- In `access-control.md`, consider making the state transitions for `Immediate Removal` and `Permanent Removal` explicitly reference sections 7-A/7-B (e.g., via anchors) so that readers can quickly navigate between the matrix and the detailed流程.
- In `CLAUDE.md`, you reference `docs/skills/docs-standard.md`; ensure that path is correct and stable or add a brief note in the file pointing to the canonical documentation-standard location to avoid future drift.

---

Sourcery 对开源项目是免费的——如果你喜欢我们的评审，请考虑分享 ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{帮我变得更有用！请在每条评论上点击 👍 或 👎，我会根据你的反馈来改进评审质量。}

Original comment in English

Hey - I've left some high level feedback:

• The access-control matrix claims to cover six states but the table currently only lists five plus omits Emeritus, so either add Emeritus as a row or adjust the wording to avoid confusion.
• In access-control.md, consider making the state transitions for Immediate Removal and Permanent Removal explicitly reference sections 7-A/7-B (e.g., via anchors) so that readers can quickly navigate between the matrix and the detailed流程.
• In CLAUDE.md, you reference docs/skills/docs-standard.md; ensure that path is correct and stable or add a brief note in the file pointing to the canonical documentation-standard location to avoid future drift.

Prompt for AI Agents

Please address the comments from this code review:

## Overall Comments
- The access-control matrix claims to cover six states but the table currently only lists five plus omits `Emeritus`, so either add `Emeritus` as a row or adjust the wording to avoid confusion.
- In `access-control.md`, consider making the state transitions for `Immediate Removal` and `Permanent Removal` explicitly reference sections 7-A/7-B (e.g., via anchors) so that readers can quickly navigate between the matrix and the detailed流程.
- In `CLAUDE.md`, you reference `docs/skills/docs-standard.md`; ensure that path is correct and stable or add a brief note in the file pointing to the canonical documentation-standard location to avoid future drift.

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[Mikuoso]

@sourcery-ai review

[sourcery-ai]

Hey - 我发现了 1 个问题，并留下了一些整体性反馈：

• 新的 7-A/7-B 政策引入了多个时间窗口（24h、7d、14d、30d）；建议在 maintainer-role.md 中增加一张简要的时间轴示意图，或者一张合并后的汇总表，这样读者无需反复回读正文就能快速理解这些截止时间之间的关系。
• 在 access-control.md 和 maintainer-role.md 中，请再次检查新状态所使用的术语和锚点是否保持一致（例如：「观察期 (Probation)」「即时除名 (Immediate Removal)」「永久除名 (Permanent Removal)」），以确保诸如 #7-a-即时除名-immediate-removal 这样的链接和引用保持稳定且语义清晰。

面向 AI Agent 的提示

Please address the comments from this code review:

## Overall Comments
- The new 7-A/7-B policy introduces several time windows (24h, 7d, 14d, 30d); consider adding a small timeline diagram or a single consolidated table in `maintainer-role.md` so readers can quickly understand how these deadlines interact without re-reading the text.
- In `access-control.md` and `maintainer-role.md`, double-check that the terms and anchors for the new states are used consistently (e.g., "观察期 (Probation)", "即时除名 (Immediate Removal)", "永久除名 (Permanent Removal)") so that links and references like `#7-a-即时除名-immediate-removal` remain stable and unambiguous.

## Individual Comments

### Comment 1
<location path="docs/governance/maintainer-role.md" line_range="95" />
<code_context>
+- **适用情形**：确认存在主观恶意或严重疏忽的前提下，恶意删除或篡改归档数据、泄露核心安全密钥、严重违法违规。无意识的违规即使后果严重，应优先走 7-B 裁决流程。
+- **流程**：任一核心维护者确认事实后，立即收回所有写权限，并在组织群聊中公告暂停其维护者身份。**24 小时内**在 `THRD-Protocol` 开 Issue 说明情况并归档。
+- **生效**：即时生效，无需表决。被除名者可在 **14 天内**发起申诉 Issue，核心维护者团队需在 **14 天内**完成复核，多数通过则维持除名，否则恢复权限。复核超时未决议的，默认维持除名。
+- **逾期与新证据**：14 天申诉窗口关闭后不再受理同一 incident 的申诉。若此后出现新证据，应作为新的违规事件重新走 7-A 或 7-B 流程，而非翻案。
+
+### 7-B. 裁决除名 (Removal by Ruling)
</code_context>
<issue_to_address>
**suggestion (typo):** 考虑将英文单词“incident”替换为中文或显式标为术语，以提升术语一致性。

在这句全中文表述中直接使用小写英文 “incident” 略显突兀。建议改为“同一事件”等中文说法；如果这是约定的专有术语，建议用反引号等方式明确标注，以保持术语风格统一。

```suggestion
- **逾期与新证据**：14 天申诉窗口关闭后不再受理同一事件的申诉。若此后出现新证据，应作为新的违规事件重新走 7-A 或 7-B 流程，而非翻案。
```
</issue_to_address>

---

Sourcery 对开源项目免费——如果你觉得我们的代码审查有帮助，欢迎分享 ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{帮我变得更有用！请对每条评论点选 👍 或 👎，我会根据你的反馈持续改进审查质量。}

Original comment in English

Hey - I've found 1 issue, and left some high level feedback:

• The new 7-A/7-B policy introduces several time windows (24h, 7d, 14d, 30d); consider adding a small timeline diagram or a single consolidated table in maintainer-role.md so readers can quickly understand how these deadlines interact without re-reading the text.
• In access-control.md and maintainer-role.md, double-check that the terms and anchors for the new states are used consistently (e.g., "观察期 (Probation)", "即时除名 (Immediate Removal)", "永久除名 (Permanent Removal)") so that links and references like #7-a-即时除名-immediate-removal remain stable and unambiguous.

Prompt for AI Agents

Please address the comments from this code review:

## Overall Comments
- The new 7-A/7-B policy introduces several time windows (24h, 7d, 14d, 30d); consider adding a small timeline diagram or a single consolidated table in `maintainer-role.md` so readers can quickly understand how these deadlines interact without re-reading the text.
- In `access-control.md` and `maintainer-role.md`, double-check that the terms and anchors for the new states are used consistently (e.g., "观察期 (Probation)", "即时除名 (Immediate Removal)", "永久除名 (Permanent Removal)") so that links and references like `#7-a-即时除名-immediate-removal` remain stable and unambiguous.

## Individual Comments

### Comment 1
<location path="docs/governance/maintainer-role.md" line_range="95" />
<code_context>
+- **适用情形**：确认存在主观恶意或严重疏忽的前提下，恶意删除或篡改归档数据、泄露核心安全密钥、严重违法违规。无意识的违规即使后果严重，应优先走 7-B 裁决流程。
+- **流程**：任一核心维护者确认事实后，立即收回所有写权限，并在组织群聊中公告暂停其维护者身份。**24 小时内**在 `THRD-Protocol` 开 Issue 说明情况并归档。
+- **生效**：即时生效，无需表决。被除名者可在 **14 天内**发起申诉 Issue，核心维护者团队需在 **14 天内**完成复核，多数通过则维持除名，否则恢复权限。复核超时未决议的，默认维持除名。
+- **逾期与新证据**：14 天申诉窗口关闭后不再受理同一 incident 的申诉。若此后出现新证据，应作为新的违规事件重新走 7-A 或 7-B 流程，而非翻案。
+
+### 7-B. 裁决除名 (Removal by Ruling)
</code_context>
<issue_to_address>
**suggestion (typo):** 考虑将英文单词“incident”替换为中文或显式标为术语，以提升术语一致性。

在这句全中文表述中直接使用小写英文 “incident” 略显突兀。建议改为“同一事件”等中文说法；如果这是约定的专有术语，建议用反引号等方式明确标注，以保持术语风格统一。

```suggestion
- **逾期与新证据**：14 天申诉窗口关闭后不再受理同一事件的申诉。若此后出现新证据，应作为新的违规事件重新走 7-A 或 7-B 流程，而非翻案。
```
</issue_to_address>

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[Mikuoso]

@sourcery-ai review

[sourcery-ai]

Hey - 我发现了 1 个问题，并且留下了一些整体性的反馈：

• access-control.md 中的链接 [除名 (Removal)](./maintainer-role.md#7-removal-for-cause) 在使用新的中文标题（## 7. 强制除名 (Removal for Cause)）时，很可能无法正确解析；建议根据实际自动生成的 ID 更新片段，或者添加一个显式锚点，以确保链接保持稳定。
• 新的 状态-权限映射 表中，将 除名 (Removal) 这一行描述为「7 天内申诉复核通过可恢复」，但 maintainer-role.md 中的详细流程同时说明 7 天后不再接受申诉；建议统一表格和对应章节中的表述，使在申诉窗口期结束后的状态为最终/不可逆这一点更加明确。

Prompt for AI Agents

Please address the comments from this code review:

## Overall Comments
- The link `[除名 (Removal)](./maintainer-role.md#7-removal-for-cause)` in `access-control.md` likely won’t resolve correctly with the new Chinese heading (`## 7. 强制除名 (Removal for Cause)`); consider either updating the fragment to match the actual auto-generated ID or adding an explicit anchor to keep the link stable.
- The new `状态-权限映射` table describes the `除名 (Removal)` row as '7 天内申诉复核通过可恢复', but the detailed flow in `maintainer-role.md` also states that appeals are not accepted after 7 days; consider aligning the wording between the table and the section to make the final/irreversible nature of the state after the appeal window explicit.

## Individual Comments

### Comment 1
<location path="docs/governance/access-control.md" line_range="82" />
<code_context>
+| :--- | :--- | :--- | :--- | :--- |
+| 正常维护者 | ✔ | ✔ | 入职 / 恢复 | 主动退出 / 休眠 / 除名 |
+| 休眠 (Dormant) | ✘ | ✔ | 180 天无协作轨迹 | 提交 PR / Issue 留言 |
+| [除名 (Removal)](./maintainer-role.md#7-removal-for-cause) | ✘ | ✘ | 裁决表决通过 | 7 天内申诉复核通过可恢复 |
+| 荣誉成员 (Emeritus) | ✘ | ✔（历史署名） | 主动退出 | — |
\ No newline at end of file
</code_context>
<issue_to_address>
**issue (bug_risk):** Double-check the internal link anchor for the "强制除名" section.

Because the heading is `## 7. 强制除名 (Removal for Cause)`, many Markdown engines will include the Chinese characters in the generated ID (e.g. `#7-强制除名-removal-for-cause`) rather than `#7-removal-for-cause`. Please confirm the actual ID in your target renderer and update this link to match so the anchor works correctly.
</issue_to_address>

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{帮助我变得更有用！请在每条评论上点击 👍 或 👎，我会根据这些反馈改进对你们的评审。}

Original comment in English

Hey - I've found 1 issue, and left some high level feedback:

• The link [除名 (Removal)](./maintainer-role.md#7-removal-for-cause) in access-control.md likely won’t resolve correctly with the new Chinese heading (## 7. 强制除名 (Removal for Cause)); consider either updating the fragment to match the actual auto-generated ID or adding an explicit anchor to keep the link stable.
• The new 状态-权限映射 table describes the 除名 (Removal) row as '7 天内申诉复核通过可恢复', but the detailed flow in maintainer-role.md also states that appeals are not accepted after 7 days; consider aligning the wording between the table and the section to make the final/irreversible nature of the state after the appeal window explicit.

Prompt for AI Agents

Please address the comments from this code review:

## Overall Comments
- The link `[除名 (Removal)](./maintainer-role.md#7-removal-for-cause)` in `access-control.md` likely won’t resolve correctly with the new Chinese heading (`## 7. 强制除名 (Removal for Cause)`); consider either updating the fragment to match the actual auto-generated ID or adding an explicit anchor to keep the link stable.
- The new `状态-权限映射` table describes the `除名 (Removal)` row as '7 天内申诉复核通过可恢复', but the detailed flow in `maintainer-role.md` also states that appeals are not accepted after 7 days; consider aligning the wording between the table and the section to make the final/irreversible nature of the state after the appeal window explicit.

## Individual Comments

### Comment 1
<location path="docs/governance/access-control.md" line_range="82" />
<code_context>
+| :--- | :--- | :--- | :--- | :--- |
+| 正常维护者 | ✔ | ✔ | 入职 / 恢复 | 主动退出 / 休眠 / 除名 |
+| 休眠 (Dormant) | ✘ | ✔ | 180 天无协作轨迹 | 提交 PR / Issue 留言 |
+| [除名 (Removal)](./maintainer-role.md#7-removal-for-cause) | ✘ | ✘ | 裁决表决通过 | 7 天内申诉复核通过可恢复 |
+| 荣誉成员 (Emeritus) | ✘ | ✔（历史署名） | 主动退出 | — |
\ No newline at end of file
</code_context>
<issue_to_address>
**issue (bug_risk):** Double-check the internal link anchor for the "强制除名" section.

Because the heading is `## 7. 强制除名 (Removal for Cause)`, many Markdown engines will include the Chinese characters in the generated ID (e.g. `#7-强制除名-removal-for-cause`) rather than `#7-removal-for-cause`. Please confirm the actual ID in your target renderer and update this link to match so the anchor works correctly.
</issue_to_address>

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[sourcery-ai]

issue (bug_risk): 请再次检查「强制除名」章节的内部链接锚点。

由于对应的标题是 ## 7. 强制除名 (Removal for Cause)，许多 Markdown 引擎会在自动生成的 ID 中包含中文字符（例如 #7-强制除名-removal-for-cause），而不是 #7-removal-for-cause。请在目标渲染环境中确认实际生成的 ID，并据此更新该链接，以确保锚点能正确工作。

Original comment in English

issue (bug_risk): Double-check the internal link anchor for the "强制除名" section.

Because the heading is ## 7. 强制除名 (Removal for Cause), many Markdown engines will include the Chinese characters in the generated ID (e.g. #7-强制除名-removal-for-cause) rather than #7-removal-for-cause. Please confirm the actual ID in your target renderer and update this link to match so the anchor works correctly.

[Mikuoso]

@yztkz