Prove two independent apps execute one pinned published capability release

[enricopiovesan]

Summary

Configure and execute two independently scoped applications against the exact shared immutable capability release selected by the reuse-contract ticket. Publish reproducible evidence from supported registry and host paths.

Why

This is the central missing proof for Traverse #1168: current consumers resolve different releases, which does not demonstrate reusable-platform behavior.

Depends on

• Define shared immutable capability release and two-app reuse contract (created with this work).
• Any explicit runtime or host prerequisite it identifies.

Definition of Done

• Both chosen applications retain distinct application manifests/configuration boundaries and distinct user-facing workflows.
• Each application resolves and consumes the same pinned published capability artifact and contract through a supported public registry/host path.
• Each app has a reproducible fresh-workspace setup that performs required registry sync/prepare, verified-cache materialization, registration/adoption where applicable, and execution without a local business-logic copy.
• An automated smoke/evidence command executes both apps and records: app version/id, manifest/config reference, capability id, immutable release version, contract version, artifact digest, registry source, host path, execution result, and trace/execution identifiers where exposed.
• The evidence asserts equality of the shared capability id, release version, contract version, and digest across both consumers, and fails on a mismatch.
• Execution requires no live network fetch after the supported preparation step and fails closed with an actionable error when required verified state is absent.
• Documentation links the repeatable command and captured evidence to Traverse #1168.

Validation

# Exact commands belong in the implementation documentation.
# Run each consumer from a fresh workspace, then run the combined evidence command.
# The combined command must exit non-zero if either app resolves a different release/digest
# or executes a copied/local capability instead of the published artifact.

Non-goals

• A shared UI, host platform, or team.
• Static manifest/catalog references without real resolution and execution.
• Version upgrade or deprecation behavior (tracked separately).

Outcome

Produces the two-app immutable-release execution evidence required by Traverse #1168.