orchestrator-workflow 0.42.0 → 0.43.1

package/CHANGELOG.md

@@ -7,6 +7,85 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [0.43.1] - 2026-10-01
+
+- Give the multi-subprocess dormant Opencode sync regression its existing
+  30-second integration-test timeout, preventing publish-runner scheduling
+  variance from tripping Vitest's five-second default.
+
+## [0.43.0] - 2026-10-01
+
+- Codex routing now resolves packaged `small`, `balanced`, and `strong` model
+  aliases; task-slicer defaults to balanced Sol at every tier, while only
+  explorer-low and implementer-low use small Luna.
+- Outward cross-check (evidence-and-probes.md, Delegate implementation): the
+  third-party pull request sentence no longer lets a later outward action
+  hide behind the "recorded once" dedup. Any further outward action on a
+  pull request already recorded as a third party's (a title/body edit, a
+  base retarget, marking it ready for review, an approval, enabling
+  auto-merge, a push to its branch, or reopening it) that a subagent of
+  the run performed, or whose actor cannot be established, is a new
+  incident, recorded and listed in `06-handoff.md` like any other. This
+  mirrors the carve-out the recorded-subagent-PR rule and the flagged-ref
+  rule already carry. Pin in `test/outward-actions.test.ts`. okf bundle
+  citations re-pointed and docs re-stamped.
+- Outward cross-check (evidence-and-probes.md, Delegate implementation): a
+  pull request's author field identifies the host account that opened it,
+  not the agent that acted through it, so any account the run's subagents
+  can act through (the orchestrator's or operator's own account, or a
+  shared bot or service account) no longer reads as a third party by
+  author alone; the orchestrator confirms with the operator or treats the
+  opener as not established instead. A pull request the run's own
+  subagent opened, or whose opener could not be established, is recorded
+  as an incident naming its number or URL (the closing incident sentence
+  now names the pushed ref and its sha or the pull request's number or
+  URL) and has no exemption: until the operator closes it or decides, it is
+  re-checked and re-flagged every later round, each re-flag recorded in
+  `03-decisions.md` as a misfire referring to the existing incident
+  decision by its D-ID, and reported to the operator again. The re-flag
+  covers only the pull request's continued existence: the round's
+  implementer return is still judged on its own merits, and any further
+  outward action on that pull request by a subagent or an unestablished
+  actor is a new incident. review-and-recovery.md's misfire rule carries
+  the matching D-ID reference. task-slicer.md's bundle-tool rebase
+  sentence now also carries contracts.md's outside-repository clause, so
+  an `allowed_changes` entry outside the bundle's repository is never
+  queried against that bundle; its subagent-contracts-superset.md
+  citation now spans the rule's full range.
+- A docs-consistency test now guards every INSTALL-AGENT.md pointer that
+  names a package README section by heading text (currently three, all
+  "Effort tiers"): the guarded heading is confirmed to still exist in
+  README.md, and a companion check confirms the extraction pattern itself
+  still matches at least one reference. `docs/verification-sets.md` is
+  now listed in `docs/okf/subagent-contracts-superset.md`'s `sources`
+  (it was already cited in the doc's prose without being declared).
+- The README section pointer guard now also scans `docs/install-reference.md`,
+  `docs/operator-install.md`, and `docs/model-routing-reference.md` (their
+  pointers used an unquoted form or the `[package README](../README.md)'s`
+  markdown-link form that the guard's phrase pattern missed; rewritten to the
+  quoted `package README's "X" section` form, and the pattern extended to
+  match both the bare and the link form, and to tolerate the words "package"
+  and "README" wrapping across a line break inside the link text). Heading
+  extraction is now a line scanner rather than a delimiter split: a fence
+  opens on a line of three or more backticks or three or more tildes
+  (indented up to 3 spaces) and closes only on a later line of the same
+  fence character, at least as long, with nothing but trailing whitespace
+  after it, so a `~~~` fence, a longer fence wrapping an inner ``` block, an
+  indented fence, and an unclosed fence (which now runs to end of file) are
+  all handled; a quoted `#` example inside any of them can no longer be
+  mistaken for a real README heading. The guard's helper functions dropped
+  an unused parameter and corrected two comments that misstated which docs
+  are scanned. A line-wrap in `docs/install-reference.md` that split
+  "repository-bound" across the line break is also fixed.
+- README restructured around a shorter package README standard: moved
+  deep reference material (architecture rationale, run contracts, install
+  internals, harness file list and read-only posture, role profile detail,
+  model routing reference, the verification-sets JSON example, and the
+  `validate-review-report` CLI reference) into `docs/*.md`, linked from a
+  new Documentation section. `files` now lists those docs so they ship on
+  npm (`docs/okf/`, the curated knowledge bundle, is not part of the
+  package and stays out of `files`).
+
 ## [0.42.0] - 2026-09-25
 
 - Outward cross-check (evidence-and-probes.md, Delegate implementation): a

package/INSTALL-AGENT.md

@@ -155,7 +155,7 @@ steps in the repository you were asked to install into.
    npx orchestrator-workflow init --yes \
      --harness <claude,codex,opencode> \
      --profile <minimal|full> \
-     [--models "explorer=<model>,task-slicer=<model>,implementer=<model>,reviewer=<model>,advisor=<model>"] \
+     [--models "explorer=<model>,task-slicer=<model>,implementer=<model>,reviewer=<model>,advisor=<model>"] [--codex-models <codex-model-aliases.json>] \
      [--routing <routing.json>] \
      [--codex-catalog <codex-catalog.json>] \
      [--tiers | --no-tiers]
@@ -313,3 +313,8 @@ steps in the repository you were asked to install into.
    role/tier; whether variants were rendered; the prior routing to use for a
    rollback; the commands actually run; any offline capability or entitlement
    gap; and conflicts left in place.
+
+`--codex-models` accepts a sparse object keyed by the internal Codex aliases
+`small`, `balanced`, and `strong`. It deliberately replaces both model and
+tier-standard effort on matching leaves, so use `--routing` to preserve or
+select a custom effort; omitted aliases preserve existing selections.