Skip to content

Fix duplicate chat demo surfaces#7

Merged
konard merged 3 commits into
mainfrom
issue-5-e1b0937faaf7
May 12, 2026
Merged

Fix duplicate chat demo surfaces#7
konard merged 3 commits into
mainfrom
issue-5-e1b0937faaf7

Conversation

@konard
Copy link
Copy Markdown
Contributor

@konard konard commented May 12, 2026 •
edited
Loading

Fixes #5.

Summary

  • Removed the duplicated custom transcript from the gallery and isolated profile pages; each profile now renders one active DemoSurface.
  • Added shared real/adapter demo surfaces so every profile verifies visible fixture messages and sent messages in the selected surface.
  • Split the nav into the pinned own component and ranked external libraries with score chips, and corrected scoring so only actual live local renderers get the live bonus.
  • Refreshed the issue-5 case-study data, saved the reported screenshots, and added the final review screenshot.

Verification

  • npm test
  • npm run demo:build
  • npm run test:e2e
  • npm run check
  • Playwright MCP manual check: assistant-ui external profile reported one demo-surface, zero .own-chat-frame nodes, and runtime-gated renderer.

Screenshot

Issue 5 chat demos

@konard
Initial commit with task details
4f52656 
Adding .gitkeep for PR creation (default mode).
This file will be removed when the task is complete.

Issue: #5
@konard konard self-assigned this May 12, 2026
@konard konard changed the title [WIP] Fixes and improvements Fix duplicate chat demo surfaces May 12, 2026
@konard konard marked this pull request as ready for review May 12, 2026 16:27
@konard
Copy link
Copy Markdown
Contributor Author

konard commented May 12, 2026

Working session summary

Implemented and pushed the fix to PR 7: #7

Changed:

  • Removed the duplicated own-chat transcript from gallery/profile pages.
  • Added one shared DemoSurface path for real local renderers and offline verified adapter demos.
  • Tightened e2e tests to assert messages appear in the active demo surface, including an explicit no-duplicate-own-chat regression.
  • Fixed ranking display/scoring and refreshed issue-5 case-study evidence/screenshots.
  • Updated PR title/body, embedded the final screenshot, and marked the PR ready.

Verified:

  • npm test
  • npm run demo:build
  • npm run test:e2e
  • npm run check
  • Playwright MCP manual UI check
  • GitHub CI for latest commit 9493463 is passing; PR merge state is clean.

Working tree is clean and the branch is pushed.

This summary was automatically extracted from the AI working session output.

@konard
Copy link
Copy Markdown
Contributor Author

konard commented May 12, 2026

🤖 Solution Draft Log

This log file contains the complete execution trace of the AI solution draft process.

💰 Cost estimation:

  • Model: GPT-5.5
  • Provider: OpenAI
  • Public pricing estimate: $33.941107

📊 Context and tokens usage:

  • 870.1K / 1.1M (83%) input tokens, 62.0K / 128K (48%) output tokens

Total: (870.1K + 22.4M cached) input tokens, 62.0K output tokens, $33.941107 cost

🤖 Models used:

  • Tool: OpenAI Codex
  • Requested: gpt-5.5
  • Model: GPT-5.5 (gpt-5.5)

📎 Log file uploaded as Repository (2 chunks) (109859KB)

Now working session is ended, feel free to review and add any feedback on the solution draft.

@konard konard merged commit 078b009 into main May 12, 2026
23 checks passed
@konard
Copy link
Copy Markdown
Contributor Author

konard commented May 12, 2026

🎉 Auto-merged

This pull request has been automatically merged by hive-mind.

  • All CI checks have passed

Auto-merged by hive-mind with --auto-merge flag

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

@konard konard

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

Fixes and improvements

1 participant

@konard