73643efcbc
The cache is a rebuildable index over gitea, never a source of truth (D4). Two tests lock that invariant where the durable cache actually lives: - packages/core: cache-purity-v0.test.ts — file-backed node:sqlite. Build the SQLite mirror from a gitea snapshot, capture every re-derived field, delete the .sqlite file, rebuild from the same snapshot, assert byte-identical. Plus a structural D4 guard: every issues-table column must map to a gitea field, so a future user-authored column can't silently break rebuild-ability. - apps/desktop: snapshot-store.test.ts — the shipped durable cache is the JSON snapshot-store. Delete the file → loadSnapshot returns null (degrades to no-cache, never throws), which is what forces the next getSnapshot to reconcile fresh from gitea. Corrupt/partial files are likewise treated as no-cache. Stands up vitest for the desktop main process (first unit tests there); electron is mocked, snapshot path is injected. No native better-sqlite3 shipped: the SQLite mirror has no consumer on any hot path yet, so wiring it into main (native module + asarUnpack + dmg re-verify) would add packaging risk for no runtime benefit. The purity invariant is proven at the seam for both caches; the native driver migration is deferred until SQLite becomes load-bearing. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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.htmlvia a static server), brand voice rules indesign_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;
.jsextensions on relative imports @commitea/corestays pure — unit-testable without Electron or network- Design tokens are the source of truth (
apps/desktop/src/renderer/src/design/, mirrored fromdocs/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