switchboard/core
Archived
1
0
Fork 0
Code Issues Pull Requests Actions Releases 9 Wiki Activity

Feat v0.6.14 visual polish #49

Merged
xcaliber merged 2 commits from feat/v0.6.14-visual-polish into main 2026-04-01 13:25:04 +00:00
Conversation 0 Commits 2 Files Changed 35 +17 -3
1 changed files with 17 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
Showing only changes of commit 56898dd875 - Show all commits

20
ROADMAP-UI.md
View File

@@ -91,7 +91,19 @@ Shipped. Stale fallback colors purged (~65 instances), fonts self-hosted
regressions (half-step tokens), theme settings default, surface overflow,
and user menu zoom drift. See CHANGELOG.md.
### v0.6.15 — Usability Survey Gate
### v0.6.15 — User Display Audit
Every place a user identity appears in the UI must show a human-readable
name, never a UUID. Fallback chain: `display_name → username → "Unknown"`.
| Step | Description |
|------|-------------|
| Participant display-name resolution | `chat-core` participants endpoint resolves `display_name` from the users table at query time instead of relying on a creation-time snapshot. If the stored `display_name` is empty, look up `users.display_name` or `users.username` by `participant_id`. |
| Audit all user-facing identity surfaces | Walk every surface that shows user identity: chat participant list, chat message sender names, chat typing indicators, workflow assignees, team member lists, admin user list, notification actor names. Ensure the fallback chain is `display_name → username → "Unknown"` everywhere. |
| SDK user-resolve utility | Add `sw.users.resolve(id)` or similar to the SDK — returns `{id, username, display_name, avatar}` with local caching. Surfaces use this instead of ad-hoc lookups. |
| Stale snapshot cleanup | Remove or deprecate the static `display_name` column in the participants table. All display names come from the users table via the resolve utility. |
### v0.6.16 — Usability Survey Gate
Make the UI machine-auditable so Claude Code can run an automated survey.
@@ -102,7 +114,7 @@ Make the UI machine-auditable so Claude Code can run an automated survey.
| Component coverage matrix | Markdown table: each kernel primitive (button, input, dropdown, dialog, toast, menu, tabs, avatar, spinner, tooltip, drawer, banner) × each surface that uses it. Identifies surfaces still using deprecated old-style components. |
| Touch target audit | Script that finds all `<button>`, `[role=button]`, clickable elements across templates and JS, checks for `min-width/min-height ≥ 44px` on mobile breakpoint. |
| Claude Code survey prompt | `docs/USABILITY-SURVEY.md` — structured prompt template that Claude Code can execute against the codebase. Sections: viewport correctness, banner integration, responsive behavior, styling consistency, accessibility basics (contrast, touch targets, focus indicators), component uniformity. Each section has pass/fail criteria and file paths to inspect. |
| Survey dry-run | Run the survey. Fix anything it catches. Tag `v0.6.15` only after clean survey. |
| Survey dry-run | Run the survey. Fix anything it catches. Tag `v0.6.16` only after clean survey. |
---
@@ -121,7 +133,9 @@ v0.6.13 Responsive & Spacing ✅ SHIPPED
↓
v0.6.14 Visual Polish ✅ SHIPPED
↓
v0.6.15 Usability Survey Gate ← Machine-audit the finished product
v0.6.15 User Display Audit ← No UUIDs in the UI, ever
↓
v0.6.16 Usability Survey Gate ← Machine-audit the finished product
```
Each version is independently shippable and testable. No version depends on