docs: re-block registry-ref on Traverse dual-mode gap

[enricopiovesan]

Summary

Attempted to implement Project 2 registry-ref-starter-process. Cannot switch the process component to registry_ref yet: Traverse main still requires contract_path on component manifests (spec 054 FR-007 not wired). Registry seed + registry sync are Done; ticket re-blocked with the real gate.

Governing Spec

• Traverse 054-public-scope-registry-ref FR-007
• docs/production-packaging.md consumer contract

Project Item

Project 2: registry-ref-starter-process — Status Blocked (Agent Unassigned)

Definition of Done

• Claimed and investigated Ready flip
• Confirmed Traverse still requires contract_path (cannot ship manifest switch)
• Board Note + draft Spec/Blocked by updated
• AGENTS / plan / packaging docs state the real remaining gate

Validation

# Traverse origin/main: WasmComponentManifestSerde.contract_path is still required String
gh project item-list 2 --owner traverse-framework --format json --limit 300 \
  --jq '.items[] | select(.note != null and (.note | test("registry-ref"))) | {status, note}'