opencode-codeops 1.8.0 → 1.8.1

package/CHANGELOG.md

@@ -2,6 +2,21 @@
 
 All notable changes to CodeOps are recorded here.
 
+## 1.8.1 — 2026-10-04
+
+### Documentation
+
+- agents: refresh project guidance with specialist facts
+- plan: record ST-43 and final verification evidence
+- plan: add ST-44 for the ask-and-create acceptance path
+- plan: record ST-34 dispatch acceptance evidence
+
+### Fixes
+
+- test: broaden availability regression guard per re-review
+- docs: complete AR #27 availability correction per phase-4 review
+- docs: correct specialist availability per ST-35 observation
+
 ## 1.8.0 — 2026-10-04
 
 ### Documentation

package/README.md

@@ -168,9 +168,10 @@ only with your explicit approval — the `--auto-design` mode cannot approve the
   listed specialists are dispatched as **additional** reviewers or executors: they never replace a
   required reviewer or gate, reviewer findings use the `SR-NNN` prefix, and the generated agent
   defaults to `reasoningEffort: max` (override it with `routing.roles.<role>.reasoning`).
-- **Fallback** — OpenCode loads agents at startup, so a specialist created during a session becomes
-  available in the next one; while unavailable, dispatch falls back to a generic subagent carrying
-  the brief excerpt and reports the fallback. No review depends on a specialist existing.
+- **Fallback** — a specialist is available as soon as its generated agent exists; OpenCode's
+  discovery timing is whatever your build provides. If it is missing, invalid, or a dispatch fails,
+  dispatch falls back to a generic subagent carrying the brief excerpt and reports the fallback.
+  No review depends on a specialist existing.
 
 Lifecycle checks: `--check` reports `INVALID`, `MISSING`, `STALE`, `ORPHAN`, `HAND-AUTHORED`, and
 `AGENTS.md` states; `--remove-custom <role> --yes` deletes the generated agent and its brief and
@@ -178,8 +179,8 @@ updates the index.
 
 > **Upgrading:** specialist agents embed the generic template contract. When a newer plugin changes
 > those templates, `--check` reports the agent as `STALE`; re-run
-> `python3 scripts/install_agents.py --project . --custom <role>` (then `--sync-agents-md`) to
-> regenerate it.
+> `python3 "${CODEOPS_PLUGIN_ROOT}/scripts/install_agents.py" --project . --custom <role>` (then
+> `--sync-agents-md`) to regenerate it.
 
 ## Requirements
 

package/_shared/quality-profile.md

@@ -13,7 +13,7 @@ Quality and routing configuration lives in `codeops/codeops.json`, validated aga
 configuration.
 
 The quality section controls independent review and stop conditions. The routing section controls
-optional roles, effort, model pins, sandboxes, and concurrency. Domain/risk tags in the active
+optional roles, effort, reasoning, model pins, sandboxes, and concurrency. Domain/risk tags in the active
 specification select additional reviewer roles. Outcome metrics are disabled unless
 `metrics.enabled` is explicitly `true`.
 

package/_shared/specialist-agents.md

@@ -5,8 +5,9 @@
 This is the **single canonical definition** of project-specific specialist subagents: how a
 capability gap is detected, how a candidate is proposed and approved, and how the specialist is
 created, used, and retired. It lives at the plugin root in `_shared/`; the participating skills
-(`make-requirements`, `make-plan`, `analyze-project`, `setup-routing`, `exec-plan`) link here
-instead of carrying copies.
+(`make-requirements`, `make-plan`, `analyze-project`, `setup-routing`) link here instead of
+carrying copies. `exec-plan` dispatches per `_shared/quality-profile.md`, which owns the
+dispatch, independence, and fallback rules.
 
 A specialist is a project-local agent that carries durable domain knowledge a generic catalog role
 does not have. Routing is an optimization and a context mechanism, **never a correctness source**.
@@ -140,6 +141,7 @@ escalation)` entry.
 The authoritative dispatch rules live in `_shared/quality-profile.md` (resolution order, finding
 prefix `SR`, additional-reviewer independence, and dynamic-packet fallback). A specialist
 dispatches only when the plan's `00-index.md` "Specialist Agents" table assigns it to the phase.
-When the agent is unavailable — for example it was created after the session started — dispatch a
-generic subagent with the complete packet, including the brief excerpt, and report the fallback.
-The phase is never marked complete unreviewed because a specialist was missing.
+When the agent is unavailable — for example its generated file is missing, its brief is invalid,
+or a dispatch fails — dispatch a generic subagent with the complete packet, including the brief
+excerpt, and report the fallback. The phase is never marked complete unreviewed because a
+specialist was missing.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "opencode-codeops",
-  "version": "1.8.0",
+  "version": "1.8.1",
   "description": "Specification-first engineering for complex systems — CodeOps plugin for OpenCode",
   "type": "module",
   "engines": {

package/skills/setup-routing/SKILL.md

@@ -90,7 +90,7 @@ Creation, after approval:
 2. Write `routing.roles.<role>` policy first when a model/effort/sandbox/reasoning override is needed: routing wins over the brief, and a policy written later makes the generated agent immediately stale.
 3. Generate the agent: `python3 "${CODEOPS_PLUGIN_ROOT}/scripts/install_agents.py" --project . --custom <role>`.
 4. Sync the index: `... --sync-agents-md`.
-5. Verify last with `... --check`, then tell the user the agent is available from the next OpenCode session.
+5. Verify last with `... --check`, then tell the user the agent is available as soon as its generated file exists (discovery timing follows the running OpenCode build).
 
 Removal: confirm, run `--remove-custom <role> --yes` (it deletes the agent and brief and syncs the index), drop the routing entry, warn when an active plan references the role, and report that `exec-plan` will fall back to a dynamic packet.