session-startlisted

## First-run onboarding (if present) !`test -f ONBOARDING.md && cat ONBOARDING.md || true` If the block above contained text, this is the first session of a freshly bootstrapped project — present the orientation to the operator, then delete the file with the Bash tool: `rm ONBOARDING.md`. The file must not persist into the next session. The `|| true` makes this a no-op on projects without the file (including mavericks itself). ## Mid-session handoff (if present) !`test -f HANDOFF.md && cat HANDOFF.md || true` If the block above contained text, read it carefully — it carries mid-session context from the previous agent turn (in-progress decisions, pending actions, warnings). Then delete the file with the Bash tool: `rm HANDOFF.md`. The file must not persist into the next session. ## Current Mavericks state !`./scripts/mavp-operator --agent` --- Read the JSON above. Key fields: - `stage` — where the initiative currently stands - `active_slices` — what is in flight and who owns it - `next_action` — what to do next - `blocker` — stop if non-null, resolve blocker first - `wave` — current wave number - `wave_session` — session counter within the wave (may be absent or null) - `permission_mode` — the configured Claude Code permission mode - `UPDATE_AVAILABLE` — framework-version notice, a self-describing sentence (may be absent when versions match) - `must_read` — files changed since the previous close-session commit, plus context_docs declared by in-flight tasks (may be abs