Swift Cycle v1.2.0 — Governance Boundaries and Shared Knowledge
Swift Cycle v1.2.0 expands lightweight project governance while keeping simple, local work fast.
New capabilities
- Knowledge Promotion — moves durable commitments, decisions, constraints, and verified evidence into responsibility-appropriate shared assets.
- State Separation — separates composite lifecycle states without imposing a fixed status schema.
- Governance Baseline — records a proportional before-state for non-trivial governance and cross-boundary work.
- Commit Boundary Planning — defines coherent, independently reviewable commit scopes before staging mixed or ordered changes.
- Source/Runtime Boundary — keeps source, artifact, runtime, and consumer claims independently evidenced and authorized.
Documentation
- Updated the English and Simplified Chinese README capability descriptions.
- Clarified that governance capabilities are trigger-based and do not burden simple changes.
- Refreshed the product narrative around Loop Engineering and evidence-backed delivery.
Boundaries
- No
PROJECT_STATE.md. - No fixed lifecycle schema.
- No new runtime dependencies, MCP servers, Registry publication, or external services.
- Existing installation and explicit invocation behavior remain unchanged.
Validation
- OpenAI
quick_validate.py: PASS gh skill publish --dry-run: PASS- Bilingual README capability and local-link checks: PASS