ad085fb4ce
Every document in the tree audited against the source, the tracker and git
history, each finding then given to a second reader tasked with refuting it.
74 raised, 12 refuted, 57 applied. No code changed.
THE README DESCRIBED A SKELETON
Its Status table — the one place a claim about what is built is allowed to live
— still read "there is no usable app yet", with Not built against Room, the four
core screens, fertility and notifications, and No round run against QA. Five
batches had shipped and three QA rounds had run.
TWO DOCUMENTS WERE SILENTLY NEVER FIRING
architecture/README.md and design/README.md wrote Governs: as prose ("the Gradle
module graph", "the design tokens in core/designsystem"). Neither contains a
path token, so doc-triggers.py reduced them to globs matching nothing, and one
real glob apiece made them look path-governing rather than subject-governing —
the state the script's own header calls invisible. Editing a Room entity never
fired the document owning the migration table. Both now fire, proved by running
the script.
SECURITY.md CLAIMED FOUR UNBUILT PROTECTIONS
App lock listed among what works offline; biometric/PIN gating described as
protecting app launch; the incognito launcher as existing; Play Billing in the
third parties table without the "not yet integrated" marker its neighbours
carry. All are Batch 06/07 work.
The advertising boundary was overstated in SECURITY.md and the README alike:
both said the ads module declares no dependency and a guard proves it. There is
no ads module. The pre-declared ":core:ads" to emptySet() rule is stricter than
the sentence it replaced and matches nothing until Batch 07, which is why the
guard is proved by injection rather than trusted.
SMALLER, EACH A REAL TRAP
WORK_CYCLE.md pointed at docs/architecture/scripts/forgejo-issue.py, a template
path absent here — missed by doc-claims.sh, which reads backticked prose and not
fenced blocks. ClaudeReport.md's Round notes said "No rounds yet" after three
rounds because ClaudeQAPlan.md's after-a-round list never named that section;
the playbook is fixed first. The instrumented-test count was eight in three
places and is four. HISTORY.md said the repository had no code and that nothing
had been tried and dropped, when three approaches had.
DELIBERATELY UNCHANGED
ClaudeReport.md's last verified build SHA stays at
|
||
|---|---|---|
| .. | ||
| README.md | ||
| banner.webp | ||
| icon.webp | ||
| logo.webp | ||
README.md
Project images
Status: Current
Owner: _null
Last reviewed: 2026-08-18
Governs: docs/data/img/** — the three files and their sizes
Review trigger: A rebrand; any change to a required name, dimension or ceiling;
any change to what the consumer accepts.
Three files, all webp, all required, at exactly these names:
| File | Dimensions | Aspect | Typical weight |
|---|---|---|---|
icon.webp |
512 × 512 | 1:1 | 8–60 KB |
logo.webp |
1024 on the long edge | whatever the lockup is | 20–190 KB |
banner.webp |
2176 × 725 | 3:1 | 30–130 KB |
Not icon.ico. The consumer checks the file's magic bytes, not its name: a
.ico, or a PNG renamed to .webp, is refused with a 415 and the project falls
back to an initials tile. That signature check is what makes it safe to render
these inline, so it is not going to be relaxed.
512 KB is a hard ceiling per file, enforced in code — the size is read from the listing before the bytes are fetched, so an oversized asset is never downloaded and simply never appears. Nothing enforces the dimensions, which is why they are written down.
Making them
magick logo-source.png -resize 512x512 -quality 82 icon.webp
identify -format '%f %wx%h %b\n' *.webp # check before committing
Quality 80–85 suits a flat mark. If a file lands over ~200 KB it is usually a photographic banner that wants a lower quality rather than fewer pixels.
Why these numbers
The icon renders small — a 44 px tile in a list, 58 px on a project header — so 512 covers the densest display several times over; the reference project deliberately halved it from 1024. The banner spans a card about 760 px wide, so ~2176 covers it at 2×, and its 3:1 shape matters more than its width because the header crops to fill. The logo has no fixed frame, so only its long edge is specified.
Extra sizes and variants are welcome beside these — icon-512.webp,
logo-dark.webp. Only the three exact names are checked for.
No placeholders ship here. An empty file is the worst of the three states: a check that asks whether the path exists calls it present, and anything reading the bytes rejects it. Absent is honest, and the conformance check reports it as absent — which is what gets it filled in.
Why the requirement exists, and what reads it: ../README.md.