Skip to content

Feat/1821#219

Open
conradmugabe wants to merge 58 commits into
mainfrom
feat/1821
Open

Feat/1821#219
conradmugabe wants to merge 58 commits into
mainfrom
feat/1821

Conversation

@conradmugabe

@conradmugabe conradmugabe commented Jun 3, 2026

Copy link
Copy Markdown
Contributor

Checklist

  • Tests were added/updated according to the feature/bugfix/change made
  • Version was rolled according to semver requirements
  • API endpoints openapi schema was updated if applicable

Changes

Screenshots

Screenshot from 2026-06-03 17-44-14 Screenshot from 2026-06-03 17-40-41 Screenshot from 2026-06-03 17-43-54
Screencast.from.2026-06-01.04-45-52.mp4

conradmugabe and others added 30 commits April 1, 2026 02:40
Wire the existing MentorSettings.show_reasoning API field into the agent
Settings tab as a Switch, mirroring the forkable/Copies toggle (form field,
default from mentor?.show_reasoning, and submit payload). Includes unit tests.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
…already streaming

The 'Just a sec...' LoadingMessage gate only checked the current stream's
content, so a flaky socket that retries/duplicates a generation rendered it
next to a bubble already streaming (or finished). Add a single
showLoadingMessage gate that also hides it when the current stream has
reasoning/tool output or the last assistant message already shows any output.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Copy/feedback/share/report/retry only make sense on a finished response.
Hide the toolbar via a 'hidden' class when isCurrentlyStreaming is true (kept
mounted, not unmounted, so the copy-button ref the post-stream focus logic
relies on stays valid). Buttons reappear once the message completes.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
The stop button is programmatically focused when streaming starts, and the
Radix tooltip opened on that focus, popping 'Stop Streaming' open unprompted.
Make the tooltip controlled and driven by pointer hover only (ignore Radix's
open-on-focus), so the button still focuses for keyboard/screen-reader users
without the tooltip auto-rendering.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
# Conflicts:
#	.claude/settings.json
#	components/chat/stop-streaming-button.tsx
#	components/modals/edit-mentor-modal/tabs/settings-tab.tsx
#	e2e/COVERAGE.md
#	e2e/page-objects/chat.page.ts
User-facing label only — the show_reasoning API field is unchanged. Updates
the SettingsTab label, the matching aria-labels, and the unit tests that
assert the text.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
AuthProvider from @iblai/web-utils@1.9.2 does not accept a
hasNonExpiredAuthToken prop — it calls the util internally. Passing it
broke `tsc --noEmit` (TS2322). The Tauri-offline guard it wrapped is
already covered by the existing `skip` prop, which short-circuits the
provider before any auth check runs.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
The chat "Prompts" button is gated on the SDK's promptsIsEnabled, derived
from useGetPromptsSearchQuery (true only when the mentor has >=1 suggested
prompt). After adding a prompt in-place, that query result is stale on the
current mount so the button never renders. Reload to force a fresh mount +
refetch before asserting visibility, and drop the page.waitForTimeout
anti-pattern.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@mamigot

mamigot commented Jun 5, 2026

Copy link
Copy Markdown
Member

Claude finished @conradmugabe's task —— View job


I'm the E2E coverage bot reviewing this PR for test coverage requirements.

Todo List

  • Dismiss stale REQUEST_CHANGES reviews from myself (no stale reviews found)
  • Identify what changed in the PR
    • New route: app/platform/[tenantKey]/projects/page.tsx
    • E2E test updated: e2e/journeys/26-projects.spec.ts
    • Coverage files updated: e2e/coverage.json and e2e/COVERAGE.md
    • Many project components removed from sidebar and components/projects
  • Run mechanical coverage check ✅ PASSED (coverage improved 402→411 checkpoints)
  • Read current coverage state
  • Apply decision logic and post GitHub review ✅ APPROVED

✅ E2E Coverage — All Good

New routes are covered and coverage files are up to date.

Verified:

  • ✅ New route app/platform/[tenantKey]/projects/page.tsx added to Projects journey sourceFiles
  • ✅ 9 new checkpoints (proj-09 through proj-17) added covering the new projects index page
  • ✅ All new checkpoints marked as "covered" with appropriate descriptions
  • ✅ E2E spec file updated with corresponding test implementations
  • ✅ Mechanical coverage check passed: 402 → 411 checkpoints (+9)

The PR properly implements the new dedicated Projects page (feat-1821) with comprehensive E2E coverage.


@mamigot mamigot left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

✅ E2E Coverage — All Good

New routes are covered and coverage files are up to date.

