Croissant Le Doux a04714bfa6 Kill screen fixtures: live/empty screens + one demo snapshot for e2e
The app is now fixture-free. All product screens render live data (via the
reconcile bridge + view builders) or an EmptyState — no hardcoded demo data,
metrics, or prose anywhere in the UI.

- Removed the `?? FIXTURE` fallbacks and embedded fake strings (fixed dates,
  'reconcile 3.2s', 'ahead of forecast', mock forecast prose) from all 10 product
  screens; each now shows an EmptyState when its live data is absent.
- directives-screen: fully live off pmstate.directives() (was seeded from a
  fixture with a fake consequence-diff card) — loading + empty states, no seed.
- use-chat: drop the CHAT seed (the model-status effect already sets the greeting).
- data/fixtures.ts → data/view-types.ts: stripped every const design fixture,
  kept only the view-model TYPES (the builder↔screen contract). Repointed imports.

Testing fixture (no live gitea), per the user's call:
- New apps/desktop/src/main/demo-snapshot.ts — one deterministic, gitea-shaped
  snapshot (issues/milestones/deps/timelines + capacity + directives + collaborators).
  Served by the reconcile/boot/collaborators/capacity/directives handlers when
  COMMITEA_E2E=1, so e2e renders it through the REAL builders with no token.
- smoke.spec rewritten to assert on the demo snapshot through the live render path;
  onboarding/offline-toggle assertions dropped (wizard is live → live-onboarding;
  offline is real state now). 12/12 smoke pass.

Verify: core tsc clean · desktop tsc clean · 12/12 smoke green (perf#32 benchmark
flakes under machine load — unrelated, passes in isolation).

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-07-10 13:21:47 -04:00

CommiTea

AI project manager built on Gitea. A deterministic scheduler does the math (Monte Carlo forecasts over your own estimate-vs-actual history); the agent — Reginald — captures work via interview, negotiates priorities, and explains the consequences. Gitea holds human-authored intent; a pm-state repo holds machine-derived state. The LLM never does math.

Structure

  • apps/desktop — Electron app (electron-vite, React, Tailwind)
  • packages/core — pure TypeScript: label schema, scheduler, gitea client (no Electron imports)
  • docs/PLAN.md — product plan (goals, phases, not-doing list)
  • docs/design/ — design handoff: tokens, component contracts, interactive prototype (docs/design/ui_kits/app/index.html via a static server), brand voice rules in design_system_readme.md

Development

yarn            # install
yarn dev        # electron app, logs tee to apps/desktop/desktop.log
yarn test       # unit tests (vitest)
yarn typecheck

End-to-end (Electron + Playwright)

yarn workspace @commitea/desktop e2e        # build, then drive the built app
yarn workspace @commitea/desktop e2e:only   # reuse existing out/ build (tight loop)
yarn workspace @commitea/desktop e2e:report # open the last HTML report

Tests launch the built app (out/main/index.js) through Playwright's _electron API — no browser project, no chromium download. Fixtures and page objects live in apps/desktop/e2e/; screenshots land in e2e/.artifacts/screens/ for visual review. Page objects use user-facing locators (getByRole/getByText), never CSS/DOM structure.

Conventions

  • Yarn 4 workspaces; ESM everywhere; .js extensions on relative imports
  • @commitea/core stays pure — unit-testable without Electron or network
  • Design tokens are the source of truth (apps/desktop/src/renderer/src/design/, mirrored from docs/design/); Tailwind maps onto the CSS custom properties, never redefines them
  • Reginald's voice rules live in docs/design/design_system_readme.md — no emoji, no point-date forecasts, wit in sentences never in buttons
Description
No description provided
Readme 2.6 MiB
Languages
TypeScript 97.8%
CSS 1.7%
JavaScript 0.4%