digestlisted

# Digest Runs as an **office-hours session** with the user present — it cannot run unattended, because its demos are interactive (it drives the live browser apps). `dispatch-jit-reminder` invokes this skill after it claims the digest jit issue (sets the project `Status` → `In Progress`). This skill owns the rest of that session and produces its output for the user. Takes two arguments: `<repo> <num>` — the digest jit issue this run covers. Work each section in order. Run every `gh`-calling command with `dangerouslyDisableSandbox: true` — see `.claude/rules/sandbox.md`. ## 1. Compute the digest window Find the window-start timestamp — the boundary before which work was already covered by a prior digest: ```bash .claude/skills/dispatch-propagate/scripts/dispatch-digest-window <repo> <num> ``` Run this with `dangerouslyDisableSandbox: true` — it calls `gh`. It prints an ISO-8601 timestamp: the previous closed digest issue's `closedAt` (steady state), or this issue's own `createdAt` when no prior closed digest exists (cold start). Capture it as `<window-start>` for the next section. ## 2. Enumerate dispatch-queue work completed in the window Collect everything merged into `natb1/commons.systems` since the window start. The workspace repo is hardcoded here on purpose: dispatch-queue work always merges into `natb1/commons.systems`, whereas the `<repo>` argument names where the *digest issue itself* lives (the repo configured in `dispatch.config/jit.json` for the real dig