content(discovery): publish verified gameplay and world pages

[zoeyrose]

Outcome

Publish /game/ and /world/ as concise, player-facing discovery pages that show what Atrinik Classic genuinely offers today and introduce its world without presenting concept art, archived claims, or future foundations as released gameplay.

Why

The current site explains project identity, licensing, and implementation paths, but it has no durable destination for visitors asking two basic questions: “What do I do in this game?” and “What kind of world is Atrinik?”

Useful, independently authored answers strengthen the discovery journey specified in #4, give search engines substantive player content to understand, and provide accurate landing pages for community referrals.

Scope

• Add a fully static /game/ page describing a carefully selected set of currently verifiable Classic gameplay systems.
• Add a fully static /world/ page giving a spoiler-conscious introduction to the setting, places, themes, and player perspective.
• Establish evidence for every concrete mechanic, availability, place, history, and content claim during implementation:
  • verify current gameplay against the supported Classic release and its owning source/content;
  • record the exact evidence reviewed in the pull request;
  • omit uncertain, historical-only, disabled, or unreachable features.
• Independently author website presentation copy. Do not copy prose, maps, art, screenshots, or other material from archived/GPL/mixed-authorship sources into the MIT website without complete applicable provenance and permission.
• Make clear that the website is a discovery layer, not the canonical gameplay, content, protocol, map, or developer-documentation authority.
• Keep current Classic capabilities separate from next-generation direction; future work may be linked but must not be framed as playable.
• Prefer authentic, current gameplay screenshots when provenance-cleared media is available. Until then, use semantic text and CSS rather than presenting the temporary concept images as gameplay or authoritative geography.
• Cross-link the pages with the homepage, /play/, /downloads/, and each other using descriptive link text.
• Add page-specific titles, descriptions, canonical URLs, semantic headings, and sitemap entries.
• Keep technical build, content-authoring, map-making, protocol, and server instructions in their owning repositories rather than creating a second documentation tree.
• Use static Astro/HTML/CSS only, with no browser JavaScript, embeds, live API dependency, CMS, database, or tracking.

Acceptance criteria

• /game/ answers what a player can actually do in the supported Classic release using specific, useful, evidence-backed descriptions.
• /world/ provides an original, accessible, spoiler-conscious introduction without claiming that concept imagery is gameplay or canonical geography.
• Every concrete feature and world claim has review evidence recorded in the pull request; unverifiable claims are removed or explicitly qualified.
• Classic and next-generation status and license boundaries are unambiguous.
• No archived prose or media is republished without the required provenance decision and exact license evidence.
• Every published visual satisfies the website media catalog contract, including source, immutable revision, digests, dimensions, creator, license, transformations, notice, and accessible alternative.
• Both pages are reachable through the player journey, have canonical metadata, and appear in the sitemap.
• The pages remain useful without images and work with keyboard-only input, representative screen readers, narrow/desktop layouts, reduced motion, and no JavaScript.
• The built output retains zero repository-authored JavaScript and passes the established security, accessibility, provenance, and performance budgets.
• npm run check, npm run build, npm run deploy:dry-run, and git diff --check pass.

Dependencies and coordination

• This delivers the gameplay, gallery, and world-discovery intent retained in Relaunch atrinik.org from the standalone MIT website repository #4 without duplicating repository technical documentation.
• Link coherently with the player journey in content(play): publish a player-first Classic getting-started path #28 and align metadata with feat(metadata): add structured identity, favicons, and page-specific previews #27.
• Coordinate all visual selection and replacement work with content(media): replace temporary generated concept art with human-created visuals #22. The pages may ship with an honest text/CSS treatment while provenance-cleared gameplay media is pending.
• The first-hour guide should link to these pages rather than repeat their feature or world overview.
• The generated-file cap must be revised deliberately before both new routes can coexist with the other proposed content routes; retain the aggregate byte and zero-JavaScript budgets.