UAT round: Preach hub, Plans screen, overscroll, jitter + share fixes (v0.48.0) - #25
Merged
Merged
Conversation
… (v0.48.0) The 2026-08-11 UAT batch: - Mark-read jitter: the plan chip unmounted (border, padding and all) for the frames the plans read was in flight — every ~30s dwell report and every mark-read write invalidates that cache since 2b7758e. PlanChip now holds the last real answer through refetch gaps; only a real answer may change what the chip shows. - The "Read through" completion toast is gone (callback + catalogue keys): you should know you read it — nothing flashes over the reader. - Plans is a destination (shell/PlansScreen.svelte), not a study-panel kind: one centered column, sectioned Running / Study a concept / Start a plan — concept studies separated from schedules ("crammed, not luxurious" UAT call). - Preach is a hub in both shells (Present + Weaves + Tags + Notes; the tab stays), and Share gains a "Share the Gospel" card opening Present onto the Romans Road — Share is the app AND the Gospel. - Dismissing the native share sheet no longer falls through to clipboard.writeText (NotAllowedError: the closing sheet still holds focus). ShareScreen + PresentHost adopt ContextMenu's AbortError rule; a genuinely blocked clipboard now toasts instead of throwing. - End-of-chapter overscroll, both shells: the scroll range runs until the chapter's last line reaches the TOP of the pane — real range, no rubber-band — for reading lying down with the bottom of the screen blocked. Firmament/Gen 1:7 "Strong's miss" could not be reproduced: corpus, both lexica and the live engine all serve H7549 in EN and DE at every gate level — suspected stale deployed build on the UAT device. e2e updated: plans specs drive the screen (panel kind removed), navbar's Preach test walks the hub, the chronological-plan test returns to Read before expecting the chip. 🤖 Generated with [Claude Code](https://claude.com/claude-code)
The restore helpers poll page.evaluate across the reload the restore itself triggers. A tick that lands in the old document's teardown throws "Execution context was destroyed", which FAILS expect.poll rather than retrying it — CI hit it twice in a row on PR #25 (legacy-restore), while the same idiom in app.spec.ts carried the same latent race. A destroyed context now reads as "navigating" and the poll keeps waiting for the new document's null. 🤖 Generated with [Claude Code](https://claude.com/claude-code)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The 2026-08-11 UAT batch, one change-set:
Fixes
UX
PlansScreen.svelte), sectioned Running / Study a concept / Start a plan — concept studies separated from schedules, one comfortable centered column.Not reproduced
Firmament/Gen 1:7 "Strong's miss": corpus, both lexica and the live engine serve H7549 in EN and DE at every gate level. Suspected stale deployed build on the UAT device; needs the version stamp if it recurs.
Verification: core tests green,
check+build green, touched e2e files green locally (full matrix in CI). Android compiles are CI's to prove, as usual.🤖 Generated with Claude Code