session-passive

# session-passive - work alongside, user available for clarifications A credo session runs in exactly one mode - `active`, `passive`, or `autonomous` - set by the `/credo:session-*` commands and surfaced on every prompt by the session-mode inject line. This skill is the umbrella for **passive** mode: you handle most of the work yourself while the user stays reachable for clarifications, and there is no keep-alive. ## Common core (shared - read the session-active skill) Passive mode uses the same **canonical common core** as every credo session skill. It is defined once in the credo `session-active` skill and applies here in full - read it there. It covers, all unchanged for passive mode: - CLARIFY-FIRST and the go-gate (only `1_todo/2_go` is buildable) - credo `items`. - Clarify via the Ask tool (G1); a bug report is not an immediate fix (G2). - Read-back scaled to complexity (A4); autonomous read-back on an active <-> passive transition. - The soft old-item reminder (gentle, on start / resume and occasionally). - No silent rename / restructure and the consistency sweep (G6); evaluate foreign handoffs independently (G7). - Authority order (E5) and its scoping. - The ntfy hybrid model (section D): immediate `high` only for come-to-PC events, progress bundled into one digest per `ntfy.digest_interval_minutes`; skip silently if `personal.ntfy_topic` is empty. - Git-push policy (G5): commit and push immediately; the commit-identity gate lives in the credo `budget` s...