guard-maturitylisted

# Guard Maturity Hook Maturity Model fitness scoring for the push guards (M2/M3/M4/M5 and any future siblings built on `push_guard_base.py`). Hooks accumulate without measurement: a guard ships, gets some intercepts, and stays forever even if it has stopped catching anything real or has started blocking on a stale rule. This skill is the measurement: real intercept counts feed real tier assignments, and the tier dictates whether a guard gets kept, promoted, or pruned. ## When to use - **Periodic review** (recommended every 30 days once telemetry is flowing): run the report, prune Inert guards, promote Proficient ones, remove Harmful ones immediately. - **Before adding a new guard**: confirm no existing guard already covers the case at a higher tier. - **Pre-release**: include the report in the release notes so the team can see which guards are paying for themselves. ## What it does 1. Calls `python3 build/scripts/aggregate_guard_intercepts.py` against `.agents/telemetry/` (or stdin if no telemetry has landed yet). 2. Pipes the JSON summary into `python3 build/scripts/classify_guard_maturity.py`. 3. Prints a table (one row per guard) sorted by tier severity: `Harmful` first, then `Inert`, then `Budding`, `Growing`, `Mature`, `Proficient`. ## Tier definitions | Tier | Age | Intercepts | Fitness | Action | |---|---|---|---|---| | Harmful | any | ≥3 | < -0.02 | Remove immediately | | Proficient | ≥60 days | ≥10 | ≥ +0.02 | Promote, keep watching | | Ma