Codex adaptation boundary

This mirror maintains only the explicitly selected project-local verification skill under .agents/skills/verify-*/. The coordinator owns the live pass and proof-orchestrator selects its proof level. Source readers may use native bounded delegation when exposed, but the sequential fallback is only a declared path here, not a live proof. A missing or unhealthy target is blocked with the attempted route and prerequisite. The maintenance flow never edits product code or global skills, and it never opens, publishes, or merges a PR without separate authorization. The bounded fixture reruns the real disposable CLI, performs syntax/version/health Doctor, records one source-wave result per feature, reconciles only its own feature files, cleans app state, persists before/after evidence, and reports FIXTURE_ONLY; a separate disposable web fixture was also re-driven through the native Codex in-app browser after drift removal with accessibility-tree and screenshot evidence. It does not claim live target coverage, PR, or native host activation.

Maintain a verification skill

A feature map rots the moment the app changes. This skill is the upkeep loop for a skill generated by /create-verification-skill (or any project-local verification skill with a feature map). The unit of rigor is the feature, not every sentence: cover every feature file from source and exercise every feature live, without terminalising every bullet.

Outcomes

Pick one, and say which:

• clean — every feature got source and live coverage; nothing worth shipping. No branch, no PR.
• changed — one PR ships proven doc, harness, or map corrections.
• blocked — coverage could not finish or a proven fix could not ship safely. Say exactly what blocked it.

Edit scope

Only edit the verification skill's own directory (its SKILL.md, features/, and any harness scripts it owns). Never edit product code during a run: a behavior the map describes that the app no longer does is either doc drift (fix the map) or a product regression (report it, don't paper over it in docs).