refactor(frontend): split log stream transport and history into modules

[abcxff]

No description provided.

[abcxff]

Stack for rivet-dev/rivet

• #5538 chore(frontend): lower log history page sizes to 50 and 100
• #5527 revert(frontend): remove destroy-time seeding for compute lo …
• #5522 refactor(frontend): extract log viewport scroll logic into u …
• #5525 refactor(frontend): split log stream transport and history i … 👈
• #5523 refactor(frontend): de-duplicate log stream lifecycle writes
• #5526 perf(frontend): skip live log tail for destroyed actors
• #5520 fix(frontend): seed compute logs only from destroy time, not …
• #5524 feat(frontend): make older-logs sentinel a clickable load bu …
• #5521 fix(frontend): cancel in-flight log history load-more on fil …
• main

Get stack: forklift get 5525
Push local edits: forklift submit
Merge when ready: forklift merge 5525

_{change qvpxmyts}

[claude]

Review

Verified this is a pure code-move refactor: use-deployment-logs-stream.ts (previously ~226 lines of mixed concerns) is split into two focused modules, with the hook re-importing them. I diffed the moved code against the original and it's textually identical (aside from rewriteLogEntry being reordered above parseSseEvent in the new deployment-logs-transport.ts, which is a no-op reorder) — no behavior changes.

Code quality

• Clean separation: deployment-logs-transport.ts owns SSE parsing/streaming/retry, deployment-logs-history.ts owns the paginated REST history fetch. Both are cohesive, reasonably sized modules.
• rewriteLogEntry lives in transport.ts and is imported by history.ts rather than duplicated — good, avoids the two modules drifting on the Cloud Run hello-message rewrite logic.
• Import direction is one-way (history.ts → transport.ts), so no circular-import risk.
• Naming (deployment-logs-history.ts, deployment-logs-transport.ts) is consistent with the existing deployment-logs.tsx / use-deployment-logs-stream.ts kebab-case convention in this directory.
• cloudEnv, MAX_RETRIES, BASE_DELAY_MS, etc. all stayed correctly scoped to where they're used; no leftover unused imports in the trimmed hook file.

Bugs / correctness

• None found. This is a mechanical extraction with matching exports/imports wired up correctly on both sides.

Test coverage

• No tests exist for this hook before or after the change, so nothing regresses here, but flagging that the retry/backoff and SSE-parsing logic in deployment-logs-transport.ts is a reasonable candidate for a focused unit test now that it's isolated in its own module (e.g. parseSseEvent and streamWithRetry's retry/backoff behavior). Not a blocker for this refactor PR.

Minor

• PR description is empty; per repo convention a short bullet list of what changed would be helpful for reviewers, even though the diff itself is easy to follow here.

Overall: safe, well-scoped refactor. No functional or security concerns.