feat(review): require repository review-skill readiness

[ss-o]

Outcome

Canonical review guidance and the documentation/plugin pilots are delivered. Every repository-health evaluation must assess review-skill presence, validity, source currency, drift, suitability, and runtime-use evidence separately.

Confirmed session scope

The maintainer explicitly excluded wider rollout and requested completion of the remaining session work. Scope is limited to canonical organization policy, health-review procedures, MCP context guidance, and the wiki and zsh-fancy-completions pilots. No remaining organization-wide installation batch is required under this issue, and this closure does not claim every active repository is covered.

Delivered

• Canonical skill and mandatory health-readiness policy: feat(review): require repository review-skill readiness #608.
• Conditional MCP context profiles and evidence guidance: feat(review): add MCP context profiles and evidence guidance #611, merged as e1f8f6c1c9dd61e87f2e5f44ef6285992b8b892d.
• Wiki pilot: feat(review): pilot MCP-aware skill and read-only health audits wiki#915, merged as 11ddc620baebe18b05915fc15d1a880c1a6b434f.
• Plugin pilot: feat(review): pilot canonical MCP-aware review skill zsh-fancy-completions#65, merged as 151c60f1a68335fd26cf4cbcdb739a14994ce96c.

Both native pilots are pinned to the canonical merge commit. Their published main copies match repeated native installations after repository formatting. The wiki health skill defaults to read-only review; the portable review skill selects checks from each repository's actual components and contracts.

Completion criteria for the confirmed scope

• Publish the canonical review skill and mandatory health-readiness policy.
• Deliver both pilots with verified immutable-source provenance and canonical content.
• Assess documentation/plugin suitability and record runtime evidence separately. Explicit Copilot skill attribution and hosted MCP calls remain unverified.
• Include review-readiness checks in new-repository and recurring health procedures.
• Record the maintainer's exclusion of wider rollout and retain the native delivery history.

Verification and limitations

All final pre-merge checks passed. Post-merge checks on the three public merge commits also passed, including wiki deployment and Cloudflare Pages. Both canonical guidance headings were verified on main. Earlier missing-link findings were resolved by canonical publication and native reinstall.

Hosted MCP configuration drafts and acceptance steps are prepared. Settings were not applied because the execution environment has no settings editor. The earlier Cloudflare documentation MCP initialization returned HTTP 403; hosted discovery and invocation remain unverified. Optional provider activation is not a clean-health requirement, and installation does not prove runtime use.

Closure

Closed and Done for the confirmed policy-and-pilots scope. Wider rollout is explicitly excluded by the maintainer, with no new scheduler or unattended installer. The original 92-active-repository inventory is historical and is not evidence of current coverage. Related recurring-operations coordination: #485.

[ss-o]

Agent handoff

Status: In progress; pilot publication prepared
Repository: z-shell/.github
Tracker/Issue: #606; recurring-operations coordination #485

Current state

The canonical policy and skill are published in #608. Pinned pilot PRs are z-shell/wiki#915 and z-shell/zsh-fancy-completions#65. Native sub-issues have verified Project 28 triage fields. The downstream issues are blocked by #607 because the required runbook anchor must reach main before their merge.

Verification

• Public local validation: 204 tests plus policy/decision validators and relevant linters passed.
• Hosted checks passed on all three public pilot PRs.
• Native provenance and repeated formatted installations were verified; both pilots use source commit db20047dd6f9aba014fadc8152b60452f20ef037.
• Copilot reviewed all pilots. Confirmed canonical validation/routing findings were addressed; explicit skill attribution remains unverified in returned comments.

Remaining delivery

The initial inventory recorded 92 active default branches without the skill and one archived repository excluded. Publishing pilot branches does not change default-branch coverage. No merge or bulk rollout was performed.

Next steps

1. Review and approve canonical PR feat(review): require repository review-skill readiness #608 for merge.
2. Verify the published procedure and complete both downstream pilots.
3. Confirm runtime attribution, then deliver the remaining catalogued repositories and the wider active organization in scoped batches with current branch/fork checks.