[ScriptedAlchemy]

Stack order (merge first → last): #4473 → #4478 → #4521 → #4526 → #4515 → #4510 → #4516 → #4524 → #4489 → #4488 → #4485

This PR is layer 10/11, based on #4489. Next: #4485.

Merge bottom to top using merge commits. After each parent merges, retarget its child to master before merging the child; this preserves the ancestry already integrated and avoids reintroducing conflicts.

Problem

The ChatGPT extension used ten recent registered projects as its entire interactive picker. It discarded the registry's completeness metadata and exposed no route to find older projects. Pending app requests also had no cancellation or stale-response ownership.

Changes

• Preserve canonical listing limit, truncation, and page-summary metadata through the bridge and view.
• Add app-only project discovery through the existing generated project_search descriptor and profile-scoped, projectless registry session.
• Add a searchable picker for project paths, aliases, IDs, and default branches. Clearing the query restores recent projects.
• Distinguish recent partial lists, complete/truncated matches, empty registry, no matches, and registry failures.
• Cancel replaced searches and navigation through the actual MCP request signal. Guard both late successes and failures so they cannot replace newer results or the selected project.
• Keep search controls, keyboard focus, and the draft usable during pending queries; cancel on host teardown and page hiding.
• Preserve direct project-ID reads, profile authorization, and mention budgets (four recent projects, eight items per project).
• Regenerate both embedded artifacts and include discovery/DOM regressions in the existing Bazel adapter test target.

Both recent and search requests retain the existing ten-project page bound. Summary counts describe the returned page; no pagination cursor or artifact-size ceiling was introduced.

Verification

• 68/68 focused extension tests passed: adapter, project-discovery, project-picker DOM, serve-session, and bridge-lifecycle suites.
• The DOM suite imports the real app and controls only its host boundary. It verifies exact-ID selection, supersession, typing/focus, stale success/failure, deep links, external host results, and teardown.
• A real MCP client/extension server test verifies cancellation propagation to the registry-call boundary.
• Server and app TypeScript checks passed; all changed test files, including live fixtures and browser harness, passed a strict TypeScript check.
• SDK build, extension build, byte-for-byte check:embedded, commit lint, and git diff --check passed.
• Extended the existing 26-project daemon fixture and added an eleven-project browser journey for discovery beyond recent projects.

Verification limits: the live production-daemon suites were not run because this environment has no built TraceDecay CLI. The connected Browser extension was unavailable, and the cloud browser's URL policy blocked the temporary preview. No browser visual pass or live-daemon conformance pass is claimed.

Fixes #4414.

[changeset-bot]

⚠️ No Changeset found

Latest commit: d449437

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR