docs: retire audit snapshots, reclassify depth-variant convention (#204 follow-ups)

[kyle-sexton]

Summary

The three follow-ups deliberately deferred out of #204 (recorded in its PR body), each decision-gated with the maintainer before editing. Net −341 lines; no plugin manifest, schema, or skill behavior touched.

#1 — Retire the audit snapshots

Delete docs/evals-coverage.md and docs/extensibility-contract-grading.md. They were hand-stamped, point-in-time records that drift the moment a plugin changes (the reorg already forced a two-layer temporal re-stamp).

Retire over generate. The durable policy already lives in docs/MIGRATION-PLAYBOOK.md — the warrant rule + consumer-verify recipe ("Evals — warrant policy and consumer-verify recipe") and the four-seams contract ("Extensibility contract v2.1"). A generator could derive only eval presence (a live glob) — the minority of one doc and none of the other; class, contract grades, and medley program state stay irreducibly hand-graded or externally-owned. Generating only the presence slice yields a half-generated hybrid that still drifts on its biggest surface. Retire is the clean fit.

Gaps captured first. Two warranted-but-unowned eval gaps were recorded only in the retired snapshot (verified still live against the tree): context7/setup and planning/wayfind. Filed durably before deletion:

• melodic-software/medley#1537 — evals(context7/setup)
• melodic-software/medley#1538 — evals(planning/wayfind)

Inbound pointers updated: README doc-index (2 bullets removed) and the playbook's evals section (now states on-demand verification instead of pointing at a deleted snapshot). No dangling references remain (repo-wide grep clean).

#2 — Reclassify the depth-variant convention tension

The playbook stated a depth/intensity variant "takes an argument, never a sibling," yet discovery's explore-deep / research-deep ship as sibling skills. Inspection shows they are structural, not depth:

• explore-deep — context: fork + agent: general-purpose: a distinct execution topology (isolated forked subagent), declared in frontmatter, not expressible as a runtime argument.
• research-deep — a dispatcher to the heaviest isolated tier (workflow engine, forked subagent, or inline fallback), with its own body and auto-invocation description.

The convention needed no exception — it needed a sharper structural/depth test. Amended to classify execution tier as a structural axis (sibling) and bind the -deep suffix to that axis, so the naming no longer reads as a violation and a future reader does not re-flag it. A true effort knob on one execution path still takes an argument. No skills renamed.

#3 — README revisit-condition dedup

Assessed, closed no-op. The coupling flagged in #204 is a documented, directional SSOT+index: docs/CATALOG-TAXONOMY.md (L71–73) declares plugin-scoped revisit conditions are owned by each plugin's README and the taxonomy "Trigger register" lists them "only as pointers." The READMEs are the single owners of genuine plugin-specific rationale; the register summarizes them. Nothing to dedup. Confirmed none of the three sections cross-names the taxonomy doc.

Verification

• scripts/validate-plugins.sh: pass (all manifests + strict catalog sync)
• scripts/run-plugin-tests.sh: 7 passed, 0 failed
• markdownlint-cli2: 0 errors on both touched markdown files
• Repo-wide grep for the retired doc names: no remaining references

Note (not in this PR)

docs/hook-migration-audit.md is the same "point-in-time audit" genus as the two retired here. Left untouched; flagged for a consistency decision in a later pass.

🤖 Generated with Claude Code

https://claude.ai/code/session_0163dXPBdRYFpx4wTtS648tE