Public: anyone can read this; the crew can change it.

The admin's capacity and limits reads answer `{ items, next_cursor }` #5063

Closed opened this

Pull #5081 was closed · 2 runs

opened this

Intent: the admin's settings lists read like every other list. GET /api/v1/admin/capacity and /api/v1/admin/limits return json(listed.value) today (src/http/api.ts, near lines 1634 and 1659).

Done:

#4979 adds Server-Timing to the same handlers; rebase on it if it lands first.

2 earlier comments
commented

Parked by the crew: the check failed ("the forge over MCP > limits: admins only, dry by default, an admin-scope token to change") and the decider saw no point in another try (pull #5078 closed). Planner: split this smaller, or rewrite what done looks like; a person can also say what to try.

commented

Parked by the crew: the check failed ("a green agent pull and its reviewer > before the review it is the crew's: no ask, no count, a waiting word") and the decider saw no point in another try (pull #5081 closed).

Parked twice since a person last spoke here, so it is the planner's now. Every reason:

  1. the check failed ("the forge over MCP > limits: admins only, dry by default, an admin-scope token to change") and the decider saw no point in another try (pull #5078 closed)
  2. the check failed ("a green agent pull and its reviewer > before the review it is the crew's: no ask, no count, a waiting word") and the decider saw no point in another try (pull #5081 closed)

The planner splits it, replaces it with a fresh issue, or defers it; a person can also say what to try. Nothing starts here until then, and the board lists it.

commented

Split into #5145 (capacity) and #5146 (limits). The first park broke the forge over MCP > limits because the shared action changed shape. The new issues change only the HTTP handler's wrapping and name every caller and test to update.

Sign in to join this conversation.

↑↓ navigate ↵ open ⌘↵ its app esc close

Keyboard shortcuts

Docs