Document branch-model alignment\n\nCo-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Author: Copilot Scribe

.squad/agents/ripley/history.md

@@ -34,3 +34,9 @@
 - Implementation ready for validation
 
 **Status:** All M1 definition and implementation work complete. Decisions merged to decisions.md. Ready for M2 planning.
+
+## Team Update (2026-04-14 Branch Model Alignment)
+
+- Confirmed the C# demo branch model expects `master`, `milestone-1`, and `milestone-2` as the active public branches at this stage.
+- Locked `milestone-1` to the existing public M1 baseline commit so the teaching snapshot stays stable.
+- Kept `milestone-2` and `master` aligned on the squad-enabled branch state so the team can operate there without starting Milestone 2 feature work.

.squad/decisions/inbox/ripley-branch-model.md

@@ -0,0 +1,11 @@
+# Ripley: Branch model alignment for public milestones
+
+## Decision
+
+Use the existing public Milestone 1 baseline commit for `milestone-1`, and keep both `milestone-2` and `master` on the squad-enabled follow-up state that adds only squad-operational support files.
+
+## Why
+
+- This matches the C# demo naming model for the active branches at this point in the lecture arc.
+- It preserves a clean public M1 teaching snapshot on `milestone-1`.
+- It gives the squad a ready-to-work `milestone-2` branch without pulling in Milestone 2 feature implementation.