The 29 Aug release cut, and eight things the owner asked for - #13
Merged
Conversation
A manual test cut of caf10bd on macOS, and the notes it produced. The cut itself was green: Release build clean, 631 tests / 1 skipped / 0 failures across 35 files. Navigation direction is correct, the done card is whole, the journal's numbers match the store exactly, and a source grep finds no network, analytics, StoreKit, notification or location API anywhere in the app. Five findings (F1-F5). The one that matters for play is F1: the first-run hint is specified as "never returns" but restart() clears the flag it reads, so it comes back on every field. F3 records that no installed simulator runtime can reach the 18.5 deployment floor, so the minimum supported OS is currently untested. F5 records that the version and build numbers are still v1.2's. Eight requests (R1-R8) raised by the owner during the pass. Two are major and both have a measurable cause rather than a taste argument: R7 - the pops do not read as distinct. Of the 100 catalog entries, zero override voice, haptic pattern or burst motion; all three fall through to the family, so 100 pops carry 10 sounds, 10 burst motions and at most 5 haptics, constant within a family. The channels are live and read - this is an authoring gap, not an engine one. R8 - the weather under-reads for two separable reasons: clear air is 44% of fields, and flowCarry is 0 for clear, snow AND fog, so half the airs move nothing at all. Also recorded: three non-findings, so nobody re-chases them. The "inert sky" and the "unpoppable orbs" were a stale window origin in the test harness, not the app. No code changed. Every item names its file, line and constant so the change can be made deliberately, one knob at a time. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01MiBreiwVPx8LF5pDdBeVff
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.
A manual test cut of
caf10bdon macOS, and the notes it produced. No code changed — this isdocs/release_cut_2026-08-29_feedback.mdonly.The cut was green
Release build clean (2 benign warnings) · 631 tests, 1 skipped, 0 failures, 35 files, 23.5 s.
Verified on device: navigation direction is correct (finger up → sky), the done card is whole (verse, counts, lifetime line, no scrim), the journal's numbers match the persisted store exactly, and a source grep finds no network, analytics, StoreKit, notification or location API anywhere in
Vesper/.Five findings
restart()clears the flag it readsJournalView.swift:560Eight requests, two of them major
R7 — the pops do not read as distinct. Measured, not asserted: of the 100 catalog entries, zero override
voice,patternorburst. All three fall through to the family, so 100 pops carry 10 sounds, 10 burst motions and at most 5 haptics, constant within a family. The channels are live and read (SceneRenderer.swift:473,GameSimulation.swift:590,HapticsEngine.swift:41) — the renderer is ready and the data is empty. An authoring gap, not an engine one.R8 — the weather under-reads, for two separable reasons:
clearis 44% of fields, andflowCarryis 0 for clear, snow and fog — half the airs move nothing at all. Storm also carries less than rain, which seems backwards.R1 (auto-rise to sky — likely already built, needs a hands-off confirm), R2 (pointer to the next stone), R3 (piercing fireworks), R4 (chain reach too wide), R5 (visible dark edge at the sky/field join), R6 (more fireworks).
Also recorded
Three non-findings, written down so nobody re-chases them. The "inert sky" and the "unpoppable orbs" were a stale window origin in my test harness, not the app.
Every item names its file, line and constant so the change can be made deliberately —
CLAUDE.md's one-knob-at-a-time rule stands.🤖 Generated with Claude Code
https://claude.ai/code/session_01MiBreiwVPx8LF5pDdBeVff