[valzargaming]

Behavior

Adds an opt-in, cached, read-only launcher directory at /.well-known/civ13/servers.json on the existing civ13.com authority. Exact canonical provider queries select civ13.com or valzargaming.com inventories. Both configuration options default to empty.

• Managed enabled servers and strict status-only inventory share uniqueness and target bounds. Status-only rows never construct or enable GameServer.
• Bounded asynchronous BYOND status queries publish only fresh, complete, online metadata, including zero-player servers. Public probes validate all IPv4 DNS answers and connect to those exact literals within one three-second deadline.
• An optional loopback-only standalone entrypoint and committed minimal dependency lock produce a checksummed directory artifact without Discord or the live bot bootstrap.
• Integration preserves current main's Windows/native supervisor, verifier and heartbeat behavior. Production DNS discovery stays inside the production profile branch, fixing the portable startup regression exposed by integration CI.

Verification

Final source head: a8df5bf3a0460a93dc3ceddcb0a491a444f48ae8.

• Independent source review covered all directory classes, HTTP/options integration, standalone entrypoint, artifact tooling and the portable DNS fix; no correctness findings remained.
• PHP 8.3–8.5 dependency, lint, five directory suites and bot regressions: passed.
• PHP 8.3–8.5 isolated bundle build, audit, verification and bundled dependency tests: passed.
• Windows/Linux PHP 8.3–8.5 portable startup contracts, local profile contracts, and passive heartbeat contracts: passed.
• Direct exact-head check reads showed 29 successful checks and the expected skipped docs publication. Artifact upload is intentionally limited to PHP 8.4.
• Local checks: directory/integration PHP lint, git diff --check, and the synthetic portable bootstrap positive/negative controls passed. No broad local suite or local dependency installation was performed.

Deployment gates

The source feature is ready for review. Production inventory/ports, proxy configuration, verified pinned artifact, actual endpoint behavior and genuine BYOND joins remain separate deployment gates. A configured empty provider returns 200/empty; an unconfigured provider returns 404; stale/warmup returns 503.

Do not bootstrap unknown autoload files, change the live vendor tree or restart the live bot for this feature. No production configuration, endpoint deployment, bot/game restart, firewall/TLS change or release was performed. See docs/launcher-directory.md and docs/launcher-directory-standalone.md.