[transitrix-foundry]

What changed

The recurring-Activity specification defines calendar gap exclusions, first-instant fold handling, and an explicit versioned policy with a bounded admission window. Worked cases distinguish late admission, missed occurrences, skipped busy steps, and invalid policy bindings. Durable runtime records belong to the executing integration.

The contract and its three navigation references distinguish accepted specification from tooling support and release availability. No new files, validators, scheduler, or runtime store are added.

How it is verified

• node scripts/check-notations.mjs (four existing warnings, no errors).
• node --test scripts/check-notations.test.mjs scripts/release-obligations.test.mjs (113 passing).
• git diff --check.
• Parsed all four YAML fragments and checked policy binding, distinct execution identities, and persistent instance examples.
• Rendered Markdown tables and examples and reviewed the full document in headless Chrome.
• Existing process examples, ACTION fields, vocabulary, validators and BPMN validation rules retain their current behavior.

Checklist

• Based on current main, one concern per PR.
• Commit signed off.
• Public content and metadata reviewed.