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>
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>
- 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>
sanitize-bookmarks.mjs accepted any JSON object and rewrote only "url" and
"title". Chrome's profile Bookmarks file keeps titles under "name" (plus
meta_info and a base64 sync_metadata blob), so it came out with every title
intact, passed the host-only leak check, and was written as "sanitized" —
the exact file a reporter whose import failed would attach.
- JSON dialects are recognised by shape (BookmarkMagic, Chrome profile,
Firefox backup); any other JSON is refused. Rewriting is default-deny: a
small tokenizer tracks the key of every string value and replaces all of
them except structural keys (types, ids, timestamps, root GUIDs), by span,
so layout and key order stay byte-identical.
- The backstop now reads the output's TEXT: for HTML it strips markup and
refuses on any word that is not a placeholder — independent of the
rewriting rules, unlike the old host-only check whose test shared its
blind spots. <DD class=…> notes, file: ICON_URIs and <H1>/<TITLE>
owner names are rewritten.
- Attribute values decode in one pass (CodeQL js/double-escaping), <DD>
bodies are found in linear time (Sonar S8786), the input is never
overwritten, size is checked before reading, and bytes are bytes.
- The 627-line file is split into scripts/sanitize/ modules; the
user-facing entry stays plain .mjs for reporters on any Node.
gen-fixture.mjs validates its flags (whole numbers >= 1, values required, no
unknown flags) and its loop visibly advances (Sonar S2189 blocker).
gen-icons.mjs says what is true: it is the icons' source of truth.
Every script now carries // @ts-check and tsconfig.scripts.json runs them
through the TS 7 tsc in `npm run check`; docs/10's size rule names .mjs.
Regenerated icons are byte-identical.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
docs/13 §6 stated as present-tense fact that "GitHub issues — templates route
bug reports with sample files", and docs/12 §5 carried the same as an unticked
box. Neither was true: .github/ held only FUNDING.yml, dependabot.yml and
workflows. Meanwhile the entire v1.0.x roadmap is "fixture + test per report",
which cannot happen if reports arrive without the file that broke.
Five issue forms plus a chooser, blank issues disabled. parser_report.yml is
the one that matters: it requires the sanitized sample, asks which browser
*version* produced the file, and asks explicitly for consent to commit the
sample as a GPL-3.0 fixture — it lives in a public repo forever, and nothing
previously asked.
scripts/sanitize-bookmarks.mjs makes "attach a sanitized sample" something a
reporter can actually do. It works by span replacement rather than by
reparsing, so every byte outside a replaced address or title is provably
untouched: BOM, doctype, line endings, tag and attribute case, quoting,
indentation and every timestamp survive, and so do the properties a parser
branches on — port, path depth, trailing slash, query-parameter count and
order, percent-escapes, HTML entities, and the distinctness of hosts that
dedupe depends on.
Its test asserts the promise rather than the implementation: for every fixture
in the repo, the sanitized file must detect as the same format, parse to the
same stats, warnings and topology — or fail with the same error code — and leak
no original hostname. Writing it immediately found three real defects: a data:
URL containing markup broke the title regex and left that bookmark's title
unsanitized; an & in an HREF came back as a bare &, silently repairing the
escaping of the file being reported; and Firefox's ICON_URI leaked a full
hostname past every other check. The last one is why URL-valued attributes are
now swept by value shape instead of by an enumerated list.
scripts/gen-fixture.mjs is the generator docs/11 §2 named, .gitignore has
always reserved a directory for, and the 2 s parse budget needed in order to be
measurable at all.
CONTRIBUTING.md collects the five-file ritual for turning a user's file into a
regression test, which was previously spread across CLAUDE.md, docs/04 and
docs/11 with no single entry point — including the .gitattributes rule that
stops EOL normalization destroying the bytes a bug depends on.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>