v0.6.1

Highlights

• Adds the product-workspace archetype for cooperating applications that jointly implement one product and share domain, protocol, client, or SDK foundations.
• Defines facade as an optional Cargo crate role, permits at most one facade, and rejects facade-only repositories with nothing to aggregate.
• Clarifies the selection boundary between application, application-collection, product-workspace, hosted-service, platform-workspace, and runtime-composition.
• Standardizes application-owned protobuf schemas on apps/<app>/contract/proto and keeps product-wide schemas in crates/proto.
• Requires application collections and product workspaces to declare at least two application sublanes.
• Documents the complete directory vocabulary and closed Cargo crate-role vocabulary, with self-checks preventing policy/documentation drift.

Consumer migration

• Vendor the 0.6.1 core.mjs byte-for-byte.
• Set the vendored-core version to 0.6.1 and pin remote CI to this release commit by full immutable SHA.
• Replace apps/<app>/contracts/proto with apps/<app>/contract/proto in application collections.
• Use product-workspace when applications share product semantics or a canonical protocol; use application-collection only when applications remain independently bounded.
• Declare a crate as facade only when it is a thin curated consumer surface; preserve each consumer repository’s existing licensing configuration.