AutoStopper

Added

• Added coordinator-owned operator lifecycle commands for mapped servers: /autostopper start <server>, /autostopper stop <server>, /autostopper restart <server>, /autostopper hold <server>, and /autostopper release <server>.
• Added command-specific permission nodes (autostopper.command.start, autostopper.command.stop, autostopper.command.restart, autostopper.command.hold, autostopper.command.release) while retaining autostopper.admin as an explicit umbrella.
• Implemented runtime shutdown holds that suppress automatic inactivity shutdown without blocking manual commands or player-driven wake-up. Holds survive unchanged reloads and clear on proxy restart, mapping removal, or mapping replacement.
• Manual stop and restart enforce strict safety invariants, refusing execution if connected players or lifecycle waiters are present, with an immediate deterministic pre-Docker safety re-check on the worker thread.
• Manual restart runs as one atomic coordinator-owned stop → start → readiness sequence under a single authoritative future.
• Surfaced hold state in /autostopper status and updated /autostopper help with permission-filtered entries and argument tab completion.
• Pinned stable Velocity 4.0.0 build 6 as the production support line on Java 25, tested by the packaged-runtime system tests and the release-candidate Docker/Minecraft gate. Velocity 3.5.1 on Java 21 remains the tested minimum/floor, and Velocity 4.1.0-SNAPSHOT on Java 25 remains clearly labelled preview validation.
• Added the RUNNING_UNVERIFIED operational state so a Docker-running container is not reported as ready until AutoStopper has completed the configured readiness contract for the current mapping lifecycle.
• Connecting players now receive authoritative inspection, startup, readiness, connection, and terminal lifecycle messages. Late arrivals see the current shared stage and unique waiter count.
• Redesigned command and chat presentation around the brand identity ("Empty servers sleep. Players wake them."). Replaced legacy bracketed prefixes with clean brand prompts (AutoStopper ›, AutoStopper ✓, AutoStopper !), added scannable deterministic status rows with humanized states and durations, and introduced permission-filtered help with fuzzy command matching.
• Added contributor-facing message style guide (docs/message-style-guide.md).
• Added structured, typed lifecycle telemetry and bounded process-lifetime observability (#74). Authoritative lifecycle operations emit machine-parsable INFO log lines (op=, server=, origin=, outcome=, elapsed_ms=, waiters=) with monotonic duration measurement, and intermediate stage durations emit DEBUG logs. Simultaneous waiters receive 1 shared startup record plus individual connection wait records. Aggregates use thread-safe bounded memory with strictly zero PII and observational exception insulation.

Changed

• Operational status now reconciles Docker observations lazily with mapping-aware lifecycle revisions. Active transitions remain authoritative, stopped/degraded Docker state overrides stale quiescent state, and results captured before reload, mapping replacement, or newer lifecycle work are discarded without eager startup readiness probing.

Fixed

• Restored command and lifecycle messages on Velocity 3.5.1 by avoiding the Adventure 5 component-builder ABI incompatibility and validating every message factory against the pinned Velocity runtimes.