--- name: pendulum-status description: "Show what Pendulum is doing in the current repository, read-only: each open Objective's state and route, and for a Blocked one or a Question the reason and the way on (resume, answer or restart), taken only on the user's yes. Use when the user asks what Pendulum is doing, what is running or queued, why an Objective is Blocked or stuck, or how to answer or resume one. Not for whether the repository is set up (pendulum-doctor) or the scorecard of finished Objectives (pendulum-score)." --- # /pendulum:pendulum-status [issue] Read GitHub and report; change nothing. A way on is one of Pendulum's labels or a comment, taken only on the user's yes. ## Read the queue 1. `gh issue list --repo OWNER/NAME --state open --label pendulum:objective --json number,title,labels,createdAt --limit 100`, and the same with `--label pendulum:draft`, merged by number (a draft may carry both). Given an issue number, `gh issue view --repo OWNER/NAME --json number,title,state,labels` alone. 2. Each one's state from its labels ([reference.md](reference.md), States). A closed issue is done. `pendulum:draft` wins over every other label: a draft, never run. An open issue without `pendulum:objective` is stopped. `pendulum:restart` on it: a restart is under way. 3. Its route: `pendulum:local`, the local loop's; any other, the Action's (the local loop's where no Action is active). 4. For a Running one, the last row of the steps table in Pendulum's progress comment on the issue: what the stage is doing now, and for how long. Show one line per Objective, oldest first: number, title, state, route, and for Blocked and Question the one-line reason (below). `pendulum wait` (the pendulum-serve skill) waits for the next change instead of asking again. ## Blocked Read the issue's comments (`gh issue view --repo OWNER/NAME --comments`) and take Pendulum's latest Blocked notice: its first line is the marker `