One-page operator quick-reference summary

[whisper67265]

Problem

The end-to-end walkthrough in GETTING-STARTED.md was thorough but not scannable at a glance. Operators returning to the repo needed a one-page summary of which workflow to run, when, and with which trigger or script—without reading every detailed section first.

Acceptance Criteria

• docs/GETTING-STARTED.md opens with an Operator checklist table covering steps 0–5 (secrets, local setup, three dispatch workflows, and mirror create-tag).
• The checklist includes dispatch-order and exit-code pointers to ARCHITECTURE §6 and the detailed walkthrough sections.
• tests/test_getting_started.bats asserts the checklist heading, trigger script names, GH_TOKEN, ARCHITECTURE return-code link, and dispatch-order guard text.

Implementation Notes

• The checklist sits above the detailed sections so the doc serves dual purpose: quick reference at the top, full walkthrough below.
• Dispatch-order and exit-code bullets reference existing issue-tracked concerns (issues 5 and 7) rather than re-documenting those contracts inline.

References

• docs/GETTING-STARTED.md
• tests/test_getting_started.bats