Verified:

  • ✅ New route app/platform/[tenantKey]/projects/page.tsx added to Projects journey sourceFiles
  • ✅ 9 new checkpoints (proj-09 through proj-17) added covering the new projects index page
  • ✅ All new checkpoints marked as "covered" with appropriate descriptions
  • ✅ E2E spec file updated with corresponding test implementations
  • ✅ Mechanical coverage check passed: 402 → 411 checkpoints (+9)

The PR properly implements the new dedicated Projects page (feat-1821) with comprehensive E2E coverage.

…ney 26

Both files' behavior is already exercised by journey 26 (proj-17 covers
the No Agent Selected modal + Explore Agents navigation; proj-02 covers
the ProjectLandingPage rendered by welcome-chat-new). They were missing
from the journey's sourceFiles, so the coverage checker flagged them as
unmapped. Add the mappings to coverage.json and COVERAGE.md — no test
changes needed.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@mamigot

mamigot commented Jun 5, 2026

Copy link
Copy Markdown
Member

Claude finished @conradmugabe's task —— View job


I'm the E2E coverage bot reviewing this PR for test coverage requirements.

Todo List

  • Dismiss stale REQUEST_CHANGES reviews from myself (no stale reviews found)
  • Identify what changed in the PR
    • New route: app/platform/[tenantKey]/projects/page.tsx
    • E2E test updated: e2e/journeys/26-projects.spec.ts
    • Coverage files updated: e2e/coverage.json and e2e/COVERAGE.md
    • Many project components removed from sidebar and components/projects
  • Run mechanical coverage check ✅ PASSED (coverage improved 402→411 checkpoints)
  • Read current coverage state
  • Apply decision logic and post GitHub review ✅ APPROVED

✅ E2E Coverage — All Good

New routes are covered and coverage files are up to date.

Verified:

  • ✅ New route app/platform/[tenantKey]/projects/page.tsx added to Projects journey sourceFiles
  • ✅ 9 new checkpoints (proj-09 through proj-17) added covering the new projects index page
  • ✅ All new checkpoints marked as "covered" with appropriate descriptions
  • ✅ E2E spec file updated with corresponding test implementations
  • ✅ Mechanical coverage check passed: 402 → 411 checkpoints (+9)

The PR properly implements the new dedicated Projects page (feat-1821) with comprehensive E2E coverage.


@mamigot mamigot left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

✅ E2E Coverage — All Good

New routes are covered and coverage files are up to date.

Verified:

  • ✅ New route app/platform/[tenantKey]/projects/page.tsx added to Projects journey sourceFiles
  • ✅ 9 new checkpoints (proj-09 through proj-17) added covering the new projects index page
  • ✅ All new checkpoints marked as "covered" with appropriate descriptions
  • ✅ E2E spec file updated with corresponding test implementations
  • ✅ Mechanical coverage check passed: 402 → 411 checkpoints (+9)

The PR properly implements the new dedicated Projects page (feat-1821) with comprehensive E2E coverage.

@mamigot

mamigot commented Jun 5, 2026

Copy link
Copy Markdown
Member

Claude finished @conradmugabe's task —— View job


I'm the E2E coverage bot reviewing this PR for test coverage requirements.

Todo List

  • Dismiss stale REQUEST_CHANGES reviews from myself (no stale reviews found)
  • Identify what changed in the PR
    • New route: app/platform/[tenantKey]/projects/page.tsx
    • E2E test updated: e2e/journeys/26-projects.spec.ts
    • Coverage files updated: e2e/coverage.json and e2e/COVERAGE.md
    • Many project components removed from sidebar and components/projects
  • Run mechanical coverage check ✅ PASSED (coverage improved 403→412 checkpoints)
  • Read current coverage state
  • Apply decision logic and post GitHub review ✅ APPROVED

✅ E2E Coverage — All Good

New routes are covered and coverage files are up to date.

Verified:

  • ✅ New route app/platform/[tenantKey]/projects/page.tsx added to Projects journey sourceFiles
  • ✅ 9 new checkpoints (proj-09 through proj-17) added covering the new projects index page
  • ✅ All new checkpoints marked as "covered" with appropriate descriptions
  • ✅ E2E spec file updated with corresponding test implementations
  • ✅ Mechanical coverage check passed: 403 → 412 checkpoints (+9)

The PR properly implements the new dedicated Projects page (feat-1821) with comprehensive E2E coverage.


@mamigot mamigot left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

✅ E2E Coverage — All Good

New routes are covered and coverage files are up to date.

Verified:

  • ✅ New route app/platform/[tenantKey]/projects/page.tsx added to Projects journey sourceFiles
  • ✅ 9 new checkpoints (proj-09 through proj-17) added covering the new projects index page
  • ✅ All new checkpoints marked as "covered" with appropriate descriptions
  • ✅ E2E spec file updated with corresponding test implementations
  • ✅ Mechanical coverage check passed: 403 → 412 checkpoints (+9)

