investigate-cronlisted

# investigate-cron Diagnose a cron run either by name and approximate execution time, or directly by the PR/task it was dispatched against. **Usage:** - `/shipwright:investigate-cron <name> <time>` — find the run of cron `<name>` closest to `<time>` - `/shipwright:investigate-cron --item <org/repo#N|taskId>` — find every dispatch across all four pipeline phases for a given PR or task Arguments: - `<name>` — cron name: `deploy`, `dev-task`, `patch`, `review` - `<time>` — approximate time the cron fired, e.g. `6pm`, `14:30`, `2:30pm PST`. Timezone defaults to Pacific if not specified. - `--item <org/repo#N|taskId>` — a PR (`org/repo#N`, e.g. `acme/x#123`) or a bare task id (e.g. `IC-1.1`). When present, no time argument is needed or used. **Examples:** - `/shipwright:investigate-cron deploy 6pm` - `/shipwright:investigate-cron --item acme/x#123` - `/shipwright:investigate-cron --item IC-1.1` --- ## Step 0: Bind invocation arguments and pick a mode Before running any steps, parse the invocation and detect which mode applies. ```bash # Set these from the user's invocation: # /shipwright:investigate-cron <name> <time> # /shipwright:investigate-cron --item <org/repo#N|taskId> # If the first argument is literally "--item", route to item mode: if [ "$1" = "--item" ]; then MODE="item" ITEM_ARG="$2" # e.g. "acme/x#123" or "IC-1.1" else MODE="name-time" CRON_NAME="$1" # e.g. deploy TIME_ARG="$2" # e.g. 6pm fi ``` For example: - `/shipwright:investig