docs(profile): clean public org README

[AlbinoGeek]

Summary

• Removes the public-facing internal TODO about bakeoff-results visibility/description
• Renames "Archived" → "Prior art" and links the archived public MCP/harness repos so visitors see intent matches GitHub archive state
• Adds bakeoff-results to Active with honest wording (approved result bundles)

Still manual (no Administration on the token)

1. Pins — recommend pinning Active public repos: bakeoff, fedbuild, discord-docs (and optionally bakeoff-results). Currently only fedbuild + bakeoff appear pinned.
2. Repo short description — bakeoff-results still says "Private staging repo…" while public. Update in repo Settings → General → Description to something like: Approved bakeoff result bundles from Rethunk-AI/bakeoff.
3. Community health — .github currently only has profile/README.md. Consider adding default SECURITY.md / SUPPORT.md (and optional CODE_OF_CONDUCT.md / CONTRIBUTING.md) at the repo root or under .github/ for org-wide defaults.

Test plan

• Merge and confirm org profile at https://github.com/Rethunk-AI renders Active + Prior art as expected
• Apply pin + description clicks above

[Copilot]

🟢 Approval recommended

Only a minor wording nit remains, with no approval-blocking issues.

Pull request overview

Updates the public organization README to clarify active projects and archived repositories.

Changes:

• Adds bakeoff-results to Active.
• Renames Archived to Prior art.
• Links and describes prior-art repositories.

File summaries

File	Summary
profile/README.md	Updates Active and Prior art repository listings.

Review details

Suppressed comments (1)

profile/README.md:23

• Because the table includes kui, which is a Web KVM UI rather than an MCP server or harness bridge, this sentence misclassifies one of the linked repositories. Broaden the wording to include related tools so the new Prior art section accurately describes every row.

Earlier MCP servers and harness bridges are **archived on GitHub** and kept for
history — not entry points. Prefer Active above.

• Files reviewed: 1/1 changed files
• Comments generated: 0
• Review effort level: Lite

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.