Add a bulk issue-snapshot read to forge for PM render and groom #110

New issue

Open

opened 2026-07-20 14:54:57 +01:00 by vnprc-agent · 0 comments

vnprc-agent commented

2026-07-20 14:54:57 +01:00

Contributor

Building the PM board snapshot and running the groom needs every issue — state, body, and comments — across the managed repos, but forge only exposes per-issue view and a list that omits comments, so assembling that data means many one-issue-at-a-time round-trips. A single bulk read that emits full issue JSON for a repo would feed render --issue-snapshot directly and cut the cross-repo survey from N requests to one per repo.

Primary goals:

One-call repo snapshot — a command returning every issue in a repo (open + closed) as JSON, including body, labels, state, and milestone.
Optional comments — a flag to include each issue's comments, so a read-only survey has full context without a follow-up call per issue.
Snapshot-ready output — shape the JSON to feed pm/render --issue-snapshot and pm/integrity-check without post-processing.

Current state

forge issue list returns a page of issues but not their comments; forge issue view <n> returns one issue with comments. Building the board snapshot or grooming across the managed repos therefore fans out into many requests. Pagination of the list path is tracked in allod/tools#89.

Scope

A read-only bulk fetch in forge plus the snapshot output shape. No write paths. The renderer and integrity-check already accept a snapshot input; this supplies it.

Building the PM board snapshot and running the groom needs every issue — state, body, and comments — across the managed repos, but `forge` only exposes per-issue `view` and a `list` that omits comments, so assembling that data means many one-issue-at-a-time round-trips. A single bulk read that emits full issue JSON for a repo would feed `render --issue-snapshot` directly and cut the cross-repo survey from N requests to one per repo. Primary goals: - **One-call repo snapshot** — a command returning every issue in a repo (open + closed) as JSON, including body, labels, state, and milestone. - **Optional comments** — a flag to include each issue's comments, so a read-only survey has full context without a follow-up call per issue. - **Snapshot-ready output** — shape the JSON to feed `pm/render --issue-snapshot` and `pm/integrity-check` without post-processing. ### Current state `forge issue list` returns a page of issues but not their comments; `forge issue view <n>` returns one issue with comments. Building the board snapshot or grooming across the managed repos therefore fans out into many requests. Pagination of the list path is tracked in allod/tools#89. ### Scope A read-only bulk fetch in `forge` plus the snapshot output shape. No write paths. The renderer and integrity-check already accept a snapshot input; this supplies it.