Run the automated full-feature browser pass + UI consistency audit #642
Labels
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: Cordy/Cairn#642
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Reminder to run the on-demand automated test pass (agreed 2026-09-22). Feature-complete; UI polish ongoing — this pass validates both.
What exists
docs/testing/feature-matrix.md— the full-product test plan: ~90 rows across sign-in, files, details pane, sharing, OCM, peering, office/WebDAV, spaces, admin, and look-and-feel, each flagged UI / API / 2-user / manual.docs/design/style-guide.md— the consistency reference (tokens, type scale, component patterns, voice) with a "known drift" list as audit starters. Any screen contradicting it is a finding even when behaviour is correct.How to run
A Claude (Opus-class) Cowork session with browser tools, driving files.c0rdyceps.ch and files-bao.c0rdyceps.ch through the matrix top to bottom. Nikola pre-signs sessions for sharer1/sharer2 (Claude cannot enter passwords); API rows use app-passwords via rclone/curl from the CI runner. UI consistency rows work from screenshots of each major surface compared against the style guide — including misaligned, out-of-shape, or missing elements, all four themes, and i18n x4.
Rules
One-time add-on: OpenCloud comparison (first run only)
Walk https://demo.opencloud.eu/ side by side with Cairn — same journeys, surface by surface (files list, right pane/details, sharing, links, search, spaces, admin where visible, mobile widths). Collect everything OpenCloud has that Cairn lacks or does differently: features, affordances, micro-interactions, layout ideas, empty states, wording. Do NOT cut one issue per gap; cut ONE consolidated finding titled "OpenCloud comparison — candidate gaps and ideas", grouped by area, each entry with a screenshot pair (theirs/ours) and a one-line note on what it buys the user. That single issue then feeds a separate decision run where Nikola picks what Cairn actually wants — a gap is only a candidate, not automatically a defect. This section applies to the first run only; drop it from subsequent runs.
Closed as superseded by #656. The first Opus attempt surfaced six operational gaps these instructions never answered (per-host session limits, screenshot upload, runner access for API rows, test-data hygiene, OpenCloud login, ordering). #656 re-cuts the brief with all six decided, and adds two scope changes: the admin dashboard is scouted in full (nikola-test as the admin login), and the OpenCloud demo is signed into directly since its credentials are displayed publicly on the login screen.