perf(web): prune duplicate shell chrome update during page rendering

[K-Laron]

Problem

renderPage(path) in src/main.js was invoking updateShellChrome(normalizedPath) twice during each route navigation:

• Once synchronously before loading the dynamic page module (ensureShell(); bindShellEvents(); updateShellChrome(normalizedPath);)
• And once again immediately after the async module chunk resolved (updateShellChrome(normalizedPath);)

Because store stats, user details, and the active route path do not change while the page module chunk is resolving, the second invocation was entirely redundant. It performed repeated calculations of store.getProgress() and store.getTotalHours(), alongside duplicate DOM writes to sidebar navigation classes, theme toggle labels, and progress bars.

Mechanism

Remove the redundant updateShellChrome(normalizedPath) call in src/main.js.
The initial call is preserved so that sidebar navigation links update immediately upon user interaction before module resolution.

Upstream Inspiration

• pingdotgg/t3code#20860: "perf(web): the open thread's chat chrome no longer re-renders on every streaming tick".
• pingdotgg/t3code#18416: "perf(client-runtime): merge shell deltas once per received batch".

Before / After Numbers

• npm test: 124/124 tests passing.
• npm run build: Vite build passes cleanly.
• Page navigation: reduces shell chrome DOM writes and store calculations from 2 runs to 1 run per route navigation.

Risk

Very Low. The shell chrome has already been rendered and updated by the initial call before module resolution.

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

[coderabbitai]

Important

• 🔍 Trigger review

This repository does not receive automatic reviews because it has fewer than 10 stars.

⚙️ Run configuration

• Configuration used: defaults
• Review profile: CHILL
• Plan: Advanced
• Run ID: 333ba44c-a523-41a9-b39d-9adef7e74732

• 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

_{Comment @coderabbitai help to get the list of available commands.}