521 B
521 B
2026-02-13
- Canonical OpenSpec sync files follow a stable template:
## Purpose+## Requirements; preserving this structure keeps delta-to-main merges consistent. - Conflict-heavy capability merges are safest when newest delta text updates requirement sentence semantics while older non-conflicting scenarios are retained.
- For policy/footer capabilities, behavior precedence can flip navigation contracts (page routes -> modals) while still preserving visibility and accessibility scenarios from older deltas.