oc-checkpoint-protocol

原文涵盖的主题

• Checkpoint Protocol
• Two versions, don't confuse them
• Problem Statement
• Core Concepts
• 1. The Checkpoint File
• 2. Checkpoint Schema
• 3. Status Values
• Resume Protocol

A cross-skill convention for session persistence. Any skill that runs multi-step workflows across conversations adopts this protocol to save, resume, and recover state without the user re-explaining context. This is a protocol, not a skill. It defines a file format, naming convention, resume behavior, and integration contract that individual skills implement. Think of it like HTTP — the spec lives here, the implementations live in each skill. protocolversion — the on-disk schema version, currently "1.1". It lives inside every checkpoint file and only changes when the file shape grows in a way the validator must know about. The validator (scripts/checkpoint.mjs) enforces it and accepts both "1.0" and "1.1". Skill release version — the version in this file's YAML frontmatter. It tracks the evolution of the docs and tooling (the pmrefs extension, the doctor/next commands, etc.) and moves independently, in lockstep with the rest of the catalog. oc-release-ops bumps it. Additive fields, two ways to ship them. An optional additive field can ride under the same wire version — pmrefs (skill release 1.2) was added under schema "1.0" with no wire bump, because old checkpoints stayed valid an

这里只展示节选，请以完整原文和当前要求为准。