v0.0.6 — first LTS

First LTS. Backspace works, both AMO validator warnings are gone, and the two features that
were sitting one hook away are wired.

Install

1. Download chevalet_note-0.0.6.zip
2. about:debugging#/runtime/this-firefox → Load Temporary Add-on… → pick the .zip
3. Click the toolbar icon and grant access to a site
4. Alt + double-click on empty page space, or right-click → Add a note here

source-0.0.6.zip is the source archive for an AMO submission — see below.

The AMO warnings, fixed

data_collection_permissions did not exist until Firefox 140, and until 142 on Android, so
declaring a floor of 128 promised support that could not be delivered. The floor is now
140 desktop / 142 Android. Raising it beats dropping the declaration: "this add-on collects
no data", stated where the browser itself can show it, is the strongest line in the listing.

One logo, and it has presence now

The toolbar icon looked like a small stamp in an empty square, and the reason was measurable:
the old mark spanned 7..53 of a 64 box, so barely 72% of the frame carried ink, and its keyline
rendered at 0.4px at 16px.

Redrawn to fill 92% of the frame, nothing thinner than 3 units, marker strokes landing at
2.25px and 1.6px in the toolbar. The weight comes from the offset register shadow rather than a
fat black outline — which was the earlier criticism. The halftone and the tilt are gone: texture
at 128px, dirt at 16px.

logo-mark.svg is deleted. One logo, in the toolbar, the tab, the popup, the settings page,
the cabinet and the store listing. All nine sizes are rasterised from it by a script in a real
Firefox, so the PNGs cannot drift away from the SVG.

Settings, inside the cabinet

Every option now lives in the cabinet, in the cabinet's own idiom rather than as a form: manila
section tabs with a cut leading edge, ruled index-card paper, paper switches that slide,
segmented choices as strips of little tabs, palette swatches with the accent showing as a marker
stroke. Each control writes straight through — no Save button, because a Save button is a way to
lose work when you close the tab.

Six sections: Where · Closing · Look · Keeping · Backup · Keys. The Keys section documents
every shortcut, with S — open this note's settings as the first row.

Two gaps closed

Pasted and dropped images work. The storage was always there; the renderer never passed the
hook. They travel as bytes with a 10 MB ceiling and a decodable-type allowlist, and they are
painted into a canvas — a content script's <img src> answers to the page's CSP and would
silently fail on a strict site.

"Save as my default" does something. Held as a sparse diff, so adding a style field later
reaches every existing note instead of being frozen out. Changing it re-resolves every note in
every open tab, and each note keeps whatever it set deliberately.

Publishing

docs/PUBLISHING.md is new and covers the whole route: listed versus unlisted and why listed is
the answer (Firefox then updates it for everyone, silently), the pre-flight checks, prepared
listing copy, the screenshot list, the data-collection answers, a draft of the reviewer notes,
and the requirement that catches most first submissions — AMO needs the original source
whenever the shipped code is minified, which ours is. source-0.0.6.zip above is that
archive.

Still open

Spike R1 — whether a content script's beforeunload actually produces a dialog on tab close —
is unanswered, which is why the close-tab warning is described as best-effort. Honest either
way, so it does not block submission. It takes a minute now: make a note, type, close the tab.

ZIP import still reads and plans without writing. Export is complete.

414 tests, web-ext lint --warnings-as-errors at 0 errors / 0 warnings / 0 notices, and
Backspace re-verified deleting in a real Firefox 155 against the real note.