content(guide): publish a verified first-hour Classic walkthrough

[zoeyrose]

Outcome

Publish /guides/first-hour/ as a task-oriented walkthrough that takes a new player from first launch through a meaningful first session in the supported Atrinik Classic release.

“First hour” describes the intended beginner scope, not a guaranteed completion time.

Why

Installation guidance alone does not teach a player how to recognize a successful connection, begin safely, understand the interface, or reach an initial objective. A verified beginner walkthrough improves activation and retention while restoring the useful intent behind the archived starter and player-guide routes identified in #4.

Scope

• Add a fully static /guides/first-hour/ route.
• Start with a concise handoff to /play/ for download and installation, then cover only first-session actions that have been verified end to end.
• Structure the guide as observable tasks with:
  • the action to take;
  • the expected visible result;
  • a concise recovery step when that result does not occur;
  • accessible text that does not rely on color, position, or screenshots alone.
• Test the walkthrough against one exact supported Classic client/server release pair and a reachable, supported player scenario before presenting it as currently actionable.
• Reuse validated release identity where possible. Record the exact version, verification date, and end-to-end test evidence in review without embedding internal topology details or mutable private infrastructure in public prose.
• If the current public service is unavailable, do not publish a false successful-connection path. Render an honest readiness note or hold the actionable portion until it can be verified.
• Keep the scope to onboarding and the first meaningful player objective. Link to /game/ and /world/ for discovery, and to owning repository documentation for advanced configuration or troubleshooting.
• Avoid example credentials, real account/character identifiers, private server details, excessive spoilers, and instructions that alter or bypass supported client configuration.
• Capture any instructional screenshots from the exact verified release, redact private identifiers, and catalog every image under the full media and provenance contract. The guide must remain understandable without images.
• Permanently redirect /page/starter_guide* and /page/player_guide* to the new route.
• Add the route to the sitemap and provide a page-specific title, description, canonical URL, semantic ordered structure, and descriptive internal links.
• Use static Astro/HTML/CSS only. Do not add browser automation, interactive tours, account handling, live APIs, embeds, analytics, or a server runtime.

Acceptance criteria

• A reviewer can follow the guide from the supported launch state through its stated first-session objective using the named Classic release.
• The pull request records the exact client/server versions, verification date, scenario prerequisites, results, and cleanup used to validate the walkthrough.
• The public page derives or links mutable release facts from validated sources and does not silently drift from the selected supported release.
• The guide does not claim successful public connection until that path has been tested end to end.
• Every step includes an observable expected result and useful recovery direction.
• Instructions remain usable without screenshots; every included image is provenance-cleared, current, accessible, and free of private identifiers.
• The two archived guide routes redirect permanently without a redirect chain.
• /play/, /game/, and /world/ are linked instead of duplicating their content or repository technical documentation.
• The route appears in the sitemap and passes internal-link, accessibility, responsive, reduced-motion, no-JavaScript, security, provenance, and performance validation.
• npm run check, npm run build, npm run deploy:dry-run, and git diff --check pass.

Dependencies and coordination

• Depends on the player journey in content(play): publish a player-first Classic getting-started path #28 for download, installation, and connection readiness.
• Requires a supported, reachable player scenario before the walkthrough may be described as currently actionable.
• Coordinate screenshot selection and provenance with content(media): replace temporary generated concept art with human-created visuals #22. A text-first guide may land earlier if it remains complete and usable without media.
• Link rather than repeat the discovery material in content(discovery): publish verified gameplay and world pages #29.
• This is the focused starter/player-guide slice of Relaunch atrinik.org from the standalone MIT website repository #4, not a replacement for Classic's technical or contributor documentation.
• The generated-file validation cap must accommodate the route or receive a deliberate, documented adjustment without loosening byte or JavaScript budgets.