Deploy page: real FAILED box screenshot (preflight catching an existing resource group)
Deploy page: terminal screenshots in a Windows PowerShell window frame
Deploy page: real GOAD-Light teardown screenshot in the Teardown section
Deploy page: real GOAD-Light terminal screenshots of the deploy, DONE box, manage help and status
Deploy page: drop the terminal images until a real GOAD-Light capture exists, text DONE and FAILED boxes back, Windows key permissions note
Deploy page: terminal images of a deploy, a failure, the manage help, status and teardown; DONE box watch line is rsp-watch
Wiki: no roadmap hint on the none teamserver, plain Prerelease status
Key pair and auto-stop names are unique per account or region, not account-global
AWS suffixed names are unique per account or region, not all account-global
GCP needs a distinct prefix per range, Proxmox and ESXi on the roadmap, drop the edition lines, compile -o refusal, execution policy note, preset OS, minilab status, owner line
Per-shell python commands for verify.py, split the run-from-source chains, teamserver forward row protocol, DRACARYS path wording, name resolution note
Correct wiki facts against the code: auto-stop and its AWS permissions, the Windows key command, VPN configs and rsp-operator, verify.py, publish, labs, ingress
Deploy and teardown output, Windows 11 default, Azure client licensing
Deploy needs Python 3.8+ on your machine; Azure resource group is named per range
Providers: full GOAD and dracarys validated on Azure, the beacon path; drop the removed WireGuard transport note
Mark Azure supported across the wiki; Kali Marketplace subscription is once per account
Add Azure to Cloud Prerequisites: auth, resource providers, sizes and quotas, the preflight
docs: dynamic version badge on Home so it tracks the latest release
docs: unify python to 3.11 and point the docker pull at :latest Matches the canvas requires-python and the main repo README. The Getting-Started quickstart now pulls :latest instead of a pinned version.
Document teardown --force for an interrupted deploy An interrupted deploy can leave instances outside terraform state that a plain teardown cannot remove; manage.sh teardown --force deletes them in the cloud first, so nothing is left billing.
Document verify.py, rsp-check, and the C2 payload recipe Deploying a Range gains a "Verify the deployment" section for verify.py (doors and stack) with pointers to rsp-check and the briefing. Redirectors and Cover Stories gains the operator payload recipe (callback domain, URI prefix, gating header) and an on-box "Checking a redirector" section for rsp-check.
Remove Schema version section from Concepts
Drop schema-version framing from Home status blurbs
Rename Library and Templates page to Library and Blueprints
Align blueprint terminology with the canvas UI The shipped canvas calls any cloneable starting point a "blueprint", both the shipped ones loaded via "Load blueprint" and a user's own topology published to the Library for others to clone. The wiki split this as "template" (shipped) vs "blueprint" (published), which contradicted the UI. Migrate the shipped-starting -point sense of "template" to "blueprint" across the concept and reference pages, keeping a private working copy as a "topology". Certificate templates, GitHub issue templates, and the [[Library and Templates]] wikilink targets are left as is.
Canvas button is Load blueprint, not Load template The toolbar button was renamed to "Load blueprint" in the shipped canvas; the wiki still called it "Load template" in three places.
docs: subjective readability and structure pass Verified subjective improvements across the wiki (clarity, structure, navigation, terminology), no command or fact changes.
docs: document the prefix as the per-range identifier for concurrent ranges Deploying-a-Range now tells users to give each concurrent range a distinct prefix; the account-global cloud names carry an automatic per-deployment suffix so ranges never collide in one account, in one region or several.
docs: prerelease consistency, readability, and reporting callout Consistency and readability pass across the wiki (terminology, schema versions, cross-links, provider matrix, grammar). Home prerelease callout now tells users to open an issue and attach the scrubbed logs/deploy-*.log for analysis.
Rename ARTIE/HAVEN to Offense/Defense across the wiki