Choose the behavior you need
Fresh documentation journeys: 2026-11-20
The tutorial programs now have independent Python and TypeScript evidence for Vercel + built-in Pi 1.5.2 + the configured Messages endpoint using deepseek-ai/DeepSeek-V4-Flash. These records include source-file hashes; compare them before assuming a later edited program has the same verification. Endpoint/account details and resource identities remain in private local evidence, so the model name alone is not a reproducible credential or universal endpoint guarantee.
Together these are four tutorial journeys and six Runs for this one configured combination, not four or six distinct compatibility combinations. They are separate from the historical MiniMax and idle-recovery matrices below. Their successful deletion records do not settle earlier unrelated unknown resources.
Evidence snapshots
Counts below were derived from JSON rows.status during this documentation update. They describe each file’s recorded timestamp. The first counts combinations; the second counts SDK rows. Do not add them into a total of passed combinations. Regenerate the table if the source files change.Read an individual record
- Identity: inspect builtin version or full OCI digest/protocol/command. Built-in and OCI OpenCode are distinct distributions.
- Model: check actual endpoint, model ID, and Messages/Chat Completions/Responses. A shared vendor does not imply equivalent protocols.
- Client: inspect independent Python/TypeScript results, installed versions, and scenarios. A Python Harness does not prove Python SDK acceptance.
- Branches: check task, upload, Tools, approval, replay, artifacts, continuation, and recovery separately. Limited contracts such as Aider must not receive credit for untested Tools/artifacts.
- Cleanup: separate successful Session teardown, earlier failed-attempt resources, and account-wide resource audits.
Status and evidence types
Contract/simulation tests prove deterministic logic; live tasks record remote behavior for that run. Registry implemented/live_resource tags do not substitute for exact end-to-end records. Documentation structure checks do not verify examples or cloud behavior.