feat(phase6): #618 Path-A inter-leg probe — capture the return-nav from live truth#717
Merged
Conversation
…om live truth #618 (Learn→Deliver handoff) has been a recurring thorn. Root-caused this session with visual ground truth (the post-Learn screen is the CommCare Learn-mode home — StandardHomeActivity/nsv_home_screen, INSIDE CommCare — NOT a "certificate screen" and NOT Connect's jobs list). There are two deterministic post-Learn pathways the system wrongly treated as one "nondeterministic" state: - Path A: just finished Learn → device on CommCare Learn home. - Path B: re-entered Connect → jobs list (already characterized; deliver-launch.yaml drives §8 opp-detail → §9 download → §10 deliver home). Deliver is only reachable via Connect's DOWNLOAD gate, so Path A MUST return to Connect first — and that return-nav was never captured live (a prior pressBack guess exited CommCare to the Android launcher and was reverted). This adds a calibration probe so the next run captures the return route from live truth instead of guessing: - new recipe connect-learn-home-deliver-probe.yaml: from nsv_home_screen, taps the "Log out of CommCare" tile (candidate return-to-Connect route), screenshotting before/after. - app-screenshot-capture: when the Deliver leg's connect-resume-opp fails on nsv_home_screen (Path A), run the probe bracketed by mobile_capture_ui_dump and upload both XML element-trees to journey-deliver/618probe-*.xml. Record Deliver `incomplete` + note; do not pass/fail on the probe. Once the dumps show the real return route, encode it as connect-resume-opp's Path-A branch (detect nsv_home_screen → return-to-Connect → existing jobs-list CTA logic) and retire the probe. Recipe resolves clean (learn-home-screen → nsv_home_screen); full suite 1883 green. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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.
Why
#618 (the Learn→Deliver inter-leg handoff) has been a long-standing Phase-6 thorn. Root-caused this session with visual ground truth: after the Learn leg, the device sits on the CommCare Learn-mode home (
nsv_home_screen/ StandardHomeActivity, inside CommCare) — not a "certificate screen" (the certificate is a section on Connect's opp-detail), and not Connect's jobs list. The system treated the two post-Learn landings as one "nondeterministic" state; they're two deterministic pathways:deliver-launch.yamldrives §8 opp-detail → §9 DOWNLOAD → §10 deliver home).Deliver is only reachable via Connect's DOWNLOAD gate, so Path A must return to Connect first — and that return-nav was never captured live (a prior
pressBackguess exited CommCare to the Android launcher and was reverted).What
A calibration probe so the next run captures the return route from live truth instead of guessing:
connect-learn-home-deliver-probe.yaml— fromnsv_home_screen, taps the "Log out of CommCare" tile (candidate return-to-Connect route), screenshotting before/after.app-screenshot-capture— when the Deliver leg'sconnect-resume-oppfails onnsv_home_screen(Path A), run the probe bracketed bymobile_capture_ui_dump, and upload both XML element-trees tojourney-deliver/618probe-*.xml. Record Deliverincomplete+ a note; do not pass/fail on the probe (it's calibration, not the journey).Next
Once the dumps show the real return route, encode it as
connect-resume-opp's Path-A branch (detectnsv_home_screen→ return-to-Connect → existing jobs-list CTA logic) and retire the probe.Recipe resolves clean (
learn-home-screen→nsv_home_screen); full suite 1883 green. Recipes are auto-discovered (no registration needed).