chore: 0.9.0

.github/workflows/accessibility.yml

@@ -28,7 +28,7 @@ jobs:
           node-version: 22
 
       # In your own repository this becomes:
-      #   uses: likeBloodMoon/eaa-kit@v0.7.0
+      #   uses: likeBloodMoon/eaa-kit@v0.9.0
       #
       # An exact release tag. There is deliberately no moving v0 tag to follow:
       # this is a 0.x package, the flags and the JSON contract can still move

CHANGELOG.md

@@ -9,7 +9,18 @@ move: the JSON report's `schemaVersion` and the baseline file's. Both are bumped
 a field is removed, renamed, or changes meaning — new fields may appear without one, so
 consumers must ignore what they do not recognise.
 
-## Unreleased — 0.9.0
+## 0.9.0 — 2026-09-24
+
+The first release since 0.7.0, and it carries 0.8.0 as well: 0.8.0 was tagged but never
+published, so its entry below is part of this release.
+
+Released with the citation check still open. The eight countries added in 0.8.0 and 0.9.0
+(Belgium, Czechia, Denmark, Finland, Ireland, Poland, Portugal, Sweden) ship with the
+`unverified` marker that `eaa-kit countries` and `docs/statement.md` show, and their
+templates cite the statute and the supervisor without article numbers or fines. Their
+citations were established from secondary sources and cross-checked against search
+excerpts from the official sites, which agree with every one of them. The check against
+the full primary text is still to be done, and the marker comes off where it is.
 
 ### Added
 
@@ -67,7 +78,11 @@ consumers must ignore what they do not recognise.
 - The baseline and review-record errors no longer put their fix in the message text. It
   moved to the error's `next` field, which the CLI prints under the message.
 
-## Unreleased — 0.8.0
+## 0.8.0 — not published
+
+Tagged on 2026-09-24, but the tag was on a commit where `package.json` still said 0.7.0,
+the release workflow stopped at its version check, and nothing reached npm. The tag was
+withdrawn and everything here shipped in 0.9.0.
 
 ### Added
 

README.md

@@ -10,7 +10,18 @@ the statute and supervisory body of **fifteen countries**: Austria, Belgium, Cze
 Denmark, Finland, France, Germany, Ireland, Italy, the Netherlands, Poland, Portugal,
 Spain, Sweden and Switzerland, each in its own language as well as English.
 
-0.7.0 makes a run cost what it should. A page that has not changed byte for byte is not
+0.9.0 needs no setup. `npx eaa-kit` on its own finds the site, audits it, writes an HTML
+report and says which command comes next. `init` fills itself in from what the built site
+states, and also writes a baseline and a GitHub Actions workflow tailored to the project.
+Every error a new user is likely to hit ends with the command to type next. A `--url` run
+checks where the address leads before it crawls: a redirect to another site is shown and
+needs a yes (or `--redirects follow`), and a sign-in wall stops the run instead of being
+audited as the site. `audit --watch` re-checks the build on every save, and eight countries
+join the statement. Their citations were established from secondary sources and are marked
+as such in `eaa-kit countries` and the docs until they are checked against the primary
+text.
+
+0.7.0 made a run cost what it should. A page that has not changed byte for byte is not
 audited again, and a run with nothing to re-audit never loads an engine at all: twenty
 pages go from ~2,520 ms to ~230 ms, which is about what starting the process costs. A
 reused result is never passed off as a fresh one — every report says how much was reused

ROADMAP.md

@@ -115,8 +115,12 @@ prevented.
 
 - `lint`, `typecheck`, `test` (with colour forced as well as without), `smoke` and the
   packaged-CLI run green across the CI matrix.
-- The citation check for 0.8.0's four countries and this release's five, recorded in the
-  changelog, before either version is tagged.
+- ~~The citation check for 0.8.0's four countries and this release's five, recorded in the
+  changelog, before either version is tagged.~~ **Changed at release:** 0.8.0 was never
+  published, and 0.9.0 shipped both with the check still open, the unverified marker on,
+  and the changelog saying so. The citations were cross-checked against search excerpts
+  from the official sites, which agree with all of them. The full check against the
+  primary text is now a 1.0 blocker.
 
 ## 0.8.0 — reach
 
@@ -221,7 +225,8 @@ look, would tell them it was clean.
 - `lint`, `typecheck`, `test`, `smoke` and the packaged-CLI run green across the CI matrix.
 - **Every citation in the four new countries' templates checked against the primary
   text**, and the checking recorded in the changelog: who checked it, against which
-  consolidated version. Until then 0.8.0 is not tagged.
+  consolidated version. Until then 0.8.0 is not tagged. (0.8.0 was not published; it
+  shipped as part of 0.9.0, with the check still open. See 0.9.0's *Done means*.)
 - `examples/` regenerated and drift-checked.
 - A changelog entry saying what was given up as well as what was added.
 

docs/integrations.md

@@ -250,7 +250,7 @@ jobs:
       - uses: actions/setup-node@v4
         with:
           node-version: 22
-      - uses: likeBloodMoon/eaa-kit@v0.7.0
+      - uses: likeBloodMoon/eaa-kit@v0.9.0
         with:
           install-command: npm ci
           build-command: npm run build

package.json

@@ -1,6 +1,6 @@
 {
   "name": "eaa-kit",
-  "version": "0.7.0",
+  "version": "0.9.0",
   "description": "WCAG 2.2 AA auditor and EU accessibility statement generator for fifteen countries (AT, BE, CH, CZ, DE, DK, ES, FI, FR, IE, IT, NL, PL, PT, SE). Audits a static build or a running site from the command line.",
   "type": "module",
   "license": "MIT",