safeguard

# safeguard ## Purpose Build safety nets before any refactoring begins. Safeguard creates characterization tests that capture current behavior, adds boundary markers to distinguish legacy from new code, freezes config files, and creates git rollback points. Nothing gets refactored without safeguard running first. <HARD-GATE> Characterization tests MUST pass on the current (unmodified) code before any refactoring starts. If they do not pass, safeguard is not complete. </HARD-GATE> ## Called By (inbound) - `rescue` (L1): Phase 1 SAFETY NET — build protection before surgery - `surgeon` (L2): untested module found during surgery ## Calls (outbound) - `scout` (L2): find all entry points and public interfaces of the target module - `test` (L2): write and run characterization tests for the target module - `verification` (L3): verify characterization tests pass on current code ## Cross-Hub Connections - `surgeon` → `safeguard` — untested module found during surgery ## Execution Steps ### Step 1 — Identify module boundaries Call `rune:scout` targeting the specific module. Ask scout to return: - All public functions, classes, and exported symbols - All files that import from this module (consumers) - All files this module imports from (dependencies) - Existing test files for this module (if any) Use `Read` to open the module entry file and confirm the public interface. ### Step 2 — Write characterization tests Create a test file at `tests/char/<module-name>.test.ts` (or ...