Skip to content

About

Controller-driven LapisMD maintenance dashboard — reviewed in Storybook slices

Resources

Stars

0 stars

Watchers

0 watching

Forks

Latest commit

 

History

56 Commits

Folders and files

NameName
Last commit message
Last commit date
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Lapis Maintenance

CI App Storybook License: AGPL v3

A maintenance inbox for GitHub repositories. See pull requests that need review, failed builds and approval waits in one place, then act on the current revision. Built with Svelte 5, Design Core and Repository UI.

Open the app · Explore Storybook

What it does

  • An inbox, Kanban board and activity view across your selected repositories.
  • Search, multiple repository/status filters, grouped linked checks and a PR workspace with Overview, Checks and lazy Activity tabs.
  • PR reviews, merges, draft readiness, workflow approvals, reruns and cancellation, with one-click activation and current-target verification.
  • Environment approval/rejection and manual workflow dispatch with typed inputs, explicit branch/tag selection and one submission bound to the commit/definition.
  • GitHub's repository rules and permissions remain authoritative. Dispatch and review acceptance are reported separately from workflow/publication success.

Open Run workflow in the header to choose a repository, an active manual workflow, and an explicit branch or tag. The app reads its declared input schema and rechecks the commit and definition before submitting once. The repository's Maintenance action acceptance workflow is a no-op for designated test environments; it never checks out code, reads secrets or publishes.

Connect GitHub

Enter a personal access token in the app. Requests go directly from your browser to GitHub; there is no application server. Fine-grained tokens cover one resource owner, and inaccessible repositories are shown explicitly.

Use repository read access for metadata, pull requests, checks, commit statuses, Actions and environments. Actions require Pull requests write, Contents write for merges, Actions write for workflows, and Deployments write plus eligible environment-reviewer status for protected environment reviews. Manage GitHub tokens.

“Remember token on this device” stores the token in this browser, separately from repository data. Use Disconnect in the profile menu to remove it and clear the active cache. Only remember a token on a device you trust.

Online remembered sessions show cached cards while GitHub validates the saved token. The preview is read-only until authentication succeeds. Existing saved logins validate once after this update to remember the identity needed for this startup path. Offline startup continues to show the reconnect screen.

Repository reads use a token-partitioned Turso WASM database with five-minute freshness, conditional requests, bounded storage and rate-limit backoff. Fresh cached details open immediately; manual refresh revalidates them. GitHub actions always re-read their target. Cached cards remain visible during background refresh, with an indicator on cards being re-fetched. Where Turso cannot start, a bounded IndexedDB cache preserves data across reloads; memory is the final fallback if both persistent stores are unavailable.

The saved board is an attention queue: open PRs, failures, approvals, blocked, running and unavailable work. Confirmed successful or cancelled workflows are removed; passing PRs remain until merged or closed. Complete repository refreshes remove resolved identities and their cached details from all saved selections. PR and workflow inventories establish completeness independently, so unrelated optional-resource failures do not block verified cleanup. Partial inventories and uncertain action outcomes do not prove that work is resolved.

All tokens share one Turso store and one IndexedDB store, each limited to 12.5 MiB and 1,000 records, with a 1 MiB limit per record including its key. Their combined serialized payload budget is 25 MiB; database/index/WAL and browser overhead are additional. Records expire after 24 hours, with cleanup during reads, writes and minute maintenance. Active legacy caches migrate through this policy; expired inactive legacy stores are removed when unlocked. Each memory fallback is capped at 25 MiB/1,000 records, and synchronous detail/resource previews at 5 MiB/100 entries per preview cache. Historical Activity and raw workflow/GraphQL inventories use only a 2 MiB, 100-response, five-minute session cache. Compact branch-health summaries remain available independently. These limits exclude the public offline app assets.

Install the app

Open the live app, then choose Install app when offered or use your browser's install menu. Chrome and Edge support installation from the address bar. In Safari on macOS, use File → Add to Dock; on iPhone/iPad, use Share → Add to Home Screen.

The installed app opens in its own window. Offline startup shows a reconnect screen; GitHub data and actions require a connection. The service worker caches only public app assets, separately from the remembered token and Turso database. It excludes authenticated responses, repository data and Storybook.

When a new version is ready, choose the Update arrow. Updates wait so they do not interrupt forms or running commands. Installation and storage are per browser profile and origin.

Development

Use Node 24.15.0 and pnpm 10.34.5.

pnpm install --frozen-lockfile
pnpm dev          # app: http://127.0.0.1:7511
pnpm storybook    # fixtures: http://127.0.0.1:7510

The local-only Maintenance/Live → GitHub session story mounts the production host for manual token testing. It is excluded from hosted Storybook and automated tests. Never put real tokens in fixtures, args or screenshots.

pnpm check
pnpm test
pnpm exec playwright install chromium
pnpm test:browser
pnpm test:storybook
pnpm build
pnpm test:pwa
pnpm build-storybook
pnpm spec:check

The production build uses /lapis-maintenance/ and hash navigation. CI deploys checked main output and fixture-only Storybook to GitHub Pages. PWA tests serve the real build without server isolation headers and exercise offline startup, cache exclusions, installation metadata, legacy migration and deferred updates. Use pnpm pwa:icons to regenerate install icons from the Lapis vector logo.

Architecture and specifications

The host owns credentials, adapters, persistence and controller lifetime. MaintenanceController owns dashboard state; read and command ports allow the same screens to run against GitHub or disposable in-memory Storybook fixtures. Public Design Core and Repository UI components provide the shell, Kanban, profile, grouped checks and PR panels.

See the implementation plan, canonical specifications, verification map, component catalog and third-party notices. Work is delivered in reviewed slices.

License

AGPL-3.0-or-later.

About

Controller-driven LapisMD maintenance dashboard — reviewed in Storybook slices

Resources

Stars

0 stars

Watchers

0 watching

Forks

Releases

Packages

Contributors

Languages