Skip to content

fix(webui): repair file opening, panel interactions and CI diagnostics - #36

Merged
Fectivnfy112357 merged 3 commits into
mainfrom
fix/transcript-file-opening
Nov 11, 2026
Merged

Fectivnfy112357 merged 3 commits into
mainfrom
fix/transcript-file-opening

Conversation

@Fectivnfy112357

@Fectivnfy112357 Fectivnfy112357 commented Nov 11, 2026 •

Copy link
Copy Markdown
Contributor

Change

Fix WebUI file opening and interaction regressions, and preserve browser diagnostics across CI steps.

  • Open explicit file references outside the workspace through the correct file/media route, keep file icons aligned with their labels, and align inline references with surrounding text.
  • Dismiss shared dialogs on backdrop clicks by default, wire local service shutdown to the server lifecycle, and keep the subscription label stable while hovering account menu items.
  • Align the session rail separators and size environment/progress sections to their contents while retaining the shared disclosure animation.
  • Give unit/integration, browser, and package diagnostics separate directories. Keep Playwright output and font caches outside those directories so later steps cannot erase or overwrite earlier evidence. Addresses the CI evidence-preservation portion of [Bug]: the agent-transcript case fails on the Windows runner and the failure leaves no evidence behind #32; this does not claim to fix the intermittent Windows first-frame failure.
  • Isolate permission test workspaces from the host temporary-directory location, update the backdrop-dismissal assertion, and refresh 15 reviewed Linux screenshot baselines for the accepted rail/progress layout.
  • Carry the existing WebUI package version update to 0.1.8.

The proposed public loading redesign is deferred and is not included.

Validation

  • Previously completed full Linux run: WebUI 302 files / 4,533 tests passed; capabilities 298 files / 6,478 tests passed, 18 skipped. The browser/policy failures from that run were repaired.
  • Failed cases rerun after repair: 16/16 browser cases passed with screenshot updates disabled; 2/2 permission cases passed with the original permission expectations retained.
  • pnpm check:source, git diff --check, pnpm build:webui: passed.
  • A fresh CI=true pnpm verify on committed head c07dcdcbf was stopped at the author's request. Source export, release tools, lint, type checks, builds, WebUI architecture gates, and package installation passed before stopping. This is not a full-green claim. The PR's Ubuntu/macOS/Windows CI checks run independently.
  • Local WebUI service restarted; root and client resources returned HTTP 200 and the WebSocket version operation succeeded.
  • Performance: basic; no performance optimization or history/storage/streaming execution change.
  • NOT RUN: Windows/macOS validation and the Windows CI flake reproduction. Browser interaction and screenshot results use the built-client fixture, not external-provider or live-account acceptance. Source release-archive validation requires a release archive.

Publication and contribution checks

  • Changes are submitted under the existing applicable licenses; no imported third-party material is added.
  • No credentials, account data, real user content, internal source history, or private review material is included.
  • No source files or Vitest suites were added or removed; source inventory validation passed.
  • Relevant behavior documentation and regression expectations are updated. Fixture results are not described as live-service acceptance.

Maintainer handoff

Publication scope and license changes: none.

Shared-source port: pending maintainer assessment for the permission-test fixture change; WebUI-specific changes remain in this fork. Independent review and CI approval remain required before merge.

- Updated package.json version from 0.1.7 to 0.1.8
- Parse absolute paths in file references regardless of workspace boundary
- Add absoluteFileLocation helper for directory-scoped file reads
- Render delivered assets with file-type icon from source filename
- Align inline file link labels to surrounding prose baseline
- Use WebuiInline for delivered asset icon-label grouping
- Accept outside-workspace links in markdown anchor rendering
- Default dialog backdrop dismiss to true instead of false
- Add HTTP shutdown endpoint with authenticated request handling
- Separate Playwright output dir from font cache directory
- Update transcript rendering and design docs
- Add integration and browser tests for new behaviors
@Fectivnfy112357 Fectivnfy112357 added the bug Something isn't working label Nov 11, 2026
@Fectivnfy112357
Fectivnfy112357 marked this pull request as ready for review November 11, 2026 09:15
@Fectivnfy112357
Fectivnfy112357 merged commit 5b4cb46 into main Nov 11, 2026
1 of 3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant