GeezerVison

Adds a compact project picker next to the organization selector on the main /agents composer, so a new chat can be filed in a project without first opening that project's page. The picker only appears when the chat-projects experiment is on, and the project page composer is unchanged.

• The trigger reads "No project" or the selected project's icon and name. The popover has a search box, a "No project" item noting that chats can't be moved into a project later, the project list, and a pinned "New project" footer.
• Only the composer's current organization's projects are listed, because the server rejects a project from another organization. Changing the organization clears the selection.
• Picking a project doesn't navigate, so the draft, attachments, model and workspace stay as they are. The page already forwards projectId from the form, so there are no page or API changes.
• The choice isn't remembered between visits. A chat can't move into a project later, so a remembered choice could file chats in the wrong project without the user noticing.
• "New project" opens the existing ChatProjectDialog, limited to the current organization, and selects the new project when it is created. The user stays in the composer.
• The new CompactProjectSelector gives each item its project ID as the cmdk value and matches search only against the project name. Names aren't unique, and cmdk's default scorer would otherwise also match the search against the ID.

Composer with both pickers	Long list with a pinned footer

Tests cover picking a project, the default of no project, clearing the selection on an organization change, selecting a project created from the picker, name-only search, and Retry after a load error. Stories cover the visual states: closed, open, loading, error, empty and a long list.