spec: adopt extraction-compatibility spec (014), amend 013 for a 20th spec it missed

[enricopiovesan]

Summary

Supersedes Codex's #58/#59 (closed) with a verified, much smaller design. Full investigation and reasoning: docs/decision-log.md entry 33.

The extracted crate resolves its own governing-spec registry at compile time, relative to its own directory. Physically relocating crates/traverse-registry/ from traverse to this repo changes which approved-specs.json that resolves to, silently breaking two runtime checks (approved_spec_registry_contains, is_governed_artifact_path) for entirely unchanged pre-existing behavior.

A full audit of the crate's compiled source (every file, not a guess) found every literal spec-ID string it hardcodes — 13 total:

• 10 real, currently-approved-in-traverse legacy IDs get a minimal passthrough entry here (specs/014-extraction-compatibility/spec.md FR-001): 002-capability-contracts, 005-capability-registry, 007-workflow-registry-traversal, 011-event-registry, 037-semver-range-resolution, 039-connector-plugin-architecture, 043-module-dependency-management, 044-application-bundle-manifest, 046-public-cli-app-registration, 055-registry-sync.
• 999-unapproved-spec is a deliberate negative-test fixture — explicitly excluded (FR-003).
• 015-metadata-graph and 026-federation-registry-routing don't exist in traverse's own current governance file at all — already-broken, pre-existing traverse-side bugs, unrelated to this extraction. Deliberately left unregistered (adding entries for IDs that were never valid would change behavior, not preserve it).

Also found (and fixed, licensed by 013's own FR-003 re-verification requirement): 002-capability-contracts also governs the crate and was missing from 013-inherited-registry-governance's source-specs table (a 20th spec, missed in the original 19-spec audit).

Zero Rust source changes. Zero new alias/retirement lifecycle — this repo's existing 013 precedent (inherited behavior preserved as-is, not re-authored) extends cleanly to this narrower problem.

Approved directly in this PR per decision 24 (co-brainstormed specs are approved by the brainstorm itself) — this session's /brainstorm with the repo owner is the approval event.

Governing Spec

• 001-registry-foundation

Project Item

• Relates to Extract traverse-registry crate + governing specs from traverse into this repo #9 (extraction-compatibility prerequisite now resolved)
• Closes spec(registry): govern extraction compatibility bridge #58
• Closes feat(registry): implement extraction compatibility bridge #59

Definition of Done

• specs/014-extraction-compatibility/spec.md added, approved
• 10 legacy-ID passthrough entries added to specs/governance/approved-specs.json, each with a unique stub file under specs/014-extraction-compatibility/legacy-ids/
• 013-inherited-registry-governance amended (licensed by its own FR-003) to add 002-capability-contracts
• 999-unapproved-spec, 015-metadata-graph, 026-federation-registry-routing deliberately excluded
• Decision-log entry 33 records the full investigation and decision

Validation

• python3 scripts/ci/capability_validation.py — passed
• python3 -m unittest scripts/ci/tests/test_capability_validation.py -v — 9/9 passing
• Local replica of the spec-alignment registry-validation logic (duplicate id/path, approved/immutable, non-empty governs, path exists on disk) — no failures across all 24 entries
• bash scripts/ci/spec_alignment_check.sh (run in CI against this PR)