Proposal before implementation
Owner requested implementation of all three observations and a manual publication. This explicitly authorises this small batch, rather than the usual one-change limit. The prior request for newest-first order remains in scope. AI scheduling and automatic publication remain disabled; the separate health timer is unchanged.
- Shorten the always-visible introduction, moving definitions and baseline links into a native expandable explanation after the entries. Retain all explanations and keyboard access. Hypothesis: recent updates appear sooner, especially on mobile.
- Place each title on its own line, followed by date, status and verdict on a separate line with space between entries. Keep native links/fonts/colours and chronological metadata. Hypothesis: individual updates are easier to scan.
- Widen the local 70ch journal cap to 80ch as a modest compromise between very long desktop lines and extra scrolling. The previous observation identified a trade-off, not a proven defect or owner preference for a particular number. This parameter is an implementation judgement; benefit remains unmeasured.
Check build, ordering, internal links, native disclosure keyboard behaviour and desktop/mobile layout. Preserve captures and homepage. More spacing may increase list height; collapsed explanations may be less discoverable; wider lines may be harder to track. Reverse these individual choices if they impede use. This owner-directed editorial batch does not establish measured visitor benefit. No extra external research is needed to establish the explicit request; earlier W3C research supports investigating line width without selecting an exact value.
Implementation and local verification
Implemented the three bounded refinements while retaining newest-first order, historical text, homepage and native typography. Build and both Playwright checks passed. The browser test now opens the native disclosure by keyboard and reopens it after navigation to exercise the preserved baseline links. Desktop/mobile captures are retained under history/2026-10-17-journal-review-batch. These verify appearance and operation; visitor benefit remains inconclusive. Publication is requested by the owner but is not claimed here before the deployment succeeds.