feat(personas): Add persona_id support to Ticket/WorkerContext and ConductorEngine
This commit is contained in:
@@ -8,9 +8,9 @@
|
||||
- [x] Task: Conductor - User Manual Verification 'Phase 1: Core Model and Migration' (Protocol in workflow.md)
|
||||
|
||||
## Phase 2: Granular MMA Integration
|
||||
- [ ] Task: Write Tests: Verify that a `Ticket` or `Track` can hold a `persona_id` override.
|
||||
- [ ] Task: Implement: Update the MMA internal state to support per-epic, per-track, and per-task Persona assignments.
|
||||
- [ ] Task: Implement: Update the `WorkerContext` and `ConductorEngine` to resolve and apply the correct Persona before spawning an agent.
|
||||
- [x] Task: Write Tests: Verify that a `Ticket` or `Track` can hold a `persona_id` override.
|
||||
- [x] Task: Implement: Update the MMA internal state to support per-epic, per-track, and per-task Persona assignments.
|
||||
- [x] Task: Implement: Update the `WorkerContext` and `ConductorEngine` to resolve and apply the correct Persona before spawning an agent.
|
||||
- [ ] Task: Implement: Add "Persona" metadata to the Tier Stream logs to visually confirm which profile is active.
|
||||
- [ ] Task: Conductor - User Manual Verification 'Phase 2: Granular MMA Integration' (Protocol in workflow.md)
|
||||
|
||||
|
||||
Reference in New Issue
Block a user