pm

Active PM orchestrator. Manages which issues are being worked on across coding threads, tracks progress, and suggests next work.

Two entry modes, plus one posture that wraps either:

• Cold start (default): Scan GitHub state, suggest next 3-5 issues, enter orchestration loop.
• Resume: Read in-flight state from session files and continue where the previous PM left off.
• Day mode (/pm day), on top of either: after the entry mode finishes, stay running — the thread becomes the repo's standing worker and keeps looping between turns instead of stopping at the end of the turn. Step 2D owns it.

Parse $ARGUMENTS in this order — day tokens first (so they never fall through to the business goal), then the cleanup flag, then the mode:

• Day mode + its flags (strip each token as you read it):

  • day (its own whitespace-delimited word) or --run → DAY_MODE=true; otherwise false.
  • --tick → DAY_TICK=true. This is internal: only the Monitor armed in 2D.2 passes it. It implies DAY_MODE=true.
  • --day-generation <token> → TICK_GENERATION. Internal, always paired with --tick or --probe-wake.
  • --probe-wake → DAY_PROBE_WAKE=true. Internal: only the bounded probe Monitor armed in 2D.7 passes it, always with --day-generation. It implies DAY_MODE=true and routes straight to 2D.7's probe-fire handler — not to 2D.3's tick, which must not run while the board is parked.
  • --cadence Nm → DAY_CADENCE_MIN=N (default 5, range [1, 60]).
  • --max-pipeline-failures N → MAX_PIPELINE_FAILURES=N (default 3, range [1, 10]).

  Validate both as unsigned integers with [[ "$v" =~ ^[0-9]+$ ]] before range-checking, and reject anything failing either test — naming the rejected input and falling back to the documented default. The pattern test is not belt-and-braces: both values are interpolated into 2D.2's --set JSON payload and into 2D.3's shell arithmetic, so 2.5 or abc does not merely produce a bad cadence, it writes a malformed day object into session state that every later read then fails on.

• Cleanup escape hatch: if the remaining $ARGUMENTS contains the --no-clean flag or a bare fast token (its own whitespace-delimited word, e.g. /pm fast), set NO_CLEAN=true and strip that flag/token from the arguments before the checks below (so it is never read as a business goal); otherwise NO_CLEAN=false. NO_CLEAN=true suppresses the always-on Step 1C inline cleanup in both modes — see Step 1C.

• Window flag: if the remaining $ARGUMENTS contains --window followed by a value, extract the complete value as WINDOW_STR and strip --window <value> from the arguments so it never falls through to the business goal. Empty WINDOW_STR means no window. Step 0b processes it. Multi-word values must be quoted (e.g. --window "3 hours", --window "until 5:00 PM") — an unquoted multi-word value will be split by the shell, leaving the first token as the value and the remaining words misread as part of the business goal.

• Mode: if the remaining $ARGUMENTS contains "resume" or "handoff", enter Resume mode (Step 1A). Otherwise enter Cold Start mode (Step 1B). Any remaining text is the business goal — the outcome to rank the backlog against (see 1B.4). Hold it in BUSINESS_GOAL (empty when none), which is what 2D.2 persists so a day loop keeps ranking against it across ticks and context turnover. No goal is fine; ranking falls back to repo signals.

Day mode composes with everything above rather than replacing it: /pm day is a cold start that then keeps running, /pm day resume resumes and then keeps running, and /pm day increase scraping throughput carries that goal into every re-rank for the whole run.

A probe wake is not a tick either. When DAY_PROBE_WAKE=true, run Step 0, then go straight to 2D.7's probe-fire handler — skip 2D.3 entirely. A probe fire exists to re-read the runway while the board is parked; running a tick from it would dispatch work into the very wall the park was called to avoid.