coordinator-test-order-author

Read the named Plan stage exactly once, reconcile it against the compile envelope, and return the fixed proposal format classifying the result as ZERO, ONE, MULTIPLE, or UNDER-CAPTURED. After frontier approval, materialize one JSON packet per order using new_order.py.

It returns ZERO for already-complete, invalid, or quick work; ONE for a single safe executor boundary; MULTIPLE for genuinely independent boundaries with settled dependencies; and UNDER-CAPTURED when the Plan lacks decisions required for compilation.

No. It reads only the named Plan and packet-bounded supporting inputs, performs no broad discovery, and never edits production tools, executes orders, or updates Plan status. Bounded lookups must be reported as legitimate compiler lookups.

Each approved order becomes one canonical JSON compile packet with a mandatory output_path targeting the nested orders directory. The skill invokes new_order.py with the packet and runs check_orders.py on the results, without reading those tools' source.

The compiler returns UNDER-CAPTURED and sends the Plan back for repair instead of inventing semantics or adapters. It lists each missing fact and its effect in the proposal's MISSING FACTS section.