lody: the rail files a session under its repository, and its headings work (RAIL-1/2/3/4, WT-TERM-1/2)

[pythonlearner1025]

Five confirmed rail findings from the canary QA sweep. Four are integration
props upstream already reads. One needs a vendor hunk.

RAIL-1 + WT-TERM-1 — a worktree session filed under "Chats" (major)

The rail groups on resolveProjectGitHubRepo(session.project), which for a
local ref reads project.githubRepoFullName. The landing writes that field
only when the daemon's name also appears in the workspace's cloud-connected
repository list. A box fills that list from itself, late, after the surface
opens. A member who picks a project inside that window loses the name for
good, because no later pass rewrites a session that already exists.

The name now comes from the daemon at the write.
readLocalProjectRepoFullName asks local-project/git-state, and
workdir-default.ts completes the ProjectRef with the answer. The backfill
gains the matching half, so sessions created before this fix get their
heading on the next open. A refusal is retried; an answer is remembered.

A clone with no GitHub remote answers no name, and its sessions stay in
Chats. That is the honest degradation the repository sweep already states.

WT-TERM-2 — the worktree glyph never rendered (minor)

The data was never missing: buildSessionListRows already sets isWorktree.
SessionRowWorktreeIndicator is rendered by upstream's own Local Projects
rows and by nothing inside SessionList, which is the only session row a
BlitzOS rail has.

Seam patch 9, four additive hunks in
vendor/lody/packages/components/src/components/session-list.tsx, declared
in BLITZ-PATCHES.md with an upstream-PR sketch. The placement is copied
from upstream's own caller. A plain row is unchanged.

RAIL-2 — the "Chats" heading could not collapse (minor)

Two causes, both ours. The header runs onNavigateToNewSession when it has
one and its toggle only when it does not, and the rail passed it to both
lists; it now goes to the repo list alone. The chats list was also handed an
empty array while collapsed, which deletes the group that draws the heading —
so the heading vanished with its rows. buildGroups takes chatsCollapsed
and skips the rows itself.

RAIL-4 — no "+" on a repo heading (minor)

onNew draws the hover "+". It opens the landing, because the landing's
project picker is the only place a BlitzOS session picks a clone.

RAIL-3 — repo groups could not be reordered (minor) — FIXED, not deferred

Upstream supports it through props this rail failed to pass. onMoveRepo
makes the handle render, and the order persists through upstream's own
repoOrderAtom — one localStorage key per workspace, already scoped by
currentWorkspaceIdAtom, which SessionSurface publishes. Nothing new is
persisted. Discovery is append-only, so a repo whose sessions are all
archived keeps its saved position.

Tests

packages/webapp/test/lody-rail-groups.test.tsx drives the real vendored
SessionList through the real SessionRailSidebar, daemon-free, with only
the session mirror and the session mutations stubbed: grouping, the glyph on
a worktree row and its absence on a plain one, the collapse toggle, the "+",
the drag handle and the saved order. It also pins the seam-9 declaration.

lody-session-workdir.test.ts covers the write and the backfill, including
the refusal and no-remote branches. lody-project-control-frames.test.ts
pins the repo-name read against a real captured daemon answer.

Gates

• npm run typecheck — pass
• npm run lint:gate — pass (74 anti-slop, 0 blitz-house, unchanged)
• BLITZDEV_MANAGED=1 npm test — 769 passed. lody-session-rail and
  lody-sharing-relay hit the known daemon boot-timeout on a shared box; both
  pass on the retry, which reported killing an orphaned daemon.

🤖 Generated with Claude Code

https://claude.ai/code/session_01UhdxNAYjV97JTv2pddcJiN