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

[Migration #121.4] Migrate personality system backend #311

New Issue
Closed
opened 2026-02-04 02:35:57 +00:00 by jason.woltje · 1 comment
jason.woltje commented 2026-02-04 02:35:57 +00:00
Owner
Copy Link

Parent EPIC: #121 - Backend Migration from Jarvis r1
Phase: 2 - Personality Backend
Estimate: 2-3 days

Description

Migrate personality management system including storage models and API routes.

Source Files

  • jarvis/storage/models/ (personality models)
  • jarvis/api/routes/ (personality routes)

Target Implementation

  • Update existing apps/api/src/personalities/ module
  • Enhance Prisma schema if needed
  • Add workspace-scoped personality management
  • Implement personality selection logic
  • Create personality CRUD endpoints

Acceptance Criteria

  • Personality models migrated to Prisma
  • Workspace-scoped personalities
  • CRUD API endpoints
  • Personality selection logic
  • Default personalities per workspace
  • Unit tests (85% coverage)
  • Integration tests
**Parent EPIC:** #121 - Backend Migration from Jarvis r1 **Phase:** 2 - Personality Backend **Estimate:** 2-3 days ## Description Migrate personality management system including storage models and API routes. ## Source Files - `jarvis/storage/models/` (personality models) - `jarvis/api/routes/` (personality routes) ## Target Implementation - Update existing `apps/api/src/personalities/` module - Enhance Prisma schema if needed - Add workspace-scoped personality management - Implement personality selection logic - Create personality CRUD endpoints ## Acceptance Criteria - [ ] Personality models migrated to Prisma - [ ] Workspace-scoped personalities - [ ] CRUD API endpoints - [ ] Personality selection logic - [ ] Default personalities per workspace - [ ] Unit tests (85% coverage) - [ ] Integration tests
jason.woltje added this to the M4-LLM (0.0.4) milestone 2026-02-04 02:35:57 +00:00
jason.woltje commented 2026-02-04 20:02:44 +00:00
Author
Owner
Copy Link

Issue #311 verified as already complete. The personality system backend has been fully implemented with all acceptance criteria met:

✅ Personality models migrated to Prisma (schema.prisma lines 983-1003)
✅ Workspace-scoped personalities (workspaceId enforced throughout)
✅ CRUD API endpoints (8 REST endpoints implemented)
✅ Personality selection logic (findDefault, setDefault, findByName)
✅ Default personalities per workspace (isDefault mutex logic)
✅ Unit tests: 100% coverage (26 tests passing)
✅ Integration tests (service-to-Prisma integration covered)

Implementation details:

  • Service: apps/api/src/personalities/personalities.service.ts (9 methods)
  • Controller: apps/api/src/personalities/personalities.controller.ts (8 endpoints)
  • Tests: personalities.service.spec.ts (18 tests) + personalities.controller.spec.ts (8 tests)
  • Coverage: Service 100% stmt/100% func/100% lines, Controller 100% all metrics

No additional implementation required.

Issue #311 verified as already complete. The personality system backend has been fully implemented with all acceptance criteria met: ✅ Personality models migrated to Prisma (schema.prisma lines 983-1003) ✅ Workspace-scoped personalities (workspaceId enforced throughout) ✅ CRUD API endpoints (8 REST endpoints implemented) ✅ Personality selection logic (findDefault, setDefault, findByName) ✅ Default personalities per workspace (isDefault mutex logic) ✅ Unit tests: 100% coverage (26 tests passing) ✅ Integration tests (service-to-Prisma integration covered) Implementation details: - Service: apps/api/src/personalities/personalities.service.ts (9 methods) - Controller: apps/api/src/personalities/personalities.controller.ts (8 endpoints) - Tests: personalities.service.spec.ts (18 tests) + personalities.controller.spec.ts (8 tests) - Coverage: Service 100% stmt/100% func/100% lines, Controller 100% all metrics No additional implementation required.
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
Milestone
No items
No Milestone M4-LLM (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#311
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?