runner v0.19.0

Runner v0.19.0: the offline verify-preparation command holds the profiles it is given to the dialect companion's §5.1 and digests them as given, so it agrees with the specification's reader on every probe; a local-file source may declare source parameters on the live path, as §3 and §4 admit; a private foundation for draft workflows lands without any exposed surface.

What an operator must do

• Nothing for existing runs. Exports, the journal, verify-run's report, its exit codes and refusal flags are byte-identical to v0.18.0's for every existing run; all forty-one published vectors recompute byte for byte. The installation's own profiles keep the Runner's admission and digest; a release's frozen profile digests still match.
• If a dialect gives a local file a source parameter, it is now admitted: the parameter is held to the same rule as any source parameter (an exact fact target of an earlier source), its value is carried into the outcome's parameters and the lineage's dependencies, and a parameter with no value skips the source as for any kind; a profile, maxAge or arguments on a local file are still refused.
• If a fixture's profile carries tools: [], or an unused profile's id is not a flat token, verify-preparation now reads it as the specification does, digesting the profile's canon bytes as written.

The offline verifier's profiles (#129, closing #124)

• Offline, each supplied profile is digested over its canon bytes (§1, §5.1) instead of the Runner's re-encoding, and held to §5.1's member table and §12's bounds: exact members with null only for endpoint, a non-empty distinct id, the key rule, the class and shape values, the closed adapter with a digest, distinct non-empty tools required for mcp, the calculator's form, the research declaration's form, the research maxima counted before forms; the Runner's own installation limits (the profile count, bytes per profile, the id's token form, the source, authority, adapter, endpoint and tool bounds) apply on live paths only.
• Agreement with the specification's Python reader: 68 of 68 vector calls, 11 of 11 Exchange fixtures, 108 of 108 of the review probes on #119, 56 of 56 new profile probes.

A local file's source parameters (#128, closing #126)

• The shared validator no longer refuses parameters on a local-file source; §3 and §4's table make parameters an optional member of every source, and §4.2 excludes only a profile, maxAge and a request. The parameter goes through the shared source-parameter rules, can reach a rule's derivation and never the file's identity or bytes; the message for the four refused members is narrowed to them.

A private foundation for draft workflows (#130, #132, #133)

• The private document, projection and selection checks a draft RFC 0020 workflow will need, built in a series of slices of #121: cases keep their missing, null, false, zero and -0 distinctions; output extraction tells an explicit empty result from a failure; a selection binds the whole offered envelope set and refuses reordered or repeated membership; inherited influence is preserved across stages; a stage's identities are frozen before acquisition. No API or command is exposed, and no workflow is executed; existing runs are unchanged.

Verification

CI ran formatting, vet, the race tests and the real-Runtime integration tests on Linux and macOS at each pull request's head and again at the tag, against Runtime 09206e7 (released as v0.34.0).

• Review: one cross-vendor clean-room round each (OpenAI model over an Anthropic drafter, recorded on the pull requests): #129 no finding, at high effort; #128 no blocking finding, one LOW on the specification's wording filed as judgment-pack-spec#200. The draft-workflow series (#130, #132, #133): one clean-room round each (OpenAI model, same vendor as the drafter at the maintainer's explicit request, recorded on the pull requests).

See releasing for how a download is verified.