Wiki Health Check — 2026-07-25
A third structured lint pass per CLAUDE.md §5.3, run about a month after the second pass (lint_report_2026-06-21b.md). Covers all 99 platform pages and 34 concept pages, plus (new this pass) the raw-source and JSONL layers directly, to answer §5.3’s “gap suggestions” question with an actual list rather than a repeated number.
0. Scope check — confirms this pass’s starting assumption
Checked filesystem modification times for every file under pages/ against the second pass’s 2026-06-21 date. Result: zero platform or concept pages changed since the last lint pass. The only modifications since then are CLAUDE.md and pages/log.md, both from this session’s earlier §9.2 schema addition (documenting the companion website’s multi-critic ratings panel convention). This means every PASS result from the second lint report — orphans, staleness, threshold, path/anchor links — still holds by construction, not by assumption; re-verified below rather than re-run from scratch where the underlying data can’t have changed.
1. Regression check on the 2026-07-25 CLAUDE.md edit — PASS
This is the one genuinely new piece of wiki-layer content since the last pass, so it gets the scrutiny the second lint report gave the risk-score restructuring. Checked:
- Every
§9.2and§2cross-reference added toCLAUDE.mdresolves to a section that actually exists in the file (no dangling§11or similar — a draft reference to a nonexistent “companion website section” was considered and correctly not included in the final edit). pages/log.md’s new top entry follows the append-only format (## [YYYY-MM-DD HH:MM] action | description) and sits above, not overwriting, the prior top entry.
Zero issues found.
2. Orphan, staleness, path/anchor-link, and threshold checks — PASS (re-confirmed, not re-run)
Per §0, these are unchanged from lint_report_2026-06-21b.md: 0 orphans, 0 mismatched “Latest Date” entries, 0 broken links, 23-of-30 keywords past the 3-platform threshold with all 23 having a concept page.
3. Carried-forward open items — both still open, unchanged
UpScrolled/Upscrolledcasing inconsistency (first flagged 2026-06-21): the page’s H1 andindex.md’s references still say “UpScrolled”; the filename and**Source:**field still say “Upscrolled.” Still cosmetic, still unfixed, still low priority.- 6 files with trailing whitespace inside verbatim block quotes (first flagged 2026-06-21b):
Facebook_Terms_of_Service.md,Instagram_Other.md,Instagram_Privacy_Policy.md,Reddit_Terms_of_Service.md,Spotify_Terms_of_Service.md,YouTube_Privacy_Policy.md. Still correctly not auto-fixed — altering whitespace inside a quoted clause is a content change requiring raw-source verification first, per CLAUDE.md’s never-paraphrase rule, not a safe mechanical cleanup.
4. Gap suggestions — 1 SUBSTANTIAL FINDING (new this pass)
CLAUDE.md §5.3 asks “what platforms or document types are missing?” Both prior lint passes answered this with a number (“53 remaining backlog,” cited from methodology.md) but never actually enumerated or characterized it. This pass did:
Finding A — the “53 remaining” backlog is not a backlog. Diffed all 96 sources/jsonl/*.jsonl filenames against pages/platforms/*.md: 53 files have no corresponding page, confirming the existing count. But checking each of those 53 files directly: all 53 are exactly 0 bytes. There is no partially-processed or overlooked JSONL data sitting uningested — every JSONL file that contains any records has already been ingested into a wiki page. methodology.md’s “53 remaining” framing is numerically correct but reads as “work remaining,” when the accurate description is “53 files tracked by the pipeline that currently contain nothing to ingest.”
Finding B — two platforms are entirely absent from the wiki despite having real, uningested raw source text. Cross-checking which platforms have zero presence anywhere in index.md (not just a missing document type, a missing platform) found exactly two:
- Bluesky —
sources/raw/Bluesky/has 29 dated captures across all three tracked document types (9 Community Guidelines, 9 Privacy Policy, 11 Terms of Service, spanning 2024-03-14 to 2025-10-23). Zero JSONL records, zero wiki presence. - Expedia —
sources/raw/Expedia/has 1 dated capture (Privacy Policy, 2022-10-19). Zero JSONL records, zero wiki presence.
Every other platform in sources/raw/ already has at least one ingested page — these two are the exception, not a sample of a larger unnoticed set. Since neither has JSONL data to drive a standard §5.1 ingest, the applicable path is the same one already used for the entire GenGA dataset: direct LLM reading of the raw captures, tagging keywords manually per CLAUDE.md’s GenGA precedent, disclosed as such on the resulting page.
This is, by dated-capture count, a bigger single gap than most already-ingested platforms — Bluesky’s 29 captures exceed e.g. BeReal’s 2 or Moltbook’s 1 — and Bluesky specifically is a live, currently-relevant decentralized social platform directly inside this wiki’s stated scope. Recommended as the highest-value next ingest target.
5. Fix applied
Added a third footnote to index.md’s Platform Overview table, matching the existing LINE/Parler and LinkedIn footnote convention, disclosing Finding A and B and linking to this report. No other wiki content was rewritten — the opening stats line (“96 PGAv2… source files tracked overall”) is numerically accurate as written and was left alone; the footnote carries the nuance, consistent with how this wiki has handled similar caveats before rather than editing the headline claim itself.
Summary
| Check | Result |
|---|---|
| CLAUDE.md §9.2 edit regression | 0 issues |
| Orphans / staleness / links / threshold | 0 issues (re-confirmed unchanged since 06-21b) |
| UpScrolled/Upscrolled naming | Still open, unchanged |
| Trailing whitespace in quotes (6 files) | Still open, unchanged, correctly not auto-fixed |
| JSONL backlog re-characterization | 53-of-53 un-ingested files confirmed empty — no real backlog |
| Missing platforms | 2 found: Bluesky (29 raw captures), Expedia (1 raw capture) — both currently absent from the wiki entirely |
The headline result of this pass isn’t a bug fix — it’s a scope correction. The wiki has been describing its own completeness in terms of a JSONL backlog number that, on inspection, is entirely empty, while two platforms with genuine, substantial raw source text sat outside that framing altogether and so were never flagged as missing by either prior pass. Neither prior lint report checked “is every platform folder in sources/raw/ represented,” only “does every ingested thing link correctly” — this pass adds that check.
See also: lint_report_2026-06-21.md · lint_report_2026-06-21b.md · methodology.md