Skip to content

Authored checkpoints: accept FRLG sections, notes, once_per_save and execution fields - #84

Merged
dayfine merged 1 commit into
mainfrom
schema/frlg-story-json
Nov 10, 2026
Merged

dayfine merged 1 commit into
mainfrom
schema/frlg-story-json

Conversation

@dayfine

@dayfine dayfine commented Nov 10, 2026

Copy link
Copy Markdown
Owner

Arduino-Source #314 (dayfine/Arduino-Source) turns every FRLG story checkpoint into an authored plan, and those plans use fields the authored-checkpoint schema rejected: `sections` of events (plain `events` still allowed), `notes`, `once_per_save`, and FRLG `execution.supplies`/`live_start`/`handoff`. This adds them to the story-checkpoint and authored-checkpoint schemas and the Python readers, still strict (unknown fields rejected, events xor sections, non-empty sections), and checks in the 35 plans from #314 at 3dcf3e8 byte for byte as fixtures; the pinned 00.05 Parcel file is unchanged. Tested with the full unittest suite on Python 3.8 and 3.12 (including the schema tests with jsonschema installed), `json_schema --check-published` and `contract_format --check`.

🤖 Generated with Claude Code

https://claude.ai/code/session_013VUubhHeYSMGSSDXZkKZss

…execution fields

Arduino-Source #314 moves every FRLG story checkpoint to an authored plan.
The common checkpoint now takes events or named sections, notes on the
checkpoint/section/event and once_per_save on events; FRLG execution takes
supplies, live_start and handoff beside menu. Schema and Python reader
accept exactly those, and the 35 plans from #314 are fixtures for both.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_013VUubhHeYSMGSSDXZkKZss
@dayfine
dayfine marked this pull request as ready for review November 10, 2026 02:43
@dayfine
dayfine merged commit d3b85b4 into main Nov 10, 2026
8 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant