Firefox Add-ons approved the first version. The owner reported it on
2026-11-21. AMO's public API shows the add-on public, version 1.3.0,
Firefox 140 or later, slug "bookmarkmagic". Both the slug URL and the
gecko-id URL the About link uses answer 200.
- README: the Firefox install row links the listing, with an AMO version
badge beside the Chrome Web Store and Edge ones.
- docs/00: the Type line, the 1.3.0 status (live on all three stores), §9
(gecko id, slug, listing), §10 item 21 done and item 24 done. Item 23's
automation state was re-checked and is unchanged: firefox-add-ons still
does not exist.
- docs/13 §8 and store/listing.*.md: the licence to pick is "GNU General
Public License v3.0 or later". AMO offers "v3.0 only" beside it, and that
is what the listing ended up with (GPL-3.0-only, per the API) — the docs
only said "v3.0". Item 21 keeps it open, along with the empty support site.
- docs/15 and CLAUDE.md: Firefox Add-ons live; 1.3.0 is on all three.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The Chrome Web Store approved 1.3.0 on 2026-11-19. Its listing shows version
1.3.0 ("Updated: November 19, 2026", 4 users) — the first update since 1.2.0,
carrying 1.2.1 as well. Firefox Add-ons is the one store still reviewing.
- docs/00: the 1.2.0, 1.2.1 and 1.3.0 status paragraphs. §10 item 20 is done,
but the 11 §5 upgrade pass and 13 §1b step 10 still have no recorded
result. Item 23 records the store automation as configured today: all
three *_AUTOPUBLISH variables are true, so a pushed v* tag is a store
submission. chrome-web-store and edge-add-ons have their secrets and the
v* tag rule but no required reviewer. firefox-add-ons does not exist yet.
- docs/15: CWS live, Firefox Add-ons in review.
- CLAUDE.md: the banner, and a carry-forward note in Phase 10: a tag is an
upload to users' browsers, so it needs the owner's go.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The owner submitted v1.3.0 to all three stores on 2026-11-18, and Edge
Add-ons approved it on 2026-11-19: the first Edge version, public, five
languages. The Chrome Web Store update and the first Firefox Add-ons
version are still in review.
- README: the Edge row of the install table links the listing, and an
Edge Add-ons version badge (a shields dynamic badge over the store's
public getproductdetailsbycrxid JSON) sits beside the Chrome Web Store
one.
- docs/00: the Type line and v1.3.0 status; §9 gains the Edge item id
(CRX ID), Product ID, Store ID and listing; §10 items 20-22 and 24
record what was submitted, what is live and what is still open (the
11 §5 passes have no recorded result; sync-on Edge is still unverified).
The 1.2.1 paragraph says it never went up on its own.
- docs/13 §9: the About link matches the CRX ID, not the Product ID; done
for 1.3.0.
- docs/15: v1.2.1 submission skipped; v1.3.0 submitted; v1.3.0 live on
Edge; Chrome Web Store and Firefox Add-ons in review.
- CLAUDE.md: the banner and the Phase 10 exit.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
BookmarkMagic went live on Edge Add-ons on 2026-11-19. Its "Store listing"
link chooses the listing by runtime.id, and only the Chrome Web Store's id
was known, so an install from Edge Add-ons was sent to the README's install
section.
storeUrlFor now looks the id up in a map of each Chromium store's item id
to its listing. Edge's item id is Partner Center's "CRX ID", which is what
an install reports; the Product ID is a different number, the one the
EDGE_PRODUCT_ID secret takes. Any other id (an unpacked build) still goes
to the install section.
Ships with the next release (CHANGELOG [Unreleased]); docs/06 §3.5 says
so.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Partner Center warned on the zh-CN description: "Avoid referencing other
browsers in your extension description such as Firefox". Edge's developer
policy (1.1.2) says a listing must not reference other browsers, and the
first Edge copy was the Chrome Web Store description with two bullets
swapped: the export bullet still listed seven browsers, and the swapped
import bullet itself named Chrome, Brave and Firefox.
- store/listing.*.md: Firefox Add-ons and Edge Add-ons get a heading
each. The Edge section is a complete description, pasted whole, that
names no browser but Edge: the profile "Bookmarks" file is the one "Edge
and similar browsers keep", HTML export is "the standard bookmark file
every major browser can import". Every other line matches the Chrome
Web Store copy; the Firefox copy is unchanged.
- tests/unit/store-listing.test.ts: one Edge description per locale, 250
to 5,000 characters, no other browser's name; and the same pattern must
find the browsers the Chrome Web Store copy lists, so it cannot pass by
matching nothing.
- docs/08 §10, docs/13 §9, docs/11 §4, store/README.md: the rule, where it
is tested, and policy 1.5.2's "should" about the privacy policy, left
as it is unless review raises it.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The hand sync every Dependabot bump needs: docs/01 §2 names the version
the lockfile holds, and Dependabot only moves the lockfile.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
v1.3.0 is tagged (signed, on 80c7190) and released: three packages and
SHA256SUMS.txt, each checksum verified after download, and both manifests
passing check-manifest as downloaded. Nothing is submitted to a store yet.
- CLAUDE.md: the banner names 1.3.0 and what it is; the doc index points
at docs/08's Firefox and Edge sections; Phase 10 gets its exit and two
things to carry forward (no Firefox in CI; every change ships in two
packages).
- docs/00: the Type line says Firefox; a v1.3.0 status paragraph; doc
suite 1.13.
- docs/15: "v1.3.0 released" with the checksums and sizes, and
"v1.3.0 submitted" pending for the owner.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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>
An adversarial review of the Firefox port found:
- #edit treated a Firefox separator as an item in three places: a folder's
count badge, whether a folder can be expanded, and whether it can be
sorted. A folder of separators and one bookmark offered Sort A-Z.
- Replace's confirmation counted every writable root, so a signed-in
Chrome's account roots, which Replace never empties, were counted among
what it would delete. In every release since 1.1.0; it now counts the
replaceable roots only.
- The store jobs checked their files against the SHA256SUMS.txt that came
in the same artifact, with --ignore-missing. Each file is now checked by
name against the published Release's checksums.
- Qodana's publish job ran only after a successful scan, so a scan failing
on findings never published them.
- getRoots' position fallback had no test. It now has two, with unknown
ids and a Bookmarks Menu listed first.
Docs follow: the two browser modules and the warning codes (02), where the
landed index is compared (05), the separator markup and folder count (06),
what the Firefox suites are (11), the release staging and environments
limited to v* tags (12, 00), and which loose entries reach the Bookmarks
Menu on Firefox (03, 04, README).
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- BUILD.md: rebuilding the release packages, written for Firefox Add-ons'
source review (Node.js 26 stated outright: the sources archive drops
.nvmrc), and useful to anyone checking a store build against the source.
- README: a browser/store/requirement table (Edge and Firefox listings not
live yet, and said so), the Firefox package on each Release is for
checking, not installing; the privacy section names the same CSP in every
browser; limits gain Firefox's separators, address and title lengths.
- SECURITY.md: the latest version on each of the three stores is supported.
- ACCESSIBILITY.md: Firefox and Edge are best effort and untested with
assistive technology; separators are drawn but not announced, and Alt+↑/↓
past one leaves the spoken position unchanged — a known limitation.
- store/listing.*.md: the AMO and Edge blocks — the two bullets that named
Chrome rewritten for browsers in general, one more limitation for Firefox,
and each store's fields. Translations best-effort.
- CHANGELOG: the 1.3.0 entry under [Unreleased] until the bump.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- ci.yml: the Firefox package is built and checked beside the Chrome one.
- release.yml: three release files — the Chromium package (Chrome Web Store
and Edge Add-ons), the Firefox package and AMO's sources archive — each
staged by exact name so a missing one fails the run, both manifests checked
against the tag, SHA256SUMS over all three.
- One store job per store (docs/12 §3), each off until its repo variable is
true, each in its own GitHub Environment holding only its own secrets, each
checking the downloaded file against SHA256SUMS before uploading. They
install tools/publish — publish-browser-extension 6.2.0 and its three
dependencies, from their own lockfile, scripts off — instead of the ~320
packages of the dev toolchain, which the single old job installed next to
four Chrome secrets.
- The old job could not have worked: it sent CWS API v1.1 credentials, and
v1.1 was shut down on 2026-10-15. store-chrome uses v2 (publisher id and a
service account) and sets CHROME_API_VERSION explicitly. store-firefox is
listed and desktop-only; store-edge sends the Chromium package.
- Dependabot watches tools/publish; the licence gate reads its lockfile too.
- qodana.yaml: clean since the first run's findings were handled, so any new
one now fails that (non-required) workflow.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
What made Firefox more than a build target (docs/02 §4, 03, 04, 05 §10):
- Roots. getRoots (now browser/roots.ts) tries Firefox's GUIDs after
folderType and the Chromium ids, and never takes the Bookmarks Menu by
position — Firefox lists it first, and the old fallback took it for the
bar, so a Replace emptied the Menu and the toolbar and restored into the
wrong roots. The Menu is a fourth destination Replace also empties.
- The Menu in the file model: root "menu" (BM JSON, additive); HTML writes
its entries loose at the top level, as Firefox's own export does; on
Firefox loose top-level entries are routed into the Menu, elsewhere a menu
folder stays a folder under Other. New-folder mode is unchanged.
- Separators come back as { type: "separator", url: "data:" }. Recognised by
type (browser/live-tree.ts): left out of exports and backups, of every
count, of the dedupe index and the duplicate finder, never a search match;
in #edit they are aria-hidden lines that take no focus or command, with
posinset counting items only, Alt+↑/↓ stepping past one as one place, and
Sort A→Z sorting each run between them. The Replace confirmation says how
many will go and that nothing brings them back; files' separators are
counted (SEPARATORS_SKIPPED).
- Move index: Chromium counts a rightward same-folder move before removal,
Firefox after. The adapter sends each its own number and the reply's index
is checked — a mismatch re-reads the tree. Before this, every rightward drag
on Firefox landed one place too far and Alt+↓ moved two.
- Firefox refuses addresses over 65 536 characters, mid-write: dropped before
planning on Firefox (URL_TOO_LONG); nothing changes on Chromium.
- Strings true in every browser: the date note says "the browser", the About
link is "Store listing" and goes to the listing the copy came from (AMO by
gecko id, the Chrome Web Store by item id, else the README's install
section); the smart-bookmark note drops "dead link". Diagnostics names the
browser. All five locales (ja/zh-CN/ro best-effort).
bookmarks.ts was over the 300-line target, so its pure half moved to
live-tree.ts and root resolution to roots.ts before anything was added.
Tests run the root, Replace, export and #edit paths over a Firefox flavour of
the fake (docs/11 §4). Also fixes the last Qodana finding, a redundant escape
in the i18n interpolation regex.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
wxt.config.ts now builds for the target browser (docs/08 §1, §9):
- `manifestVersion: 3` for every target — WXT built Firefox as MV2;
- Firefox gets browser_specific_settings.gecko — the permanent id
bookmarkmagic@poli0981.dev, strict_min_version 140.0 (the first that
accepts data_collection_permissions, which AMO requires of new add-ons),
and data_collection_permissions { required: ["none"] } — and no
minimum_chrome_version; Chrome keeps its floor of 136;
- Vite targets firefox140 for that package;
- the sources archive AMO reviews leaves out coverage, captures, store copy,
docs, tests and tools.
Permissions, CSP, pages and icons are identical in both packages.
check-manifest.mjs takes --browser chrome|firefox, mapped through a fixed
table to .output/<target>-mv3 (still no path from the command line), and
pins each package's exact key set and floor; the gecko block is compared key
order aside. New npm scripts: build:firefox, zip:firefox; verify:full builds
and checks both packages.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Docs first, as CLAUDE.md requires; the code follows in this branch.
- 08: the manifest per target (two packages from one source, MV3 for
both); Firefox's gecko id, data-collection declaration, floor 140 and
source-code submission; Edge takes the Chrome package unchanged.
- 02 §4, 03 §1/§3, 04, 05 §10: Firefox's GUID roots and fourth root, the
Bookmarks Menu (`root: "menu"`, unmarked entries routed into it on
Firefox); separators recognised by type, kept out of the file model and
shown as untouchable lines in #edit; the move index sent by each browser's
own rule and checked against the reply; addresses Firefox refuses dropped
before planning; separators a file holds counted.
- 06/07: the About link follows the install; three strings that blamed
Chrome for what every browser does are reworded; new keys listed.
- 11: a Firefox flavour of the fake, and a manual pass on real Firefox and
Edge (including Edge signed in with sync) before the first submissions.
- 12/13: three store jobs, each in its own environment with only its own
secrets and a four-package install; CWS API v2 (v1.1 died 2026-10-15);
AMO and Edge runbooks for the first, manual uploads.
- 09/14 and legal/: three stores named; a clarification, not a
LEGAL_VERSION bump.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The first scan found 27 issues and no defect:
- two regular expressions that could be simpler, fixed: the sanitizer's
[\p{Extended_Pictographic}] class and wxt.config.ts's split(/[/]/). A third
is in src/ and waits for the 1.3.0 change, so this branch still builds
byte-for-byte what v1.2.1 shipped;
- 24 that contradict a rule of this repository, switched off in
qodana.yaml with the reason beside each: JSDoc completeness (doc comments
here are prose, docs/10 §6), bitwise operators in the PNG CRC-32 of
gen-icons.mjs, and the deliberately doubled dark palette in tokens.css.
`publish` failed: the qodana-report artifact holds a zip whose entries have
absolute names, so a glob for the SARIF found nothing. It now extracts the
one entry /qodana.sarif.json by name.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Recorded now rather than with the port, because the maintenance
announcement names it (docs/15, docs/00 §7). Settled with the owner: gecko
id bookmarkmagic@poli0981.dev, desktop only (Firefox for Android has no
bookmarks API), MV3 everywhere, and Firefox separators shown, protected and
warned about rather than stored in a file format.
The roadmap is pruned to what MAINTENANCE.md allows: scheduled snapshots
need the alarms permission and leave it; the permission rule joins the never
list; the fflate zip export, the duplicate auto-merge assistant and
bookmarklet notes are not planned; the old v1.3 "resilience" becomes v1.4.
MAINTENANCE.md no longer lists "a dependency advisory" as a release trigger
on its own: with no runtime dependencies, an advisory against the build
tools needs a release only if it changed what ships.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
qodana.yml runs qodana-js (Ultimate, QODANA_TOKEN) on pushes to main, pull
requests, a weekly schedule and by hand, in two jobs (docs/12 §2.7):
- `scan` installs the dev dependencies with scripts off — qodana-js resolves
types through them — and holds only a read-only GITHUB_TOKEN; PR comments
and annotations are off, the SARIF report is kept as an artifact;
- `publish` installs nothing and uploads that SARIF to code scanning
(category qodana), so the findings sit beside CodeQL's.
The action is pinned to the commit of v2026.2.2 (the newest tag is younger
than the 7-day cooldown). Sharing a runner with dependency code is recorded
as an exception to the Sonar rule: the token can only upload reports.
triage.yml, from review of the first draft:
- comment and close first, label last — the label is what a re-run reads as
done, so it must not exist before the work;
- an `enhancement` issue with no answer to the form is closed only when the
owner added the label; otherwise it goes to needs-triage;
- checkout and setup-node pinned to commits, no cache: this workflow runs
them with a write token on events anyone can trigger.
README gains the Qodana badge.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
MAINTENANCE.md is the policy: dependency updates on a schedule, high and
critical advisories fixed as soon as a fix exists, major platform upgrades,
bug/UI/UX/accessibility/translation fixes, and features only when they are
on docs/15's roadmap or genuinely needed.
- The feature form asks one required question — on the roadmap, needed for
a fix, or something new — and links the policy and Discussions › Ideas.
- scripts/triage.mjs decides what happens, as a pure, unit-tested function;
.github/workflows/triage.yml carries it out with `gh` alone. Something new
is labelled maintenance-mode, commented and closed as not planned; the two
in-policy answers get needs-triage; an outside `feat…` pull request is
closed the same way. Owner, members, collaborators, bots and `roadmap` are
exempt.
- pull_request_target checks out the base branch only, runs nothing from the
pull request, and never interpolates a title or body into the shell.
- README gains a status badge and a "Project status" section; CONTRIBUTING,
the PR template and the issue chooser say what is accepted.
- docs: 00 status, 11 inventory, 12 §2.6 and §5 (labels), 13 §6, 15 (a
pointer to the policy, not a copy, and the decision-log rows); CLAUDE.md
Phase 10.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
scripts/check-licenses.mjs reads package-lock.json, where npm records each
package's own `license` field, and fails on anything outside two lists
(docs/09 §3.2):
- what the build compiles into the extension (svelte, clsx, wxt,
@wxt-dev/browser) must be permissive and GPL-3.0-compatible;
- everything else is build tooling that never ships, so file-level copyleft
(MPL-2.0, lightningcss) is also accepted; AGPL, source-available terms and
missing or custom licences are not.
SPDX expressions are evaluated, nothing is installed or fetched, and the
tests call the functions directly rather than spawning the script. It runs
in `verify`, CI's quality job and the release build.
The shipped list moves out of wxt.config.ts into
scripts/credited-packages.mjs, so the build gate, the notices test and the
licence gate read one list instead of two copies and a regex.
legal/THIRD_PARTY_NOTICES.md said the tooling was all MIT/Apache-2.0/ISC; the
lockfile also has BSD, 0BSD, MIT-0, BlueOak, CC0 and MPL-2.0. Corrected — a
description of tooling that never ships, so no LEGAL_VERSION bump (14 §3.1).
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Dependabot's #39-#41 moved the packages and left the rest behind, as
docs/15 (2026-11-10) says it always does:
- biome.json and docs/10 name the schema of Biome 2.6.6;
- docs/01 records Biome 2.6.6, knip 6.44.2 and jsdom ^31.0;
- docs/12 §2.5 names the scan action's new pin, v8.4.1;
- docs/11 §6 gains a jsdom 31 column for the 100k parse (median of three
runs, 2 484 ms) instead of overwriting the jsdom 29 figure.
docs/09 §3.1: npm audit now reports 14 high findings with one root cause,
picomatch GHSA-fc5q-39xc-vjpf, for which no fixed version exists. It is the
toolchain's glob engine, matching patterns this repository writes, and
never ships (--omit=dev stays 0). The deepmerge row goes: GitHub withdrew
that advisory on 2026-11-16.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Signed tag v1.2.1 on d61318a (PR #37, merged at the reviewed head). The
Release asset verifies against SHA256SUMS.txt (4975b5df…ca13254, 106 290
bytes); its manifest differs from 1.2.0's in `version` alone and the file
inventory is the same. `announce` and the store publish were skipped, as
their variables are unset.
Still the owner's: the docs/11 §5 pass with the 1.2.0 -> 1.2.1 upgrade over
an existing profile, a real Windows contrast theme and a screen-reader pass
over Alt+Up/Down, and the store upload.
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
stores/edit-live.ts was untested — it is the block that used to sit in
EditTab's onMount, where nothing measured it. As a .ts module it counts, and
SonarCloud's new-code gate failed at 73.6 % (80 % required).
edit-live.test.ts drives it with wxt/browser mocked to hand-fired event
emitters and a hand-fired frame: one patch per frame, a parentless created
node ignored, nothing patched during Chrome's own import and one re-read
after it, a re-read on a wholesale reorder, and a teardown that detaches every
listener and drops what was queued. connectLive takes the batcher's scheduler
as an optional argument for that.
Co-Authored-By: Claude Fable 5.2 <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>
Two independent reviews, of the code and of the documentation against it.
Code:
- A first click on a row button or a chevron jumped the tree to the top:
handing focus to the tree with no row focused made it pick the first one.
The clicked control's row becomes the focused one, and the tree only picks
the first row for a focus that came from the keyboard — which also stops a
plain click on a row in a scrolled tree from landing on the wrong row.
- Three forced-colours rules lost to more specific ones: the selected theme
lost its label on hover, About's status-bar entry had no right edge, and a
drop into the focused folder showed nothing.
- Under a search, Alt+Up/Down announced the position among all siblings while
the row's aria-posinset counts the ones on screen; it announces the latter.
Moves run one at a time, and the live region is emptied before each
message so a repeated text is spoken.
- The preview's "Show more" was still 22 px; the ring on "Show earlier / Show
more" and on the "Move to…" folders was clipped; placeholders used the
browser's grey, which no contrast test saw.
- EditTab's script was over the 150-line limit: its live-sync wiring moves to
stores/edit-live.ts.
Documentation:
- ACCESSIBILITY.md promised more than the code does in nine places ("every
clickable target is 24 px", "nothing times out", "focus is always a 2-pixel
ring", four operating systems "supported"). Rewritten to what the source
supports; the untested list and the known limitations grew.
- docs/05, 06, 10, 11, 13, 15 and CLAUDE.md corrected where they named tests
that did not exist, miscounted, or were overtaken by the fixes above.
tests: a managed node, hidden siblings under a search and an in-flight move
for nudge; the statement's key table is checked against tree-keyboard.ts.
capture/about.png shows the new About link.
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
Svelte's a11y_* checks are compiler warnings, and a warning never failed
anything: `npm run check` now runs svelte-check with --fail-on-warnings. It is
the only lint that reads the markup (Biome skips .svelte). The suite is at
zero warnings; the two deliberate exceptions carry a svelte-ignore.
scripts/screenshots.mjs built its sample tree without parentId, which Chrome
gives every node but the root. In the harness nothing could be placed beside
a sibling and the toolbar's Sort stayed disabled on a bookmark — found while
driving Alt+Up/Down through it.
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
The tree's keys are shown nowhere in the UI, and someone who meets a barrier
has no route from inside the product to reporting it. About now links
ACCESSIBILITY.md beside the changelog — the file, not an address: no email
appears on an in-product surface (docs/06 §3.5).
links.test.ts pins the URL and the file's existence, as it does for the
changelog. The label is new in all five locales; ja, zh-CN and ro are
best-effort like the rest of those files.
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
Placing an item before or after a sibling took a drag: "Move to…" only
appends, and Sort A→Z was the one keyboard reorder (WCAG 2.1.1; backlog since
the 1.1.0 review). Alt+Up and Alt+Down now move the focused row one place
among the siblings on screen.
No second write path: nudgeTarget picks the neighbour, and the drag's own
planDrop and moveTo do the rest, so a key and a drag cannot disagree about
what is legal — nothing happens at either end of a folder, on a permanent
root, on a managed node or while a bulk command runs. A polite live region
speaks "<title>: position n of m": aria-posinset changes too, but a screen
reader does not re-read the active descendant for an attribute change.
Focus no longer falls to <body>:
- a route change that takes the focused control with it ("Open in Edit" on
the import report) moves focus to <main> — only when it was lost, and not
while the page loads;
- after "keep the first of each", to the panel's close button;
- after a confirmed toolbar Sort A→Z, whose button is disabled while it runs,
to the tree.
EditTab's dialogs move to EditDialogs.svelte to keep the tab under 300 lines.
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
Found by an audit of src/ after a keyboard-only and Narrator pass over 1.2.0
found nothing; verified in a headless Chrome driven over CDP against the
harness, with forced-colors emulated.
- The theme control's ring was invisible. It is inset to stay inside the
group's border, and roving focus only ever lands on the selected segment,
which is filled with --accent: accent on accent. It is --accent-fg now, 4px
in, so the fill shows on both sides of it.
- Contrast themes (forced-colors) remove every fill, shadow and background
image. The tree's focused row and drop lines, the selected theme, the
current tab and status-bar entry, the selected mode and format cards, the
progress fill and the drop zone's dashed edge each get a system-colour
equivalent. A border or outline wherever the state has a label: Chrome
paints a backplate behind forced text, and a label on a Highlight fill
became a box that hid it.
- Every pointer target is at least 24 x 24 px: the row buttons (22), the
three disclosure chevrons (16, now one Disclosure component with a grown
hit area), the toast and dialog dismiss buttons, the popup's gear, the
picker's "Show more".
- A click on a row button or the chevron hands focus back to the tree.
Chrome focuses a tabindex="-1" button on click and the tree ignores keys
aimed at a row's own control, so one click switched the arrow keys off;
"Move to…" from the row button now returns focus to the tree as well.
tests: focus-ring.test.ts fails on an inset ring over an accent fill;
forced-colors.test.ts holds the list of components that must carry the block.
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
ACCESSIBILITY.md at the repository root, after opensource.guide's
accessibility practices and the accessibility-toolkit template: WCAG 2.2 AA
as a goal and not a conformance claim, supported environments, the tree's
full key table (shown nowhere in the UI), what was tested and with what
(keyboard only and Narrator with Chrome on Windows 11), what was not, the
known limitations, and how a report is handled by a one-person project.
Intake: an "accessibility" issue form and label, accessibility@poli0981.dev
in the issue chooser and the README's contact table, an interface section in
CONTRIBUTING.md and in the PR checklist.
tests/unit/accessibility-statement.test.ts pins the routes and the key
table, since nothing in the build reads the file.
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
v1.2.0 is on the store (listing observed 2026-11-10: version 1.2.0, updated
November 7, five languages); CLAUDE.md, docs/00 and docs/15 still said it had
not been submitted.
docs/06 §5 now specifies what an audit of src/ found the 1.2.0 keyboard and
Narrator pass could not: a ring inside a filled control takes the fill's text
colour, forced-colours equivalents for every state shown by a fill or a
shadow, Alt+Up/Down as the keyboard's before/after (through planDrop, docs/05
§10), three more places focus fell to <body>, row buttons handing focus back
to the tree, and 24 px targets.
docs/11 §5 gains the checks no script runs: a screen reader, a contrast
theme, 200 % zoom, and "ACCESSIBILITY.md is still true". docs/12 §4 says an
accessibility fix is a patch. docs/15 schedules what is not closed.
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>
Signed tag on e2f36bc; the Release zip (105 284 bytes) passes
`sha256sum -c`, and its manifest differs from 1.1.0's only in `version`,
with _locales/zh_CN and _locales/ro added. Store submission, the upgrade
pass and the two new listing languages stay with the owner.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The template still asked for "all three" locales; it now points at
LOCALES and the Romanian `few` form (docs/07 §5).
Co-Authored-By: Claude Opus 5.5 <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>
Translations (an independent native-style review of every key):
- ro export.csvNote said the bookmarks-bar folder itself is lost on CSV
export; only *which* folder is the bar is lost.
- ro: counts that are plain numbers use a label form ("Omise — deja în
acest browser: {n}") so 1 never reads as a plural; "din Chrome" for
the brand; mode names quoted exactly; the tagline, appDesc and listing
summary as a noun phrase instead of an informal imperative; the
backup promise in replaceWarning made explicit; GPL wording.
- zh-CN: quoted mode names match the real labels (全部替换); 一半 no
longer claims 50%; one name for Chrome's Bookmarks file; 您 only where
it earns its place; the English-only note no longer implies
translations exist.
- Uncertain strings carry TODO(review-zh/ro) for the native pass.
Code:
- Each language option carries its own `lang`, so endonyms are voiced
and drawn in their language (WCAG 3.1.2; Chinese vs Japanese glyphs).
- resolveLocale ignores -u-/-x- subtags; the docs/07 table states that
an explicit script wins and other zh regions get zh-CN.
- The listings' LANGUAGES line is built from LOCALES, and format tests
derive their locale lists, so a new locale cannot slip past them.
- screenshots.mjs back under 300 lines: one job list for --shoot.
- Unneeded casts removed from dictionaries.test.ts; docs/11 describes
the popup shots and what the sweep cannot cover.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- store/listing.zh_CN.md and store/listing.ro.md (best-effort, marked
TODO(review-zh) / TODO(review-ro)); every listing and the README now
name all five languages.
- The translation issue form offers 简体中文 and Română; CONTRIBUTING
explains the plural forms and the comma-below rule, and points at
docs/07 §6.
- scripts/screenshots.mjs photographs every locale, and the popup per
theme and language.
- tests/unit/i18n/touch-points.test.ts holds the files that cannot import
LOCALES (harness, check-manifest, the form, the listings) to the list;
the cedilla scan covers the Romanian listing too.
- Comments that said "three locales" or "VI/JA" now say what they mean.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- ro.ts, ro-notices.ts and ro-import.ts, written from Chrome's own ro
terminology (marcaj, Bara de marcaje, dosar) in the polite plural, and
marked TODO(review-ro) until a native pass (docs/07 §4).
- The first locale with three plural forms: every plural key carries
one / few / other ("1 marcaj", "5 marcaje", "20 de marcaje"); count-less
labels repeat the bare noun (docs/07 §5).
- Tests: comma-below ș ț only (a cedilla anywhere in the Romanian files
fails, comments included), "de" only in `other`, selectPluralForm at
the CLDR boundaries (0, 1, 2, 19, 20, 101, 120), tPlural end to end,
and ro-RO collation for Sort A→Z.
- _locales/ro/messages.json; check-manifest requires it.
- Română joins every dictionary's endonym list.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- zh-CN.ts, zh-CN-notices.ts and zh-CN-import.ts, written from Chrome's
own zh-CN terminology (书签, 书签栏, 文件夹, 导入, 导出) and marked
TODO(review-zh) until a native pass (docs/07 §4).
- _locales/zh_CN/messages.json; check-manifest requires it.
- resolveLocale maps zh, zh-CN, zh-SG and zh-Hans* to zh-CN. zh-TW,
zh-HK, zh-MO and zh-Hant* get English, matching Chrome's own manifest
fallback (docs/07 §1-2).
- <html lang="zh-CN"> makes Chrome draw Simplified glyphs rather than
Japanese ones; Sort A→Z collates by pinyin.
- 简体中文 joins every dictionary's endonym list.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Groundwork for zh-CN and ro, with no new language yet (docs/07 §2, §5):
- resolve-locale.ts exports LOCALES; Locale is derived from it. dicts,
TAGS, the storage allow-list and the Settings choices all follow it, the
first two as Record<Locale, ...> so a missing table is a compile error.
- Dict is Localized<typeof dict>: plural branches may carry `few`.
selectPluralForm keeps `few`; requiredPluralForms says which forms a
locale's own Intl.PluralRules need.
- dictionaries.test.ts checks plural shape per locale, guards against
locales that need zero/two/many, holds the endonyms equal, and pins
the Dict type with @ts-expect-error cases.
- manifest.test.ts maps locales to _locales directories, rejects strays
and caps appDesc at 132 characters; options, links and storage tests
iterate LOCALES.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
v1.1.0 cleared CWS review (listing shows 1.1.0, 6 users, observed
2026-11-06). The dashboard's install figures make Simplified Chinese and
Romanian the next minor, so the spec says the new thing before the code:
- 07: one LOCALES list, the zh-CN/ro resolution table (Traditional
Chinese falls back to English, matching Chrome's manifest fallback),
a third plural form for Romanian, tone and glossary per language,
the best-effort review policy, and a new §6 "Adding a locale".
- 12 §4: a new UI language is a minor; translation fixes stay patches.
- 15: v1.2 is languages; the old v1.2 items move to v1.3.
- 00, 02, 03, 06, 08, 11, 13, 14 and CLAUDE.md follow.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- docs/15: Phase 7 done (#26–#29); a "v1.1.0 released" row with the signed
tag on 9040f84, the checksum-verified zip and its manifest diff against
1.0.1 (version, Chrome floor, CSP — nothing else); a pending "submitted"
row; a decision-log row on why the tag moved.
- docs/00: the header says released, not in preparation; §10 item 12 lists
what is still human-only for the store; doc suite 1.9.
- docs/13 §7: the one case where re-pointing a tag is right — a run that
failed before any Release existed.
- CLAUDE.md: phases 0–7 complete; the Phase 7 exit as it stands.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The first tag run of the split release workflow (v1.1.0) failed in "Gate +
package": actions/upload-artifact skips hidden paths by default, `.output`
is one, so `.output/*-chrome.zip` and `.output/SHA256SUMS.txt` matched
nothing and `if-no-files-found: error` stopped the job. The publish job was
skipped, so no Release or asset was created.
The build job now copies both files into a plain `dist/` and uploads that.
The artifact layout the publish and store jobs download is unchanged, and
`include-hidden-files` stays off, so nothing else under `.output` can be
swept into a release.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>