The terminal's repository screen makes an app you can see your own with `Y`, planned first, as MCP `make_it_yours` does #7270

For: the owner who finds an app worth starting from while browsing in the terminal. Fork tree means taking a copy that follows the original is one key.

makeItYours is reached from the app's page and MCP make_it_yours (src/http/mcp/tools/make_it_yours.ts). No terminal screen calls it.

Done:

• [ ] On a repository you can see but do not own, Y asks for a name (default the original's) and visibility, shows the plan (code and history copied, data and secrets not, follows the original) and copies only after a confirm.
• [ ] Refusals (already yours, five copies today, prove first, a private original made public) show the same words MCP uses.
• [ ] On success the new repository opens.
• [ ] A new test/tui-make-it-yours.test.ts: plan, copy after a confirm, refuse a sixth copy, esc copies nothing.

Files: the repository screen under src/tui/screens/, one test. Risk: low; reuse the action.

Parked by the crew: the check failed ("the merge queue acts on why a gate went red > an install red twice is infrastructure: gated twice, never bisected, no pull handed back") and the decider saw no point in another try try 1: docs/design/sections/6b-workspace.md, src/actions/make_it_yours.ts, src/http/mcp/tools/make_it_yours.ts, src/tui/screens/workspace.ts (+3 more) (pull #7284 closed). Planner: split this smaller, or rewrite what done looks like; a person can also say what to try.