bullswarm 0.38.0 → 0.38.2

package/AGENTS.md

@@ -51,11 +51,17 @@ before doing anything. Their readers and stored formats are unchanged.
    outlives a step is the 100% refusal marker a usage limit writes when the
    meter cannot be read, and it counts only when its reset was named or
    measured, never guessed (`refusalResetKnown` in `src/meters/framework.js`).
+   Beside it sits one plan fact: `state.strategy.planExcludedModels[pool]`,
+   the models a provider said that pool's subscription does not include
+   (failure kind `model-not-in-plan`). It is a fact about the plan, like its
+   price, not a spent or dead pool: the pool stays pickable with its other
+   models, and the record ends when the subscription changes or the operator
+   turns the model back on (`src/lib/strategy.js`).
    Recursion depth is core-owned via env (`BULLSWARM_DEPTH`).
 5. Workflow dispatches honor the same guarantees as single runs, in
    `src/workflow/v2-dispatch.js`: `BULLSWARM_DEPTH` is checked and propagated
    (`assertDepthAllowed` and `childDepthEnv` in `dispatchV2Action`), pools at
-   a spent window are excluded (`preparePools`), and a sign-in failure is
+   a spent window are excluded (`preparePools`, in `dispatch-pools.js`), and a sign-in failure is
    failure kind `auth`: the step's retry skips every pool in the dead
    credential's group (`upstreamGroupOf`), a choice held for that dispatch
    only and never stored. A step's `route`, the run's pin and the step's

package/CHANGELOG.md

@@ -2,6 +2,92 @@
 
 ## Unreleased
 
+## 0.38.2 — Three large files split into one-concept modules
+
+- internal: the three largest workflow files are split into one-concept
+  modules, with no behaviour change. `src/workflow/dashboard.js` goes from
+  3,613 lines to 2,002 plus 24 `dashboard-*.js` modules (1,837 lines);
+  `step-model.js` from 2,540 to 588 plus 18 `step-model-*.js` modules (2,213
+  lines); `v2-dispatch.js` from 2,039 to 1,191 plus 8 `dispatch-*.js` modules
+  (917 lines). Each old file still exports the names the product reads from
+  it; names only tests read are now imported from the module that holds them.
+
+## 0.38.1 — Fewer wasted retries, honest no-pool reasons
+
+- no eligible pool: when a pool lacks a tier only because free models are
+  off for it, or because its plan was seen not to include the tier's model,
+  the reason now says so (`free models are off for <pool>`, `<pool> has no
+  <tier>-tier model its plan includes (plan excludes <models>)`, or `<model>
+  is not in <pool>'s plan` for a model the step names), also under a step's
+  route and in `run --dry-run`. Before, a routed step read only `no
+  enabled pool left has a model on the <tier> tier`.
+- dispatch: a worker can mark a blocker it may not change by starting a `##
+  Not done` line with `outside:` (`- outside: tests/router.test.js fails on
+  main before this change`); work tasks now ask for this. A step that fails
+  `failed-evidence`, `not-produced` or `semantic` with such a line skips its
+  one automatic retry and comes back to you at once, its `why` ending `retry
+  skipped: the worker reported a blocker outside this step: <item>`; the saved
+  attempt lists every such item as `outsideBlockers`. `schema` and process
+  failures keep their retry.
+- workflow add: a fragment may carry `blocks: {"<new step id>": ["<existing
+  step id>", ...]}` to make existing steps that have not started also wait for
+  a step it adds, for example a fix in front of a report (then `step accept`
+  the failed step). It is the one change a fragment may make to an existing
+  step; a started step, a loop's step, a gate, a loop or a cycle is refused in
+  fragment words. A step already blocked behind a failed step stays blocked
+  (it is not reset and blocked again). The output prints `waits    step <id>
+  now also waits for <ids>`, and `--json` carries `waits`.
+- advisories: a new `suite-wider-than-files` advisory names a step that owns
+  files but runs a command check naming none of them (a bare `npm test`),
+  because a failure elsewhere in the suite would fail a step that cannot fix
+  it. Scope the command, or run the suite in a check step. Like every advisory
+  it never refuses a program or changes an exit code.
+- advisories: with `--json`, `workflow goal` and `workflow plan validate` no
+  longer print advisory text; the advisories are in the JSON as `advisories`
+  (the detached launch document always, a foreground result when there are
+  any). In human mode `plan validate` now prints them on stderr, as `workflow
+  goal` does.
+- run --json: the verdict has top-level `pool` and `model`, the last attempt's
+  (null when nothing was dispatched). `pick` keeps them too. Small flat
+  objects such as the reasoning record now print on one line, so the verdict
+  stays within 60 lines.
+- workflow runs: the goal column skips constraint sentences that follow a
+  dropped leading folder (`Work in /abs/path (git branch x). Do not commit.
+  Fix the parser crash.` shows `Fix the parser crash.`); a goal that is only
+  constraints shows the folder name.
+- strategy: new `bullswarm strategy set-free <allow|never> [--pool <name>]
+  --yes` (and `set-free reset --pool <name>`) stops free models being
+  suggested, applied or dispatched, for every pool or one; a pool's own
+  setting wins. A pool left with only free models for a tier is out of that
+  tier with the reason `free models are off for <pool>`: a step no pool can
+  take says it in its `why` and `routeCandidates`, `run --dry-run` says it
+  too, and `strategy show` prints it under the tier. A model you name
+  yourself is still allowed. `strategy show` prints a `free models:` line, and
+  the low tier's basis stops putting free models first when every pool has
+  them off.
+- providers: a connector may list `modelPlanSignatures`, the text its CLI
+  prints when the subscription's plan does not include the requested model
+  (Command Code: `MODEL_NOT_IN_PLAN`). Only the provider's error output is
+  read: stderr, and on an event stream the records the provider flags as
+  errors (read even when the worker exits 0), so a worker's reply that quotes
+  the code, even on a line starting `Error:` or in a clean final record, is
+  still a reply. A hit is the new failure kind
+  `model-not-in-plan` (a process failure, labelled `model not in plan`): the
+  step's retry goes to another pool, and `state.strategy.planExcludedModels`
+  records the model for that pool. The pool keeps running its other models;
+  strategy, rungs, pins and dispatch pass that model over on that pool only.
+  `strategy show` prints `not in plan: <pool>: <model>`. `strategy
+  include-model <model>`, a changed `strategy set-subscription`, or turning
+  the model back on for the pool clears it, and `workflow resume` reruns such
+  a step.
+- command-code: models are ranked by family (astra, sol, gpt, terra, luna,
+  mini, fable, opus, sonnet, haiku, grok), so a newly listed model is ranked
+  the day it appears and the newer version of a family ranks first
+  (`gpt-6.1-sol` above `gpt-5.6-sol`, `claude-opus-5-5` above
+  `claude-opus-4-7`). Dated prices and the deliberate overrides (`gpt-5.4` and
+  `grok-4.5` medium, `minimax-m3` high) stay as rows; kimi and glm stay
+  unranked.
+
 ## 0.38.0 — The removals release: v3 only, saved runs view-only, less code
 
 - removed: the mechanisms program v3 replaced (0.37.0) no longer run. The