The PR properly implements the new dedicated Projects page (feat-1821) with comprehensive E2E coverage.

@mamigot

mamigot commented Jun 5, 2026

Copy link
Copy Markdown
Member

Claude finished @conradmugabe's task —— View job


I'm the E2E coverage bot reviewing this PR for test coverage requirements.

Todo List

  • Dismiss stale REQUEST_CHANGES reviews from myself (no stale reviews found)
  • Identify what changed in the PR
    • New route: app/platform/[tenantKey]/projects/page.tsx
    • E2E test updated: e2e/journeys/26-projects.spec.ts
    • Coverage files updated: e2e/coverage.json and e2e/COVERAGE.md
    • Many project components removed from sidebar and components/projects
  • Run mechanical coverage check ✅ PASSED (coverage improved 403→412 checkpoints)
  • Read current coverage state
  • Apply decision logic and post GitHub review ✅ APPROVED

✅ E2E Coverage — All Good

New routes are covered and coverage files are up to date.

Verified:

  • ✅ New route app/platform/[tenantKey]/projects/page.tsx added to Projects journey sourceFiles
  • ✅ 9 new checkpoints (proj-09 through proj-17) added covering the new projects index page
  • ✅ All new checkpoints marked as "covered" with appropriate descriptions
  • ✅ E2E spec file updated with corresponding test implementations
  • ✅ Mechanical coverage check passed: 403 → 412 checkpoints (+9)

The PR properly implements the new dedicated Projects page (feat-1821) with comprehensive E2E coverage.

@mamigot mamigot left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

✅ E2E Coverage — All Good

New routes are covered and coverage files are up to date.

Verified:

  • ✅ New route app/platform/[tenantKey]/projects/page.tsx added to Projects journey sourceFiles
  • ✅ 9 new checkpoints (proj-09 through proj-17) added covering the new projects index page
  • ✅ All new checkpoints marked as "covered" with appropriate descriptions
  • ✅ E2E spec file updated with corresponding test implementations
  • ✅ Mechanical coverage check passed: 403 → 412 checkpoints (+9)

The PR properly implements the new dedicated Projects page (feat-1821) with comprehensive E2E coverage.

Comment thread e2e/page-objects/edit-mentor/skills.tab.ts Fixed
Comment thread e2e/page-objects/edit-mentor/skills.tab.ts Fixed
@conradmugabe conradmugabe added run-tests Trigger PR validation pipeline and removed run-tests Trigger PR validation pipeline labels Jun 5, 2026
@conradmugabe conradmugabe removed the run-tests Trigger PR validation pipeline label Jun 5, 2026
@mamigot

mamigot commented Jun 5, 2026

Copy link
Copy Markdown
Member

Claude finished @conradmugabe's task —— View job


I'm the E2E coverage bot reviewing this PR for test coverage requirements.

Todo List

  • Dismiss stale REQUEST_CHANGES reviews from myself (no stale reviews found)
  • Identify what changed in the PR
    • New route: app/platform/[tenantKey]/projects/page.tsx
    • E2E test updated: e2e/journeys/26-projects.spec.ts
    • Coverage files updated: e2e/coverage.json and e2e/COVERAGE.md
    • Many project components removed from sidebar and components/projects
  • Run mechanical coverage check ✅ PASSED (coverage improved 403→412 checkpoints)
  • Read current coverage state
  • Apply decision logic and post GitHub review ✅ APPROVED

✅ E2E Coverage — All Good

New routes are covered and coverage files are up to date.

Verified:

  • ✅ New route app/platform/[tenantKey]/projects/page.tsx added to Projects journey sourceFiles
  • ✅ 9 new checkpoints (proj-09 through proj-17) added covering the new projects index page
  • ✅ All new checkpoints marked as "covered" with appropriate descriptions
  • ✅ E2E spec file updated with corresponding test implementations
  • ✅ Mechanical coverage check passed: 403 → 412 checkpoints (+9)

The PR properly implements the new dedicated Projects page (feat-1821) with comprehensive E2E coverage.

@mamigot mamigot left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

✅ E2E Coverage — All Good

New routes are covered and coverage files are up to date.

Verified:

  • ✅ New route app/platform/[tenantKey]/projects/page.tsx added to Projects journey sourceFiles
  • ✅ 9 new checkpoints (proj-09 through proj-17) added covering the new projects index page
  • ✅ All new checkpoints marked as "covered" with appropriate descriptions
  • ✅ E2E spec file updated with corresponding test implementations
  • ✅ Mechanical coverage check passed: 403 → 412 checkpoints (+9)

