terrymanu commented on PR #39626: URL: https://github.com/apache/shardingsphere/pull/39626#issuecomment-5453592754
### Result **Review Result: Mergeable** The separate Local Candidate Preflight output format has been removed. Every complete code review now uses the Formal Review structure. ### Evidence - Formal reviews now require `### Result`, one `Review Result` line, `### Evidence`, and `### Coverage`. - Local candidates use the same `Mergeable`, `Not Mergeable`, and `Review Incomplete` decisions as public PRs. - Local-only changes remain clearly separated from the public PR state in `### Coverage`. - PR Discussion Reply remains available only when explicitly requested. - The only remaining `Local Preflight` text is a negative canary assertion preventing that format from returning. - Skill validation: passed. - Harness tests: 46/46 passed. - Semantic policy canaries: 92/92 passed. - Source-read traces: 130/130 passed. - Critical regressions: none. - `AGENTS.md`: 25,920/26,000 bytes. ### Coverage Candidate type: authorized local candidate based on `3d06d0f17eb4e2a4edc244aae49a501f8ea4d5ff`. Reviewed changes: - `/Users/zhangliang/IdeaProjects/shardingsphere/AGENTS.md` → mandates Formal Review for every complete review or recommendation. - `/Users/zhangliang/IdeaProjects/shardingsphere/.codex/skills/review-pr/SKILL.md` → removes the Local Candidate Preflight mode, result labels, and output template. - `/Users/zhangliang/IdeaProjects/shardingsphere/.codex/skills/review-pr/references/evidence-access.md` → removes obsolete Local-mode terminology while preserving local-candidate evidence boundaries. - `/Users/zhangliang/IdeaProjects/shardingsphere/.codex/harness/agents/cases.toml` → adds a critical regression canary enforcing the formal structure and forbidding `Local Preflight`. The pre-existing untracked `__pycache__` directories were not modified. No Git commit was created. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
