provider-step-usage-v1-0-0

Provider step usage

Candidate executable asset for independent review. Not registered, approved, activated, or generated by the unsuccessful DjimitFlo factory run. This package was implemented by Codex under an explicit operator mandate; it conveys no execution authority.

Provenance: independently checked OpenCode proof task deployed-provider-opencode-proof-20261101-r2 recorded 7101 tokens although its step totals summed to 13941. The example below is synthetic numeric reconstruction; no provider payloads or credentials are included. This package does not patch the runtime adapter or claim to measure cost, energy, task success, or completeness of a stream. It measures only the supplied step records.

Contract and execution

Run node run.mjs with a JSON object on stdin containing exactly events_json, a string of newline-delimited JSON events. Output is {tokens,steps}. Run verification with node --test run.test.mjs. No network, credentials, shell evaluation, or external dependencies are used. Bash is declared solely for the existing governed invocation interface; content cannot add commands or permissions.

Only OpenCode type: "step_finish" records with part.id and part.tokens.total are measured. Totals must be explicit nonnegative safe integers. Repeated part IDs with identical totals and session/message scope count once; conflicting repeats fail. Missing stable part IDs fail rather than using array position or timestamps. Other valid typed event objects are ignored. Invalid JSON, malformed records, missing measurements, unsafe sums, or ambiguous totals fail with exit code 1, no stdout result, and a payload-free error code on stderr. Explicit measured zero is valid; unknown usage is never converted to zero.

Input and decoded events are each bounded to 262144 UTF-8 bytes (the entire stdin JSON envelope must fit). Blank lines are allowed. A partial stream is not evidence of full-run usage; callers must independently establish completeness and provider semantics before attributing this total to a run.

Example

Input: {"events_json":"{\"type\":\"step_finish\",\"part\":{\"id\":\"a\",\"tokens\":{\"total\":6840}}}\n{\"type\":\"step_finish\",\"part\":{\"id\":\"b\",\"tokens\":{\"total\":7101}}}"}

Output: {"tokens":13941,"steps":2}

Version changes must create a new immutable package and follow existing review and promotion gates. Do not infer approval from these local tests or from this document.