# The extracted text behind `../adrio-designations.md`

**Why this directory exists.** `adversarial-reviewer` (2026-08-28, C10): the
`sha256` digests in that file cover the **raw HTML**, but Finding 4's term counts
were taken from **extracted text produced by an uncommitted script** — so the
counts were unverifiable by construction (R14) even though the digests were not.

`extract.mjs` is that script. `*.txt` are its outputs, which are what every
count in `../adrio-designations.md` was run against.

## Reproducing

```sh
curl -sSL -o <slug>.html "https://adr-ontario.ca/<slug>/"
node extract.mjs <slug>.html > <slug>.txt
```

The five slugs are listed in the provenance table of `../adrio-designations.md`,
which also carries each file's raw-HTML byte count and `sha256`.

**Expect small differences in the character totals if you re-implement the
extraction.** Both review agents reproduced every digest, every byte count and
every term count exactly; one got 1924 / 2806 / 4121 / 3510 / 2496 characters
against this script's 1932 / 2814 / 4151 / 3524 / 2504, because tag-stripping
inserts whitespace differently. **The term counts are the finding; the character
totals are only a size indicator.**

⚠️ **The digests are valid until ADRIO's next WordPress plugin update.** The
served HTML carries 17 `?ver=` strings that are static plugin versions today
(`?ver=1.3.12`, `?ver=2.3.2`, …) — which is *why* these pages hash reproducibly
where the LAT pages could not. Those strings will move when ADRIO updates a
plugin. **A future digest mismatch is most likely a plugin bump, not tampering
and not a changed designation name** — re-run the term counts before concluding
anything from a mismatch.