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>
This commit is contained in:
poli0981andClaude Fable 5.2 committed 2026-11-10 11:29:46 +07:00
1 parent d61318aed7
commit 47206cc6c2
3 files changed
+19 -12

No files matched your search

+9 -5
View File
@@ -9,10 +9,9 @@ This file is the entry point; the `docs/` suite is the specification.
> **BookmarkMagic is published on the Chrome Web Store and has real users**
> (v1.0.0 live by 2026-08-03; v1.0.1 live, confirmed on the listing
> 2026-10-28; v1.1.0 live, confirmed on the listing 2026-11-06; v1.2.0 live,
> confirmed on the listing 2026-11-10; v1.2.1 prepared 2026-11-10, ⚠️ not yet
> submitted).
> Phases 0–8 are complete and Phase 9 (v1.2.1) is prepared; the project is in
> **maintenance**.
> confirmed on the listing 2026-11-10; v1.2.1 released on GitHub 2026-11-10,
> ⚠️ not yet submitted).
> Phases 0–9 are complete; the project is in **maintenance**.
> That changes the rules of the game:
>
> - Every change now reaches installed users through a store review. It needs a
@@ -194,7 +193,12 @@ goal is WCAG 2.2 AA **as a goal** — never write "conforms" or "compliant"
without an audit to cite. The review found the first draft of the statement
overclaiming in nine places ("every clickable target", "nothing times out"):
check each sentence of it against the source, not against the intention.
**Exit:** v1.2.1 prepared 2026-11-10. Human-only ⚠️: the `11 §5` pass with the
A third: **code moved out of a component starts counting.** SonarCloud's
new-code gate (80 %) failed the first push because the live-sync wiring left
`EditTab` for a `.ts` module with no test. Extracting to stay under a size
limit is half the job; the test is the other half.
**Exit:** ✔ v1.2.1 tagged and released 2026-11-10 (signed tag on `d61318a`,
checksum-verified zip). Human-only ⚠️: the `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+↑/↓, the zip upload, and the native
review of the two new strings.
+9 -6
View File
@@ -26,16 +26,18 @@
> `e2f36bc`); the listing was observed showing **version 1.2.0** (`Updated:
> November 7, 2026`, 5 languages) on 2026-11-10. Installed users are on 1.2.0.
>
> **v1.2.1 — accessibility — is prepared, not yet released.** An accessibility
> statement (`/ACCESSIBILITY.md`) and the fixes an audit found (`06 §5`).
> ⚠️ It needs the owner's manual pass, including the 1.2.0 → 1.2.1 upgrade
> over an existing profile, and a hand upload to the store (`13 §1b`).
> **v1.2.1 — accessibility — is RELEASED on GitHub, not yet on the store.**
> Tagged and released 2026-11-10 (signed tag on `d61318a`, checksum-verified
> zip): an accessibility statement (`/ACCESSIBILITY.md`) and the fixes an
> audit found (`06 §5`). ⚠️ It still needs the owner's manual pass, including
> the 1.2.0 → 1.2.1 upgrade over an existing profile, and a hand upload to
> the store (`13 §1b`); until it clears review, installed users stay on 1.2.0.
>
> The project is now in **maintenance**, not construction: every change from
> here reaches installed users through a store review, so it needs a version
> bump, a CHANGELOG entry and an update submission (`13 §1b`). Sequencing lives
> in `/CLAUDE.md`; what is still open is in §10 below.
> **Doc suite version:** 1.10 (2026-11-10 — v1.2.0 live; v1.2.1 accessibility)
> **Doc suite version:** 1.11 (2026-11-10 — v1.2.1 released on GitHub)
---
@@ -254,7 +256,8 @@ Derived identifiers (canonical across docs and code):
### v1.2.1 (added 2026-11-10)
15. ⚠️ **v1.2.1 to the store.** The usual `11 §5` pass plus the **1.2.0 →
15. ⚠️ **v1.2.1 to the store.** The GitHub Release exists and is verified
(`15`'s progress table). The usual `11 §5` pass plus the **1.2.0 →
1.2.1 upgrade over an existing profile**, then the Release zip uploaded in
the dashboard. No listing change: a patch (`13 §5`).
16. ⚠️ **The accessibility checks no script can run** (`11 §5`): a Windows
+1 -1
View File
@@ -34,7 +34,7 @@ Build-phase breakdown lives in `CLAUDE.md` (single source for sequencing).
| **v1.2.0 submitted** | ✔ by 2026-11-07 | uploaded to the CWS dashboard by hand, with the 简体中文 and Română listing languages (`13 §1b` step 6, `13 §4`) |
| **v1.2.0 published** | ✔ observed 2026-11-10 | the listing shows version 1.2.0 (`Updated: November 7, 2026`), 3 users, "5 languages" — English, Tiếng Việt, română, 中文(中国), 日本語. ⚠️ As for 1.0.1 and 1.1.0, `13 §1b` step 10 (clean-profile install of the published build + upgrade re-check) has no recorded result |
| 9 — v1.2.1 accessibility | ✔ 2026-11-10 | `ACCESSIBILITY.md` and its intake (issue form, PR checklist, `accessibility@`); the defects an audit of `src/` found that a keyboard-and-Narrator pass had not — an invisible focus ring on the theme control, no forced-colours support, drag-only reordering (Alt+↑/↓), focus dropped on `<body>` in three places, targets under 24 px; dependency sync after Dependabot #31/#32/#35/#36 (`06 §5`) |
| **v1.2.1 released** | ⚠️ pending | signed tag + GitHub Release once the PR is merged |
| **v1.2.1 released** | ✔ 2026-11-10 | PR #37, merged at the head that was reviewed. Signed tag on `d61318a`, GitHub Release with a `sha256sum -c`-verified zip (`4975b5df…ca13254`, 106 290 bytes). Its manifest differs from 1.2.0's only in `version`, and the file inventory is the same. SonarCloud's new-code gate failed the first push at 73.6 % — the live-sync wiring moved out of `EditTab` had no test — and passed once it had one. `announce` and store publish skipped (variables unset) |
| **v1.2.1 submitted** | ⚠️ pending | owner: the `11 §5` pass incl. the **1.2.0 → 1.2.1 upgrade over an existing profile**, a Windows contrast theme and a screen-reader pass over Alt+↑/↓, then the zip upload (`13 §1b`) |
**Verified on real browsers 2026-07-25:** Chrome and Brave, unpacked build.