Croissant Le Doux 94199639f2 feat: read the real gitea backlog into the app (P1 thin slice)
The app now displays its own live backlog instead of fixtures. First
end of the sync loop — the tap-root (#1) grows list reads and a read
path through the Electron main process.

- @commitea/core: client gains `listIssues` (paginated, PRs excluded)
  and `listMilestones`; a `lifecycle-v0` mapper (closed→done,
  labelled/milestoned→triage, bare→diagnosis — steeping/review await
  event inference in P1-5). +10 unit tests.
- main: gitea bridge over IPC (token stays in main, never the renderer);
  config from env / .env.local; gated off under COMMITEA_E2E so the
  committed e2e stays on fixtures. Preload exposes the typed bridge.
- renderer: useBacklog() reconciles once on mount; issuesToBoardColumns
  shapes real issues into The pot. Board takes optional real columns +
  a loading state, falling back to demo fixtures when unconfigured.

Verified: 14 e2e green (fixture mode) + a gated live spec that launches
against the real repo — the board renders the actual 25 open + 9 closed
issues (screenshot). SQLite mirror + reconcile-on-a-timer + lifecycle
event inference are the next slices (#2/#3/#5).

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-07-08 16:57:57 -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%