Separate example setup from synthetic test releases
This commit is contained in:
@@ -293,7 +293,16 @@ coverage.
|
||||
|
||||
## Issue 9: Separate synthetic bootstrap versions from maintained examples (P2)
|
||||
|
||||
Status: open. Category: broken adoption example and incomplete cutover guidance.
|
||||
Status: complete. Category: broken adoption example and incomplete cutover guidance.
|
||||
|
||||
**Completion:** Maintained module skeletons no longer pin synthetic releases.
|
||||
Example setup explicitly selects compatible released tooling and documents source
|
||||
verification in disposable checkouts. Workflow fixtures generate their synthetic
|
||||
declarations. Current-source tool registration and all three example profiles,
|
||||
including native version injection, pass offline; mapped launchers/workflows and
|
||||
tagged-tool retries retain isolated fixtures. Adoption and migration guidance
|
||||
cover coordinated tool/workflow upgrades and historical retries. The pending
|
||||
release notes record concrete example pins as normal version-selection work.
|
||||
|
||||
**Evidence:** All three maintained
|
||||
[multi-module declarations](../../examples/multi-module/) require ReleaseKit
|
||||
|
||||
Reference in New Issue
Block a user