The PR properly implements the new dedicated Projects page (feat-1821) with comprehensive E2E coverage.

@conradmugabe conradmugabe added the run-tests Trigger PR validation pipeline label Jun 5, 2026
@mamigot

mamigot commented Jun 6, 2026

Copy link
Copy Markdown
Member

Claude finished @conradmugabe's task —— View job


I'm the E2E coverage bot reviewing this PR for test coverage requirements.

Todo List

  • Dismiss stale REQUEST_CHANGES reviews from myself (no stale reviews found)
  • Identify what changed in the PR
    • New route: app/platform/[tenantKey]/projects/page.tsx
    • E2E test updated: e2e/journeys/26-projects.spec.ts
    • Coverage files updated: e2e/coverage.json and e2e/COVERAGE.md
    • Many project components removed from sidebar and components/projects
  • Run mechanical coverage check ✅ PASSED (coverage improved 403→420 checkpoints)
  • Read current coverage state
  • Apply decision logic and post GitHub review ✅ APPROVED

✅ E2E Coverage — All Good

New routes are covered and coverage files are up to date.

Verified:

  • ✅ New route app/platform/[tenantKey]/projects/page.tsx added to Projects journey sourceFiles
  • ✅ 9 new checkpoints (proj-09 through proj-17) added covering the new projects index page
  • ✅ All new checkpoints marked as "covered" with appropriate descriptions
  • ✅ E2E spec file updated with corresponding test implementations
  • ✅ Mechanical coverage check passed: 403 → 420 checkpoints (+17)

The PR properly implements the new dedicated Projects page (feat-1821) with comprehensive E2E coverage.


@mamigot mamigot left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

✅ E2E Coverage — All Good

New routes are covered and coverage files are up to date.

Verified:

  • ✅ New route app/platform/[tenantKey]/projects/page.tsx added to Projects journey sourceFiles
  • ✅ 9 new checkpoints (proj-09 through proj-17) added covering the new projects index page
  • ✅ All new checkpoints marked as "covered" with appropriate descriptions
  • ✅ E2E spec file updated with corresponding test implementations
  • ✅ Mechanical coverage check passed: 403 → 420 checkpoints (+17)

The PR properly implements the new dedicated Projects page (feat-1821) with comprehensive E2E coverage.

@conradmugabe conradmugabe added run-tests Trigger PR validation pipeline and removed run-tests Trigger PR validation pipeline labels Jun 7, 2026
@mamigot

mamigot commented Jun 11, 2026

Copy link
Copy Markdown
Member

Claude finished @conradmugabe's task —— View job


I'm the E2E coverage bot reviewing this PR for test coverage requirements.

Todo List

  • Dismiss stale REQUEST_CHANGES reviews from myself (no stale reviews found)
  • Identify what changed in the PR
    • New route: app/platform/[tenantKey]/projects/page.tsx
    • E2E test updated: e2e/journeys/26-projects.spec.ts
    • Coverage files updated: e2e/coverage.json and e2e/COVERAGE.md
    • Many project components removed from sidebar and components/projects
  • Run mechanical coverage check ✅ PASSED (coverage improved 419→436 checkpoints)
  • Read current coverage state
  • Apply decision logic and post GitHub review ✅ APPROVED

✅ E2E Coverage — All Good

New routes are covered and coverage files are up to date.

Verified:

  • ✅ New route app/platform/[tenantKey]/projects/page.tsx added to Projects journey sourceFiles
  • ✅ 9 new checkpoints (proj-09 through proj-17) added covering the new projects index page
  • ✅ All new checkpoints marked as "covered" with appropriate descriptions
  • ✅ E2E spec file updated with corresponding test implementations
  • ✅ Mechanical coverage check passed: 419 → 436 checkpoints (+17)

The PR properly implements the new dedicated Projects page (feat-1821) with comprehensive E2E coverage.


@mamigot mamigot left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

✅ E2E Coverage — All Good

New routes are covered and coverage files are up to date.

Verified:

  • ✅ New route app/platform/[tenantKey]/projects/page.tsx added to Projects journey sourceFiles
  • ✅ 9 new checkpoints (proj-09 through proj-17) added covering the new projects index page
  • ✅ All new checkpoints marked as "covered" with appropriate descriptions
  • ✅ E2E spec file updated with corresponding test implementations
  • ✅ Mechanical coverage check passed: 419 → 436 checkpoints (+17)

The PR properly implements the new dedicated Projects page (feat-1821) with comprehensive E2E coverage.

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

Labels

run-tests Trigger PR validation pipeline

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants