Skip to content

fix: allow historical transcript rows when starting relay requests - #86

Merged
ScriptedAlchemy merged 1 commit into
mainfrom
fix/historical-relay-coverage
Sep 17, 2026
Merged

ScriptedAlchemy merged 1 commit into
mainfrom
fix/historical-relay-coverage

Conversation

@ScriptedAlchemy

@ScriptedAlchemy ScriptedAlchemy commented Sep 17, 2026

Copy link
Copy Markdown
Owner

Automatic MCP messaging can fail before sending when a bot's older transcript contains a send-message without a run ID. The relay currently validates those historical rows as though they were new output.

Validate run IDs only after the established checkpoint. Historical rows retain structural validation and cannot be forwarded; new output without a run ID pauses intake before correlation updates, forwarding, or checkpoint advancement. Whole-page client-nonce matching, duplicate checks, page bounds, and gap checks remain unchanged.

Validation:

  • Regression test failed with the reported Message coverage lacks requestId error before the fix.
  • Engine and transcript integration tests: 43 passed.
  • Independent review: PASS; reviewer also re-ran all 28 engine tests.
  • Full npm run check passed: source validation, build, artifact validation, typecheck, 392 unit tests, and 15 MCP route tests.

Includes a patch changeset. Live Agent Bundle messaging is not yet claimed fixed; the installed MCP still runs the older package.

@changeset-bot

changeset-bot Bot commented Sep 17, 2026

Copy link
Copy Markdown

🦋 Changeset detected

Latest commit: 0dce5e3

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package
Name Type
grok-bot-cli Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Sep 17, 2026

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review Completed 2026-09-17T01:09:11.134616Z 0dce5e3 PR opened
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@ScriptedAlchemy
ScriptedAlchemy merged commit a31df6f into main Sep 17, 2026
0 of 2 checks passed
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.

1 participant