docs(governance): AGM date, FAQ anchor fix, interim board reconcile, CONTRIBUTORS.md

[bokelley]

Summary

Pre-GA transparency hardening against skeptical-reporter scrutiny. Six changes, one PR:

• Name the first AGM explicitly as May 6, 2026 in CHARTER.md, server/public/governance.html, and the FAQ — replacing a vague "2026" target. Adds "record date" language so the voting-eligibility window is clear.
• Reconcile the governance-page interim board with CHARTER.md. Malovrh (Celtra) and Masse (Triton Digital) replace Rothenberg and Schreurs, who are not directors per the Charter. Uniform initials avatars across all four entries so the page reads consistently.
• Fix the dead FAQ anchor referenced from the AI Disclosure page. The link faq#what-is-aao-s-relationship-with-scope3 did not resolve; rename the FAQ entry to "How is AAO related to Scope3?" for a punctuation-free slug, mirrored in the main-site AI Disclosure HTML.
• Rewrite the Scope3 FAQ to lead with the board-composition number rather than burying it; replace the soft "no single company controls" framing in "Who created AdCP?" with concrete interim-board composition and AGM date; disclose the seed-loan repayment source (membership revenue) and reference the annual financial report.
• Soften the AAMP comparison. AAMP is still defining its normative surface, so we describe the layer distinction as our read of published work streams rather than asserting AAMP's scope on its behalf. Added a "Layer" row to the comparison table.
• Correct hub.html fallback data that fabricated officer titles ("Chairman", "President", "CTO") for individuals who don't hold those roles. Now reflects the four actual interim directors with the accurate "Interim director" title.
• Add CONTRIBUTORS.md crediting external issue authors, PR authors, and working-group participants alongside Scope3 staff. Linked from CHARTER.md §7 (Transparency principles) and the FAQ "Who created AdCP?" entry. GitHub-rendered links use absolute docs URLs so the anchors resolve from the GitHub UI.

Removes orphaned server/public/ruben-schreurs.png (no longer referenced).

Also filed: follow-up comment on #2302 scoping the rc.1→rc.2 staleness sweep across whats-new-in-v3.mdx, release-notes.mdx, and prerelease-upgrades.mdx.

Test plan

• Platform-agnostic lint passes (node tests/check-platform-agnostic.cjs)
• vitest suite passes (pre-commit hook, 587 tests)
• TypeScript typecheck passes (pre-commit hook)
• Docs-expert review addressed (Must Fix items resolved)
• Copywriter review addressed (lead-with-the-number, AAMP softening, 501(c)(6) consistency)
• Code-reviewer review addressed (GitHub .mdx link rendering, orphaned asset removed, hub.html fallback reconciled)
• Security review clean (no protocol/auth/data-exposure changes; all published data already public)
• Manual: verify Mintlify-rendered anchor #how-is-aao-related-to-scope3 resolves from both ai-disclosure surfaces post-deploy
• Manual: spot-check governance.html board grid renders the initials avatars cleanly on the existing .board-photo gradient

🤖 Generated with Claude Code

[github-actions]

Schema Link Check Results

Commit: 9f70dfe - docs(contributors): correct name (Lizzie, not Liam) Lawlor

⚠️ Warnings (schema not yet released)

These schemas exist in source but haven't been released yet. The links will be broken until the next version is published:

• https://adcontextprotocol.org/schemas/v3/enums/specialism.json
  • Schema exists in latest (source) but not yet released in v3
  • Action: This link will work after next 3.x release is published

---

To fix: Either:

1. Wait for the next release and merge this PR after the release is published
2. Use latest instead of a version alias if you need the link to work immediately (note: latest is the development version and may change)
3. Coordinate with maintainers to cut a new release before merging