Skip to content

Require bounded normal, failure and recovery journey checks - #1

Merged
sturec5 merged 2 commits into
mainfrom
codex/bounded-journey-recovery
Oct 10, 2026
Merged

sturec5 merged 2 commits into
mainfrom
codex/bounded-journey-recovery

Conversation

@sturec5

@sturec5 sturec5 commented Oct 10, 2026

Copy link
Copy Markdown
Owner

What this changes, and why

Recovery can be inferred from an error screen without actually exercising its recovery control. Phase 9 now asks for normal use, one representative failure, and recovery within the selected journey, while reusing evidence and keeping execution limits explicit.

Adds the approved 11-line block to Phase 9 and updates the required plugin/marketplace version fields from 1.8.1 to 1.9.0.

Gates

  • ./check.sh exits 0 (names, non-English text, commit messages, refs and authorship checked; case-sensitive and measured-figure lists not configured)
  • python3 .github/verify.py exits 0
  • ./check_test.sh passes: 18 passed, 0 failed
  • Plugin and marketplace versions bumped together, as required for a payload change
  • git diff --check clean; diff limited to the protocol and the two version manifests

@sturec5
sturec5 merged commit e9d59fe into main Oct 10, 2026
1 check passed
@sturec5
sturec5 deleted the codex/bounded-journey-recovery branch October 10, 2026 16:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants