| Both sides previous revisionPrevious revisionNext revision | Previous revision |
| provenance:privacy:cookies [2026/09/10 16:44] – Full review log for all three focused passes with acceptances and rejections; record that the generic pass was not run. Authored by Claude karel.kubicek.claude | provenance:privacy:cookies [2026/09/17 07:23] (current) – Markup rendering sweep: wrap escapes, CLI flag typography, and heading quotes. Authored by Claude. karel.kubicek.claude |
|---|
| - **{[lin2024_browsing]}'s 28.50% unclassified.** Read out of Table 1 with its caption ("The total, mean, and median of cookie counts in each category identified by Cookie-Script across 255 websites"), because the extraction had the percentage without the instrument or the population. | - **{[lin2024_browsing]}'s 28.50% unclassified.** Read out of Table 1 with its caption ("The total, mean, and median of cookie counts in each category identified by Cookie-Script across 255 websites"), because the extraction had the percentage without the instrument or the population. |
| |
| ===== 6. What the ''[F]'' full-text probes say, and what they do not ===== | ===== 6. What the [F] full-text probes say, and what they do not ===== |
| |
| Denominator **5,869** readable files. A name match is a **mention** — it counts reference-list entries and related-work sentences — and is never added to an ''[E]'' count. Generic words (''entropy'', LLM names) are only counted **within 150 characters of the word "cookie"**, because unqualified they match password and DNS papers. | Denominator **5,869** readable files. A name match is a **mention** — it counts reference-list entries and related-work sentences — and is never added to an ''[E]'' count. Generic words (''entropy'', LLM names) are only counted **within 150 characters of the word "cookie"**, because unqualified they match password and DNS papers. |
| Checked before saving: the key does not exist in ''literature:bibliography'' (0 matches), the DOI does not exist (0 matches), and ''scripts/bib_dedup_scan.py'' reports no new A/B/C/D candidate pair involving it. The one pre-existing [C] pair the scan reports (''bratton2019_replication'' / ''sumner2014_exaggeration'') is unrelated to this run and untouched. | Checked before saving: the key does not exist in ''literature:bibliography'' (0 matches), the DOI does not exist (0 matches), and ''scripts/bib_dedup_scan.py'' reports no new A/B/C/D candidate pair involving it. The one pre-existing [C] pair the scan reports (''bratton2019_replication'' / ''sumner2014_exaggeration'') is unrelated to this run and untouched. |
| |
| Every other citekey on the page already existed. **20 distinct keys, 65 markers carrying 68 citekey instances, 136 rendered ''bibtex_citekey'' spans** (the plugin emits two per instance) and **20 references**. | Every other citekey on the page already existed. **20 distinct keys and 20 references.** The check that matters is the invariant, not a snapshot: the plugin emits **two ''bibtex_citekey'' spans per citekey //instance//** — not per marker, because three markers here are multi-key — so rendered spans must equal twice the number of comma-separated keys in the source's ''{[…]}'' markers, and distinct rendered references must equal distinct source keys. Both held at every save. A literal span count is not published here because it changes with every edit and would be stale within the hour. |
| |
| **The new key did not render until the bibliography's own cache was purged.** Immediately after saving, ''privacy:cookies'' showed 19 references instead of 20: ''cahn2016_cookies'' resolved to nothing, with no warning of any kind. ''?purge=true'' on ''privacy:cookies'' alone did not fix it; ''?purge=true'' on **''literature:bibliography''** did. Anyone adding a key should count rendered references against distinct source keys after purging both pages, not assume a save is enough. | **The new key did not render until the bibliography's own cache was purged.** Immediately after saving, ''privacy:cookies'' showed 19 references instead of 20: ''cahn2016_cookies'' resolved to nothing, with no warning of any kind. ''?purge=true'' on ''privacy:cookies'' alone did not fix it; ''?purge=true'' on **''literature:bibliography''** did. Anyone adding a key should count rendered references against distinct source keys after purging both pages, not assume a save is enough. |
| |
| <bibtex bibliography></bibtex> | <bibtex bibliography></bibtex> |
| | |
| | ===== Markup sweep, 2026-09-17 ===== |
| | |
| | Mechanical rendering repair only: a fresh live raw/XHTML export of 188 pages was checked with ''check_wrap.mjs'' and ''check_typography.mjs''. Affected plugin tags, CLI flags and heading markup were repaired; no figures or substantive prose were changed. The resulting source and rendered DOM were re-checked after saving. |
| |
