mosaic/stack
1
0
Fork 0
Code Issues 10 Pull Requests Actions Packages Projects Releases 2 Wiki Activity

[INFRA-002] Database schema for job tracking #164

New Issue
Closed
opened 2026-02-01 07:24:04 +00:00 by jason.woltje · 0 comments
jason.woltje commented 2026-02-01 07:24:04 +00:00
Owner
Copy Link

Summary

Add Prisma schema for runner_jobs, job_steps, and job_events tables.

Schema Design

See: docs/3-architecture/mosaic-component-architecture.md#database-schema

Enums

  • RunnerJobStatus: PENDING, QUEUED, RUNNING, COMPLETED, FAILED, CANCELLED
  • JobStepPhase: SETUP, EXECUTION, VALIDATION, CLEANUP
  • JobStepType: COMMAND, AI_ACTION, GATE, ARTIFACT
  • JobStepStatus: PENDING, RUNNING, COMPLETED, FAILED, SKIPPED

Models

  • RunnerJob - links to agent_tasks, tracks job status/progress
  • JobStep - granular step tracking within a job
  • JobEvent - immutable audit log for event sourcing

Tasks

  • Add enums to schema.prisma
  • Add RunnerJob model with workspace and agent_task relations
  • Add JobStep model with job relation
  • Add JobEvent model for event sourcing
  • Create migration
  • Test migration on dev database

Files to Modify

  • apps/api/prisma/schema.prisma

Acceptance Criteria

  • prisma migrate dev succeeds
  • All foreign key relationships valid

Related

## Summary Add Prisma schema for runner_jobs, job_steps, and job_events tables. ## Schema Design See: docs/3-architecture/mosaic-component-architecture.md#database-schema ### Enums - RunnerJobStatus: PENDING, QUEUED, RUNNING, COMPLETED, FAILED, CANCELLED - JobStepPhase: SETUP, EXECUTION, VALIDATION, CLEANUP - JobStepType: COMMAND, AI_ACTION, GATE, ARTIFACT - JobStepStatus: PENDING, RUNNING, COMPLETED, FAILED, SKIPPED ### Models - RunnerJob - links to agent_tasks, tracks job status/progress - JobStep - granular step tracking within a job - JobEvent - immutable audit log for event sourcing ## Tasks - [ ] Add enums to schema.prisma - [ ] Add RunnerJob model with workspace and agent_task relations - [ ] Add JobStep model with job relation - [ ] Add JobEvent model for event sourcing - [ ] Create migration - [ ] Test migration on dev database ## Files to Modify - apps/api/prisma/schema.prisma ## Acceptance Criteria - prisma migrate dev succeeds - All foreign key relationships valid ## Related - Epic: #162 - Depends on nothing (first schema work)
jason.woltje added this to the M4.2-Infrastructure (0.0.4) milestone 2026-02-01 07:24:04 +00:00
jason.woltje added the apip0apiphase-1 labels 2026-02-01 07:24:04 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
ai
AI/LLM integration
 api
Backend/API work
 api
auth
Authentication
 database
database
Database/schema work
 devops
Docker/deployment
 docs
Documentation
 frontend
graph
knowledge-module
migration
Data migration
 orchestrator
Orchestrator service (apps/orchestrator/)
 p0
Critical priority
 p1
High priority
 p2
Medium priority
 p3
Low priority
 performance
Performance work
 phase-1
phase-2
phase-3
phase-4
phase-5
plugin
MoltBot plugin work
 search
security
Security-related
 setup
Initial setup
 testing
Testing/QA
 web
Frontend work
No Label api api p0 phase-1
Milestone
No items
No Milestone M4.2-Infrastructure (0.0.4)
Projects
Clear projects
No project
Assignees
Clear assignees
jason.woltje
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: mosaic/stack#164
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?