chore(release): prepare 0.2.8

[kitlangton]

Why

Logs stored as Info, INFO, or info could be omitted by severity filters or split into separate aggregate buckets. Maintenance fix #19 is merged, but npm still serves 0.2.7.

What Changes

Bump @kitlangton/motel from 0.2.7 to 0.2.8 so the existing tag-triggered workflow can publish #19. Keep bundled synthetic fixtures generic by using example-chat-model consistently for both synthetic model fields.

Case	Released Behavior
Search for INFO, Info, or info	Match all three stored spellings; return the original text
Severity statistics, including attribute-filtered statistics	Combine variants into uppercase groups
Severity facets	Combine variants into uppercase values
Severity search on retained logs	Use the new case-insensitive severity/time index

Scope

This PR owns the package version and two synthetic fixture values; provider metadata, shipped fixtures, and exports are unchanged. The implementation and seven regression tests are already on main in #19. No lockfile version exists to update; the repository uses version commits and tags rather than Changesets or a checked-in changelog. Feature PRs #12 and #15 and dependency upgrade #18 remain excluded.

The complete rebuilt tarball was rescanned and checked against the release worktree; both installed synthetic model fields are generic. Publication follows review and CI for the release commit.

Verification

bun install --frozen-lockfile
bun run typecheck
bun run web:typecheck
bun run web:build
bun run test
bun run release:validate
npm pack --dry-run --json --ignore-scripts
npm pack --json --pack-destination "$PACK_DIR"

Full suite: 211 passed, zero failed, 1,526 assertions across 14 files. All 11 real TUI tests ran using an isolated tuistory 0.0.9/node-pty 1.0.0 toolchain and relay. The suite used isolated XDG state; release validation used isolated runtime/database paths and port.

The packed artifact was installed into a standalone clean consumer. Its installed motel CLI queried seeded services; its TUI rendered at 160x40, navigated into trace detail, resized to 80x24, and quit normally with no repository TSX transform configuration. HTTP checks verified mixed-case severity searches, both aggregation paths, facets, and the query-plan index. Packaged web HTML served with a browser-style Accept: text/html header. The installed MCP binary initialized as 0.2.8, listed 19 tools, reported the isolated daemon, and returned all three severity spellings through motel_search_logs.

Known nonfatal warnings: the existing web bundle exceeds Vite's 500 kB warning threshold; a clean install resolves the upstream platform-node-shared caret to rc.112 and reports its Effect peer mismatch, while the exercised runtime paths pass. The first full-suite attempt had one isolation-harness failure caused by an explicit database override; the complete rerun with isolated XDG state passed without source changes.