Implement Component Model WIT host-capability activation

[enricopiovesan]

Goal

Implement Spec 135: a versioned component-wit-v1 execution path that validates declared Component Model WIT imports and resolves them only through explicitly activated target-local host bindings.

Definition of done

• Preserve all core-Wasm/WASI Host ABI v1 behavior and fixtures unchanged.
• Validate Component Model WIT metadata against exact required manifest imports.
• Implement registration, explicit activation, exact compatibility, target selection, trust/conformance evidence, deterministic errors, and redacted trace evidence.
• Add fake traverse:platform/recording-host@0.1.0 tests for status/start/stop/events, missing host, version mismatch, target mismatch, permission/background outcomes, and redaction.
• Document migration from core-Wasm and Callweave WIT identity.

Governing artifacts

• Spec 135-component-model-wit-host-capabilities v0.1.0
• ADR-0068
• Decision 79

Blocker

This ticket becomes Ready only after the governing-artifact approval PR merges.

[enricopiovesan]

Decision record

Question: Which already-governed tickets should move to Ready now?

Options considered:

• A — Both #1341 and #1242
• B — Only #1341
• C — Only #1242
• D — Neither until #1291 ADR lands

Recommendation: A

Decision: A — promote #1341 and #1242 to Ready now.

Why: Spec 135 + ADR-0068 + Decision 79 are Approved; needs-spec on this ticket is stale. #1242 is already no-spec-needed under Spec 520.

Consequences / governing-artifact changes:

• Remove needs-spec; add spec-complete
• Add to Project 1 if missing; set Status → Ready
• #1291 ADR + decision-log package lands as separate closeout (not a blocker for this Ready move)

[enricopiovesan]

Governing package for the Ready promotion is in the open ADR-0069 / Decision 82 PR on docs/issue-1291-single-role-service-type-adr.