1636d6bada
Turns the single-serial-worker scheduler into a capacity-aware, multi-lane one. Configured team members become lanes; an issue runs on its assignee's lane (or the earliest-free lane), its duration scaled by that lane's throughput (focusFactor × allocation). Every forecast — Focus cone, Runway, milestone drill-in — is now capacity-aware. core (@commitea/core): - capacity/capacity-v0: CapacityMember + capacityPerWorkday + parseCapacityConfig (clamps, drops invalid; degrades to []). - scheduler/scheduler-capacity-v0: scheduleWithCapacity reuses the v0 topo order + critical path, re-lays work across lanes (layoutOnLanes, resolveLanes, makespan). Empty workers → the single serial plan verbatim. - forecast() gains options.workers: each MC trial lays sampled durations across the lanes and takes the makespan; serial path unchanged. SchedulableIssue gains assignee; ScheduledItem gains worker. - 11 new tests (parse/clamp, parallelism halves makespan, speed scaling, assignee routing, cross-lane deps, forecast makespan shrinks with lanes). app: - pm-state capacity/members.json read (readCapacity + pmstate:capacity bridge); useCapacity hook → workers; forecastBacklog/runwayView/milestoneView pass workers. - Runway Capacity card shows the real config (person · focus · alloc · pd/day). Config lives in pm-state (D4); seeded christian(0.8)/stephen(0.6×0.5). Degrades to the fixture/serial when absent. Verified: 128 core tests green, desktop typecheck clean, 14 fixture e2e green. Live: the capacity card is real, and the P2 forecast shifts 32d→37d — honest, since real focus factors (<1) replace the v0 focus-1.0 assumption. 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