Eve library

Lilith web and PWA · Meet Lilith chapter 1 · verification receipt · 10 September 2026

Guide

Revision 1

On this page

Scope: the tail of the track's opening chapter. The rewrite itself shipped earlier on 10 September (e42c00542cb), but its closing tasks did not: the chapter had no capture, had never been swept in a browser, had no narration for its new slides' successor and no receipt, and chapters two and three closed ahead of it. This pass finishes it. Twelve inherited slides are now nineteen: a cover, three section dividers, fourteen content slides and a close, in sections of four, six and four. The brief records what the chapter is for and why each treatment was chosen; the track brief is meet-lilith-track.md; state.json holds the exact counts, tool results and findings.

What was checked#

  • The chapter's capture, which it did not have. assets/lilith-web-pwa/update-notice.png is the shipped PwaUpdatePrompt, rendered from its pinned component with no mocked boundaries at all — the notice fetches nothing and reads no store, so there was nothing to stand in for. Forty-one repository files were read from the pin and hashed. The route context is not written by the harness: it is what resolvePwaUpdateRouteContext('/domains/nisaba') returns, so the heading, the paragraph and the dismiss label on the capture are the product's own reading branch, and a change to that route table fails the run instead of quietly leaving stale copy under the pins. Three runs produced identical bytes.
  • The fixture states the phase honestly. PwaBootstrap sets version: null in the waiting phase — a build label only arrives with the worker's own update message, which is the other phase — so the fixture carries no version and the card reads "Service worker update · 9:31 PM". The time is held more than an hour in the past on purpose: inside an hour the component formats a relative minute count against Date.now(), which would move between runs.
  • The pins are measured, and they are outside the card. The first placement put five 30px callouts on the capture and covered the kicker, the build line and the opening words of "1 offline change is waiting to sync" — the exact thing the legend asks the reader to read. They now sit in gutters beside the card. That is not only tidier: in the side layout the capture's column is sized from the frame's own aspect ratio, so the scale it is drawn at depends only on the frame's height. Horizontal padding is free and vertical padding shrinks the card. The frame is therefore the card plus 56px left and right and nothing above or below, and the harness asserts every pin clears the card at the smallest scale the figure is ever drawn at.
  • The slide the sweep caught. member-design-language ran 16.1px past its page at 1280×720 and pushed the narration chrome off screen. One evidence line was carrying a wrapped second line; "Visible focus, stable targets and reduced-motion behavior remain available" became "Visible focus, stable targets and reduced-motion parity", which is the source document's own term for it. Nothing else in the chapter moved.
  • Browser rendering. eve-edition-review.mjs --guide v1-web-pwa sweeps all 19 slides at 1440×900, 1280×720 with audio chrome, 390×844 and in print — 76 measurements, no spill, no document overflow, no page errors, no findings.
  • Narration. One track rendered on this host's CPU and verified with --check --ids; the chapter runs 28.9 minutes and the library is complete at 1888.5 minutes with nothing pending.
  • PDF. 19 pages, exact authored visual text on every one, in order, read back from the downloadable decks/v1-web-pwa.pdf — which was still the twelve-page pre-rewrite export and is now the delivered one.
  • Suites and lint. Python 472 passed, 0 failed. Node 444 of 446 — the two failures are the pre-existing Cannot find module 'zod'. ruff check, ESLint on the new harness and Prettier on every touched file are clean.
  • Bindings. No assignment or teaching record binds a slide in this chapter, which was checked when the rewrite shipped and is unchanged by one added slide. The two records that do name its slides list the complete sequence and both grew by a row: authoring/composition-pilot.json and the slide-brief table in authoring/v1-web-pwa-guide.md, asserted together by test_composition.CompositionAudit.

Why this surface, and where it sits#

The chapter's spine is that a local acknowledgement is local. Its PWA thread was a source excerpt — the exact body of applyWaitingServiceWorker, whose true means only that a message was posted — followed by a decision tree of what still has to be observed. Between a claim about a function and a diagram of outcomes, the missing slide was the one place a member ever meets either: the card the refresh control lives on. It carries five things worth pinning, and every one of them is a statement about this device — the staged state, the build that applies itself when the last tab closes, the held write, and two controls that are both real answers and neither of which confirms anything.

What this chapter found and did not fix#

The notice's kicker is painted #99F6E4 on a reading route and #d8cdb6 otherwise, both on cream paper. On the shipped Lilith ground that is far below the 4.5:1 the design tokens hold everywhere else; the two values read as leftovers from a dark theme, and the same component's own comments record two earlier visual regressions on this surface. It is a product defect, not a presentation one, and fixing it would move the pin under a capture in three chapters, so the capture shows the kicker exactly as it ships and the legend does not depend on reading it off the image.

Files#

  • Manuscript: content/72-lilith-web-pwa.json
  • Capture: assets/lilith-web-pwa/update-notice.png, assets/lilith-web-pwa/provenance.json
  • Harness: tools/presentations/tests/lilith-web-pwa-capture.mjs
  • Fixture: authoring/lilith-web-pwa-fixture.json
  • Deck: decks/v1-web-pwa.html, decks/v1-web-pwa.pdf
  • Evidence: browser-report.json, pdf-contract.json, state.json