Skip to content

feat(apps): add execution tables to local + cloud drizzle schemas#10

Draft
aryasaatvik wants to merge 1 commit intofeat/trigger-propagation-cli-mcpfrom
feat/app-drizzle-schemas-executions
Draft

feat(apps): add execution tables to local + cloud drizzle schemas#10
aryasaatvik wants to merge 1 commit intofeat/trigger-propagation-cli-mcpfrom
feat/app-drizzle-schemas-executions

Conversation

@aryasaatvik
Copy link
Copy Markdown
Owner

Stacked review copy of upstream RhysSullivan#400 · stacked on RhysSullivan#399.

Prev: feat/trigger-propagation-cli-mcp
Next: feat/api-executions-list-endpoints


See upstream PR #400 for full description.

Adds the three `execution*` tables to both app drizzle schemas
(sqlite + postgres) so `executor.executions` writes actually land on
disk in real deployments. Until this PR, persistence silently
no-op'd because the `storage-drizzle` adapter throws on unknown
models (absorbed by the engine's `silent` wrapper but no row gets
written).

- `apps/local/src/server/executor-schema.ts`: three sqlite tables
  matching the DBSchema shape from `@executor/sdk` (scope_id PK on
  execution, standalone PK on child rows, matching indexes for
  scope / status / trigger_kind / created_at / tool_path /
  namespace).
- `apps/cloud/src/services/executor-schema.ts`: mirror in pg-core
  with `bigint` for epoch-ms columns and `timestamp` for Date
  columns.
- Fresh `drizzle-kit generate` output on each app's `drizzle/` dir
  (local `0004_fancy_red_wolf.sql`, cloud
  `0006_panoramic_mother_askani.sql`).

No test changes — the MCP stdio integration test already exercises
this path end-to-end (runs `return 2+2` through the daemon, which
now successfully records + returns "4" as expected).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant