First deployment

.sisyphus/notepads/sync-p12-p16/decisions.md

@@ -0,0 +1,5 @@
+## 2026-02-13
+
+- Applied chronological conflict resolution order exactly as requested: p12 -> p13 -> p14 -> p15 -> p16, with p16 language/behavior taking precedence on overlapping requirement text.
+- Created new capability specs in canonical form for all delta-marked additions missing from `openspec/specs/*`.
+- Kept pre-existing requirements/scenarios unless superseded by explicit newer behavioral changes (e.g., footer policy navigation replaced with modal disclosure behavior).

.sisyphus/notepads/sync-p12-p16/issues.md

@@ -0,0 +1,3 @@
+## 2026-02-13
+
+- Markdown LSP diagnostics are unavailable in this workspace (`No LSP server configured for extension: .md`), so spec-file verification relied on structural diff review instead of LSP validation.

.sisyphus/notepads/sync-p12-p16/learnings.md

@@ -0,0 +1,5 @@
+## 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.

.sisyphus/notepads/sync-p12-p16/problems.md

@@ -0,0 +1,3 @@
+## 2026-02-13
+
+- None unresolved in the p12-p16 spec merge scope.