claude-dev-env 8.126.1 → 8.126.2

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -69,9 +69,12 @@ Read the JSON report and worker log after the process ends. The JSON fields are
69
69
  The runner writes one summary line with the selected account, exit code, and
70
70
  report path.
71
71
 
72
- When the command exits 3 and the report has `"account": "wait"`, no account is
73
- eligible. Report the picker's reason and reset time. Do not fall back to the
74
- Agent tool. Claude can also return exit 3 after a worker starts. When the
72
+ When the command exits 3 and the report has `"account": "wait"`, read the
73
+ picker's reason and follow the exit 3 steps in
74
+ [Proof before a pull request](~/.claude/docs/rule-guides/proof-before-pull-request.md).
75
+ Do not fall back to the Agent tool, except where those steps send the work
76
+ there after a failed meter read.
77
+ Claude can also return exit 3 after a worker starts. When the
75
78
  report account is `main`, `second`, or `extra_2` and later, report the child's
76
79
  exit code and result. Exit 124 with reason `timeout` means the worker ran past
77
80
  `--timeout-minutes`.
@@ -31,7 +31,7 @@ The broker stores cached meters, spent marks, and Claude session bindings in one
31
31
  | Code | Meaning |
32
32
  | --- | --- |
33
33
  | `0` | `choose` or `check` found an account, or the job exited successfully. |
34
- | `3` | No account clears its floor. The decision includes `resets_at`. |
34
+ | `3` | Wait. No account clears its floor, no read account clears its floor while other meters went unread, or no account meter could be read. The reason says which. The decision includes `resets_at`. |
35
35
  | `4` | A Claude job stopped with `advisor_blocked`, or every Claude account was unusable: each had no token or was signed out. |
36
36
  | `127` | A Codex job timed out, its command could not start while no Codex roster is configured, or the command could not start on any account in the roster. |
37
37
  | Other command code | `run` returns the command's exit code after a served response. |
@@ -30,7 +30,11 @@ For a change to Claude Code behavior, such as a hook, skill, rule, setting, prom
30
30
  - Start the broker from your own shell, with your environment as is. The broker reads the account meters with your session's credentials and starts Claude without your session's variables.
31
31
  - Leave out `--bare` and `claude plugin eval`. Both drop the hooks and settings the user runs with.
32
32
  - Read the broker report for the account it chose. Read the stream for the hook events and their output, `permission_denials`, the final result, and the token usage on the result event.
33
- - When the broker exits 3 with action "wait", no account has room. Treat that as a blocked proof and report its reason and `resets_at`. Spawn Claude only through the broker.
33
+ - When the broker exits 3 with action "wait", read its reason. Start headless Claude only through the broker.
34
+ - "no account has room" means each account is below its usage floor. Treat that as a blocked proof and report the reason and `resets_at`.
35
+ - "no readable account has room" means each read account is below its usage floor, and the reason names the accounts whose meter went unread. Run the broker once more after `resets_at`. When it waits again, treat that as a blocked proof.
36
+ - "no account meter could be read" means the meter reads failed, often with HTTP 429. Usage may be left, and `resets_at` is when the broker checks again. Run the broker once more after `resets_at`.
37
+ - When that second run also says "no account meter could be read" in a cloud session, the session's own account has usage, because the session runs on it. Run the step with a subagent of the session, on the `--model` and `--effort` pair of the broker call, and in its own worktree when it edits code. In the proof, name the route and quote each account's unread reason. Outside a cloud session, a second wait is a blocked proof.
34
38
 
35
39
  Report it in the pull request body under "Proof in practice". List each command you ran, quote the output lines that show the effect, and state the difference between the runs with and without the change. The run on the target the change exists to fix belongs in this section before the pull request opens. List a condition the change does not target, such as an older data shape, under a "Not covered" heading at the same level.
36
40
 
@@ -51,6 +51,12 @@ the wait reason names each account whose meter could not be read. A window the
51
51
  usage endpoint returns as `null` holds no account back, but an account needs at
52
52
  least one window with a percent to have room.
53
53
 
54
+ A wait whose reason starts "no account meter could be read" is a failed read,
55
+ and the account may have usage left. An HTTP 429 from the usage endpoint holds
56
+ that account's probe for 5 minutes.
57
+ [Proof before a pull request](rule-guides/proof-before-pull-request.md) says
58
+ what a session does next.
59
+
54
60
  ```
55
61
  python packages/claude-dev-env/scripts/account_broker.py choose --product claude
56
62
  ```
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "claude-dev-env",
3
- "version": "8.126.1",
3
+ "version": "8.126.2",
4
4
  "description": "Claude Code development standards — rules, hooks, agents, commands, and skills",
5
5
  "type": "module",
6
6
  "bin": {