hook-bypass-reviewlisted

# hook-bypass-review ## Purpose Periodically audit `work/current/hook-bypass.md` for entries that should be removed (expired, completed, or never followed up) and patterns that suggest a hook is too aggressive rather than the bypass being legitimate. Invoke before `yakos archive` (so stale bypasses don't roll into the archive) and weekly during long projects. ## Scope Reads only: - `work/current/hook-bypass.md` (the active bypasses) - `work/current/logs/<hook>.ndjson` (to confirm hook fire history) Writes nothing automatically — outputs a structured report the operator reviews. ## Automated pass Walk every `## bypass:<id>` entry in the Active entries section. For each: ```markdown ### bypass:<id> - **Hook:** <hook name from the entry> - **Created:** <ts> - **Expires:** <ts> - **Status:** - **EXPIRED** (Expires has passed) — should be removed - **STALE** (Created > 7 days ago, no Follow-up activity) — review - **ACTIVE** (within Expires) — fine - **Pattern check:** has this Scope been bypassed > 2 times in the last 14 days? - If yes → suggests the underlying hook is too aggressive for this project; recommend tuning the hook rather than repeating the bypass. Cite the previous bypass entries. - **Follow-up status:** does the Follow-up field describe a concrete action that's been done? - If no → the bypass is unaccounted for; surface to operator. ``` ## Manual pass Operator reads the report. For each EXPIRED entry: remove from hook-bypass.md (or