MADE 0.6.0

MADE 0.6.0 strengthens execution ownership and makes returning to a state durable. It also fixes counted-join publication and rebuilds the documentation around installation, authoring, execution and embedding. Hosts remain responsible for launching workers and performing external work.

Breaking changes: upgrade clients with the engine

Completion now requires the unchanged claim_fence returned by the accepted claim. Capture it before starting work and send it with the result. Missing or malformed fences are invalid requests; wrong or superseded fences are refused without appending events, changing outputs/context or clearing the replacement worker’s lease. Never attach an old result to a newer claim’s fence. Fencing does not undo external side effects. (#127)

Rust EmbeddedMade::start_step now returns StartCeremonyStepOutput. Use claim.attempt() where needed, retain claim.claim_fence().clone(), and pass the fence as the fifth argument to CompleteCeremonyStepInput::new. Application-owned run_step retains its accepted fence automatically.

Report ids, reconsideration conditions and scoped recipients now share a 100-item limit and uniqueness after whitespace normalization. Reports and conditions must be nonempty; omitted or empty transport recipients mean the whole table. Report ids and conditions retain input order; role ids remain an ordered set. Invalid commands are rejected, not shortened or deduplicated. Rust callers must handle validated types and fallible constructors, including GenerateCeremonyReportInput::new. (#100)

Durable execution and authoring

• Transitions seal a destination state_visit and exact step reset set. Re-entering a state starts fresh work while retaining prior executions. State visits, state repetition, step repetition and retry attempts remain distinct coordinates. (#129)
• Analysis warns when global all_steps_completed waits for downstream work it prevents from running. The warning does not change the guard’s execution semantics. (#143)
• Definitions using steps_completed:n now publish, reopen from SQLite and execute across the shared surfaces. The fix preserves other guards’ canonical bytes. (#150)

Before upgrading writers, preserve a consistent SQLite backup and update clients. Historical events remain readable without rewriting their bytes; older binaries are not guaranteed to read newly appended visit schemas. An executable downgrade alone is not a store rollback. Follow the migration guide.

Documentation and installation

The new documentation includes complete examples and a MADE wordmark in SVG, ASCII and Unicode forms. Two historical archives preserve 95 files with byte-length and SHA-256 manifests.

MADE’s catalogue is now made, displayed as MADE, with plugin identity made@made. It remains in this repository’s existing marketplace branch, which now points to this release. Plugin assets for four platforms are public. See plugin installation for setup and migration from the old catalogue.