chore: sync template files and configuration

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

Author: Jonathan D.A. Jewell

.github/PROVEN-INTEGRATION.md

@@ -0,0 +1,28 @@
+# proven Integration Plan
+
+This document outlines the recommended [proven](https://github.com/hyperpolymath/proven) modules for FireFlag.
+
+## Recommended Modules
+
+| Module | Purpose | Priority |
+|--------|---------|----------|
+| SafeStateMachine | State machines with invertibility proofs for feature flag transitions | High |
+| SafeOrdering | Temporal ordering with causality proofs for flag change history | High |
+| SafeCapability | Capability-based security for flag access control | Medium |
+
+## Integration Notes
+
+FireFlag as a feature flag system benefits from formally verified state management:
+
+- **SafeStateMachine** is perfect for modeling feature flag states (enabled/disabled/percentage rollout/etc.). The `ReversibleOp` type ensures flag changes can be safely rolled back, and `GuardedTransition` enforces pre/post conditions on state changes.
+
+- **SafeOrdering** tracks the history of flag changes with verified causality. When debugging which flag change caused an issue, the happens-before relation provides definitive ordering of events.
+
+- **SafeCapability** controls who can modify which flags. The `attenuate` function ensures permissions can only be reduced, never escalated, and `AuditedStore` logs all flag access.
+
+Together these modules provide a feature flag system where state transitions are provably correct and reversible, with full audit capability.
+
+## Related
+
+- [proven library](https://github.com/hyperpolymath/proven)
+- [Idris 2 documentation](https://idris2.readthedocs.io/)