Problem / why
The two-component example added in V4 should become a permanent member of the fleet so the
schema-2 multi-component path is continuously exercised on every release-candidate fleet run,
not just once at feature time.
Scope (firm intent)
- Promote the V4 two-component example to a permanent fleet coverage case, exercising the full
lifecycle (versioning, promotion, hotfix, rollback, release) per component.
Files / areas touched
- Fleet configuration and the example repo's suite.
Tests and coverage required
- The example repo runs as part of the standard fleet rotation and stays green.
Acceptance criteria
- The multi-component example is a permanent fleet case covering the full per-component
lifecycle.
Dependencies
Blocked by R4 and X1 (so the permanent case covers the complete shipped surface).
Problem / why
The two-component example added in V4 should become a permanent member of the fleet so the
schema-2 multi-component path is continuously exercised on every release-candidate fleet run,
not just once at feature time.
Scope (firm intent)
lifecycle (versioning, promotion, hotfix, rollback, release) per component.
Files / areas touched
Tests and coverage required
Acceptance criteria
lifecycle.
Dependencies
Blocked by R4 and X1 (so the permanent case covers the complete shipped surface).