aa1d805e04
This repository is the one the template's README describes: 205 issues, zero
milestones, and severity labels spelled "P0 Critical" / "P1 High" / "P2 Medium",
which privacyllc.dev reports as NOT ADOPTED rather than as 87% complete.
Six markdown records described the same work and none pointed at the tracker.
Two of them said the project was in "Phase 5" while the code was at 0.9.3.
Migrated, then deleted in this commit:
FUTURE.md -> docs/history/BATCH_LEDGER.md (Archived). Its open
items were all already filed as issues, so nothing
needed migrating into the tracker
HISTORY.md -> docs/history/DEVELOPMENT_LOG.md, verbatim, 0 lines lost
DEVELOPMENT_LOG.md -> the same file, as a second labelled block. Not
interleaved: the changelog has three duplicated version
headings, so one date order would have implied more
than the record supports
PROJECT.md -> docs/planning/PROJECT_PLAN.md
STRUCTURE.md -> the agent pipeline into README.md; its versioning rules
retired
BUILD_SUMMARY.md -> BATCH_LEDGER.md. Its embedded SQL schema deliberately
NOT carried: it predated the UNIQUE constraint on
leads.email, and server/index.js owns the schema
SCRIPTS.md -> docs/TOOLS.md, corrected for the SSR + prerender build
Moved with history (git detects all four as renames):
OVERHAUL_PLAN.md, review.md, project-requirements.md, docs/zoho-setup.md
Kept because this project earned them: the five-agent pipeline, the design
system in OVERHAUL_PLAN.md (Status: Current, with a front-note saying which half
is history), the positioning argument in REDESIGN_REVIEW.md, and REQUIREMENTS.md
whole, including its change policy.
Deleted from the template because they do not apply, each said out loud in
DOC_TRUST_MAP.md: QA pass I (no money moves), the authorisation checklist group
and the session-token row (no accounts, no sessions), and one PRECAUTIONARY
paragraph in SECURITY.md about holding credentials on behalf of users — there
are none, and PROJECT_PLAN.md records accounts as out of scope. Pass H was kept
and rewritten: its authorisation half does not apply, its what-a-stranger-can-
reach half is the most exposed surface here.
Also removed: main.js, the old static site's hash router, referenced by nothing
and preserved in .drop/; and test-results/.last-run.json, a May Playwright
artifact reading {"status":"failed"} for a suite that does not exist.
The repository was made private on Forgejo before this commit. That is what let
the internal history be committed rather than exempted — null/fruit-fall is
already private and reports normally.
Two defects found on the way in and fixed here: zoho-setup.md told admins to
edit `server/zoho/`, a directory that has never existed in any commit (the
mapping is in server/index.js), and README.md's route list still advertised
/8x8, removed at 0.6.6, while omitting /privacy-policy.
Branding: icon.webp and logo.webp converted from this project's own marks in
assets/. banner.webp is absent and is filed as an issue rather than faked.
Verified: verify.sh 3/3, doc-claims 71 claimed paths all present, backup and a
first-ever restore of the live leads database (2 tables, 3 rows, under 1s).
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
|
||
|---|---|---|
| .. | ||
| README.md | ||
| 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 with this template. 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.