MAESTRO Integration

CARL 0.3.0 added a typed surface that MAESTRO (and any MAESTRO-aware tool) uses to persist, re-run, and introspect chains. You can use these directly too.

Piece	What it’s for
Preflight	Statically ask what a chain needs (tools / MCP servers / skills) before running — and what’s missing.
RunRecord	A durable, replayable audit record of one execution (chain + input + result + timing).
MAESTRO metadata	A typed provenance block on the chain (task, attached files, tags) — and re-priming a context from it.

These are the building blocks behind MAESTRO’s Library: save a generated chain with its metadata, preflight it before a re-run, execute, and store a RunRecord of each run.