Copilot instructions

1# Repository Baseline
2 
3Prefer explicit behavior and readable boundaries, and keep the repository coherent as those behaviors evolve.
4 
5Keep changes scoped, but do not leave clear downstream drift behind when the follow-through is small and certain.
6 
7Default closure policy: reconcile small and certain downstream follow-through in the current pass. Carry broader, riskier, or less certain follow-through forward explicitly.
8 
9## Follow-Through Triggers
10 
11When a change shifts behavior or expectations that other surfaces encode, review those downstream surfaces for drift.
12