Define shared immutable capability release and two-app reuse contract

[enricopiovesan]

Summary

Choose one already-published Traverse capability release and two independently scoped App-References applications that will consume that exact immutable artifact and contract. Record the supported registry/host route and exact pinning rule that subsequent tickets implement.

Why

Traverse #1168 requires evidence of actual cross-product reuse, rather than catalog references, copied business logic, or two consumers resolving different releases. This ticket establishes a reproducible, reviewable baseline before either consumer is changed.

Scope

• Select one public capability whose semantics fit two distinct user-facing app workflows.
• Select two existing independent applications, each with a separate application manifest/configuration boundary.
• Define the exact namespace, capability id, artifact digest, contract version, and immutable release version both will consume.
• Define the supported registry sync/prepare and host resolution path for each app.

Definition of Done

• Decision record identifies the chosen capability and the two applications, including their distinct user-facing purposes.
• The selected release is publicly published and immutable; its capability id, semver version, contract version, and artifact digest are recorded.
• Each app has a documented manifest/configuration boundary and an explicit supported registry_ref or equivalent public registry reference to the same exact release; no floating range may resolve different artifacts.
• The record identifies the public registry sync/prepare, verified-cache, registration, and execution host paths used by each app.
• The record states that neither application copies the capability business logic or embeds a private/local substitute.
• Any unavailable platform/runtime prerequisite is linked as a concrete upstream dependency; no fake registry, cache, or resolution path is introduced.

Validation

• Independently resolve the pin from a fresh workspace for each selected app and compare capability id, release version, contract version, and digest; all four values match.
• Review both manifests/configuration files to confirm distinct application identities and no local implementation of the shared capability.

Non-goals

• Changing Traverse registry lifecycle policy.
• Implementing new runtime resolution behavior.
• Claiming two-app reuse before the execution evidence ticket is complete.

Downstream

Blocks the two-app execution and lifecycle-evidence tickets for Traverse #1168.