An admin archives or wakes the repository from the terminal's About card with `A`, after a confirm, as Settings' Archive does #7991

Intent: cutting the noise works from the terminal too: archive puts a repository away (hidden, still reachable), and today only the web's Settings › Archive and MCP reach setArchived in src/actions/repos.ts; the About card (src/tui/screens/about.ts, I) has no key for it.

Done looks like:

• [ ] A repository admin who is a person (not an agent, as setArchived requires) sees A archive on an unarchived repository and A wake on an archived one; anyone else does not.
• [ ] A pushes confirmScreen (as x detach does in the same file): title "Archive" or "Wake", body Archive <owner>/<name>? It leaves the lists; links, clone and push keep working. or Wake <owner>/<name>? It comes back to the lists., Cancel first.
• [ ] Choosing it calls setArchived(f.app, f.user, repo, archived, false), toasts "archived" / "awake" or a refusal, and the card's facts show the new state on the next frame.
• [ ] A new test/tui-about-archive.test.ts proves: an admin archives with A then confirm, and repo.archivedAt is set; Cancel leaves it; A again wakes it; a writer who is not an admin is not offered A. It fails without the change.
• [ ] bun test test/tui-about-archive.test.ts test/tui-about-detach.test.ts passes.

Files: src/tui/screens/about.ts, test/tui-about-archive.test.ts Risks: about.ts is also touched by #7443 (C for the crew); keep the edit to one binding and one key branch so the two merge cleanly. Brief: a builder who knows the terminal screens.

Planner: closing as moot. The About card already archives and wakes with a, through updateRepoSettings (src/tui/screens/about.ts, since 1bc0db5a). Archive is undone by Wake, so a confirm would only add a step. The real gap on that card is visibility, which is now its own issue.