[PR #5536] [MERGED] test(cli): retain recovery guidance in filtered failures #6953

Closed
opened 2026-11-01 21:44:17 +00:00 by bsakaguchi · 0 comments
Owner

📋 Pull Request Information

Original PR: https://github.com/morluto/rea/pull/5536
Author: @gensokyo-dev
Created: 10/20/2026
Status: ✅ Merged
Merged: 10/20/2026
Merged by: @gensokyo-dev

Base: main ← Head: fix/5431-cli-recovery-assertions


📝 Commits (1)

  • ba78f5f test(cli): retain recovery guidance in filtered failures

📊 Changes

1 file changed (+28 additions, -6 deletions)

View changed files

📝 tests/boundary/cli/filteredFailureOutput.test.ts (+28 -6)

📄 Description

Summary

Follow up #5470 / #5431: align the CLI filtered-failure regression with the shared recovery contract. A test introduced by the main update still expected the old generic remediation and caused four final CI failures. Runtime code and public contracts are unchanged.

Merged as 55cce6fc1 using the human owner's explicit override authorization after reproducing all observed compiled failures on the unchanged CI main baseline. This does not turn incomplete/red compiled CI into a passing result.

Change and scope

Check that JSON, TOON, YAML and Markdown preserve recovery guidance despite output filtering, including tools/list, operation identity and the original missing-file diagnostics. Parse JSON/YAML to verify inspect_input_contract in both compact and full envelopes. Normalize display whitespace so YAML wrapping does not become a semantic assertion.

Semantic owner: existing shared domain projection; this change only exercises its CLI consumer. No provider, target authority, Evidence, schema, generated metadata, installation or compatibility changes. Additional scope approval is not applicable.

Validation performed

  • Actual failing base: #5470 final shard reported four legacy-text failures in filteredFailureOutput.test.ts.
  • Focused CLI regression: 5 passed; browser/oversized MCP recovery suites: 11 passed. The combined seven-suite diagnostic run had 62 passed, 5 failed, 2 skipped; all five other failures reproduced in an isolated pre-change c374c2fe7 worktree (TypeScript application graph, two EVM cancellation-warning cases, malformed Protobuf trailer deadline and Electron path-message wording). Those unrelated owners are unchanged.
  • npm run check — passed: typecheck, lint/module boundaries, all-file formatting, knip, metadata and architecture guards.
  • Independent codex exec ... review --uncommitted — no actionable defects; reviewer did not execute tests. Tests above ran separately.
  • GitHub Greptile review — passed with no inline findings. CI run 39435467316 passed build, static checks and all 12,301 source tests (nine named skips). The compiled suite is not green: shard 5 passed 2,392 tests and failed two EVM cancellation cases plus one JSON staging-cleanup case; fail-fast cancelled four peers. An isolated worktree at this run's main base cf5194f68 reproduced exactly those three failures, with 39 passes and two skips. The unchanged owning implementations are outside this follow-up. No additional failures appeared in the cancelled peer logs before cancellation; incomplete compiled coverage is not claimed as passing.
  • No runtime performance change is claimed. CLI tests completed in 81 ms in the combined run. Full real-provider qualification was not repeated for this test-only follow-up.

Author readiness

Human owner: @gensokyo-dev

Recorded at the human owner's explicit instruction and authorization in the task conversation; implementation review and executed validation were performed by Codex.

  • I reviewed the final diff and relevant existing code, understand the change and its edge cases, and take responsibility for the complete PR, including AI-assisted work.
  • I checked the evidence above, confirmed it supports the current change, and recorded meaningful validation gaps.
  • I declare this PR ready for initial maintainer review.

Before merge

  • This PR addresses a concrete problem or an agreed enhancement.
  • Material scope and authority questions are resolved, and any required maintainer scope decision covers the final diff.
  • The PR has one focused outcome and the title follows type(scope): outcome.
  • Related issue is linked, or the reason for not linking one is stated above.
  • Tests cover changed observable behavior and meaningful failure paths.
  • Owning docs, contracts, and generated metadata are updated where needed.
  • User-visible CLI/MCP changes include representative output.
  • I checked the final diff for secrets, unrelated cleanup, and unsupported claims.

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/morluto/rea/pull/5536 **Author:** [@gensokyo-dev](https://github.com/gensokyo-dev) **Created:** 10/20/2026 **Status:** ✅ Merged **Merged:** 10/20/2026 **Merged by:** [@gensokyo-dev](https://github.com/gensokyo-dev) **Base:** `main` ← **Head:** `fix/5431-cli-recovery-assertions` --- ### 📝 Commits (1) - [`ba78f5f`](https://github.com/morluto/rea/commit/ba78f5f0298372f67116f9436d2404f3c2fe52a6) test(cli): retain recovery guidance in filtered failures ### 📊 Changes **1 file changed** (+28 additions, -6 deletions) <details> <summary>View changed files</summary> 📝 `tests/boundary/cli/filteredFailureOutput.test.ts` (+28 -6) </details> ### 📄 Description ## Summary Follow up #5470 / #5431: align the CLI filtered-failure regression with the shared recovery contract. A test introduced by the main update still expected the old generic remediation and caused four final CI failures. Runtime code and public contracts are unchanged. Merged as `55cce6fc1` using the human owner's explicit override authorization after reproducing all observed compiled failures on the unchanged CI main baseline. This does not turn incomplete/red compiled CI into a passing result. ## Change and scope Check that JSON, TOON, YAML and Markdown preserve recovery guidance despite output filtering, including `tools/list`, operation identity and the original missing-file diagnostics. Parse JSON/YAML to verify `inspect_input_contract` in both compact and full envelopes. Normalize display whitespace so YAML wrapping does not become a semantic assertion. Semantic owner: existing shared domain projection; this change only exercises its CLI consumer. No provider, target authority, Evidence, schema, generated metadata, installation or compatibility changes. Additional scope approval is not applicable. ## Validation performed - Actual failing base: [#5470 final shard](https://github.com/morluto/rea/actions/runs/39432049829/job/118660054488) reported four legacy-text failures in `filteredFailureOutput.test.ts`. - Focused CLI regression: **5 passed**; browser/oversized MCP recovery suites: **11 passed**. The combined seven-suite diagnostic run had 62 passed, 5 failed, 2 skipped; all five other failures reproduced in an isolated pre-change `c374c2fe7` worktree (TypeScript application graph, two EVM cancellation-warning cases, malformed Protobuf trailer deadline and Electron path-message wording). Those unrelated owners are unchanged. - `npm run check` — passed: typecheck, lint/module boundaries, all-file formatting, knip, metadata and architecture guards. - Independent `codex exec ... review --uncommitted` — no actionable defects; reviewer did not execute tests. Tests above ran separately. - GitHub Greptile review — passed with no inline findings. [CI run 39435467316](https://github.com/morluto/rea/actions/runs/39435467316) passed build, static checks and all 12,301 source tests (nine named skips). The compiled suite is not green: [shard 5](https://github.com/morluto/rea/actions/runs/39435467316/job/118674944454) passed 2,392 tests and failed two EVM cancellation cases plus one JSON staging-cleanup case; fail-fast cancelled four peers. An isolated worktree at this run's main base `cf5194f68` reproduced exactly those three failures, with 39 passes and two skips. The unchanged owning implementations are outside this follow-up. No additional failures appeared in the cancelled peer logs before cancellation; incomplete compiled coverage is not claimed as passing. - No runtime performance change is claimed. CLI tests completed in 81 ms in the combined run. Full real-provider qualification was not repeated for this test-only follow-up. ## Author readiness Human owner: @gensokyo-dev Recorded at the human owner's explicit instruction and authorization in the task conversation; implementation review and executed validation were performed by Codex. - [x] I reviewed the final diff and relevant existing code, understand the change and its edge cases, and take responsibility for the complete PR, including AI-assisted work. - [x] I checked the evidence above, confirmed it supports the current change, and recorded meaningful validation gaps. - [x] I declare this PR ready for initial maintainer review. ## Before merge - [x] This PR addresses a concrete problem or an agreed enhancement. - [x] Material scope and authority questions are resolved, and any required maintainer scope decision covers the final diff. - [x] The PR has one focused outcome and the title follows `type(scope): outcome`. - [x] Related issue is linked, or the reason for not linking one is stated above. - [x] Tests cover changed observable behavior and meaningful failure paths. - [x] Owning docs, contracts, and generated metadata are updated where needed. - [x] User-visible CLI/MCP changes include representative output. - [x] I checked the final diff for secrets, unrelated cleanup, and unsupported claims. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
bsakaguchi 2026-11-01 21:44:17 +00:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
morluto/rea#6953
No description provided.