Clean up specs-testing repo files vs the dev-testing-round agent/scripts

[nathanacurtis]

Context

Surfaced during dev-testing round 0013. The specs-testing repo's files have drifted out of sync with what the /dev-testing-round skill, dev-testing-analyze agent, and scripts/test-round.sh actually expect. Several stale/overlapping artifacts caused confusion mid-round.

Cleanup needed

Manifests (most confusing):

• Multiple overlapping manifests in data/: manifest.anova-testing.md (what the wide round actually uses — 20 components), specs-testing.manifest.md (expected to be canonical but isn't), manifest.library.md, manifest.config-tests.md. Decide the canonical wide-round manifest and rename/consolidate so it's unambiguous. (Per-component fixtures like tests/0012/manifest.md and dsPage.manifest.md are scoped on purpose — leave those.)

Deprecated parity fixture:

• specs/anova-testing-plugin.yaml is dead (the /dev-testing-round Step-1 freshness gate still references it). Remove it and rewire the parity step to the current plugin-export workflow (tests/NNNN/plugin*.yaml).

Config layout:

• Root specs.config.yaml + data/ are now the live setup; reconcile vs the older configs/ propagation fixtures and the paths the scripts assume.

Agent/skill vs repo drift:

• Audit /dev-testing-round, .claude/agents/dev-testing-analyze.md, and scripts/test-round.sh against the actual repo layout; update the freshness gate, baseline logic, and artifact expectations.

instanceExamples parent mismatch (fixture data):

• Library file example instances live under Ready-made examples; the specs-testing file uses Examples. The root config's instanceExamples.parentNames: [Examples] will miss library-file instanceExamples. Reconcile fixture parent names vs config.

Outcome

A clean, documented mapping of "what the testing-round agent/scripts expect" ↔ "what's in the repo", with stale files removed.