126 Commits
Author SHA1 Message Date
poli0981andClaude Opus 5.5 acad57acf4 docs: v1.3.0 is on Firefox Add-ons too — all three stores live
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>
2026-11-21 22:54:53 +07:00
poli0981andClaude Opus 5.5 33c4d517b4 docs: v1.3.0 is live on the Chrome Web Store; tags now publish
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>
2026-11-19 16:44:13 +07:00
poli0981andClaude Opus 5.5 28c27154ac docs: Edge Add-ons is live; record the v1.3.0 submissions
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>
2026-11-19 07:32:59 +07:00
poli0981andClaude Opus 5.5 ce97979706 fix(about): send Edge Add-ons installs to their listing
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>
2026-11-19 07:32:59 +07:00
poli0981andClaude Opus 5.5 1657646b01 docs(store): Edge listing names no other browser
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>
2026-11-18 23:45:49 +07:00
poli0981andClaude Opus 5.5 bcc4c81a8c docs(01): knip 6.45.1, after Dependabot #45
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>
2026-11-18 22:21:38 +07:00
poli0981andClaude Opus 5.5 46093b7bd1 docs: record v1.3.0 as released
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>
2026-11-18 22:21:38 +07:00
dependabot[bot] 938ad5d8ab chore(deps-dev): Bump knip
Bumps the dev-minor-and-patch group with 1 update: [knip](https://github.com/webpro-nl/knip/tree/HEAD/packages/knip).


Updates `knip` from 6.44.2 to 6.45.1
- [Release notes](https://github.com/webpro-nl/knip/releases)
- [Commits](https://github.com/webpro-nl/knip/commits/knip@6.45.1/packages/knip)

---
updated-dependencies:
- dependency-name: knip
  dependency-version: 6.45.1
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: dev-minor-and-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
2026-11-18 22:16:05 +07:00
poli0981andClaude Opus 5.5 80c7190864 chore(release): 1.3.0
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>
v1.3.0
2026-11-18 22:10:35 +07:00
poli0981andClaude Opus 5.5 ffceb4bd54 fix: review findings — separators are not items, Replace counts what it deletes
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>
2026-11-18 22:10:35 +07:00
poli0981andClaude Opus 5.5 23f6386d3d docs: Firefox and Edge for users — install, build, limits, listings
- 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>
2026-11-18 22:10:35 +07:00
poli0981andClaude Opus 5.5 dc4cd06cbb ci: build both packages, and publish to three stores from isolated jobs
- 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>
2026-11-18 22:10:35 +07:00
poli0981andClaude Opus 5.5 2eaa1acce4 feat(firefox): the right roots, the Bookmarks Menu, separators and move index
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>
2026-11-18 22:10:35 +07:00
poli0981andClaude Opus 5.5 779335802a build(firefox): a second package, MV3, held to its own manifest gate
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>
2026-11-18 22:10:35 +07:00
poli0981andClaude Opus 5.5 355443ef6b docs: specify Firefox (AMO) and Edge Add-ons support for v1.3.0
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>
2026-11-18 22:10:35 +07:00
poli0981andClaude Opus 5.5 8519e7c39e fix(qodana): act on the first run, and read the report where it really is
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>
2026-11-18 21:03:47 +07:00
poli0981andClaude Opus 5.5 76a57fb739 docs: GO for Firefox and Edge as v1.3; the roadmap under maintenance mode
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>
2026-11-18 21:03:47 +07:00
poli0981andClaude Opus 5.5 0ec5187e4b ci: Qodana for JS, and a harder triage workflow
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>
2026-11-18 21:03:47 +07:00
poli0981andClaude Opus 5.5 eabffbe652 feat(repo): maintenance mode, with triage that closes out-of-policy requests
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>
2026-11-18 21:03:47 +07:00
poli0981andClaude Opus 5.5 11e7e50fe6 build: a licence gate over every package in the lockfile
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>
2026-11-18 21:03:47 +07:00
poli0981andClaude Opus 5.5 4b10749582 chore(deps): finish the Dependabot bumps and record the picomatch advisory
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>
2026-11-18 21:03:47 +07:00
dependabot[bot] 77de0de1d5 chore(deps-dev): Bump jsdom from 30.1.3 to 31.0.0
Bumps [jsdom](https://github.com/jsdom/jsdom) from 30.1.3 to 31.0.0.
- [Release notes](https://github.com/jsdom/jsdom/releases)
- [Commits](https://github.com/jsdom/jsdom/compare/v30.1.3...v31.0.0)

---
updated-dependencies:
- dependency-name: jsdom
  dependency-version: 31.0.0
  dependency-type: direct:development
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>
2026-11-18 20:32:06 +07:00
dependabot[bot] 43681ecd1f chore(deps-dev): Bump the dev-minor-and-patch group with 2 updates
Bumps the dev-minor-and-patch group with 2 updates: [@biomejs/biome](https://github.com/biomejs/biome/tree/HEAD/packages/@biomejs/biome) and [knip](https://github.com/webpro-nl/knip/tree/HEAD/packages/knip).


Updates `@biomejs/biome` from 2.6.4 to 2.6.6
- [Release notes](https://github.com/biomejs/biome/releases)
- [Changelog](https://github.com/biomejs/biome/blob/main/CHANGELOG_v1.md)
- [Commits](https://github.com/biomejs/biome/commits/@biomejs/biome@2.6.6/packages/@biomejs/biome)

Updates `knip` from 6.44.1 to 6.44.2
- [Release notes](https://github.com/webpro-nl/knip/releases)
- [Commits](https://github.com/webpro-nl/knip/commits/knip@6.44.2/packages/knip)

---
updated-dependencies:
- dependency-name: "@biomejs/biome"
  dependency-version: 2.6.6
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: dev-minor-and-patch
- dependency-name: knip
  dependency-version: 6.44.2
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: dev-minor-and-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
2026-11-18 20:26:58 +07:00
dependabot[bot] 6047f5bf30 ci(deps): Bump SonarSource/sonarqube-scan-action
Bumps the actions group with 1 update: [SonarSource/sonarqube-scan-action](https://github.com/sonarsource/sonarqube-scan-action).


Updates `SonarSource/sonarqube-scan-action` from 8.4.0 to 8.4.1
- [Release notes](https://github.com/sonarsource/sonarqube-scan-action/releases)
- [Commits](https://github.com/sonarsource/sonarqube-scan-action/compare/4d1dc0c91ee400dcf8a6dddf2f705ac36542e304...e805d875275f728fac1885b413934be6d7c63f65)

---
updated-dependencies:
- dependency-name: SonarSource/sonarqube-scan-action
  dependency-version: 8.4.1
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: actions
...

Signed-off-by: dependabot[bot] <support@github.com>
2026-11-18 20:26:38 +07:00
poli0981andClaude Fable 5.2 47206cc6c2 docs: record v1.2.1 as released on GitHub
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>
2026-11-10 11:29:46 +07:00
poli0981andClaude Fable 5.2 d61318aed7 test(edit): cover the live-sync wiring that left EditTab
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>
v1.2.1
2026-11-10 11:18:58 +07:00
poli0981andClaude Fable 5.2 0bd2aabbf2 chore(release): 1.2.1
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>
2026-11-10 11:18:58 +07:00
poli0981andClaude Fable 5.2 2be6955087 fix(review): code and documentation review findings for 1.2.1
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>
2026-11-10 11:18:58 +07:00
poli0981andClaude Fable 5.2 8d9739cab4 build: svelte-check fails on warnings; the harness gives every node a parentId
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>
2026-11-10 11:18:58 +07:00
poli0981andClaude Fable 5.2 9d4458ae4b feat(about): link the accessibility statement
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>
2026-11-10 11:18:58 +07:00
poli0981andClaude Fable 5.2 e4f2a93820 fix(edit): Alt+Up/Down reorders from the keyboard; focus is no longer dropped
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>
2026-11-10 11:18:58 +07:00
poli0981andClaude Fable 5.2 bf3eb9f22b fix(a11y): a focus ring that shows on a filled control, forced colours, 24 px targets
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>
2026-11-10 11:18:58 +07:00
poli0981andClaude Fable 5.2 073a7cd654 docs(a11y): an accessibility statement, and a way to report a barrier
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>
2026-11-10 11:18:58 +07:00
poli0981andClaude Fable 5.2 e5d1cf5bf5 docs: specify the accessibility work for v1.2.1; record v1.2.0 as live
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>
2026-11-10 11:18:58 +07:00
poli0981andClaude Fable 5.2 21b04c3e96 chore(deps): sync the Biome schema, the Vitest range and the pinned-version docs
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>
2026-11-10 11:18:58 +07:00
dependabot[bot] 8c4d75fe08 chore(deps-dev): Bump the dev-minor-and-patch group with 6 updates
Bumps the dev-minor-and-patch group with 6 updates:

| Package | From | To |
| --- | --- | --- |
| [@biomejs/biome](https://github.com/biomejs/biome/tree/HEAD/packages/@biomejs/biome) | `2.6.3` | `2.6.4` |
| [@types/node](https://github.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/node) | `26.6.5` | `26.6.6` |
| [@vitest/coverage-v8](https://github.com/vitest-dev/vitest/tree/HEAD/packages/coverage-v8) | `5.0.5` | `5.1.0` |
| [knip](https://github.com/webpro-nl/knip/tree/HEAD/packages/knip) | `6.43.0` | `6.44.1` |
| [svelte-check](https://github.com/sveltejs/language-tools) | `4.7.7` | `4.7.8` |
| [vitest](https://github.com/vitest-dev/vitest/tree/HEAD/packages/vitest) | `5.0.5` | `5.1.0` |


Updates `@biomejs/biome` from 2.6.3 to 2.6.4
- [Release notes](https://github.com/biomejs/biome/releases)
- [Changelog](https://github.com/biomejs/biome/blob/main/CHANGELOG_v1.md)
- [Commits](https://github.com/biomejs/biome/commits/@biomejs/biome@2.6.4/packages/@biomejs/biome)

Updates `@types/node` from 26.6.5 to 26.6.6
- [Release notes](https://github.com/DefinitelyTyped/DefinitelyTyped/releases)
- [Commits](https://github.com/DefinitelyTyped/DefinitelyTyped/commits/HEAD/types/node)

Updates `@vitest/coverage-v8` from 5.0.5 to 5.1.0
- [Release notes](https://github.com/vitest-dev/vitest/releases)
- [Changelog](https://github.com/vitest-dev/vitest/blob/main/docs/releases.md)
- [Commits](https://github.com/vitest-dev/vitest/commits/v5.1.0/packages/coverage-v8)

Updates `knip` from 6.43.0 to 6.44.1
- [Release notes](https://github.com/webpro-nl/knip/releases)
- [Commits](https://github.com/webpro-nl/knip/commits/knip@6.44.1/packages/knip)

Updates `svelte-check` from 4.7.7 to 4.7.8
- [Release notes](https://github.com/sveltejs/language-tools/releases)
- [Commits](https://github.com/sveltejs/language-tools/compare/svelte-check@4.7.7...svelte-check@4.7.8)

Updates `vitest` from 5.0.5 to 5.1.0
- [Release notes](https://github.com/vitest-dev/vitest/releases)
- [Changelog](https://github.com/vitest-dev/vitest/blob/main/docs/releases.md)
- [Commits](https://github.com/vitest-dev/vitest/commits/v5.1.0/packages/vitest)

---
updated-dependencies:
- dependency-name: "@biomejs/biome"
  dependency-version: 2.6.4
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: dev-minor-and-patch
- dependency-name: "@types/node"
  dependency-version: 26.6.6
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: dev-minor-and-patch
- dependency-name: "@vitest/coverage-v8"
  dependency-version: 5.1.0
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: dev-minor-and-patch
- dependency-name: knip
  dependency-version: 6.44.1
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: dev-minor-and-patch
- dependency-name: svelte-check
  dependency-version: 4.7.8
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: dev-minor-and-patch
- dependency-name: vitest
  dependency-version: 5.1.0
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: dev-minor-and-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
2026-11-10 08:28:08 +07:00
dependabot[bot] 533809ce4f ci(deps): Bump SonarSource/sonarqube-scan-action
Bumps the actions group with 1 update: [SonarSource/sonarqube-scan-action](https://github.com/sonarsource/sonarqube-scan-action).


Updates `SonarSource/sonarqube-scan-action` from 8.3.0 to 8.4.0
- [Release notes](https://github.com/sonarsource/sonarqube-scan-action/releases)
- [Commits](https://github.com/sonarsource/sonarqube-scan-action/compare/d209202bc7d53ff1cc128f7f907dac145c9d6ae9...4d1dc0c91ee400dcf8a6dddf2f705ac36542e304)

---
updated-dependencies:
- dependency-name: SonarSource/sonarqube-scan-action
  dependency-version: 8.4.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: actions
...

Signed-off-by: dependabot[bot] <support@github.com>
2026-11-10 08:27:54 +07:00
dependabot[bot] f65264a020 chore(deps-dev): Bump wxt from 0.21.4 to 0.21.5
Bumps [wxt](https://github.com/wxt-dev/wxt) from 0.21.4 to 0.21.5.
- [Release notes](https://github.com/wxt-dev/wxt/releases)
- [Commits](https://github.com/wxt-dev/wxt/compare/wxt-v0.21.4...wxt-v0.21.5)

---
updated-dependencies:
- dependency-name: wxt
  dependency-version: 0.21.5
  dependency-type: direct:development
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
2026-11-06 20:21:22 +07:00
dependabot[bot] c5dd04a1b8 chore(deps-dev): Bump the dev-minor-and-patch group with 3 updates
Bumps the dev-minor-and-patch group with 3 updates: [@biomejs/biome](https://github.com/biomejs/biome/tree/HEAD/packages/@biomejs/biome), [knip](https://github.com/webpro-nl/knip/tree/HEAD/packages/knip) and [svelte](https://github.com/sveltejs/svelte/tree/HEAD/packages/svelte).


Updates `@biomejs/biome` from 2.6.2 to 2.6.3
- [Release notes](https://github.com/biomejs/biome/releases)
- [Changelog](https://github.com/biomejs/biome/blob/main/CHANGELOG_v1.md)
- [Commits](https://github.com/biomejs/biome/commits/@biomejs/biome@2.6.3/packages/@biomejs/biome)

Updates `knip` from 6.42.1 to 6.43.0
- [Release notes](https://github.com/webpro-nl/knip/releases)
- [Commits](https://github.com/webpro-nl/knip/commits/knip@6.43.0/packages/knip)

Updates `svelte` from 5.57.2 to 5.57.3
- [Release notes](https://github.com/sveltejs/svelte/releases)
- [Changelog](https://github.com/sveltejs/svelte/blob/main/packages/svelte/CHANGELOG.md)
- [Commits](https://github.com/sveltejs/svelte/commits/svelte@5.57.3/packages/svelte)

---
updated-dependencies:
- dependency-name: "@biomejs/biome"
  dependency-version: 2.6.3
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: dev-minor-and-patch
- dependency-name: knip
  dependency-version: 6.43.0
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: dev-minor-and-patch
- dependency-name: svelte
  dependency-version: 5.57.3
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: dev-minor-and-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
2026-11-06 20:06:02 +07:00
poli0981andClaude Opus 5.5 c42681fb04 docs: record v1.2.0 as released on GitHub
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>
2026-11-06 19:41:02 +07:00
poli0981andClaude Opus 5.5 e2f36bc6b1 chore(github): the PR checklist names every locale
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>
v1.2.0
2026-11-06 19:31:50 +07:00
poli0981andClaude Opus 5.5 46606dce94 chore(release): 1.2.0
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>
2026-11-06 19:31:50 +07:00
poli0981andClaude Opus 5.5 63dcf0d4fc fix(review): translation and code review findings for zh-CN and ro
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>
2026-11-06 19:31:50 +07:00
poli0981andClaude Opus 5.5 c667a0b4c9 chore(i18n): store listings, translation form and harness for zh-CN and ro
- 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>
2026-11-06 19:31:50 +07:00
poli0981andClaude Opus 5.5 49ce0bf868 feat(i18n): Romanian (ro)
- 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>
2026-11-06 19:31:50 +07:00
poli0981andClaude Opus 5.5 254409dd3b feat(i18n): Simplified Chinese (zh-CN)
- 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>
2026-11-06 19:31:50 +07:00
poli0981andClaude Opus 5.5 a95663a1f9 refactor(i18n): one LOCALES list and a third plural form
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>
2026-11-06 19:31:50 +07:00
poli0981andClaude Opus 5.5 71d969e673 docs: record v1.1.0 as live; specify zh-CN and ro for v1.2.0
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>
2026-11-06 19:31:50 +07:00
poli0981andClaude Opus 5.5 b73803a718 docs: record v1.1.0 as released on GitHub, and the moved tag
- 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>
2026-10-29 04:22:22 +07:00
poli0981andClaude Opus 5.5 9040f84fe2 ci(release): stage the release files outside the hidden .output directory
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>
v1.1.0
2026-10-29 04:13:17 +07:00