Skip to content

Fix reproducible answer continuation into live chat#556

Closed
HomenShum wants to merge 1 commit into
mainfrom
codex/receipt-continue-chat
Closed

Fix reproducible answer continuation into live chat#556
HomenShum wants to merge 1 commit into
mainfrom
codex/receipt-continue-chat

Conversation

@HomenShum

Copy link
Copy Markdown
Owner

What changed

  • separates immutable receipt reruns from Continue in chat
  • restores the receipt prompt, answer, and source lineage above the real live composer
  • persists bounded role-aware continuation context and parent hash for reload recovery
  • redacts private continuation context from public hash receipts
  • fixes mobile min-content expansion that clipped the transcript and composer
  • keeps the route-lazy markdown editor out of Workbox precache so dependency drift cannot trip the 2 MiB ceiling

Root cause

The reproducible answer page only linked to a fresh rerun and the chat launch/runtime contract had no parent transcript. The first responsive journey also exposed automatic grid min-content sizing expanding the restored chat beyond the mobile viewport.

Validation

  • npx tsc --noEmit --pretty false
  • 14 focused continuation/chat lifecycle/honesty/composer tests
  • 13 design-system tests
  • 3 Playwright pixel journeys: receipt desktop, continued chat desktop, continued chat mobile
  • zero console errors, mojibake, or horizontal overflow; mobile composer enables after follow-up input

Local no-lock dependency extraction repeatedly omitted unrelated transitive files while building; the application and PWA bundles completed before the missing-package resolver report. Required clean-install CI remains the release gate.

No out-of-band Convex deploy was performed.

@vercel

vercel Bot commented Jul 16, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
nodebench-ai Building Building Preview, Comment Jul 16, 2026 9:43pm

Request Review

@github-actions

Copy link
Copy Markdown

PR size advisory

This PR adds 457 lines of substantive change. CONTRIBUTING.md defines a soft limit of ~400 LOC.

If the PR is genuinely cohesive (e.g. an architecture map, a generated migration, a deletion of a dead module), no action is needed. Otherwise consider:

  • splitting into 2-3 PRs along independent concerns
  • pre-discussing the architecture change in a GitHub Discussion before merge

This is advisory — it does not block the merge.

@HomenShum
HomenShum enabled auto-merge (squash) July 16, 2026 21:43
@HomenShum

Copy link
Copy Markdown
Owner Author

Superseded by the repository-style-compliant replacement PR from the same commit.

@HomenShum HomenShum closed this Jul 16, 2026
auto-merge was automatically disabled July 16, 2026 21:44

Pull request was closed

@HomenShum
HomenShum deleted the codex/receipt-continue-chat branch July 16, 2026 21:44
@github-actions

Copy link
Copy Markdown

✅ Dogfood Visual QA Gate: PASSED

Check Status
Screenshots 23 captured (pass)
Walkthrough 9 chapters (pass)
Key Frames 9 extracted (pass)
Scribe Steps 8 how-to steps (pass)
Build success
Artifacts

Download the dogfood-evidence-0411d49 artifact from the Actions tab for full screenshots, frames, and walkthrough video.


Generated by Dogfood QA Gate

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