The site-admin palette entries live beside their screens, and AGENTS.md says a new screen adds its entry there #7732

For: finish what the cloud/domains/owner move started, so the admin screens that are added most often no longer edit src/tui/forge.ts.

Done:

• [ ] every entry forgeCommands offers only when session.user?.isAdmin === true (sentinel through forges, as main has them) is an exported entry in its own screen module and listed in ENTRIES in the order shown today; entries offered to everyone (home, explore, profile, the repo verbs, family) stay in forge.ts
• [ ] test/palette-roster.test.ts passes unchanged
• [ ] one short paragraph in AGENTS.md: a new terminal screen exports its entry from its own module and adds one line to src/tui/screens/entries.ts

Files: src/tui/forge.ts, src/tui/screens/entries.ts, the screen modules whose entries move, AGENTS.md. No other doc, no README. Risk: medium — it conflicts with open pulls that add palette entries; move in one commit per few screens and rebase on main before push.