fix(extension): stop emitting modulepreload hints Chrome rejects (#113)

* docs(extension): complete the v1.3.5 changelog

Six of the eight user-visible changes since v1.3.4 had no entry, including
Reports — a whole feature — and the 21-day habit challenges.

The section only listed the two sync items added while writing them today,
because entries were being appended as work landed rather than reconciled
against what had actually shipped. Everything from #61 through #91 predates
that habit and slipped through.

Added: Reports, habit challenges and real streaks, the challengeLengthDays
clear that never travelled, the description/links clear that never
travelled, the Google sign-in popup dying mid-OAuth, and backups carrying
sync state.

Left out deliberately: #88's type-error cleanup and the shared wire-contract
refactor, which change nothing a user can see. The clear-propagation *bug*
that refactor fixed is listed; the refactor itself isn't.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

* fix(extension): stop emitting modulepreload hints Chrome rejects

A freshly loaded extension lists five errors on its own page:

  A preload for 'chrome-extension://…/assets/index-….js' is found, but is
  not used because it is a cross-world extension resource mismatch.

One per shared chunk. Vite emits <link rel="modulepreload" crossorigin> for
each, and Chrome refuses them under a chrome-extension:// origin.

Nothing was broken by it — the hints are discarded and the modules still
load through the import graph, which is why the popup has always worked.
But a page of red on a newly installed extension is its own problem, and it
would have been the first thing a reviewer saw.

The hint buys nothing here regardless: it exists to start fetches earlier
over a network, and these files are already on disk.

Pre-existing, not new — the published 1.3.4 builds the same way. Worth
fixing before 1.3.5 goes out rather than after.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 5 <noreply@anthropic.com>

Author: carpe-diem

extension/vite.config.ts

@@ -38,6 +38,16 @@ export default defineConfig({
   build: {
     outDir: resolve(__dirname, 'dist'),
     emptyOutDir: true,
+    // Vite emits <link rel="modulepreload" crossorigin> for every shared
+    // chunk. Chrome rejects each one under a chrome-extension:// origin —
+    // "cross-world extension resource mismatch" — and lists them all as
+    // errors on the extension's own page. Nothing breaks: the hints are
+    // discarded and the modules still load through the import graph. But
+    // a page of red on a freshly installed extension is its own problem.
+    //
+    // The hint buys nothing here anyway. It exists to start fetches earlier
+    // over a network; these files are already on disk.
+    modulePreload: false,
     rollupOptions: {
       input: {
         popup: resolve(root, 'popup/index.html'),