Promoted scripts/bootstrap.sh out of draft state. The bootstrap script that handles curl-installable Aerodrome installs has carried a "DRAFT" marker since the early scaffolding days — header version 3.0.3-draft, title line ending in "(DRAFT)", and a multi-paragraph DRAFT NOTICE block at the top listing four conditions that needed to be true before the script would actually work: the GitHub repo had to be public, the Releases-based publishing flow had to be live, the GitHub Releases API endpoint had to return real release data, and install.aerodromeadsb.com had to redirect to the canonical bootstrap URL on raw.githubusercontent.com. All four are now satisfied: the repo went public earlier today, eleven Releases have shipped through the v3.0.x cluster, the API endpoint returns real data (the in-app update channel polls it every check cycle), and the Cloudflare DNS + Single Redirect that took install.aerodromeadsb.com live was verified end-to-end earlier this session. The DRAFT NOTICE block is therefore stale and actively misleading — a user reading the script would see "NON-OPERATIONAL until..." conditions that are demonstrably already met.
Three changes land in v3.0.12: (1) header version bumped from 3.0.3-draft to 3.0.12 to match the parent release (and to make --help output a real version string rather than a placeholder), (2) title line scrubbed from "Aerodrome — Curl Install Bootstrap (DRAFT)" to just "Aerodrome — Curl Install Bootstrap", (3) the entire DRAFT NOTICE block removed and the "Headline command (post-launch)" / "Local testing today" lines collapsed into a clean "Headline command" / "Local testing" pair (the post-launch qualifier no longer applies; the local-testing example was pinned to a v2.97.4 zip filename which is ancient — replaced with a generic aerodrome-vX.Y.Z.zip placeholder that doesn't go stale on every release). The show_help() heredoc at the bottom of the header was already clean (already used the generic vX.Y.Z placeholder) so no change needed there.
No functional change. Same prereq detection, same OS-compat handling, same version resolution, same download/verify, same prompts, same install.sh handoff. The DRAFT scrub is purely a cosmetic and documentation correction reflecting that the script's prerequisites are now real.
What's NOT in v3.0.12 yet: an end-to-end clean-VM dogfood of the actual install flow. The bootstrap has been exercised locally via --from-zip paths many times and the curl-redirect surface was verified through HTTP-level smoke tests (302 + correct Location header + Cloudflare server header + content match), but no fresh Ubuntu droplet has actually run bash <(curl -fsSL https://install.aerodromeadsb.com) end-to-end through the prereq install + GitHub fetch + zip download + sha verify + interactive prompts + install.sh handoff + service start. That dogfood is the gate on announcing the install URL in the README and the in-app About panel; until it passes, the URL stays live but unannounced (working for anyone who already knows it, not promoted to new users). Whichever release follows v3.0.12 (presumably v3.0.13) will land the README + About-panel announce after the dogfood succeeds — splitting promotion from announce keeps the README on main from referencing an install URL that hasn't been end-to-end verified.