- Drop value-level `RightPanelTabSchema` import from RightPanel.tsx;
  it dragged the kolu-common runtime graph (including anthropic SDK via
  AgentInfoSchema) into the client bundle and broke tree-shaking. Iterate
  via `Object.keys(TABS)` — the `Record<RightPanelTab, TabDef>` already
  gives us compile-time exhaustiveness.
- Mark integration packages + kolu-common as `sideEffects: false` so
  future value-level imports don't silently regress tree-shaking.
- Raise workbox precache limit to 4 MiB for the highlight.js + lowlight
  bundle that git-diff-view pulls in.
- Replace shell-out to `git diff --no-index` with `diff.createPatch` on
  the fetched old/new content — same Myers algorithm, no exit-1 quirks
  for untracked files, simpler code.
- Add `data-active` to tab buttons; use it + `state: "attached"` in the
  e2e step defs so tests pass regardless of in-repo vs no-repo tab state
  and without racing the diff renderer's ResizeObserver.

Preferences are recoverable — every field can be re-toggled by the user
— so a schema mismatch should reset to defaults, not require a migration
entry per change. `getServerState` now runs `PreferencesSchema.safeParse`
on the persisted blob and falls back to `DEFAULT_PREFERENCES` on any
mismatch. Migrations remain for `recentRepos`, `recentAgents`, and
`session` — accumulated user data the user can't reconstruct.

Drops the v1.8.0 migration added in 2608c3a (RightPanelTab enum
collapse) and reverts SCHEMA_VERSION to 1.7.0; the safeParse path
handles the stale "files"/"git" tab values for free.

Updates the state.instructions.md rule to document the split:
preferences = safeParse, user data = migration. Regenerated
.claude/rules/state.md via just ai::apm.

…nd !

…row panel

… gutter

…p empty spans

…igration"

The user prefers explicit migrations across all PersistedState fields
over the safeParse-on-read shortcut for preferences. Restore the v1.8.0
migration that coerces stale RightPanelTab values, bump SCHEMA_VERSION
back to 1.8.0, and revert the state.instructions.md rule to its original
"must add a migration" wording.

This reverts the structural change in e11e658 while keeping the original
v1.8.0 migration from 2608c3a.

Per PR review on packages/common/src/index.ts:51 — single-letter status
codes belong in `z.enum(["M","A","D","R","C","U","T","?"])`, narrowed to
the set `git.status` actually surfaces (excludes " " unmodified and "!"
ignored). `getStatus` now coerces the porcelain letter via `safeParse`,
falling back to "?" defensively if simple-git ever surfaces an unknown
code.

- Path-traversal guard: `resolveInRepo` now returns both abs + rel path;
  every downstream git invocation uses the normalized rel, so no code
  path reads the raw untrusted `filePath` string (closes the apparent
  bypass — the guard was complete, but reviewers had to trust the
  ordering; the normalized return makes it mechanical).
- Log security events: `resolveInRepo` calls `log.error` before
  throwing, so a path-escape attempt surfaces in the operator log.
- Tighter `readHeadContent` catch: dropped the `cat-file -e` probe;
  call `git show` directly and only swallow the specific
  "does not exist in" / "exists on disk, but not in" messages that
  mean "absent from HEAD". Permission denied, corrupted repo, missing
  HEAD now propagate to the client instead of becoming a silent empty.
- Empty-diff observability: `log.warn` when both `git diff HEAD --` and
  `--no-index` produce zero output for a file the status listed. Rare
  but possible (mode-only change already reset, race with external
  `git reset`), worth a log line for operators.

Move the `resolveInRepo` helper out of `git-review.ts` — it's not
git-specific, it's the generic "resolve untrusted child path under
trusted root, or reject" guard that any RPC handler touching the
filesystem wants. Now lives in `safe-path.ts` as `resolveUnder(root,
child)`.

While moving:
- Switch the check from `startsWith(rootAbs + path.sep)` to the
  `path.relative` idiom (`..` prefix ⇒ outside). Same guarantee, no
  trailing-slash / path-sep gotcha, and `rel` is what we return anyway
  — one computation instead of two.
- `getDiff` now passes the pre-validated absolute path (`abs`) to the
  `git diff --no-index` fallback instead of the relative one.
  `--no-index`'s behavior w.r.t. cwd is less stable than
  `git diff HEAD --`, and the whole point of this guard is that no
  downstream subprocess sees the raw untrusted string.

Verified via live chrome-devtools-mcp probe that rendered diff metrics
are identical pre/post refactor.

Clicking the active file row toggles selectedPath to null, which
collapses back to the "Select a file to view its diff" fallback.
Previously a re-click was a silent no-op.

e2e: extended the "lists changed files and opens a diff on click"
scenario with a second click + a new "should not render a diff view"
assertion (waits for the diff row to detach).