GeezerVison

PATCH /api/v2/chats/{chat} now accepts project_id. A UUID moves an idle
root chat into a project of its owner and organization; uuid.Nil removes
it from its project. The project checks are the ones of chat creation,
now shared by validateChatProjectSelection.

The chatstate machine gains a SetProject transition, allowed only from
W, E0 and E1. SetFamilyProject locks the root first and then each
subagent chat, so a busy family returns 409 and the move never overlaps
a step. chatd publishes a project_change watch event for each family
member after the commit.

The chat menu (sidebar row, top bar and project page row) gets a "Move to
project" submenu for the owner of a root chat that is not archived, behind
the chat-projects experiment. It lists the projects of the chat's
organization from the project list the sidebar already loaded, marks the
current project, and ends with "Remove from project". While the chat or a
subagent runs, the submenu is off and shares the Archive agent hint.

moveChatToProject() updates the cached lists and the chat optimistically,
restores only project_id on failure, and refetches the lists when it
settles. project_change watch events update project_id in other tabs and
refetch the filtered lists, and the project page drops rows whose chat
moved to another project.

The new-chat composer no longer says that a chat cannot move later.

…olders in the sidebar

- Keep each sidebar row's wrapper mounted when the chat's drag eligibility
  changes, so a status change no longer remounts the row and closes its menu.
- Share one ChatDropArea for project folders and Chats, drawn as an outline.
- Read dnd-kit drag data through type guards instead of casts.
- Group projects with Object.groupBy instead of a module cache.
- Add stories for the Move to project submenu states and a drag over a folder.
- Tidy test fixtures, queries and comments.

…jects

- Add stories for an unfiled chat's submenu and the blocked menu item.
- Restore plain project fixture IDs in tests.
- Clarify comments on the project grouping, the blocked prop and drop lookup.
- Name the arrow-key check in the keyboard getter and drop a no-op class.

… root row to move a chat family

Subagent rows rendered inside the draggable wrapper of their root, so a
drag that started on a subagent row moved the root chat. The drag handle
is now the root row itself, and the subagent subtree stays outside it.

…pe dnd-kit drag data guards

…d moves and drop folder opening

Assert the move failure toast still shows after the menu closes, assert a
drop opens its target folder, and stub the projects request in the row
remount test so it no longer reaches a real server.

chatgpt-codex-connector Bot left a comment

…ed chat in the cache, not the DOM

FE1 leaves rendered presence to screenshots. The row menu test now checks
the move request and the project page's own list cache, and the new
ChatMovedToAnotherProject story shows that the page leaves out a cached
chat of another project.

chatgpt-codex-connector Bot left a comment

… its project

A chat moved out of its project, or whose project was deleted, kept the
memory index the model saw there, while the memory tools were gone. A
root chat outside a project now has an empty index, so its next turn
start sends an update that removes those memories. Such a chat reads the
prompt only at turn start, the only step where that removal can be due.

Object.groupBy needs Chrome 117 and Safari 17.4, and the browserslist
supports Chrome 111 and Safari 16.4 with no polyfill, so the Move to
project menu threw on those browsers. lodash groupBy keeps the server
order of the projects.

syncMemoryIndex and memoryIndexMessage now call the loaded chat messages
history, and the doc comment says plainly when a chat outside a project
reads its prompt rows.

chatgpt-codex-connector Bot left a comment

… drags by name

dnd-kit's default announcements read the draggable and droppable IDs, so
a screen reader heard "move:<id>" and "project:<id>" during the new
keyboard drag. The sidebar's DndContext now announces the chat title and
the folder name, and pin drags keep the defaults.

…ed" in the drag announcement

User-facing strings in site/src use "canceled". The drag test now reads
the dnd-kit live region by its status role instead of searching for
visually hidden text.

chatgpt-codex-connector Bot left a comment

…ithout Move to project in stories

The archived, shared and subagent menu cases asserted DOM absence in
Vitest, which the frontend contract (FE1) leaves to screenshots. Three
stories now open those menus with the chat-projects experiment on, and
the Vitest absence checks are removed.

