2ad6721e94
Add an append-only execution ledger with one fold task every 5 seconds. Participants fold claimed rows in one transaction: workflow statistics, execution quota usage, and Insights hourly buckets. Add hard execution quotas per workflow and project. An atomic Redis or memory counter admits a run, and the started row commits with the execution row. Postgres and SQLite are both supported. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| insights | ||
| instance-registry/frontend | ||
| mcp/frontend | ||
| otel/frontend | ||
| quick-connect/backend | ||
| type-availability-policies/frontend | ||
| README.md | ||
Modules
Feature modules carved out of packages/frontend/editor-ui. Each one is a workspace package at
<name>/frontend: source-only (main: "src/index.ts", no dist), consumed by the editor-ui shell
through Vite aliases.
Backend modules can be built workspace packages at <name>/backend. Add each packaged backend
module to packages/cli/src/modules/modules.manifest.ts. The manifest uses lazy imports so a
disabled module does not load its package. Backend modules that have not moved to a package still
load from packages/cli/src/modules/<name>.
packages/modules itself stays tracked even when it holds nothing: turbo rejects a --filter
whose directory does not exist.
CI splits the two halves by path. The frontend jobs select packages/modules/*/frontend. The backend
jobs exclude that same path instead of all of packages/modules, so a <name>/backend package gets
backend CI on the day it appears. Both filters live in the root test:ci:* scripts and in the two
backend jobs in .github/workflows/test-unit-reusable.yml.