docs: record the v1.0.0 release and what is still open
Status header, the docs/15 progress table and the docs/00 §10 manual list now say where the project actually is: all six phases done, v1.0.0 tagged and released, submitted to the Chrome Web Store and in review. §10 gains two items that were being carried in commit messages and memory rather than anywhere a reader would find them: - `npm run dev:firefox` is untested against the dependency overrides. Four of them sit under web-ext-run and no gate exercises that script. Firefox is a v1.0 non-goal so it blocks nothing, but nobody should assume it works. - The 2 s parse budget is unmeasured on a real browser. The recorded 2869 ms is a jsdom figure and settles nothing either way. The decision log gains the overrides rationale and why the release announcement is continue-on-error. The review-habit note is updated with phase 4 and 5 (19-of-33 and 8-of-20 confirmed), plus the two patterns this build kept demonstrating: the worst findings were in work added earlier in the same branch, and three defects reached main that no automated gate could have caught — a missing space, a glyph that reads as a letter, and a permission grant that failed CI at startup with no jobs and no log. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
2 files changed
+43
-13
No files matched your search
@@ -5,11 +5,12 @@
|
||||
> **Owner:** poli0981 (GitHub) / SkullMute
|
||||
> **Repo:** `poli0981/bookmarkmagic` ✔
|
||||
> **License:** GPL-3.0-or-later
|
||||
> **Status:** In development — **Phases 0–4 complete** (scaffold, core library,
|
||||
> browser layer + import, export + edit, and i18n/theming/Settings/About/Legal
|
||||
> Gate). Verified working on real Chrome and Brave, 2026-07-25. Next: Phase 5
|
||||
> (hardening + release prep). Sequencing lives in `/CLAUDE.md`.
|
||||
> **Doc suite version:** 1.3 (2026-07-26 — Phase 4 reconciliation)
|
||||
> **Status:** **v1.0.0 released and submitted to the Chrome Web Store**
|
||||
> (2026-07-26) — all six build phases complete, awaiting store review. Signed
|
||||
> tag `v1.0.0`, GitHub Release with a checksum-verified zip. Verified working on
|
||||
> real Chrome and Brave. Sequencing lives in `/CLAUDE.md`; what is still open is
|
||||
> in §10 below.
|
||||
> **Doc suite version:** 1.4 (2026-07-26 — v1.0.0 release)
|
||||
|
||||
---
|
||||
|
||||
@@ -127,9 +128,21 @@ Derived identifiers (canonical across docs and code):
|
||||
4. ✔ Donate URLs resolved from `.github/FUNDING.yml` (`14 §5`).
|
||||
✔ Contact email filled in and confirmed live: `contact@poli0981.dev`
|
||||
(`legal/PRIVACY.md`), alongside the GitHub Issues link.
|
||||
5. Chrome Web Store: developer account already paid ✔ — create the item,
|
||||
fill the Privacy tab per `08_MV3_COMPLIANCE.md`.
|
||||
6. Repo secrets + settings per `12 §5` (incl. disabling CodeQL "Default setup").
|
||||
5. Chrome Web Store: developer account paid ✔, item created and **submitted
|
||||
2026-07-26 — in review**. Listing copy and the Privacy tab answers come from
|
||||
`13 §3` and `08 §5`. **Still open:** the promo images, and the store URL for
|
||||
the README once the listing is public.
|
||||
6. Repo secrets + settings per `12 §5`. ✔ CodeQL "Default setup" is already
|
||||
disabled (the advanced workflow uploads SARIF cleanly). **Still open, both
|
||||
optional:** the `DISCORD_*` webhooks — without them the announce job is
|
||||
skipped rather than fatal — and the four `CHROME_*` secrets, which are only
|
||||
needed if `CWS_AUTOPUBLISH` is ever set to `true` for v1.1+.
|
||||
7. **Untested:** `npm run dev:firefox` against the `overrides` block in
|
||||
`09 §3.1`. Four of those overrides sit under `web-ext-run` and no gate
|
||||
exercises that script. Firefox is a v1.0 non-goal (§7), so this blocks
|
||||
nothing — but do not assume it works.
|
||||
8. **Unmeasured:** the 2 s parse budget on a real browser (`11 §6`). The
|
||||
recorded 2869 ms is a jsdom figure and settles nothing.
|
||||
|
||||
## 11. Reading order
|
||||
|
||||
|
||||
+22
-5
@@ -17,7 +17,8 @@ Build-phase breakdown lives in `CLAUDE.md` (single source for sequencing).
|
||||
| 2 — Browser layer + #import | ✔ 2026-07-25 | adapter, write queue, stores, full import flow incl. forced backup |
|
||||
| 3 — #export + #edit | ✔ 2026-07-25 | tri-state picker, tree CRUD, search, duplicates, DnD + keyboard parity |
|
||||
| 4 — i18n, theming, Settings, About, Legal Gate | ✔ 2026-07-26 | switcher + theme controls, six-row `#settings`, `#about`, first-run gate; Intl retrofit; store-backed Toast |
|
||||
| 5 — Hardening + release prep | next | CI stubs per `12 §2`, CHANGELOG, README, full QA, `wxt zip` clean install |
|
||||
| 5 — Hardening + release prep | ✔ 2026-07-26 | contrast tokens + a test that enforces them, `EditTab` split under the hard limit, CHANGELOG + README, four CI callers, T1–T8 pass, clean-room `wxt zip` |
|
||||
| **v1.0.0 released** | ✔ 2026-07-26 | signed tag, GitHub Release with a `sha256sum -c`-verified zip, submitted to the Chrome Web Store — **in review** |
|
||||
|
||||
**Verified on real browsers 2026-07-25:** Chrome and Brave, unpacked build.
|
||||
Until that point every phase had been tested only against a hand-rolled
|
||||
@@ -34,10 +35,24 @@ the path the `$state`-proxy `DataCloneError` would have broken; and the Phase
|
||||
2–3 import/export/edit flows still working after Phase 4 touched their tabs and
|
||||
the settings store.
|
||||
|
||||
Each of phases 1–4 was adversarially reviewed after implementation and each
|
||||
review found real defects (7, 13 and 14 in phases 1–3) — several in the paths
|
||||
that delete bookmarks. Budget that review into the remaining phases; a green
|
||||
test run has not once meant "done" on this project.
|
||||
Every phase was adversarially reviewed after implementation and **every review
|
||||
found real defects** — 7, 13 and 14 in phases 1–3, 19-of-33-filed in phase 4,
|
||||
8-of-20 in phase 5 — several in the paths that delete bookmarks. Budget that
|
||||
review into any future work; a green test run has not once meant "done" on this
|
||||
project.
|
||||
|
||||
Phase 5's own lesson is worth keeping: its three worst findings were defects in
|
||||
work added **earlier in the same branch** — a release workflow that would have
|
||||
failed on the first tag, a contrast test blind to its own bypass (`opacity` on
|
||||
text, which a token-level check cannot see), and a README claiming a test
|
||||
asserted the *built* manifest when it only read the config source. Review new
|
||||
work as hard as old work.
|
||||
|
||||
And three defects reached `main` that no automated gate could ever have caught,
|
||||
all found by a human looking at the running extension or at a real CI run: the
|
||||
footer's missing space, a moon glyph that renders as a capital "C", and a
|
||||
reusable-workflow permission grant that produced a `startup_failure` with no
|
||||
jobs and no log.
|
||||
|
||||
Phase 4's own review filed 33 findings across six lenses; 19 survived
|
||||
adversarial verification. The most serious was a first-run dead-end: the gate
|
||||
@@ -133,6 +148,8 @@ attestation resolver, deadlocking it until reload.
|
||||
| 2026-07-26 | The gate's acceptance checkbox deliberately resets if the user navigates away and back — an un-submitted legal affirmation is not worth persisting | 14 §2 |
|
||||
| 2026-07-26 | Both entrypoints await settings (Manager also legal) **before** `mount()`, trading a blank frame for no locale/theme/gate flicker | 02 §2 |
|
||||
| 2026-07-26 | **Known limitation:** two open Manager tabs do not sync settings or acceptance to each other; last write wins. No `storage.onChanged` listener in v1 | 03 §4 |
|
||||
| 2026-07-26 | Transitive dev-dep CVEs fixed with a `package.json` `overrides` block rather than by waiting on parents — every parent pinned a vulnerable range, which is why Dependabot's own PRs all failed | 09 §3.1 |
|
||||
| 2026-07-26 | The release announcement is `continue-on-error`. A missing Discord webhook made the real v1.0.0 run red on a release whose zip and checksums had published correctly; a red run on a good release trains you to ignore the colour | 12 §2.3 |
|
||||
| 2026-07-26 | Gate-blocked tabs stay **clickable**; what blocks a route is the gate replacing the tab body, not an inert button. Disabling them removed the only in-app path back to the accept UI | 06 §3 |
|
||||
| 2026-07-26 | Failure UI shows the localized sentence and puts the raw browser error in a separate detail block — `detail ?? t(key)` made every translation dead code | 02 §7 |
|
||||
| 2026-07-26 | `--accent-fg` is redefined in the dark blocks alongside `--accent`; white on the lightened violet measured 3.67:1 | 06 §5 |
|
||||
|
||||
Reference in new issue
Block a user