Local-first state
The page foregrounds local behavior and workspace continuity so visitors immediately understand that LabFlow is a real execution surface, not a mood board.
LabFlow turns workflow sprawl into a controlled terminal surface for tasks, sessions, memory, status, and doctor checks. Built around the real repo entry points, it stays aligned with the product you actually ship.
Current truth
The page speaks in operational language because LabFlow already has a real command surface, local state, and proof visibility. The copy is structured to reinforce what exists now rather than sell a fictional platform layer.
The page foregrounds local behavior and workspace continuity so visitors immediately understand that LabFlow is a real execution surface, not a mood board.
The central interaction is the command switcher because that is the cleanest way to visualize the system without inventing a dashboard that the repo does not promise.
Status, schema health, and doctor checks are presented as visible operating states. That strengthens the repo’s technical identity and lowers landing-page fluff.
Repo entry points
Why this matters
Core command surface
This section stays tightly aligned to the repo’s stable core so the homepage supports the CLI instead of competing with it.
Bootstrap or repair workspace state so the system starts cleanly.
Manage lightweight tasks without dragging users into dashboard overhead.
Track active work sessions and retain useful history for continuity.
Keep local notes and tags available for later execution context.
Expose workspace health, schema state, and proof visibility clearly.
Check environment basics and drift so issues surface before they spread.
Start locally
pnpm install
pnpm validate:manifest
pnpm generate:docs
pnpm verify:generated-docs
pnpm build
pnpm test
pnpm proof:verify
pnpm check:shell
pnpm release:readiness
Local CLI usage
pnpm exec labflow --help
pnpm exec labflow init
pnpm exec labflow task add "Ship release hardening"
pnpm exec labflow status --json
Deployment target
This package includes a GitHub Pages workflow because it is the cleanest deployment target for a static homepage sitting next to a public GitHub repo. It keeps hosting simple, reviewable, and low-friction.