Updated just now.
2026-09-05 — A redesign of the Extras screen in the family app had a fault where opening its web address directly showed the old ungrouped layout: the new two-column arrangement only appeared after the reader clicked one of the section buttons at the top. The cause was that the cards on the page are filled in by background data feeds, so the first attempt to arrange them found nothing there yet, and a feed that had already finished before the arranging code ran never triggered a second attempt. It now retries on a short timer for up to ten seconds and stops as soon as the arrangement succeeds. Confirmed on a cold load with no clicking at all, checked three times over fourteen seconds. One separate fault remains open and is not being written up as finished: the two columns stop short of the bottom of the left-hand navigation rail, leaving a band of empty space, and nine ways of fixing that are already recorded as measured dead ends.
2026-09-05 — A redesign of the Extras screen in the family app had four of its build steps never actually reach the live site. The published page was loading version five of that redesign's stylesheet and script while the build was on version eleven, because publishes made from other working branches reverted the page that loads them, three separate times. That means the desktop layout of the screen was being judged against a page that did not contain it, which is why those measurements kept disagreeing with each other. The redesign is now re-landed and confirmed live at version twelve: the desktop screen no longer scrolls and each section is drawn inside one fixed frame with its content in two columns. One fault is still open and is deliberately not being written up as finished. The columns stop short of the bottom of the app's left-hand navigation rail, leaving a visible band of empty space at the foot of the screen. Nine ways of fixing that have now been tried and measured as dead ends, including two applied directly to the element in a live browser, and every one is written down so the next attempt does not repeat them.
2026-09-05 — The desktop layout of the family app's Extras screen no longer scrolls. The screen holds four section panels in its markup: Beach and Cenote, Family Vault, Transcribe, and an older Meditation panel that the new design keeps hidden, so a person sees three. Each panel is now drawn inside a single fixed frame the height of the browser window, with its content in two columns and the long lists scrolling inside their own cards rather than stretching the page. Three faults were found and fixed while doing this, one of which had made all four of those panels render at once and divide the available height between them instead of showing only the chosen one. One fault remains and is deliberately not being written up as finished: the two columns stop short of the bottom of the app's left-hand navigation rail, leaving a visible band of empty space at the foot of the screen.
2026-09-05 — The desktop layout of the family app's Extras screen no longer scrolls: each section is drawn inside a single fixed frame the height of the window, with the content sitting in two columns and the long lists scrolling inside their own cards. Three faults were found and fixed along the way, including a rule that made all four sections render at once and split the space between them. One fault remains and is not yet fixed: the two columns stop short of the bottom of the menu beside them, leaving a band of empty space, because the section box is not stretching to fill the area it sits in.
2026-09-05 — The Pearl skin for the family app's Extras screen is now on the main branch rather than a side branch, and is live at family.heroesandsidekicks.io behind the skin=pearl flag. This mattered because the site is published from several working branches at once and whichever publishes last wins: twice on the same day another branch's publish quietly removed the two lines that load the new design, leaving the files reachable but unused and the screen looking untouched. Both times it was caught by reading the actually-served page rather than trusting the earlier check. Landing the work on the shared branch means any future publish from any branch carries it.
2026-09-05 — The Transcribe section of the family app's Extras screen now renders in the Pearl design on the live site at family.heroesandsidekicks.io behind the skin=pearl flag. There is a card for pasting video links with a Grab and transcribe button in the Mauve accent, a card for dropping in a recording, and a list of finished transcripts that scrolls inside its own card, each row keeping its working Download link. Underneath sit the coach profile chips, styled in ink rather than the accent. The names of the transcripts are never read or copied.
2026-09-05 — The Family Vault section of the family app's Extras screen now renders in the Pearl design on the live site at family.heroesandsidekicks.io behind the skin=pearl flag. The send form is a glass card holding two labelled fields, a note box, a drop zone for files and a Save note button in the Mauve accent; below it the list of recently filed documents scrolls inside its own card, headed by a count of how many files are there. The two dropdowns are the app's own native controls, restyled rather than replaced, so the page's existing script still reads them unchanged. The names of the filed documents are never read or copied.
2026-09-05 — The family app's Extras screen now renders its Beach & Cenote section in the Pearl design on the live site at family.heroesandsidekicks.io behind the ?skin=pearl flag. The swim report is the one dark card, with the best beach's name in the Mauve accent; the beaches and cenotes lists are two glass cards whose rows scroll inside them. All 26 spot tiles and all 52 map and conditions links still work, because the existing page elements were regrouped and restyled rather than rebuilt, leaving the app's own extras script untouched. Without the flag the screen is unchanged.
⚠️ claimed done with only 1 of the required 2 independent verifications — shown as in progress, not done
Definition of done: the relevant item prints the relevant item
Proof: the relevant item (CREATED BY STEP 4)
Verified: 2026-09-06 — prints the required line VERBATIM, plus the end-to-end proof added on 2026-09-06 (the relevant item), so the check is now known to be able to FAIL, not merely to pass. Not 100%: this step's gate is "STEP 3 is signed", and Beach & Cenote is refused pending the governed map edit.
Definition of done: links + the relevant record + contract-check updated in an hour the Shopping lane does not hold; parity PASS; fence 0 with the flag off (all four tabs) and on
Proof: the relevant item prints PASS; the check's the relevant item prints 0
Verified: 2026-09-06 — the relevant item prints the relevant item. · 2026-09-06 — parity the relevant item ✓. 🔴 the relevant item prints the relevant item, and the changed key is the relevant item — ANOTHER LANE'S SURFACE, carrying Pearl's own ink (the relevant item) while THIS lane's flag is off. the relevant item is correctly scoped to the relevant item, so the un-skinned app has drifted from the fence baseline rather than this lane leaking. NOT re-baselined: re-baselining is how a fence stops being a fence. Handed to the To-Do lane.
⚠️ claimed done with only 1 of the required 2 independent verifications — shown as in progress, not done
Definition of done: header anchors at 0 at both viewports; the relevant item
Proof: the check's the relevant item and the relevant item
Verified: 2026-09-06 — the relevant item prints the relevant item; the full the relevant item run carries ZERO header mismatches and zero unmeasured header anchors at both viewports.
⚠️ claimed done with only 1 of the required 2 independent verifications — shown as in progress, not done
Definition of done: beach anchors at 0; the relevant item
Proof: the check's the relevant item and the relevant item
Verified: 2026-09-05 (100%, measured on the deployed URL signed in as nick; contract-check 542 PASS with the 22 pre-existing FAIL; asset-version parity 12 passed 0 failed)
⚠️ claimed done with only 1 of the required 2 independent verifications — shown as in progress, not done
Definition of done: vault anchors at 0; the relevant item; no file name in evidence
Proof: the check's the relevant item and the relevant item
Verified: 2026-09-05 (100%, measured on the deployed URL signed in as nick)
⚠️ claimed done but no VERIFIED line names a real browser drive-through — a UI-facing step needs one, not an API call standing in for it
Definition of done: transcribe anchors at 0; the drive lines ✓ (or the recorded NOT MEASURABLE state for a real submit)
Proof: the check's the relevant item and the relevant item
Verified: 2026-09-05 (100%, measured on the deployed URL signed in as nick) · 2026-09-05 (100%, measured on the deployed URL signed in as nick, after landing on main)
⚠️ claimed done but no VERIFIED line names a real browser drive-through — a UI-facing step needs one, not an API call standing in for it
Definition of done: the relevant item, N read from the ground-truth file (17 on the approval-day source)
Proof: the check's the relevant item
Verified: 2026-09-05 (70%, measured on the deployed URL signed in as nick; three defects found and fixed this pass, one remaining and named) · 2026-09-05 (70%, measured on the deployed URL signed in as nick) · 2026-09-05 (70%, measured at stylesheet version 12 on the deployed URL signed in as nick) · 2026-09-05 (75%, measured at script version 13 on the deployed URL signed in as nick) · 2026-09-06 (100%, measured on the deployed URL signed in as nick at css v40 / js v37) — the relevant item on all three sections AND the cold load, with the relevant item, which is EXACTLY this step's stated bar. ⚠️ Correcting a reading made earlier the same night: Vault measuring 1 was treated as a shortfall against a committed the relevant item showing 2, and the tool's settle was tuned chasing that 2. THIS step's definition says 1, and 42 seconds of direct observation showed the section holds exactly ONE list, wrapped the instant it exists, nothing ever left unwrapped. The plan's bar was right; the stale evidence file was the anomaly. · 2026-09-06 — the relevant item (10 unique strings × 5 containers). 🔴 THE DEFINITION POINTS AT A NUMBER ITS NAMED SOURCE NO LONGER HOLDS: the relevant item was recaptured 2026-09-05 at class level and carries NO states figure at all — its counts are the relevant record So "17 on the approval-day source" cannot be read from the file the step names. The substitute basis was MEASURED rather than assumed: the relevant item yields 11 literal state assignments, 10 unique, with **0 concatenations and 0 template literals skipped** — nothing is being missed by the parse. The check is complete against the app's real strings; the plan text is what is out of date.
⚠️ claimed done with only 1 of the required 2 independent verifications — shown as in progress, not done
Definition of done: 1024 phone layout without horizontal scroll in every section; chrome measured and any gap handed off
Proof: the check's the relevant item and the relevant item
Verified: 2026-09-06 — the relevant item (no horizontal scroll in any section at any width in the band); the relevant item measured, and the active-pill / badge-colour gap HANDED OFF to the owning lane rather than silently painted here.
Definition of done: the relevant item ×6 on the live URL; six side-by-side PNGs; Sienna's verdict; the verifier's verdict
Proof: the check's the relevant item run on the live URL (evidence file the relevant record, CREATED BY STEP 14's run)
Definition of done: the relevant item on the live URL as Nick and as Chantelle
Proof: the evidence file the relevant record (CREATED BY STEP 15's run)
Definition of done: two VERIFIED lines per step; postmortem written; derived progress figure quoted
Proof: the relevant item