v4.5.0 — Chronos × Native /goal Integration

Native /goal ("Set a goal Claude checks before stopping") landed in Claude Code and Codex. This release reframes Chronos as a discipline layer on top of /goal.

• Reframed as a /goal wrapper — Chronos layers its discipline on top of /goal (the persistence engine) instead of owning the loop: verification gate, priority cycle, audit log
• Goal-statement model (no auto-invocation) — Chronos cannot call /goal programmatically (no slash-command tool), so it generates a goal statement with its rules baked in and the user sets /goal once. The earlier "auto-delegation" framing was an impossible fiction and was removed
• 3-tier persistence fallback — /goal (tier 1) -> Stop hook / notify (tier 2) -> direct loop (tier 3). Hooks preserved so Chronos keeps working on Gemini / older builds (parity)
• Hard guard against hook collision — setup-loop --goal-mode removes any existing loop-state.md across .claude/.codex/.chronos, so the Stop hook has nothing to re-inject. Collision is impossible at the code level, verified with isolated .ps1/.sh tests
• Codex vs Claude /goal differences documented — same entry syntax, different completion judging (Codex runs commands directly; Claude's evaluator only sees chat output). Goal statements now require "print the verification result to chat" + a turn cap for cross-CLI compatibility