Skip to content

fix: Home estimate label, Get started card, Activity conflict clear and status-coloured health (Spec fix-ux-residuals) - #1467

Merged
github-actions[bot] merged 6 commits into
mainfrom
fix-ux-residuals-final
Oct 2, 2026
Merged

github-actions[bot] merged 6 commits into
mainfrom
fix-ux-residuals-final

Conversation

@Dumbris

@Dumbris Dumbris commented Oct 2, 2026

Copy link
Copy Markdown
Member

The last open items of the Spec 109 done check, fixed test-first inside the files Spec 109 owns (Home, Activity, Server Detail, macOS Home). There is no backend change, no new dependency and no golden change.

What changes for the user

Web UI Home

  • The hub chip, the Token Savings Details stat and the details title badge now say "estimate" while the core reports an estimated figure, the same wording Usage already used. Once a real retrieve_tools call has been observed the markers disappear.
  • A fresh instance with no server configured shows a "Get started" card (Add a server, Connect a client, Run setup wizard) in place of the green "All clear" banner, and the top usage strip is hidden. Any attention item still wins, and nothing flashes before the server list has loaded. mcpproxy attention still prints "All clear".

Web UI Activity

  • "Clear filters" on the server/tool conflict banner now refetches once and shows rows instead of leaving "No activity records found". Removing either conflicting chip does the same.
  • The Tool calls "N blocked" chip names refused attempts and opens the blocked rows. An empty Tool calls table with blocked attempts in the window offers "Show N blocked attempts". The Events tile reads "1 call" instead of "1 calls".

Web UI Server Detail

  • The header badge, the Health tile and the Configuration Health badge colour by health status, never by level. A quarantined server reads "Needs review" in warning on all three instead of a green badge beside a grey "Blocked". A disabled server reads "Disabled" in grey. A payload without status (an older core) renders as before.

macOS app

  • The Home hub badge shows the same "estimate" capsule as the Token Savings card, through a shared presentation so the two cannot drift.

CLI, REST and MCP are unchanged.

Audit findings

  • Done-check item C (estimate label) and issue 1394 item 1.
  • Done-check item D (Activity clear filters, blocked attempts, "1 calls") and issue 1394 item 2.
  • Done-check item E (health colour by status).
  • Fresh-instance Home false "All clear".

Spec and tests

Spec: specs/109-ux-navigation-consistency (tasks T166 to T171, research D36, spec.md US1-4, FR-051, FR-070, FR-073, url-filter-contract, health-vocabulary, parity row 22, acceptance index, quickstart recipe fix-ux-residuals, docs/web-ui/dashboard.md).

New tests: home-token-savings-estimate, home-getting-started, activity-scope-conflict-clear, activity-blocked-in-calls-view and server-detail-health-status-colour (vitest), and HomeTokenSavingsBadgeTests (XCTest). home-attention was updated to use a configured server. Full vitest, vue-tsc, the frontend build, the full swift test suite and the Spec 109 traceability and parity Go tests pass.

Left for follow-up issues: refused attempts in the default Tool calls view across Web, macOS and CLI together; the "1 calls" label on the profile card (Spec 108); sharing the status-to-tone map and the estimate tooltip; a macOS Home getting-started card.

Refs #1394 (items 1 and 2 are fixed here; the low items stay open).

@cloudflare-workers-and-pages

cloudflare-workers-and-pages Bot commented Oct 2, 2026 •

Copy link
Copy Markdown

Deploying mcpproxy-docs with  Cloudflare Pages  Cloudflare Pages

Latest commit: 4ec9ce7
Status: ✅  Deploy successful!
Preview URL: https://1a84d918.mcpproxy-docs.pages.dev
Branch Preview URL: https://fix-ux-residuals-final.mcpproxy-docs.pages.dev

View logs

F1.1 (confirmed): removing a conflicting server/tool chip, or Clear filters,
with a profile/client/token scope in the URL sent two requests, the first
without the scope. The conflicting URL made toRest() return null, so the scope
dropped out of the request until the router.replace settled and the scope key
changed. profile/client/token do not depend on the server/tool pair, so
Activity now reads them with toRest({ ignoreConflict: true }); the scope key
no longer flips on conflict resolution and the single refetch carries it.
loadActivities() still issues nothing while scopeConflict is set.
@github-actions

github-actions Bot commented Oct 2, 2026 •

Copy link
Copy Markdown
Contributor

📦 Build Artifacts

Workflow Run: View Run
Branch: fix-ux-residuals-final

Available Artifacts

  • archive-darwin-amd64 (31 MB)
  • archive-darwin-arm64 (28 MB)
  • archive-linux-amd64 (19 MB)
  • archive-linux-arm64 (17 MB)
  • archive-windows-amd64 (31 MB)
  • archive-windows-arm64 (27 MB)
  • frontend-dist-pr (0 MB)
  • installer-dmg-darwin-amd64 (27 MB)
  • installer-dmg-darwin-arm64 (24 MB)
  • smart-mcp-proxymcpproxy-goN1NFO1.dockerbuild (0 MB)

How to Download

Option 1: GitHub Web UI (easiest)

  1. Go to the workflow run page linked above
  2. Scroll to the bottom "Artifacts" section
  3. Click on the artifact you want to download

Option 2: GitHub CLI

gh run download 37012258733 --repo smart-mcp-proxy/mcpproxy-go

Note: Artifacts expire in 14 days.

@codecov-commenter

Copy link
Copy Markdown

⚠️ Please install the 'codecov app svg image' to ensure uploads and comments are reliably processed by Codecov.

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

@github-actions github-actions Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Approved (Model B): Paperclip review verdicts = ACCEPT and qa-gate green at this head SHA. Arming auto-merge; GitHub merges when all required checks pass.

@github-actions
github-actions Bot merged commit 10463f8 into main Oct 2, 2026
59 checks passed
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