Source pin: 1ceae52c7896a59ac74a4429d410f3218f0b91c6. Guide/slide:
v1-web-pwa / pwa-install-update; preserve the existing ID and eleven-slide
guide order. This is a pilot candidate, not an accepted benchmark.
Visual thesis: one exact, readable source excerpt in the cream-and-ink workspace uses aligned margin explanations and a terracotta emphasis on its returned boolean; code and interpretation remain distinct without decorative syntax colors, boxes or unsupported lifecycle arrows.
Content plan: introduce the V1.0 web-install boundary, inspect the body of
applyWaitingServiceWorker, identify its absent-worker guard, posted message
and local return, then distinguish those facts from worker activation, a reload
and server acknowledgement. Preserve the existing manifest, native availability,
route-sensitive update, queue/privacy and stale-content explanations in notes.
The next account slide continues the distinction between a control and its
owning effect. The source excerpt is not a screenshot or an observed device run.
Interaction thesis: retain slide navigation/entrance, explanation disclosure and the center width transition with reduced-motion parity. Each annotation stays beside its exact source band on wide screens and immediately after it on narrow screens. The entire specimen remains readable without hover, animation or a new inspector, including print.
Specimen and source boundaries#
Use exactly lines 147–152 of the pinned
apps/oshun/web/src/lib/pwa-service-worker.ts: the body excerpt excludes the
signature and final function brace, retains the blank line and original code
bytes, and labels those omissions as an excerpt. Three annotations cover the
guard, message and return. Line numbers identify source locations, not automatic
presentation ordinals. No three-annotation quota is part of the renderer.
The helper returns false when no waiting worker exists. Otherwise it calls
postMessage with OSHUN_SKIP_WAITING and returns true without an activation
acknowledgement. A synchronous posting exception escapes; true must not be
described as any independently verified worker or page state. Controlled source
execution will verify absence, posted payload, immediate return, repeat calls
and exception behavior, not an actual browser-worker lifecycle.
The inspected consumer in PwaBootstrap.tsx preserves relaunch/scroll state,
sets apply intent before posting, and handles reload separately. The inspected
worker message branch calls self.skipWaiting(). Those separate excerpts help
bound the source review but are not new end-to-end deployment evidence. Do not
silently enlarge the helper specimen's claim to those consumers.
The pinned manifest declares Lilith, /?surface=pwa and standalone display.
Store policy disables native availability and directs installation to the web
guide. Some manifest screenshot labels still say six rooms; they are not proof
of release eligibility, representative screenshots or a changed four-room
promise. No image asset is introduced for this code-mechanism treatment.
Contract and viewing rules#
annotated-source carries exact source/revision/symbol/start-line/line content
plus separately authored annotation nodes. Each node has a stable ID, source
line range, title and interpretation. Ordered ranges must partition the excerpt
without missing or duplicated lines. Sources must be cited, the declared pin
must match the library, and building must compare the exact lines with the Git
snapshot. An authored imitation cannot pass as an exact excerpt.
Keep Georgia titles and Arial body/code text; source whitespace is preserved by
native pre/code semantics without introducing a third typeface. The code is
not a terminal mockup. Soft wrapping changes display only, never characters or
source line identity. Begin with 18px source/body and 16px provenance/line
labels; inspect actual compact playback, 320px width, long uneven source text,
fallback fonts, enlarged text and page-fit PDF before accepting those
provisional floors. Use a full source filename in accessible detail; the
on-slide artifact identity can use its exact basename and symbol with the full
pinned path in provenance.
Neutral reader tasks: What causes false? What exactly happened before true was returned? Does true establish that the worker activated or the page refreshed? Where would you inspect the original source? Willing-reader sessions remain pending; tests and model observations are separate evidence.