be70c8607d
Replace the demo cone on Morning service with a real, seeded Monte Carlo forecast over the open backlog. The LLM never does this — it's plain, reproducible code (evidence-based scheduling). core (@commitea/core/forecast-v0): - Code-resident lognormal cold-start priors per estimate bucket (D3): sampled actual = estimate * exp(N(mu, sigma)), mu > 0 (actuals run long), sigma shrinks as tickets grow. Replaced by the team's empirical fit at n >= 20 (#5 supplies the actuals). - forecast(): seeded mulberry32 + Box-Muller over the scheduler's deterministic order (order is fixed from estimates/deps; only durations vary, so the cone stretches, never reorders). Returns p50/p80/p95 landing + a per-issue burn-up curve (p10/p50/p90). 12 unit tests; reproducible. renderer: - lib/dates.ts: working-day -> calendar mapper (skips weekends) + buildBurnUpData. - BurnUpCone gains a data-driven twin; falls back byte-identical to the fixture cone when no forecast (demo mode unchanged). - Focus card shows the real "80% of the open backlog lands by <range>", real scope count, and names the cold-start priors. v0 scope (each a later slice): single serial worker (capacity is #8); cold-start priors only (empirical fit is #5); no historical actual polyline (needs lifecycle events, #5). Header chrome (reconcile time, ahead/behind badge) stays fixture until milestone due dates land. Verified: 51 core tests green, desktop typecheck clean, 14 fixture e2e green, live spec asserts the real cone renders (25 open issues, "lands by Nov 11-27"). 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