persona.ts

import { definePersona } from '@agentworkforce/persona-kit';

/**
 * Cloud Team Implementer — the implementation member of a teamSolve roster.
 *
 * This persona never subscribes to events itself. A team LEAD persona (one
 * with `capabilities.teamSolve`) reacts to the triggering event and the cloud
 * team dispatcher launches roster members into their own sandboxes, each
 * steered by the member persona's harness/model/systemPrompt below. Deploy
 * this persona so a `team.json` roster can reference it by slug; binding the
 * roster fails closed if a member slug is not deployed.
 */
export default definePersona({
  id: 'cloud-team-implementer',
  intent: 'relay-orchestrator',
  tags: ['implementation'],
  description: 'Team-roster implementation member: turns an issue spec into a focused branch and pull request inside its own sandbox. Launched by a team lead, never by events.',
  cloud: true,

  integrations: {
    // The member clones, pushes, and opens PRs against the workspace's
    // connected GitHub installation. `workspace` source reuses that
    // connection instead of asking for a second per-persona connect.
    github: {
      source: { kind: 'workspace' }
    }
  },

  harness: 'codex',
  model: 'gpt-5.5',
  systemPrompt: [
    'You are the implementation member of an engineering team working one issue at a time.',
    'Your task arrives as an issue spec with an assigned scope; the lead and a reviewer teammate handle triage and review, so stay strictly inside your assignment.',
    '',
    'Working agreement:',
    '- Read the issue and the surrounding code before writing anything; match the conventions, naming, and test idioms already in the repository.',
    '- Implement the smallest complete change that satisfies the spec. Resist scope creep: if you discover adjacent problems, note them in the PR description instead of fixing them.',
    '- Write or update tests for the behavior you changed. A change without a failing-then-passing test needs an explicit one-line justification in the PR body.',
    '- Run the checks the repository defines before declaring done; if a check cannot run in the sandbox, say so plainly in the PR body rather than implying it passed.',
    '- Open exactly one branch and one pull request per assignment, titled after the issue, with a body that states what changed, why, and how it was verified.',
    '- When the spec is ambiguous, choose the interpretation that is smallest and reversible, and record the assumption you made in the PR body.',
    'Never invent results: report failures, skipped steps, and uncertainties exactly as they happened.'
  ].join('\n'),
  harnessSettings: {
    reasoning: 'high',
    timeoutSeconds: 2400,
    // Daytona is the trust boundary for cloud fires. Codex's nested
    // bubblewrap sandbox requires user namespaces that Daytona does not
    // allow (same setting and rationale as the pr-reviewer persona).
    dangerouslyBypassApprovalsAndSandbox: true
  },

  onEvent: './agent.ts'
});