Scope: the fourth chapter of the Tara · continue track. Thirty-four inherited slides became forty-two: a cover, six section dividers, thirty-four content slides and a close. Every inherited slide kept its id, and nothing was merged. The brief records what the chapter is for and why each treatment was chosen; state.json holds the exact counts, tool results and findings.
What was checked#
- Build freshness.
build-eve-oshun.py --checkpasses on the delivered tree: 1,525 slides and 664 sources. The chapter is 42 slides running 46.6 minutes, with one table, fourteen diagrams and three captures. - Executed evidence. The inherited characterization harness,
pinned-tara-consumer-continuity.test.mjs, passes all 15 tests on this host, including the one that checks every inspected Tara source is byte-identical to the citation pin. The continuation model was executed from the pinned source on the running example: an in-progress record at 140 of 300 seconds gives 47% complete · resume from 2:20, the same record marked abandoned gives Ended early · restart from the beginning, and a record below the five-percent floor gives Just started. The three captures are reused from the practise track's pinned bundle (assets/tara-web-practice/manifest.json), whose checks include six authored transcript lines, one completion post with no reflection write, and an offline queue that reconnecting does not replay. - An adversarial source check. An independent reviewer checked every claim in the draft against the pinned players, routes, repositories, standalone apps, watch code and the handbook, and found nineteen that were wrong or overstated. Each was verified at the pin and fixed before the first build. The completion post never carries a reflection, because the note box appears after it is sent. The captions are five generic lines, and only the transcript is the authored script. The favourites view on the same route reads and removes service favourites. The haptic compiler has a caller; only the phone push lacks one. The standalone apps have their own device vibration pacing. The Oshun mobile Tara route is a fifth surface. A record below the floor reads Just started. The source labels the plan fixture a sample for demos. The standalone player also saves on pause, seek and close. The library imports, the journal limit, the premium rule, the sleep state's owner, the second browser test and the handbook's wording were each corrected too.
- Bindings.
assignments/v1-tara-consumer-continuity.jsonwas re-reviewed: ten units ofV1/features/domain-tara.md, 53 evidence entries, every fingerprint, explanation and rationale refreshed. Its test now asserts the Eve edition, the six dividers and the three captures, and still invalidates the review when the cross-device explanation changes or the haptic-delivery slide goes.check-center-coverage.py --checkreports no stale bindings. - Browser rendering.
eve-edition-review.mjs --guide tara-consumer-continuitysweeps all 42 slides at 1440×900, 1280×720 with audio chrome, 390×844 and in print — 168 measurements, no findings, no page errors. - Narration. Forty-two tracks rendered on this host's CPU and verified with
--check --ids, and the library-wide check verifies every track. - PDF. 42 pages, exact authored visual text on every one, in order, and
check-pdf.pypasses, including its table-header floor on the one table. - Suites and lint. Python 479 passed, 0 failed. Node 489 of 489.
ruff checkon the touched tests and Prettier on every touched file are clean.
What was not checked#
- No device run. Quick reset and sleep downshift are connected in source and in the inherited automation; neither was run on a phone here.
- No transport. No checkpoint crossed a device, no favourite was added from a web button, no reflection was read back after the Saved label, and no watch pulsed.
- No live member. The captures render pinned components over declared sample data; nothing here reads a deployed service or a real member's records.