[PR #7209] [CLOSED] test(setup): expect the forwarded MCP response limit in registrations #7718

Closed
opened 2026-11-03 13:39:52 +00:00 by bsakaguchi · 0 comments
Owner

📋 Pull Request Information

Original PR: https://github.com/morluto/rea/pull/7209
Author: @kaoru0822-kitauji
Created: 10/26/2026
Status: ❌ Closed

Base: main ← Head: test/setup-forwarded-response-limit


📝 Commits (1)

  • f8ee47c test(setup): expect the forwarded MCP response limit in registrations

📊 Changes

1 file changed (+2 additions, -1 deletions)

View changed files

📝 src/mcpStartupPolicy.test.ts (+2 -1)

📄 Description

What broke: main CI fails Source tests and Portable tests (for example, run on 2be39ef47) in src/mcpStartupPolicy.test.ts › "forwards curated launch limits without copying transport or unrelated settings". The test still reproduces on b3818bbba.
Fix: update that test to the current setup contract. 6819cc5b8 intentionally forwards an explicit REA_MCP_MAX_RESPONSE_BYTES: it is documented in docs/client-configuration.md and covered by registrationRuntimeEnvironmentCli.test.ts. The older #7049 test still expected the setting to be dropped.
Risk: test-only; no runtime change.

Summary

This restores a green main. The production behavior from 6819cc5b8 is unchanged. Only the stale module expectation is updated.

Problem and expected behavior

explicitSetupRegistrationEnvironment({ …, REA_MCP_MAX_RESPONSE_BYTES: "20971520", UNRELATED: "dropped" }) now returns REA_MCP_MAX_RESPONSE_BYTES. The test expected it to be absent, because #7049 had classed it as a transport setting. The newer explicit selection list and its docs say setup forwards it.

Change and scope

  • Expect REA_MCP_MAX_RESPONSE_BYTES to be forwarded, and keep UNRELATED dropped.
  • Rename the test: it no longer claims that "transport" settings are excluded.
  • Not applicable: maintainer scope decision. This is an ordinary fix within existing boundaries.

Contract and boundary impact

  • Semantic owner and earliest changed stage: src/application/SetupRegistrationEnvironment.ts (unchanged); only the test changes.

  • Contribution scope fit and linked maintainer decision: not applicable (test alignment with 6819cc5b8).

  • CLI and MCP/tool-catalog contract: none.

  • Provider, bridge, target-format, or platform compatibility: none.

  • Evidence, artifact, provenance, or reconstruction contract: none.

  • Target selection, authority, upstream behavior, and cleanup details: not applicable.

  • Generated metadata, package, or installation impact: none.

  • Documentation or usability only; no target interaction.

Evidence and regression coverage

  • Tests updated: src/mcpStartupPolicy.test.ts.
  • Base reproduction: on b3818bbba, npm run test:local -- src/mcpStartupPolicy.test.ts → 1 failed, 5 passed. The received object contains REA_MCP_MAX_RESPONSE_BYTES: "20971520".
  • Remaining proof gaps: none known. The forwarding itself is already covered end to end by tests/acceptance/setup/registrationRuntimeEnvironmentCli.test.ts, which this PR does not change.

Validation performed

  • npm run test:local -- src/mcpStartupPolicy.test.ts — 6 passed.
  • npm run format:check — all matched files use the correct format.
  • npm run check:fast — typecheck and lint, 2 tasks successful.

Compatibility, safety, and release

  • Breaking changes or migration steps: none.
  • Real Hopper/Ghidra, browser, or OS coverage: not applicable.
  • Package or release metadata impact: none.
  • Security, privacy, process, or containment review: none.

Author readiness

Human owner: @kaoru0822-kitauji

  • 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. (No issue: this is a direct main-health fix.)
  • 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. (None.)
  • I checked the final diff for secrets, unrelated cleanup, and unsupported claims.

🤖 Generated with Claude Code


🔄 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/7209 **Author:** [@kaoru0822-kitauji](https://github.com/kaoru0822-kitauji) **Created:** 10/26/2026 **Status:** ❌ Closed **Base:** `main` ← **Head:** `test/setup-forwarded-response-limit` --- ### 📝 Commits (1) - [`f8ee47c`](https://github.com/morluto/rea/commit/f8ee47cc486a7f246c6c98a7df0d4a6b4c92b78c) test(setup): expect the forwarded MCP response limit in registrations ### 📊 Changes **1 file changed** (+2 additions, -1 deletions) <details> <summary>View changed files</summary> 📝 `src/mcpStartupPolicy.test.ts` (+2 -1) </details> ### 📄 Description **What broke:** main CI fails Source tests and Portable tests (for example, run on 2be39ef47) in `src/mcpStartupPolicy.test.ts` › "forwards curated launch limits without copying transport or unrelated settings". The test still reproduces on b3818bbba. **Fix:** update that test to the current setup contract. 6819cc5b8 intentionally forwards an explicit `REA_MCP_MAX_RESPONSE_BYTES`: it is documented in `docs/client-configuration.md` and covered by `registrationRuntimeEnvironmentCli.test.ts`. The older #7049 test still expected the setting to be dropped. **Risk:** test-only; no runtime change. ## Summary This restores a green main. The production behavior from 6819cc5b8 is unchanged. Only the stale module expectation is updated. ## Problem and expected behavior `explicitSetupRegistrationEnvironment({ …, REA_MCP_MAX_RESPONSE_BYTES: "20971520", UNRELATED: "dropped" })` now returns `REA_MCP_MAX_RESPONSE_BYTES`. The test expected it to be absent, because #7049 had classed it as a transport setting. The newer explicit selection list and its docs say setup forwards it. ## Change and scope - Expect `REA_MCP_MAX_RESPONSE_BYTES` to be forwarded, and keep `UNRELATED` dropped. - Rename the test: it no longer claims that "transport" settings are excluded. - Not applicable: maintainer scope decision. This is an ordinary fix within existing boundaries. ## Contract and boundary impact - Semantic owner and earliest changed stage: `src/application/SetupRegistrationEnvironment.ts` (unchanged); only the test changes. - Contribution scope fit and linked maintainer decision: not applicable (test alignment with 6819cc5b8). - CLI and MCP/tool-catalog contract: none. - Provider, bridge, target-format, or platform compatibility: none. - Evidence, artifact, provenance, or reconstruction contract: none. - Target selection, authority, upstream behavior, and cleanup details: not applicable. - Generated metadata, package, or installation impact: none. - [x] Documentation or usability only; no target interaction. ## Evidence and regression coverage - Tests updated: `src/mcpStartupPolicy.test.ts`. - Base reproduction: on b3818bbba, `npm run test:local -- src/mcpStartupPolicy.test.ts` → 1 failed, 5 passed. The received object contains `REA_MCP_MAX_RESPONSE_BYTES: "20971520"`. - Remaining proof gaps: none known. The forwarding itself is already covered end to end by `tests/acceptance/setup/registrationRuntimeEnvironmentCli.test.ts`, which this PR does not change. ## Validation performed - `npm run test:local -- src/mcpStartupPolicy.test.ts` — 6 passed. - `npm run format:check` — all matched files use the correct format. - `npm run check:fast` — typecheck and lint, 2 tasks successful. ## Compatibility, safety, and release - Breaking changes or migration steps: none. - Real Hopper/Ghidra, browser, or OS coverage: not applicable. - Package or release metadata impact: none. - Security, privacy, process, or containment review: none. ## Author readiness Human owner: @kaoru0822-kitauji - [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. (No issue: this is a direct main-health fix.) - [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. (None.) - [x] I checked the final diff for secrets, unrelated cleanup, and unsupported claims. 🤖 Generated with [Claude Code](https://claude.com/claude-code) --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
bsakaguchi 2026-11-03 13:39:52 +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#7718
No description provided.