[dop42]

Operators following the old setup could miss a required resource, fail pool activation, have no pictures or overwrite local configuration during an upgrade. The getting-started path now covers the current installation end to end:

• Three required resources, exact directories/load order, compatible game/runtime and dependency versions.
• MySQL/MariaDB installation, dedicated account, process/service environment, identity export and complete staff ACL example.
• Separate opx_images uploader and server key setup, outbound HTTP allow-list, logical names and catalogue diagnostics.
• Pool assets 0.3.1, compatible client ArchiveXL installation, one-table activation, 15+1 rack, modes/controls and installed-optics assistance.
• Configuration review, surveyed locations, required restarts, safe staged upgrades and durable economy/legacy receipt handling.
• Symptom-based troubleshooting and corrections to the resource overview, own-overlay notifications and fuel default.

Source: opx_infinity 594b9b2665bb8c10e82746c07256c57bab8e909f; opx_pool_assets 0.3.1; actual image uploader and server implementations; Open77 host, startup, SQL and ACL guides; Open2077 ArchiveXL open77/cyberpunk-2.5 instructions and v1.27.5-open77.6 release. Companion framework PR: opx77-framework/opx_infinity#156.

Validation: content/link checks (288 pages, zero problems), type check; production build passed (all six operator guides exported); CI required before merge. API coverage compared against main: both check 2,786 published names and report the same 933 existing failures from reference pages that lag runtime development; this operator setup update introduces none. No runtime/placement changes or new in-game verification claims.

Closes #17
Closes #18
Closes #19