Publish two independent-app reuse evidence for governed capabilities

[enricopiovesan]

Problem

Traverse has composition evidence within a reference workflow, but not a public demonstration that the same published governed capabilities serve two independent products with contract-level configuration.

Scope

Add or adapt two independently useful reference apps that consume at least two shared published capabilities without copying their business logic.

Definition of done

• Two separately runnable reference apps use the same pinned published capability versions from the registry.
• Each app has a distinct product goal and only contract-level configuration differs where appropriate.
• Both apps validate and execute through supported public consumption paths, with reproducible commands and safe trace evidence.
• A compatible capability version upgrade and a deprecated-version path are demonstrated across both consumers.
• The evidence identifies app-specific shell/glue versus shared governed capability code.
• The documentation gives a concrete public-vs-app-private capability decision rule.
• CI prevents the examples from substituting copied business logic for the shared capabilities.

Dependencies

Requires published registry artifacts suitable for both apps.

[enricopiovesan]

Governance audit

No new spec or ADR is required. This is evidence work under existing publication/consumption policy. It must use published artifacts and supported public paths; any requested new registry lifecycle, promotion, or discovery behavior becomes a separately governed registry issue.