Firefox and Microsoft Edge Add-ons, and maintenance mode. Permissions are
unchanged; nothing re-asks for consent (LEGAL_VERSION stays 1).
- package.json and the lockfile's root at 1.3.0; CHANGELOG [1.3.0] with
Added / Changed / Fixed / Packages.
- docs/00 §10 items 19-26: what only the owner can do for this release
(the store uploads, the first AMO and Edge submissions by hand, the store
environments, real-browser QA, native review).
- docs/15: Phase 10 in the progress table; 1.2.1 may be skipped on the
store, since 1.3.0 contains it.
- docs/13 §8: the sources archive rebuilt every file of the Firefox
package byte for byte. docs/08 §9: Options can open a second Manager tab
on Firefox.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Accessibility. An accessibility statement and its intake, Alt+Up/Down to
reorder from the keyboard, Windows contrast themes, and the focus and
target-size fixes an audit of src/ found. Permissions unchanged;
LEGAL_VERSION unchanged.
The built manifest differs from the v1.2.0 release asset in `version` only;
the file inventory is identical.
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
Dependabot bumped @biomejs/biome to 2.6.4 and left the `$schema` URL in
biome.json at 2.6.2; `vitest` stayed at ^5.0.5 beside a ^5.1.0 coverage
plugin that docs/01 says must match it.
docs/01 §2 now states what is installed (WXT 0.21.5, Svelte 5.57.3,
svelte-check 4.7.8, Knip 6.44.1, Vitest 5.1.0) and docs/12 the Sonar scan
action's pin (v8.4.0).
WXT 0.21.4 -> 0.21.5 passed the built-manifest diff docs/12 §2.3 requires:
manifest.json byte-identical to the v1.2.0 release asset, same file
inventory, CSS identical, +33 bytes in one chunk from Svelte 5.57.3.
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
Simplified Chinese and Romanian (docs/07). Permissions, the Chrome
floor and LEGAL_VERSION are unchanged; the built manifest differs from
1.1.0 only in `version`, plus the two new _locales directories.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Every dev dependency moves to the newest release that has been public for
at least 7 days, and that rule is now enforced rather than remembered:
.npmrc sets min-release-age=7 and Dependabot gets a 7-day cooldown on both
ecosystems. `npm ci` was verified to ignore the age rule for versions
already in the lockfile, so it only shapes what gets locked.
vitest / coverage-v8 4.1.10 -> 5.0.5 (suite passed unchanged)
@biomejs/biome 2.5.5 -> 2.6.2 (exact)
svelte 5.56.8 -> 5.57.2
vite-plugin-svelte 7.2.0 -> 7.3.1
svelte-check 4.7.4 -> 4.7.7
jsdom 30.0.1 -> 30.1.3 (dom-environment canary first)
knip 6.29.0 -> 6.42.1
wxt 0.21.3 -> 0.21.4 (+ transitive vite 8.3.5)
npm audit: 13 (7 high) -> 3 low, all one deepmerge advisory with no fixed
release, inside vite-plugin-svelte's dev-time option merging; documented in
docs/09 §3.1. --omit=dev stays 0. This supersedes Dependabot #19-#25.
The six-entry overrides block is deleted: none of those packages is in the
tree any more (WXT 0.21 dropped web-ext-run, Vite 8 bundles with rolldown),
and a stale override would silently pin a package the day it came back.
WXT got the built-manifest diff the 2026-08-03 decision requires: identical
keys and values apart from the deliberate minimum_chrome_version, identical
file inventory. Biome 2.6 began formatting Markdown and YAML, so both are
excluded rather than letting a formatter reflow hand-written docs.
dependabot.yml now keeps WXT out of the routine group and ignores majors of
the TypeScript pair and @types/node.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Node 26 entered Active LTS on 2026-10-28 and Node 24 went to maintenance on
2026-10-20, so the toolchain moves with them: .nvmrc, engines and @types/node
all say 26.
TypeScript 7.0 is GA but still has no programmatic API, and svelte-check
peers `typescript ^5 || ^6`. So this uses Microsoft's documented
side-by-side aliases instead of choosing one:
"@typescript/native": "npm:typescript@~7.0.2" -> tsc (7.0.2)
"typescript": "npm:@typescript/typescript6@~6.0.2" -> the 6.0.3 API
`npm run check` therefore type-checks .svelte files with TS 6 (svelte-check)
and every .ts file with both. `tsc --version` is 7.0.2; `tsc6` is 6.0.3.
tsconfig targets ES2025 with lib ES2025, which is only honest if the oldest
Chrome allowed to install has every ES2025 built-in. That is Chrome 136
(RegExp.escape), so minimum_chrome_version goes 120 -> 136 and Vite's
build.target follows the same CHROME_FLOOR constant. manifest.test.ts pins
all three so they cannot drift apart. Users below 136 keep what they have
installed; they just stop receiving updates.
Built output: the manifest changes only minimum_chrome_version, the JS chunks
are byte-identical apart from a CSS hash, and the CSS loses one
-webkit-user-select prefix Chrome 136 no longer needs.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The first CI run on this branch failed `npm run check` with 18 errors —
"Cannot find name 'node:fs'" — including in `tests/unit/styles/contrast.test.ts`,
which this branch never touched. So it was not the new test: the package has
always used Node types without declaring them.
Two things hid it. WXT 0.20 supplied `@types/node` transitively and 0.21 does
not, and this worktree sits under the parent checkout, so TypeScript walked up
to `E:\bookmarkmagic\node_modules\@types\node` and resolved them anyway — even
after a correct `npm ci` in the worktree itself. A green local type-check in a
worktree is therefore weaker evidence than it looks, which is now written down
in CLAUDE.md next to the existing worktree gotcha.
Types only: erased at build, nothing ships, so hard rule 2 — zero *runtime*
dependencies — is untouched, and the built manifest and bundle are unchanged.
docs/01 §2 records it with the reason, since that table is the pinned-version
spec rather than a summary of it.
This is the failure the tag run would otherwise have hit, and the reason a red
CI is worth reading before merging rather than after tagging.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Applied directly rather than merged: both branches predate this phase and would
have reverted `verify:full`.
**wxt ^0.20.27 → ^0.21.3.** A 0.x minor is semver's breaking slot, and WXT is
what emits the shipped manifest — so the acceptance test was a byte diff of the
built artifact, not a green suite. Manifest, file inventory (content hashes
stripped) and bundle size all came out identical, permissions unchanged, zip
name unchanged. It *did* break two things, both dev-only: `wxt/testing` split
into `wxt/testing/fake-browser` and `wxt/testing/vitest-plugin`, and
`tabs.create` is now typed as returning void.
That split is the point of the ritual. `npm run test` passed before the bump and
the *config load* failed after it — while `tests/unit/manifest.test.ts`, the
test that looks like it guards the manifest, would have stayed green whatever
WXT emitted, because it reads wxt.config.ts and a WXT upgrade cannot change that
file. The check-manifest key-set gate added in the previous commit is what makes
the next one CI's problem rather than a manual comparison someone has to
remember to do.
**jsdom ^29.1.1 → ^30.0.1.** Canary first: tests/unit/dom-environment.test.ts
pins the parse5 behaviour the Netscape walk depends on — implied end tags, and
`:scope >` from an element root. It passed, then the parser, fixture and
round-trip suites, then coverage, all unchanged. The 2 869 ms figure in
docs/11 §6 is now labelled as a jsdom 29 number; a DOM major invalidates it
rather than updating it.
**svelte-check ^4.7.3 → ^4.7.4.** A patch.
npm audit stays at 0, and none of the six `overrides` can be dropped yet.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Six Dependabot alerts (1 critical, 3 high, 1 medium, 1 low) plus six further
`npm audit` highs, all in transitive DEV dependencies whose parents pin them to
vulnerable ranges. That pinning is why Dependabot's own per-package PRs could
not fix any of them — every one of those runs failed. `overrides` is the npm
mechanism for precisely this case.
shell-quote 1.7.3 -> ^1.9.0 wxt > web-ext-run > fx-runner
adm-zip 0.5.18 -> ^0.6.0 wxt > web-ext-run > firefox-profile
tmp 0.2.5 -> ^0.2.6 wxt > web-ext-run
uuid 8.3.2 -> ^11.1.1 wxt > web-ext-run > node-notifier
esbuild 0.27.7 -> ^0.28.1 vite, wxt, unplugin
brace-expansion 1.1.16 -> ^5.0.8 web-ext-run > multimatch > minimatch
The last one is the whole second cluster: `npm audit` reported six highs that
were one brace-expansion DoS propagating through minimatch -> multimatch ->
web-ext-run -> wxt, with fixAvailable:false because multimatch pins minimatch.
`npm audit` now reports 0. It already reported 0 for `--omit=dev`, and still
does: the shipped extension has no runtime dependencies, so none of this was
ever in the artifact.
Correcting something I wrote in the dependabot.yml comment and repeated in a
PR: I said these advisories had "no reachable patched version". That was wrong
— every one of them had a patched version. What they lacked was a path
Dependabot could take on its own.
Re-verified after the overrides: lint, check, knip, coverage, guard, build,
check:manifest and zip all pass, and the built manifest is still exactly
["bookmarks","storage"] at version 1.0.0.
⚠️ Four of the six live only under web-ext-run, the Firefox dev runner behind
`npm run dev:firefox` — a v1.0 non-goal per docs/00 §7, and the one script no
gate exercises. docs/09 §3.1 records that, plus when each override can be
dropped.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Scaffolds the project per CLAUDE.md Phase 0 and docs/01, 02, 06, 07, 08, 10.
Both entrypoints render, and `npm run verify` is green.
- WXT 0.20.27 + Svelte 5 runes + TypeScript 6 strict, srcDir: 'src'.
- Manifest carries exactly ["bookmarks", "storage"], no host permissions, no
background worker, and never loosens the MV3 default CSP. Verified against
the built artifact, not just the config.
- scripts/guard.mjs implements the canonical grep gate from docs/08 §3 as a
single Node-stdlib script, so the same gate runs locally and in CI and
cannot drift between them.
- scripts/gen-icons.mjs writes placeholder PNGs by hand (zlib + CRC32), so no
image dependency enters the tree and the manifest loads before the designed
icon exists.
- i18n: en/vi/ja dictionaries with `satisfies Dict` (never `as const` — see
docs/07 §2), plus a pure resolve-locale module so locale mapping is testable
without the runes runtime.
- Tests run under jsdom, including an environment canary asserting the
implied-end-tag DL nesting and `:scope >` behaviour the Netscape parser will
depend on, and that a parsed hostile document stays inert.
- legal/ drafts, SECURITY.md, FUNDING.yml and .nvmrc land now because the
About tab and first-run gate link to them from the very first screens.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>