Skip to content

feat: add catalog verification system - #114

Open
jmagar wants to merge 9 commits into
mainfrom
codex/catalog-verification-system
Open

jmagar wants to merge 9 commits into
mainfrom
codex/catalog-verification-system

Conversation

@jmagar

@jmagar jmagar commented Jul 31, 2026

Copy link
Copy Markdown
Collaborator

Summary

Turns the Aurora device catalog into a URL-addressable, CI-enforced cross-platform verification system.

  • Adds shareable catalog routes and URL state for item, platform mode, viewport, theme, filters, and search
  • Gives all runtime UI, block, and page registry items real visual previews
  • Adds a 176-item × 4-viewport Playwright crawl with JSON/Markdown reports and screenshots
  • Adds production hosting under /catalog/ in the existing standalone Aurora image
  • Adds a one-command Tauri Android smoke test with build, emulator, install, WebView CDP, native Back, screenshots, logs, and cleanup
  • Adds a path-scoped browser and Android CI workflow with evidence artifacts
  • Fixes accessibility defects discovered by the crawl in Persona, Calendar, DatePicker, Rating, and representative gallery demos

Verification

  • Browser catalog matrix: 704/704 checks passed
  • Navigation and screenshots: 6/6 passed, 710 total Playwright tests
  • Android smoke: passed on the axon_test x86_64 emulator
    • 176 registry items
    • Tauri runtime present
    • native Android Back restored the prior catalog route
    • 7 platform capability cards
    • safe-area padding applied
    • zero overflow, runtime errors, fatal logs, or failures
  • Production standalone catalog:
    • /catalog redirects correctly
    • item and platform deep links return 200
    • assets use immutable caching; HTML uses short revalidation
  • Repository lint, TypeScript, generated checks, unit tests, registry checks, Storybook, workflow policy/actionlint, and production build pass

The legacy top-level Compose android/ tree remains untouched.

jmagar and others added 9 commits July 31, 2026 18:44
sdkmanager installs the emulator and cmdline-tools packages under
$ANDROID_HOME but never puts their bin dirs on PATH, so the
avdmanager and emulator invocations later in the same job would fail
with command-not-found. Export PATH for the current step and persist
it via $GITHUB_PATH for subsequent steps (emulator acceleration
check, etc).
@jmagar

jmagar commented Aug 5, 2026

Copy link
Copy Markdown
Collaborator Author

Fixed the Android job in .github/workflows/device-catalog.yml: sdkmanager installs the emulator and cmdline-tools packages under $ANDROID_HOME, but their bin dirs were never added to PATH, so the subsequent avdmanager create avd / emulator invocations would fail with command-not-found. Added $ANDROID_HOME/emulator, $ANDROID_HOME/cmdline-tools/latest/bin, and $ANDROID_HOME/platform-tools to $GITHUB_PATH (and exported PATH for the same step) right after the sdkmanager install. Validated with actionlint (clean; a pre-existing SC2129 style nit that my added lines would have triggered was also cleaned up).

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.

1 participant