Repository navigation
v7.204.12
Host contract drift (v2): vendored types and corpus refreshed to @opencode/plugin@2.3.0
The vendored OpenCode 2 plugin types (src/host/v2/types.ts) and the committed
host-contract corpus (tests/fixtures/host/expected-structure-v2.json) were pinned to
@opencode/plugin@2.0.26 while the published package advanced to 2.3.0; the weekly
host-contract-check reported structural drift and auto-filed #3732 (and #3552 at the
2.2.5 snapshot). Both now pin 2.3.0 and the weekly check reports STRUCTURE_MATCH.
The vendored surface now carries the 2.1–2.3 additions, compiler-verified against the
tagged tarballs (the surfaces the adapter and type-probe cover): Context.credential (activate), Context.experimental (terminal read,
stateless generate, artifact) and the deprecated top-level Context.generate;
SessionRequestMessage (readonly nullable-text content, wired into the context event);
SessionCompactionResult.native (replacing the providerState era); the
SessionModelResolve / SessionIdle / fork hook payload families with a payload-typed
session hook registration; the paginated session.list ({data, cursor}) and the
deprecated session.instructions entries; 2.3.0 AgentEditor readonly signatures; and
the 2.3.0 permission assert input (optional agent/save/metadata/source, readonly
arrays).
Behavior: types-only for the adapter except one contract-alignment change — the v2
guidance context hook now replaces message elements instead of mutating the host's
message objects in place when writing transformed text parts back (the published
content array is readonly at 2.3.0; the event array itself is still rewritten in place,
so guidance delivery is unchanged).
New surfaces are documented per-hook in docs/host/v2-hook-inventory.md with the
adoption owner (#3642); no new hook is adopted at runtime in this change.
What changed
-
PR_FEEDBACK verification rejections stop consuming gate state (#3644 AC1): a
swarm-pr-feedback:verificationrequest whose lanes own an item not in the
requested inventory (or doubly-claim an item) is now rejected by a request-pure
shape check that runs BEFORE any state mutation — before PR_FEEDBACK activation on
a fresh session and before the append-only inventory declaration on an active one.
Previously the typo'd inventory was persisted first, so the corrected retry was
wedged by the append-only rule ("may not be removed or renamed"). The stateful
predicates (duplicate batch id, capacity, cross-batch ownership) are unchanged. -
Unlaunchable base/micro lane agents are refused before activation (#3644 AC2):
base and micro admission now runs the samevalidateLaneAgentlaunchability probe
the lane launcher uses (including the bare-canonical-role registry refusal on
prefixed-only multi-swarm hosts), so such requests no longer activate the workflow
and bind/record state before launch rejects them. The set of rejected requests is
unchanged — only the durable-state consumption moves. -
stage-b-test lanes carry the verdict-mandate suspension clause (#3645): the
fourth ordered PR-feedback gate now gets the same controller-authored PROTOCOL
SELECTION clause the other four gates have, suspending the test_engineer prompt's
task-keyed[TESTED]"STRUCTURED VERDICT LINE" mandate in favor of the gate's
item-keyed[STAGE-B-TEST] | <item_id> | PASSsettlement rows — closing the same
conflict class that voided reviewer lanes before the clause mechanism existed. -
Both #3752 residual paths are fixed in this PR (maintainer decision, option
(b)): a verification dispatch rejected for a STATEFUL reason after an inventory
amendment (duplicate batch id, capacity after prune, cross-batch exclusivity)
no longer persists the amendment — the dispatch path runs
declareAndEnforcePrFeedbackVerification, a single-bind/single-write
transaction, so the corrected retry is never wedged; and every recognized
PR_FEEDBACK lane mode (verification + the four ordered gates) probes agent
launchability at the admission site before any gate record is written.
Why
Follow-ups from PR #3632's post-delivery breadth review (closure-ledger rows FB-010
and closeout MEDIUM-1): two state-consuming rejection paths and one unsuspended
static verdict mandate survived the dispatch-integrity pass.