…e rule above its three stories

The JSDoc on the first story became that story's description in Storybook, where "these menus" had no referent. A plain comment above the group keeps the rule out of a single story's docs.

chatgpt-codex-connector Bot left a comment

…ove after the menu closes

The refused-move test waited for the menu item to leave the DOM before it
checked the toast. The update now rejects only after the select, so the
test still shows that the toast outlives the menu without a DOM check.

The sidebar drags used @dnd-kit/core, @dnd-kit/sortable, and
@dnd-kit/utilities. They now use @dnd-kit/react 0.5.1, with
@dnd-kit/dom and @dnd-kit/abstract pinned to the same version.

The Accessibility plugin is off because it gives each drag handle
role="button", and the handles are chat links. ChatDragAnnouncer reads
drag events through useDragDropMonitor and writes the instructions and
the live announcements. A pinned drag now also announces the position.

Up and Down still move a keyboard drag to the next folder. After an
optimistic pin reorder, focus goes back to the dragged link. The click
guard after a drop is removed, because the pointer sensor stops the
click after a drag.

jaaydenh left a comment

Two drags regressed in the move to @dnd-kit/react.

A drop with the pointer on a muted folder moved the chat into the
folder next to it. When no enabled target is under the pointer, the
default collision detector falls back to the dragged row's overlap.
The folders and Chats now use pointerIntersection, so a drop counts
only for the target under the pointer, as before. @dnd-kit/collision
0.5.1 becomes a direct dependency for it.

A keyboard drag could not reach Chats when Chats is taller than the
window. The arrow key scrolls the next target into view, but dnd-kit
measures the targets again only after the drag has moved, and it does
not recheck a position that has not changed. The targets now measure
themselves right after the scroll.

…lapsed Projects section under a chat drag

A chat dragged over the collapsed Projects header now opens the section,
so the folders can take the drop. The section stays open, like a click on
the header. Until that drag ends, the header stays a target that moves
nothing, so a drop there leaves the chat in place and the live region
says it did not move. Keyboard drags reach the header with Up and the
folders with Down. Pinned rows still never target Projects.

… target under the drag while the list scrolls

A wheel turn during a mouse drag scrolled the list under the still
pointer, but the drop stayed on the folder that had been under it.
dnd-kit 0.5.1 measures the targets again after a scroll, but its
collision check skips an unchanged drag position. A new plugin checks
the targets again on each scrolled frame.

In a scrolled list, a keyboard drag stuck on one folder because
dnd-kit's Scroller scrolled the list after each step, away from the
drag's still position. The plugin turns Scroller off during a keyboard
row drag, which already scrolls each target into view itself.

…yboard drag targets and the drop announcement in step

After a scroll, measuring the targets again for a keyboard step made
dnd-kit check collisions at the old drag position. That check could
change the target, and dnd-kit ignores collisions until React renders
after a target change, so the target under the moved drag was lost: Up
from the tall Chats read "not over", and the next Down kept the folder
above as the target. The keyboard step now turns the collision checks
off until the move has set the new position, then checks once.

dnd-kit can also report a new target after a drag ends, until React
renders the end, which replaced the drop announcement. The announcer
ignores those reports.

Add the SetProject transition to the transition list and the execution
state diagram, note that a root chat's project can change after
creation, and describe how a moved chat's memory index is brought up to
date at its next turn.

The PATCH /api/v2/chats/{chat} section said the endpoint emits no state
transitions unless the request changes archived. A project_id change now
applies SetProject to the chat family, so list its supported states and
refusals.

Brings in origin/main through mike/move-chats-chatd. Chat creation on
main now checks project access with chatd.ChatProjectUsableBy, so
validateChatProjectSelection uses that check for both creation and
moves.

A move accepts the same projects as chat creation, which now include
projects shared with the chat's owner. Extend the owner-check test to
share the project and move the chat, and describe the rule on
UpdateChatRequest.ProjectID.