Deck keywords to PetroScript

Generated by tools/generate_reference_pages.py from the keyword registry, the importer’s disposition tables, the summary family registry and the public surface. Do not edit this file: python tools/generate_reference_pages.py --check fails on drift.

One line per keyword, so grep GRIDFILE docs/reference/eclipse-to-petroscript.md returns the whole answer. Headings are the deck section a keyword belongs to.

Statuses:

• semantic — the importer reads the keyword into semantic objects.
• captured-into-run — the keyword is a run setting the loader states on the model; the spelling names the field that holds it (on ps.Output, ps.Numerics or ps.Capacity).
• recorded-directive — a runtime message directive the importer reads past; the model holds nothing of it.
• lexical — block-comment mechanics the reader consumes before any handler runs; the note is what the keyword does to the text around it.
• deferred — not inverted yet; the note is the boundary.
• non-goal — deliberately outside the semantic API; the note is the reason.
• no-import-handler — the compiler emits the keyword, the importer does not dispatch it by name yet.
• not-yet — PetroScript has no statement for it yet and the importer does not read it; the note says where Flow documents it or what Flow does with it.
• RPTRST mnemonic, RPTSCHED mnemonic — a word of those report cards, written from ps.Output.