feat(metadata): govern public authorship disclosures in repository descriptions

[zoeyrose]

Outcome

Make Atrinik's public repository metadata a governed, reviewable expression of
the project identity: human-made game content and art, with software developed
primarily through Codex-driven agentic workflows under human direction.

Repository descriptions are currently configured live but are not represented
in this repository's desired state, so they can drift and none contains the
requested authorship/development disclosure.

Scope

• Add a validated per-repository metadata contract for GitHub descriptions and
  relevant homepage URLs, covering every active repository and preserving
  intentional archived-repository wording.
• Extend the publisher to compare live metadata, print a complete plan, and
  apply only explicitly authorized changes. Preserve repository IDs, archive
  state, default branches, and all unrelated policy.
• Use a concise role-based description strategy:
  • content, sound, and resources foreground human-created world/media
    and the no-generative-AI content policy;
  • classic identifies the human-origin 2009 Crossfire/Daimonin lineage and
    present Codex-led code maintenance without erasing upstream contributors;
  • server, client, editor, renderer, protocol, and
    content-toolkit identify the agentic clean-room Go/Rust/Protobuf
    reimplementation where space permits;
  • infrastructure repositories remain accurate and concise instead of
    repeating a slogan at the expense of their actual role.
• Add and generate an Atrinik organization profile README from
  community-health/ (the live .github repository has issues disabled).
  Present a readable project matrix, the human-made-world/agent-driven-code
  framing, Classic history, next-generation direction, and contribution links.
• State that direct human code contributions are welcome and use the same
  license, review, provenance, and validation gates. Do not claim every code
  commit is agent-written or publish an unverifiable percentage.
• Keep “generative AI” distinct from in-game NPC/artificial intelligence.

Acceptance criteria

• Desired-state validation requires one bounded description for every
  governed active repository and detects unknown, missing, duplicate, or
  over-length metadata.
• Plan mode reports exact live/desired description and homepage drift with
  no mutation; apply remains separately authorized and idempotent.
• Tests cover unchanged state, targeted updates, API failure, identity
  drift, archived repositories, and rollback/retry behavior.
• The generated organization profile renders correctly and links the
  canonical project, Classic, content, next-generation, website, and
  contribution surfaces.
• Descriptions accurately separate human-authored content from
  agent-assisted code and preserve Crossfire, Daimonin, Zoey Rose, and
  wider contributor credit at the appropriate longer-form surfaces.
• bin/validate, publisher plan/tests, shell validation, ShellCheck,
  actionlint where affected, and git diff --check pass.

No live descriptions should be changed merely while implementing the schema:
review the complete plan first and use the repository's documented explicit
apply workflow.