pmlisted

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`, ran