The app picker on a new forge lists each app once: the owner's public repositories, not the crew's forks of them #11634

The apps picker on /forges/new now lists each repository once, as its source, and crew forks no longer appear. Tests for the picker, the 150-repo pages and the new-forge suites pass, plus bun x tsc --noEmit, scripts/gate.ts and design-lint. I did not run the full suite, and I did not check production for duplicate names.

What changed

• A new listReposToTake in src/core/repos.ts builds the list. A repository is listed if it is public, not archived, and not owned by a crew agent. It must be the signed-in person's own, or someone else's source repository that runs an app.
• A fork of a listed parent is dropped, so the owner sees each name once. Agents' repositories are never listed. The person's own come first, then everything else, each group by latest push. A signed-out visitor gets no repositories.
• At ten items or fewer, the box shows all of them, with no inner scroll and no filter bar. Above ten, the filter and chips appear as before. This is a new plainUpTo option on pickList in src/web/pick.ts.
• test/repos-to-take.test.ts covers one source repository with four agent forks showing one row, a visitor seeing nothing, and another person's non-app repository being left out. It also checks the plain and filtered modes.
• Four existing tests now create their repositories as public (test/pick.test.ts, test/new-forge-pick-150.test.ts, test/new-forge.test.ts), because the picker is public-only now.

What I chose not to do

• Own private repositories: your own private repositories no longer appear, because the issue says public. If you want your own private ones listed too, it is a one-clause change.
• "Shareable" marking: the repo has no "shareable" flag, and templates already have their own dropdown. "Meant to be taken" is therefore "a public source repository that runs an app". A real flag would be a separate change.
• Submit check: the submit check still accepts any repository the person can read, so a hand-made form post can still name a fork. Only the picker narrowed.

To try it: sign in and open /forges/new. The apps list should show each of your public repositories once, with no crew forks.

Closes #11623

The apps picker on /forges/new now lists each repository once, as its source, and crew forks no longer appear. Tests for the picker, the 150-repo pages and the new-forge suites pass, plus bun x tsc --noEmit, scripts/gate.ts and design-lint. I did not run the full suite, and I did not check production for duplicate names.

What changed

• A new listReposToTake in src/core/repos.ts builds the list. A repository is listed if it is public, not archived, and not owned by a crew agent. It must be the signed-in person's own, or someone else's source repository that runs an app.
• A fork of a listed parent is dropped, so the owner sees each name once. Agents' repositories are never listed. The person's own come first, then everything else, each group by latest push. A signed-out visitor gets no repositories.
• At ten items or fewer, the box shows all of them, with no inner scroll and no filter bar. Above ten, the filter and chips appear as before. This is a new plainUpTo option on pickList in src/web/pick.ts.
• test/repos-to-take.test.ts covers one source repository with four agent forks showing one row, a visitor seeing nothing, and another person's non-app repository being left out. It also checks the plain and filtered modes.
• Four existing tests now create their repositories as public (test/pick.test.ts, test/new-forge-pick-150.test.ts, test/new-forge.test.ts), because the picker is public-only now.

What I chose not to do

• Own private repositories: your own private repositories no longer appear, because the issue says public. If you want your own private ones listed too, it is a one-clause change.
• "Shareable" marking: the repo has no "shareable" flag, and templates already have their own dropdown. "Meant to be taken" is therefore "a public source repository that runs an app". A real flag would be a separate change.
• Submit check: the submit check still accepts any repository the person can read, so a hand-made form post can still name a fork. Only the picker narrowed.

To try it: sign in and open /forges/new. The apps list should show each of your public repositories once, with no crew forks.

Four of juniper's five points are fixed. Point 1 (queue order) and the submit-check part of point 4 I did not change. I ran bun x tsc --noEmit (clean) and the new-forge picker tests (all pass); there is no scripts/gate.ts in this clone, and I did not run scripts/design-lint.ts, which only applies to src/web/ changes.

What changed

• Dedupe before the limit (2). listReposToTake now decides the candidates and drops any fork whose parent is also a candidate in SQL, before LIMIT. The JS post-filter is gone, so a parent can't be cut off while its fork stays listed.
• Tests (3). The test file now covers these cases:

- Another person's public source repo with an app is offered, after the viewer's own. - An archived repo is dropped. - A fork of a listed parent is dropped. - With limit = 1, the parent is the row that survives, not the fork. - pickList is now imported at the top of the file.

• Terminal door and docs (5). The terminal new-forge screen (src/tui/screens/newforge.ts) has no list. It takes free-text owner/name, so it never shows forks and needs no change. I added a "Which repositories" paragraph to docs/features/pick-list.md, which is where the picker is documented.

What I did not do

• Submit check (4). It still accepts any readable repository. I did not validate posted apps against listReposToTake. The terminal field, the API, and curated packs (resolveRepos) all post owner/name for repos the list deliberately omits, such as a private repo the person can read or a repo with no app. Restricting the submit would break those. The picker is a convenience; read access stays the boundary. I wrote this into the docs paragraph too. If you want a stricter submit for the web form only, say so and I'll do it as a separate change.
• Queue order (1). This does not unblock any of the pipeline issues (#6534, #6611, #5276, #3316). It is a small, self-contained bug fix to the picker, and I can't claim more than that. Whether it jumps the queue is for a person to decide.

To try it: sign in, open /forges/new, and check that each of your public repos appears once with no crew forks.

🤖 Generated with Claude Code