[omridevk]

Devframe migration PR 2 (sessions group), stacked on the 1b login PR (#692). Draft until review.

What this does

• Contract: the sessions schemas and error maps are named exports, shared by oRPC and Devframe.
• Core: each sessions procedure body is one plain function; the oRPC procedure and a conciv:sessions:* Devframe function both call it, with the same error codes. Every sessions change publishes the list to shared state conciv:sessions; publishes run one at a time on a @tanstack/pacer queue so the last write is the latest list, and chat turns publish when they start and end so the running flag and title stay current.
• Client: hubRoutedRpc(rpc, hub, groups) sends the listed groups' procedures to conciv:<group>:<proc> and leaves everything else on oRPC. Query utils are built over it, so query keys and invalidation are unchanged and direct rpc.sessions.* callers move without edits. A coded hub error counts as an answer for reachability; only DISCONNECTED reads as unreachable.
• Widget: DEVFRAME_GROUPS = {'sessions'}. The router reads conciv:sessions for its whole lifetime (started at creation, stopped with its disposers) and writes it into the sessions.list query, so the selector follows renames and deletes made elsewhere without a refetch. The read waits for trust without a timeout, so a widget that logs in late still follows the list.
• Extension: browserClient fetches the connection meta of the base it was given instead of reusing the first engine the page met; the reconnecting client reports status per attempt (see below).
• Tests: kit.rpc.sessions.* sites use kit.hub; widget and embed sessions faults and waits use devframe-faults (new awaitCompletedCall); the oRPC-only rpc-wire helper is gone.

Behaviour notes

• A hub call fails with the connection attempt in flight. While the engine refuses connections, a routed hub call waits only for the current attempt (or the next one if the client is between attempts) and rejects with DISCONNECTED when it fails, so a dead engine at boot shows "couldn't reach the engine" and one Retry recovers. A call on a closed hub connection rejects at once.
• Per-attempt connection status. The reconnecting client now reports connecting at the start of every attempt and disconnected after each failed one, instead of staying disconnected through all retries. Status listeners see the pair repeat while an engine is down; reachability ignores connecting, so the online flag is unchanged.
• Path-only hub base. browserClient resolves a base such as /__conciv/ against the page before fetching the connection meta, so page-origin hubs (Next, webpack, rspack) connect.

Not moved here

• harness-testkit kit.session / cleanup still call oRPC: the testkit cannot see the conciv:sessions:* function types (the declare module 'devframe' augmentation lives in @conciv/core, which the testkit does not depend on). Moves in PR 20 with the rest of the oRPC removal.
• Native CLI sessions appearing on disk do not publish (no server event exists); the widget's own refetch covers them as before.

🤖 Generated with Claude Code

[coderabbitai]

Important

Draft PR not reviewed

Draft PRs are not automatically reviewed by default.

• Trigger a manual review

To automatically review draft PRs, update your CodeRabbit configuration:

reviews:
  auto_review:
    drafts: true

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

Share

• X
• Mastodon
• Reddit
• LinkedIn

CodeRabbit Verify

• Run CodeRabbit Verify to test the changes in this pull request.