docs(discovery): audit and correct external Atrinik listings

[zoeyrose]

Outcome

Create a maintained inventory of Atrinik's external listings and backlinks, correct stale or misleading records, and consistently direct visitors to the canonical player journey on atrinik.org.

The repository should own the canonical facts, proposed corrections, target URLs, and public result evidence. It must not own third-party credentials or imply authority to contact maintainers, claim accounts, or edit external services.

Why

Third-party records can surface before the canonical website in branded searches. Stale platform, release, website, or playability claims confuse potential players and divide the project's limited search authority.

Known records worth reviewing include:

• LinuxLinks;
• SourceForge;
• relevant Crossfire/fork-history pages;
• open-source game directories and preservation lists;
• Atrinik organization and repository website metadata.

Accurate corrections and editorial links are a free source of qualified referral traffic. Paid backlinks, reciprocal-link schemes, automated submissions, and indiscriminate directory placement are not.

Scope

• Add a repository-owned discovery inventory recording, for each relevant result:
  • public URL and service;
  • current owner or public correction/claim mechanism;
  • date and method of verification;
  • inaccurate or obsolete claims;
  • proposed factual replacement copy;
  • canonical Atrinik destination;
  • approval, submission, and public-result status.
• Establish one reviewed fact sheet covering:
  • the maintained Classic line and incomplete replacement foundations;
  • supported platforms and immutable current release;
  • licensing and authorship boundaries;
  • founding/history claims;
  • current public-play and server availability;
  • canonical homepage, download, play, source, and issue URLs.
• Prioritize records that are already indexed, have relevant audiences, contain incorrect links, or can provide an editorial backlink.
• Prepare concise correction text for each priority record. Ground every claim in repository or deployed-service evidence.
• Review Atrinik-owned GitHub profile/repository website fields for consistent canonical links.
• Record only public result URLs and non-personal status evidence. Do not commit credentials, private correspondence, account identifiers, or personal contact details.
• Recheck accepted corrections periodically so they do not drift from current releases or service availability.
• Do not advertise a continuously playable public game until the public discovery/connect path has passed its owning readiness checks.

Important

Inventory, fact-checking, and draft preparation are authorized repository work. Contacting an external maintainer, claiming a listing, changing an organization/profile field, creating an account, or submitting a correction requires a maintainer to authorize the exact target and action first. Record that authorization in this issue before performing the external write.

Acceptance criteria

• A version-controlled discovery inventory covers the known records above and any additional high-value branded results found during the audit.
• Every proposed correction cites current authoritative evidence and distinguishes Classic from the replacement foundations.
• Canonical destinations are deliberate and do not rely on mutable release URLs, tracking redirects, or a service that is not ready.
• The fact sheet and per-site drafts contain no unsupported platform, uptime, feature, authorship, or release claims.
• The process explicitly rejects paid links, link exchanges, mass submissions, and misleading keyword placement.
• No third-party contact, claim, account creation, profile change, or submission occurs without target-specific maintainer authorization recorded here.
• For each authorized correction, the final public URL, date, observed result, and any remaining discrepancy are recorded without private correspondence or credentials.
• Website validation and git diff --check pass for repository changes.

Dependencies

• Relaunch atrinik.org from the standalone MIT website repository #4 owns the canonical information architecture, player routes, redirects, and honest availability states.
• content(media): replace temporary generated concept art with human-created visuals #22 owns human-created, provenance-cleared public imagery for listings that accept media.
• chore(seo): establish search indexing and webmaster baseline #25 owns the authoritative search-indexing baseline.
• content(play): publish a player-first Classic getting-started path #28 owns the canonical player journey that corrected listings should eventually target.
• atrinik/metaserver-worker#18 owns the final public discovery, publishing, and rendezvous endpoint boundaries. External copy must not promise a working public-play path before that cutover and its consumer releases are proven.