test: add agent lifecycle browser regression#7
Merged
roackb2 merged 1 commit intoJul 12, 2026
Merged
Conversation
02ae02a
into
codex/project-bound-agent-conversation
1 check passed
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
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.
What changed
1.61.1and add a focused GitHub Actions job with failure artifactsWhy
The lifecycle behavior in #6 was manually browser-verified, but the MVP needs a committed regression that can catch storage, hydration, streaming, and reset regressions across a real browser reload. Component-only tests would not exercise those boundaries.
The route fixture intentionally owns deterministic HTTP/SSE responses only. It does not reproduce Heddle run coordination or server session policy; those remain covered in the companion server repository.
Dependency and rollout
Validation
npm cinpm run test:agent(7 passed)npx tsc --noEmitnpm run lint(0 errors; 11 existing warnings)npm run test:agent:e2efrom a cold start (1 passed)npm run buildnpm audit --omit=devcontinues to report the existing Next/Geist PostCSS advisory (3 moderate); this PR adds only a pinned dev dependency and does not change the production dependency finding.