opentine v0.34.0: price the evidence, preserve the context

v0.34.0 refreshes the signed pricing catalog from 231 to 248 cards. It also includes the v0.31–v0.33 timestamp, rewind, and fork improvements now documented on the site.

The common theme is preserving what the evidence actually supports: a known price at a known time, a verified original file, an explicitly edited event, or a timestamp checked against operator-supplied roots.

Catalog coverage is not a price guess

The release catalog was checked by the project against provider pricing pages on 2026-11-03. Added coverage includes GPT-6.1 Terra and several older OpenAI models, Gemini 2.5 variants, two Grok 4.20 variants, and Mistral-hosted GLM and DeepSeek models. Added catalog cards do not necessarily mean newly launched models.

tine pricing check
tine pricing show openai gpt-6.1-terra
tine pricing list --provider mistral
tine price run.tine --json

Long-context rules, audio dimensions, provider endpoints, and effective dates still matter. A Mistral-hosted model card does not establish the direct provider's price.

When a launch date is unpublished, new cards begin on 2026-11-03; older runs remain cost-unknown. Mistral Large 4's changed rate starts on that date because the actual change date is unknown. Its 2026-10-21 through 2026-11-02 interval reports unknown rather than receiving a guessed current rate.

The catalog guide lists additions and date boundaries. This is a signed release snapshot, not a guarantee of live provider pricing or endpoint availability.

Fork edits extend to repository history

Since v0.33, edited forks work with repository --ref paths and repo-fork --from-event, not only portable files. The edited event replaces the fork-point event, remains unexecuted, and records its operation log under fork_overrides.edit, bound by the run object ID.

--unset PATH deletes a key or list item; --set PATH[+]=VALUE appends to a list. Edits apply in order: file, set, then unset. The edited step's own transcript turns are dropped because they describe the replaced call; unscoped turns remain. Unedited fork identities are unchanged.

See the fork guide before constructing an edit. Invalid paths still refuse rather than silently changing another field.

Rewind can use verified originals

v0.32 records first-edit originals for supported Claude Code transcript/live paths and Gemini imports. Rewind prefers the original replayed through recorded edits, checking stored digests along the way.

tine rewind run.tine --json

Per-file recovery reports exact, reconstructed, or skipped, with fallback details when an original is unusable. Originals changed by redaction are not written as if they were authentic original bytes. Older artifacts do not gain missing evidence retroactively, and rewind stays dry-run-first.

Timestamp checks are now published

v0.31 added RFC 3161 sidecars and offline local-root verification:

tine timestamp data run.tine
tine timestamp attach run.tine token.tsr
tine verify run.tine --offline --tsa-roots tsa-roots.pem --json

Token fetching remains your job. Missing roots are unavailable, not passes; timestamp checks are not required checks. A timestamp does not independently prove who authored a run or that every recorded event is true. Read the timestamp guide for the verification boundary.

Upgrade without changing the v4 contract

python -m pip install --upgrade "opentine==0.34.0"

Python remains 3.11–3.14. Final writes default to v4 and require readers 0.26 or newer. Bare migration writes a sibling file; use --dry-run for preview only. Read the upgrade guide, GitHub release, and tagged changelog for exact release behavior. The package is on PyPI.