admin
9a55f0bbc7
The app is no longer the unmeasured view. Solved against the laptop frame, your Facebook Lite shot gives a visible window of x 349..1290 and your Chrome-mobile shot x 349..1291 -- the LITE APP CROPS EXACTLY LIKE SIGNED-IN MOBILE WEB, and both agree with the emulator's 351..1289. Their profile circle is at x 645..1021 from y 451, LOWER than the emulator's y 369, so that figure was pessimistic rather than wrong and the margin it bought was real. Five views measured now; the signed-out one is still the binding constraint. Cover C follows your draft: the wordmark big on top (88 px, was 44), a small gap, then the catchphrase. The catchphrase is ONE line, not the two you drew, and the measurement forces it: with the signed-out circle starting at y 232, a wordmark that size plus two catchphrase lines cannot both sit above it. Drawn as two lines it measured 392 sampled text pixels behind that circle -- "saját szabályaid" read "saját szab" there, which is the R-919 defect itself. Sizing the two lines to fit instead drops the capital to 25 px, the legibility floor. One line keeps the wordmark big, the capital at 34 px and every measured view clean: 0 text pixels behind any circle. The laptop moved right and shrank to 540 px to free the width; 64% of it is cropped or covered somewhere, which the build reports and which is what the decor layer is for.
documentation/backlog/
OPEN-ITEMS.md is the register of open work and the file to read first — it holds only what is
open, one row per item, every row with a category, a severity, a state and an owner (the layout is at its
top). CLOSED-ITEMS.md holds every finished row, compressed, with the commit that keeps its full text;
a row moves there in the same commit that closes it (scripts/closed_register_gate.py RULE 3).
ROADMAP.md holds intentions — features and spikes that do not exist yet — and ROADMAP-HISTORY.md
the shipped and killed ones. An R-n id is minted once and never reused.
The other files in this folder — verdict per file (2026-10-03 triage)
| File | Verdict |
|---|---|
SPEC-app-data-placement-2026-08-21.md |
KEEP — still referenced by open rows R-352 (placement still open) and R-368. |
SPEC-r85-phase4-5-2026-07-26.md |
KEEP as history — a spec of shipped work (R-85, agent v0.104.0). CONTEXT.md and architecture/00-capability-map.md link here. |
FOLLOWUP-nas-automount-guest-reboot-reassert.md |
FINISHED, kept in place — shipped in agent v0.84/v0.85 (CAMPAIGN-3). Not moved because CONTEXT.md, controller/network-storage-nas.md and felhom-controller/CONTEXT.md link to this path. |
Moved to documentation/archive/ on 2026-10-03 (finished; nothing open refers to them):
FIX-M18-NOTES.md— dump re-validation every 5 min. FIXED in controller v0.62.0 @f8afe5c(2026-06-14).FIX-M19-NOTES.md—deriveStackNamemisattribution edge. FIXED in controller v0.62.0 @6bab68b(2026-06-14).FOLLOWUP-golden-default-controller-tag.md— the golden baked a stale controller. FIXED in felhom-agent @ceca355(2026-07-03):build-golden.shv2.0.0 makes the controller tag a mandatory argument. Evidence:../audits/DRILL-golden-098-2026-07-03.md.DIAGNOSIS-f9-storage-registration-gap-2026-06-14.md— a read-only diagnosis of June 2026, superseded by the shipped F9 fixes (controllerCHANGELOG.mdcites it as history).
The archive also holds OPEN-ITEMS-narratives-2026-10-03.md: the campaign write-ups, rulings and ranking
paragraphs that sat between the register's tables until the triage, word for word.