packages/opencode/test/session/session.test.ts (1)

268-293: Use testEffect(...) and it.live(...) for this Effect + live-state test.

This test exercises Effect services with live git/filesystem/database state, so it should follow the established pattern in other test files: import testEffect from test/lib/effect.ts, define const it = testEffect(...) at the top, and use it.live(...) instead of test(...) with manual Effect.runPromise(...).

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@packages/opencode/test/session/session.test.ts` around lines 268 - 293,
Replace the plain Jest test with the project’s Effect-aware pattern: import
testEffect from "test/lib/effect.ts" and define const it = testEffect(...) at
the top of the file, then change test("backfill preserves legacy session updated
time", ...) to it.live("backfill preserves legacy session updated time", async
() => { ... }); inside the test body stop calling
Effect.runPromise(SessionNs.backfillExecutionContext) directly and instead run
the backfill as part of the effect test runtime (i.e., invoke
SessionNs.backfillExecutionContext through the it.live/Effect runtime), keeping
the rest of the logic (SessionNs.create, Database.use updates, assertions on
time_updated, and SessionNs.remove) intact so the test uses the live
git/filesystem/database fixtures consistently.

packages/app/src/pages/layout.tsx (1)

651-664: 💤 Low value

Optional: Consider batching upsert state updates.

The multiple setPawworkSessionWindowState calls could trigger separate re-renders. While the conditional guards limit this in practice, wrapping in batch() would ensure a single update cycle when multiple properties change.

♻️ Optional batch optimization

 const upsertPawworkWindowSession = (info: Session) => {
   if (info.parentID || info.time?.archived) return
+  batch(() => {
     setPawworkSessionWindowState("normal", (current) =>
       sortPawworkSessionWindowSessions([...current.filter((session) => session.id !== info.id), info]),
     )
     if (store.pawworkPinnedSessions.includes(info.id)) {
       setPawworkSessionWindowState("pinned", (current) =>
         sortPawworkSessionWindowSessions([...current.filter((session) => session.id !== info.id), info]),
       )
     }
     if (params.id === info.id) {
       setPawworkSessionWindowState("active", info)
     }
+  })
 }

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@packages/app/src/pages/layout.tsx` around lines 651 - 664, The
upsertPawworkWindowSession function calls setPawworkSessionWindowState up to
three times which can cause multiple renders; wrap those state updates in a
single batch() call (or the appropriate React/third-party batching util) so the
updates to "normal", "pinned" and "active" are applied in one
transaction—identify upsertPawworkWindowSession and replace the separate
setPawworkSessionWindowState invocations with a single batch(() => { ... })
block that performs the same filtered/updated assignments for each state key,
preserving the conditional checks for info.parentID, info.time?.archived,
store.pawworkPinnedSessions.includes(info.id), and params.id === info.id.

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes