fix(review,work-items,claude-ops): correct the gh --paginate array-merge claim and conform per_page=100

plugins/claude-ops/.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "$schema": "https://json.schemastore.org/claude-code-plugin-manifest.json",
   "name": "claude-ops",
-  "version": "0.29.1",
+  "version": "0.29.2",
   "description": "Claude Code operations toolkit. Eight skills: audit-install-state (read-only audit of the machine-scope ~/.claude installation directory and ~/.claude.json \u2014 full inventory split into an authored surface and rolled-up bulk trees, product-managed retention vs genuinely unmanaged state, filename-scheme resolution before any process-liveness check, and deliberate/mid-experiment detection; reports, never deletes), observability (read locally captured telemetry \u2014 OTEL store, collector, hook-event JSONL, ccusage \u2014 with trend reports and store pruning), known-issues (search known Claude product GitHub bugs, check service health, maintain a persistent tracked-issue registry), changelog (ingest Claude Code changelog entries and integrate them into the current repo), plugins (bring a machine's plugin fleet current on demand \u2014 marketplace refresh, effective-scope updates including in-repo project/local installs, new-plugin install per policy, scope-divergence detection and explicit convergence), morning-brief (read-only gh-based operator morning view \u2014 queue-label counts, merge-ready PRs, parked decisions with their RECOMMENDED lines, and loop-lane telemetry freshness), lanes (start/restart/stop/status loop lanes as named background Claude Code sessions seeded from canonical prompt files, with per-lane model/effort, a repo-pull + marketplace-refresh launch step, and a consume-restarts action \u2014 an OS-schedulable reader that relaunches stopped lanes whose telemetry carries a restart_request), and a re-runnable setup action that settles where the known-issues registry lives. Plus a family of seven advisory *-audit telemetry-emitter hooks (API errors, config changes, instruction loads, permission denials, pre-compaction, skill usage, tool failures) that emit the shared hook-telemetry envelope, and a reference sink that maps envelopes into the hook-events.jsonl the observability skill reads.",
   "author": {
     "name": "Melodic Software",

plugins/claude-ops/CHANGELOG.md

@@ -3,6 +3,29 @@
 All notable changes to the `claude-ops` plugin are documented here. Format follows
 [Keep a Changelog](https://keepachangelog.com/en/1.1.0/); this plugin uses semantic versioning.
 
+## [0.29.2]
+
+### Changed
+
+- **`skills/lanes/scripts` `--paginate` reads now carry `per_page=100`.**
+  `restart-consumer.sh`'s telemetry-comment read and `telemetry-upsert.sh`'s comment listing
+  paginated without a page size — complete, but non-conformant with the published pagination rule
+  and 3.3x the requests at the 30-item default. No behavior change: both folds are page-shape
+  agnostic. `telemetry-upsert.test.sh`'s `gh` stub matched the list endpoint with an exact `*/comments`
+  suffix, which the query string would have fallen through silently; it now matches the query form
+  explicitly.
+
+### Fixed
+
+- **`telemetry-upsert.sh`'s slurp rationale no longer misdescribes `gh --paginate`.** The comment
+  above the comment listing claimed `--paginate` "concatenates one JSON array per page". It does
+  not: with no `--jq`, `gh` merges array-shaped pages into ONE array, so `jq -s 'add'` unwraps a
+  one-element slurp rather than concatenating. `--paginate` is still load-bearing (it is what makes
+  a page-2 comment visible at all) and `add` is still correct — but for a different reason than the
+  comment gave, and a reader trusting it would mispredict the next endpoint's shape. Same correction
+  applied to the pagination fixture's header comment in `telemetry-upsert.test.sh`. Measured against
+  `gh` 2.95.0.
+
 ## [0.29.1]
 
 ### Changed

plugins/claude-ops/skills/lanes/scripts/restart-consumer.sh

@@ -771,7 +771,7 @@ lane_comment_bodies() {
     jq -c --arg l "$lane" '[ (.[$l] // [])[] | .body // "" ]' "$TELEMETRY_JSON_FILE" 2>/dev/null || return 1
     return 0
   fi
-  raw="$(gh api --paginate "repos/$repo/issues/$issue/comments" -q '.[] | {body}' 2>/dev/null)" || return 1
+  raw="$(gh api --paginate "repos/$repo/issues/$issue/comments?per_page=100" -q '.[] | {body}' 2>/dev/null)" || return 1
   printf '%s' "$raw" | jq -s -c '[ .[].body // "" ]' 2>/dev/null || return 1
 }
 

plugins/claude-ops/skills/lanes/scripts/telemetry-upsert.sh

@@ -337,11 +337,14 @@ fi
 
 # --- List existing comments (paginated, raw) ---------------------------------
 # Fetch raw JSON and select in-script rather than via `gh --jq`, so the whole
-# two-tier detection is one auditable jq program. --paginate concatenates one
-# JSON array per page; `jq -s 'add'` slurps them into a single array — without
-# it, an existing comment on page 2 of a busy tracking issue is invisible and we
+# two-tier detection is one auditable jq program. With no `--jq`, `gh` merges
+# array-shaped pages into ONE array, so `jq -s 'add'` unwraps a one-element
+# slurp rather than concatenating pages — but it is not optional: supplying
+# `--jq` would suppress that merge and restore per-page emission, and `add`
+# keeps this correct under either shape. `--paginate` itself is what makes an
+# existing comment on page 2 of a busy tracking issue visible; without it we
 # would POST a duplicate, the exact failure this script exists to prevent.
-raw_pages="$(gh api --paginate "repos/$REPO/issues/$ISSUE/comments" 2>/dev/null)" || {
+raw_pages="$(gh api --paginate "repos/$REPO/issues/$ISSUE/comments?per_page=100" 2>/dev/null)" || {
   err "failed to list comments on $REPO#$ISSUE (gh api)"
   exit 5
 }

plugins/claude-ops/skills/lanes/scripts/telemetry-upsert.test.sh

@@ -142,8 +142,9 @@ if [[ "$url" == */issues/comments/* ]]; then
 fi
 # List comments (GET, --paginate): serve the fixture verbatim. Logged like every
 # other call so a pre-write rejection can assert an EMPTY log — proving zero API
-# calls, not merely zero mutations.
-if [[ "$url" == */comments ]]; then
+# calls, not merely zero mutations. The query string is matched explicitly rather
+# than with a bare `?` glob, which would also swallow `/commentsX`.
+if [[ "$url" == */comments || "$url" == */comments'?'* ]]; then
   printf 'CALL method=GET url=%s\n' "$url" >>"$STUB_LOG"
   cat "${STUB_COMMENTS_FILE:-/dev/null}"
   exit 0
@@ -293,7 +294,9 @@ assert_eq "instance-suffixed marker is a valid --marker" 0 "$rc"
 
 # ============================================================================
 # pagination — sentinel comment on a SECOND page is still found (no duplicate)
-# --paginate concatenates one array per page; the script slurps them.
+# Real `gh --paginate` merges array pages into one array, but the script's
+# `jq -s 'add'` is correct under either shape, so the fixture feeds it the
+# harder one: a page-per-document stream.
 # ============================================================================
 cat >"$TMP/paged.json" <<JSON
 [

plugins/review/.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "$schema": "https://json.schemastore.org/claude-code-plugin-manifest.json",
   "name": "review",
-  "version": "0.18.3",
+  "version": "0.18.4",
   "description": "Code-review toolkit: six read-only reviewer agents (code, security, architecture, doc drift, build/test/lint, CI-log audit) plus two orchestration skills — a single-lens quality gate and a multi-surface review fan-out with severity-ranked, deduplicated findings.",
   "author": {
     "name": "Melodic Software",

plugins/review/CHANGELOG.md

@@ -3,6 +3,21 @@
 All notable changes to the `review` plugin are documented here. Format follows
 [Keep a Changelog](https://keepachangelog.com/en/1.1.0/); this plugin uses semantic versioning.
 
+## [0.18.4]
+
+### Fixed
+
+- **`agents/ci-log-auditor.md`'s `add` rationale no longer misdescribes `gh --paginate`.** Finding
+  6 told the reader that `/annotations` pages are "concatenated" arrays combined with `add`. They
+  are not concatenated: with no `--jq`, `gh` merges array-shaped responses into ONE JSON array and
+  emits a document per page only for object envelopes like `check-runs`, so `jq -s` there yields a
+  one-element slurp that `add` unwraps. The published command was already correct — only the
+  mechanism claim was wrong, in a file whose whole subject is being factually right about
+  pagination, so a reader who believed it would mispredict the shape of the next endpoint. The
+  prose now states both branches and names the condition that selects between them (`--jq`
+  suppresses the merge), which also reconciles it with the per-page `--jq` caveat stated nine lines
+  above it. Measured against `gh` 2.95.0.
+
 ## [0.18.3]
 
 ### Fixed

plugins/review/agents/ci-log-auditor.md

@@ -62,7 +62,7 @@ gh api --paginate "repos/<owner>/<repo>/commits/<sha>/check-runs?per_page=100" \
   | jq -s -r '"total_count=\(.[0].total_count) returned=\([.[].check_runs[]] | length)"'
 ```
 
-`/annotations` is shaped differently — a bare JSON array with no envelope and no `total_count` — so the assertion above is not available there and `--paginate` is the only guard. Concatenated pages are arrays, so they are combined with `add`, not by reaching through a wrapper:
+`/annotations` is shaped differently — a bare JSON array with no envelope and no `total_count` — so the assertion above is not available there and `--paginate` is the only guard. With no `--jq`, `gh` merges array-shaped pages into **one** JSON array, emitting a document per page only for object envelopes like `check-runs` — so `jq -s` here yields a one-element slurp and `add` unwraps it rather than concatenating pages. Supplying `--jq` suppresses that merge and restores per-page emission, which is why the per-page caveat above still governs any reduction pushed into the filter:
 
 ```bash
 gh api --paginate "repos/<owner>/<repo>/check-runs/<check-run-id>/annotations?per_page=100" \

plugins/work-items/.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "$schema": "https://json.schemastore.org/claude-code-plugin-manifest.json",
   "name": "work-items",
-  "version": "0.35.2",
+  "version": "0.35.3",
   "description": "Manages development work items through a provider-neutral tracker seam that ships with the plugin (bundled dispatcher plus github and local-markdown adapters; seam plugin-dir canonical, adapters consumer-local-first): dashboard, taxonomy-labeled creation, a race-safe assignee-plus-lease claim protocol, recurring-schedule checks, TODO scanning, stale-lease auditing, plan decomposition into vertical-slice items, raw-intake triage (issues and unsolicited PRs through raw, verified, briefed, autonomous-eligible states), plus the two work-items loop lanes of the loop-lane convention: a self-paced autonomous work-loop drain (work-class admission gate, adaptive item cap, PR-only) and an attended attend-queue escalation lane. The re-runnable setup skill binds the provider (.work-item-tracker.json), seeds the recurring-schedule seam (.github/recurring-schedule.json), and remaps canonical role labels.",
   "author": {
     "name": "Melodic Software",

plugins/work-items/CHANGELOG.md

@@ -3,6 +3,21 @@
 All notable changes to the `work-items` plugin are documented here. Format follows
 [Keep a Changelog](https://keepachangelog.com/en/1.1.0/); this plugin uses semantic versioning.
 
+## [0.35.3]
+
+### Changed
+
+- **Every `--paginate` list read now carries `per_page=100`.** `skills/attend-queue/SKILL.md`,
+  `skills/work-loop/reference/telemetry-upsert.md`,
+  `tools/work-item-tracker/adapters/github/common.sh` (`wit_list_lease_comments`), and
+  `tools/work-item-tracker/adapters/github/reclaim.sh` (comment activity and timeline
+  cross-references) paginated without a page size. These were not truncation defects — `--paginate`
+  fetches every page regardless — but they were non-conformant with the pagination rule
+  `source-control:pull-request`'s readiness reference publishes, and at the 30-item default they
+  cost 3.3x the requests. No behavior change: each site's downstream fold (`jq -s 'add // []'` /
+  `'add // 0'`) sums or concatenates per-page results, and `gh` applies `--jq` per page under either
+  page size, so the same value is produced from fewer pages.
+
 ## [0.35.2]
 
 ### Fixed

plugins/work-items/skills/attend-queue/SKILL.md

@@ -133,7 +133,7 @@ esac
 }
 MARKER="work-items:attend-queue@$INSTANCE"
 SENT="<!-- claude-ops:lane-telemetry marker=$MARKER -->"   # $BODY_FILE MUST open with this line
-LOOKUP() { gh api --paginate "repos/$REPO/issues/$ISSUE/comments" \
+LOOKUP() { gh api --paginate "repos/$REPO/issues/$ISSUE/comments?per_page=100" \
   --jq ".[] | select(.body | startswith(\"$SENT\")) | .id"; }
 SENTINEL_OK() { # $1 = text; true iff line 1 is exactly $SENT and >=16 payload bytes follow
   [ "$(printf '%s' "$1" | head -c ${#SENT})" = "$SENT" ] &&

plugins/work-items/skills/work-loop/reference/telemetry-upsert.md

@@ -40,7 +40,7 @@ that cannot produce a conforming id stops the lane rather than yielding a marker
 ```bash
 MARKER="work-items:work-loop@$INSTANCE"
 SENT="<!-- claude-ops:lane-telemetry marker=$MARKER -->"   # $BODY_FILE MUST open with this line
-LOOKUP() { gh api --paginate "repos/$REPO/issues/$ISSUE/comments" \
+LOOKUP() { gh api --paginate "repos/$REPO/issues/$ISSUE/comments?per_page=100" \
   --jq ".[] | select(.body | startswith(\"$SENT\")) | .id"; }
 SENTINEL_OK() { # $1 = text; true iff line 1 is exactly $SENT and >=16 payload bytes follow
   [ "$(printf '%s' "$1" | head -c ${#SENT})" = "$SENT" ] &&

plugins/work-items/tools/work-item-tracker/adapters/github/common.sh

@@ -186,7 +186,7 @@ wit_emit_item() {
 # {id, node_id, body, created_at} for lease-marker comments, ascending id.
 wit_list_lease_comments() {
   local owner="$1" repo="$2" number="$3"
-  wit_run_gh read api --paginate "repos/$owner/$repo/issues/$number/comments" \
+  wit_run_gh read api --paginate "repos/$owner/$repo/issues/$number/comments?per_page=100" \
     --jq '[.[] | select(.body | startswith("<!-- work-item-lease v1")) | {id, node_id, body, created_at}]'
   printf '%s\n' "$WIT_GH_OUT" | jq -c -s 'add // []'
 }

plugins/work-items/tools/work-item-tracker/adapters/github/reclaim.sh

@@ -43,11 +43,11 @@ fi
 renewed_at="$(jq -r '.renewed_at' <<<"$lease_json")"
 
 # Activity check: non-lease comments since renewed_at, or open cross-referenced PRs.
-wit_run_gh read api --paginate "repos/$owner/$repo/issues/$number/comments" \
+wit_run_gh read api --paginate "repos/$owner/$repo/issues/$number/comments?per_page=100" \
   --jq "[.[] | select((.body | startswith(\"<!-- work-item-lease v1\") | not) and .created_at > \"$renewed_at\")] | length"
 comment_activity="$(printf '%s\n' "$WIT_GH_OUT" | jq -s 'add // 0')"
 
-wit_run_gh read api --paginate "repos/$owner/$repo/issues/$number/timeline" \
+wit_run_gh read api --paginate "repos/$owner/$repo/issues/$number/timeline?per_page=100" \
   --jq '[.[] | select(.event == "cross-referenced" and (.source.issue.pull_request // null) != null and .source.issue.state == "open")] | length'
 pr_activity="$(printf '%s\n' "$WIT_GH_OUT" | jq -s 'add // 0')"