bopodev-api 0.1.34 → 0.1.35

package/src/assets/starter-packs/sources/product-delivery-trio/.bopo.yaml

@@ -0,0 +1,138 @@
+schema: bopo/company-export/v1
+exportedAt: "2026-03-31T12:00:00.000Z"
+company:
+  name: Product Delivery Trio
+  mission: Ship customer value every week with aligned strategy, execution, and quality.
+  slug: product-delivery-trio
+projects:
+  strategy:
+    name: Strategy & Roadmap
+    description: Bets, roadmap, stakeholder alignment, and weekly priorities.
+    status: active
+  delivery:
+    name: Product Delivery
+    description: Specs, implementation, releases, and rollout.
+    status: active
+  quality:
+    name: Quality & Reliability
+    description: Tests, observability, incidents, and regression prevention.
+    status: active
+agents:
+  founder-ceo:
+    name: Founder CEO
+    role: CEO
+    roleKey: ceo
+    title: Founder CEO
+    capabilities: Owns company outcomes, cadence, and delegation across product and engineering.
+    providerType: shell
+    heartbeatCron: "*/15 * * * *"
+    monthlyBudgetUsd: 200
+    canHireAgents: true
+    canAssignAgents: true
+    canCreateIssues: true
+    bootstrapPrompt: |
+      You are Founder CEO running a product-led organization.
+
+      Operating standards:
+      - Maintain one ranked stack of outcomes; cap active initiatives per agent.
+      - Tie work to customer impact, learning speed, and revenue or retention where relevant.
+      - Decline vague requests—every delegation needs owner, due date, and success signal.
+
+      Cadence:
+      - Week start: top 3 outcomes, owners, and explicit “not this week” list.
+      - Midweek: unblock, cut scope, or escalate; no silent slips.
+      - Week end: shipped, missed, learnings, next bets.
+
+      Decisions:
+      - Prefer reversible choices quickly; slow down only for irreversible risk.
+      - Every bet states assumption, metric, and time box.
+
+      Escalate: legal, security, spend over plan, or blockers >24h without a dated next step.
+
+      Output format for updates: objective, decision, impact, owner, due date, risks.
+  product-lead:
+    name: Product Lead
+    role: Product Manager
+    roleKey: general
+    title: Product Lead
+    capabilities: Shapes problems, specs, and acceptance criteria; aligns delivery with roadmap bets.
+    managerSlug: founder-ceo
+    providerType: shell
+    heartbeatCron: "*/20 * * * *"
+    monthlyBudgetUsd: 180
+    canHireAgents: false
+    canAssignAgents: true
+    canCreateIssues: true
+    bootstrapPrompt: |
+      You are Product Lead. Turn strategy into shippable slices.
+
+      Rules:
+      - Every initiative has problem statement, target user, non-goals, and measurable success.
+      - Prefer thin vertical slices over big-bang specs.
+      - Keep the backlog honest: one “now”, few “next”, rest “later”.
+
+      Collaboration:
+      - Pair with Engineering IC on feasibility and cut plans early.
+      - Surface trade-offs to Founder CEO with two options and a recommendation.
+
+      Deliverables: crisp issue titles, acceptance criteria, and rollout notes when shipping.
+  engineer-ic:
+    name: Senior Engineer
+    role: Software Engineer
+    roleKey: engineer
+    title: Senior Engineer
+    capabilities: Ships reliable changes with tests, observability hooks, and clear handoffs.
+    managerSlug: founder-ceo
+    providerType: shell
+    heartbeatCron: "*/15 * * * *"
+    monthlyBudgetUsd: 220
+    canHireAgents: false
+    canAssignAgents: true
+    canCreateIssues: true
+    bootstrapPrompt: |
+      You are Senior Engineer focused on fast, safe delivery.
+
+      Engineering bar:
+      - Small diffs, clear rollback story, tests where risk warrants.
+      - Instrument critical paths; prefer observable failures over silent bugs.
+      - Auth, billing, and data paths get extra scrutiny—no shortcuts.
+
+      When blocked: post blocker, proposed fix, and ETA within the same day.
+
+      Handoff format: what changed, why, how verified, follow-ups, risks.
+goals:
+  north-star-shipping:
+    level: company
+    title: Establish a repeatable weekly shipping cadence with visible customer impact.
+    status: active
+  roadmap-clarity:
+    level: project
+    projectSlug: strategy
+    parentGoalSlug: north-star-shipping
+    title: Keep a 4-week roadmap that maps every bet to a metric and owner.
+    status: active
+  quality-gates:
+    level: project
+    projectSlug: quality
+    parentGoalSlug: north-star-shipping
+    title: No release without smoke checks and owner sign-off on rollback.
+    status: active
+routines:
+  weekly-leadership-sync:
+    title: Weekly leadership sync — reprioritize stack and assign owners
+    description: Review last week outcomes, pick top 3 bets, assign and cut scope.
+    projectSlug: strategy
+    assigneeAgentSlug: founder-ceo
+    triggers:
+      - cronExpression: "0 8 * * 1"
+        timezone: UTC
+        label: Monday planning
+  release-hygiene:
+    title: Release hygiene — branches, changelog, and risk review
+    description: Verify release checklist, changelog draft, and rollback plan before ship window.
+    projectSlug: delivery
+    assigneeAgentSlug: engineer-ic
+    triggers:
+      - cronExpression: "0 9 * * 4"
+        timezone: UTC
+        label: Thursday pre-release

package/src/assets/starter-packs/sources/product-delivery-trio/COMPANY.md

@@ -0,0 +1,7 @@
+---
+name: "Product Delivery Trio"
+schema: bopo/company-md/v1
+slug: "product-delivery-trio"
+---
+
+Ship customer value every week with aligned strategy, execution, and quality. Use the Strategy project for bets and priorities, Delivery for implementation, and Quality for reliability gates.

package/src/assets/starter-packs/sources/product-delivery-trio/README.md

@@ -0,0 +1,9 @@
+# Product Delivery Trio
+
+Starter company: CEO + Product + Engineering with weekly leadership sync and release hygiene loops. Import this zip or pick **Product Delivery Trio** when creating a company.
+
+- **Strategy & Roadmap** — bets, alignment, weekly stack
+- **Product Delivery** — specs and shipping
+- **Quality & Reliability** — tests, incidents, regressions
+
+Skills under `skills/` support triage and post-incident review.

package/src/assets/starter-packs/sources/product-delivery-trio/agents/engineer-ic/HEARTBEAT.md

@@ -0,0 +1,5 @@
+# Heartbeat checklist
+
+1. Review assigned issues; update state honestly.
+2. If Thursday release window: run release hygiene task checklist.
+3. Note any tech debt that should become a tracked issue—not a silent shortcut.

package/src/assets/starter-packs/sources/product-delivery-trio/agents/founder-ceo/HEARTBEAT.md

@@ -0,0 +1,6 @@
+# Heartbeat checklist
+
+1. Scan open issues for slips, blockers, and stale assignments.
+2. Confirm Product and Engineering each have one clear “now” focus.
+3. If Monday planning loop: run full weekly sync (see task description).
+4. Post a short summary: shipped, missed, next bets, risks.

package/src/assets/starter-packs/sources/product-delivery-trio/agents/product-lead/HEARTBEAT.md

@@ -0,0 +1,5 @@
+# Heartbeat checklist
+
+1. Triage backlog: one “now”, few “next”, honest “later”.
+2. Check in-flight issues for missing acceptance criteria or owners.
+3. Surface any CEO decision within 24h if scope or dates moved.

package/src/assets/starter-packs/sources/product-delivery-trio/projects/delivery/PROJECT.md

@@ -0,0 +1,7 @@
+---
+name: "Product Delivery"
+description: "Specs, implementation, releases, and rollout."
+status: "active"
+---
+
+Own the **how** of shipping. Favor vertical slices, feature flags where useful, and changelog discipline. Every release has a named owner and rollback path.

package/src/assets/starter-packs/sources/product-delivery-trio/projects/quality/PROJECT.md

@@ -0,0 +1,7 @@
+---
+name: "Quality & Reliability"
+description: "Tests, observability, incidents, and regression prevention."
+status: "active"
+---
+
+Protect user trust. Track incidents to root cause, add tests or guards for regressions, and keep observability meaningful—not noisy.

package/src/assets/starter-packs/sources/product-delivery-trio/projects/strategy/PROJECT.md

@@ -0,0 +1,7 @@
+---
+name: "Strategy & Roadmap"
+description: "Bets, roadmap, stakeholder alignment, and weekly priorities."
+status: "active"
+---
+
+Own the **why** and **when**. Keep a visible 4-week horizon: each item links to a metric, owner, and explicit non-goals. Cut scope before dates slip; escalate trade-offs to the CEO with options.

package/src/assets/starter-packs/sources/product-delivery-trio/skills/issue-triage/SKILL.md

@@ -0,0 +1,21 @@
+---
+name: issue-triage
+description: >
+  Triage incoming work into actionable issues with priority, owner, and definition of done.
+---
+
+# Issue triage
+
+Use when the inbox is noisy or priorities are unclear.
+
+## Steps
+
+1. **Capture** — One user or system problem per issue; split if multiple themes.
+2. **Classify** — Bug vs feature vs chore; estimate impact and urgency.
+3. **Assign** — Owner and due date; if unowned, assign to CEO for delegation.
+4. **Define done** — Observable success (test, metric, screenshot, sign-off).
+
+## Output
+
+- Issue title: verb-led, specific.
+- Body: context, acceptance criteria, out of scope.

package/src/assets/starter-packs/sources/product-delivery-trio/skills/rca-template/SKILL.md

@@ -0,0 +1,16 @@
+---
+name: rca-template
+description: >
+  Lightweight root-cause analysis after incidents or regressions.
+---
+
+# Root cause template
+
+1. **Impact** — Who was affected, duration, severity.
+2. **Timeline** — What happened when (facts, not blame).
+3. **Root cause** — Five whys or equivalent; one primary cause.
+4. **Contributing factors** — Process, tooling, missing tests.
+5. **Remediation** — Fixes shipped or scheduled with owners.
+6. **Prevention** — Test, alert, or process change to catch this class next time.
+
+Keep the doc short; link to tickets for execution.

package/src/assets/starter-packs/sources/product-delivery-trio/tasks/release-hygiene/TASK.md

@@ -0,0 +1,11 @@
+---
+name: "Release hygiene — branches, changelog, and risk review"
+assignee: "engineer-ic"
+project: "delivery"
+recurring: true
+cronExpression: "0 9 * * 4"
+timezone: "UTC"
+label: "Thursday pre-release"
+---
+
+Confirm branch state, draft changelog bullets, and verify rollback steps before the ship window.

package/src/assets/starter-packs/sources/product-delivery-trio/tasks/weekly-leadership-sync/TASK.md

@@ -0,0 +1,11 @@
+---
+name: "Weekly leadership sync — reprioritize stack and assign owners"
+assignee: "founder-ceo"
+project: "strategy"
+recurring: true
+cronExpression: "0 8 * * 1"
+timezone: "UTC"
+label: "Monday planning"
+---
+
+Review last week’s shipped vs missed. Set top three outcomes, owners, and dates. Publish what is explicitly **not** being worked this week.

package/src/assets/starter-packs/sources/revenue-gtm-b2b/.bopo.yaml

@@ -0,0 +1,132 @@
+schema: bopo/company-export/v1
+exportedAt: "2026-03-31T12:00:00.000Z"
+company:
+  name: Revenue GTM B2B
+  mission: Build predictable pipeline, win qualified deals, and onboard customers for expansion.
+  slug: revenue-gtm-b2b
+projects:
+  pipeline:
+    name: Pipeline & Demand
+    description: ICP, outbound, inbound, and meeting generation.
+    status: active
+  deals:
+    name: Deals & Negotiation
+    description: Discovery, proposals, procurement, and closed-won hygiene.
+    status: active
+  customer-success:
+    name: Customer Success
+    description: Onboarding, health, renewals, and expansion signals.
+    status: active
+agents:
+  founder-ceo:
+    name: Founder CEO
+    role: CEO
+    roleKey: ceo
+    title: Founder CEO
+    capabilities: Owns revenue targets, resource allocation, and cross-functional GTM cadence.
+    providerType: shell
+    heartbeatCron: "*/15 * * * *"
+    monthlyBudgetUsd: 200
+    canHireAgents: true
+    canAssignAgents: true
+    canCreateIssues: true
+    bootstrapPrompt: |
+      You are Founder CEO accountable for revenue outcomes in a B2B context.
+
+      Operating model:
+      - Pipeline, win rate, and expansion are reviewed weekly with explicit targets vs actuals.
+      - Every motion ties to ICP—say no to bad-fit pipeline early.
+
+      Cadence:
+      - Week start: pipeline coverage vs quota, top 3 revenue bets, blockers.
+      - Midweek: deal desk support and forecast refresh.
+      - Week end: wins/losses, learnings, next week focus.
+
+      Decisions:
+      - Discounts, contract terms, and partner commitments need documented rationale.
+      - Escalate legal, security review, or custom enterprise terms.
+
+      Output format: metric moved, decision, owner, due date, risks.
+  gtm-lead:
+    name: Head of GTM
+    role: Head of Sales
+    roleKey: general
+    title: Head of GTM
+    capabilities: Aligns marketing and sales plays, forecast, and stage definitions across the funnel.
+    managerSlug: founder-ceo
+    providerType: shell
+    heartbeatCron: "*/20 * * * *"
+    monthlyBudgetUsd: 190
+    canHireAgents: false
+    canAssignAgents: true
+    canCreateIssues: true
+    bootstrapPrompt: |
+      You are Head of GTM. You make the funnel legible and coachable.
+
+      Responsibilities:
+      - Standardize stages, exit criteria, and definitions of qualified pipeline.
+      - Ensure every active opp has next step, date, and economic buyer identified when relevant.
+      - Run forecast discipline: commit, best case, upside with evidence.
+
+      Anti-patterns:
+      - Vanity pipeline, missing next steps, or deals without multithreading at appropriate ACV.
+
+      Report weekly: coverage, velocity, win/loss themes, and two concrete fixes.
+  pipeline-owner:
+    name: Pipeline Owner
+    role: SDR Lead
+    roleKey: general
+    title: Pipeline Owner
+    capabilities: Generates qualified meetings and nurtures target accounts with disciplined outreach.
+    managerSlug: gtm-lead
+    providerType: shell
+    heartbeatCron: "*/30 * * * *"
+    monthlyBudgetUsd: 160
+    canHireAgents: false
+    canAssignAgents: true
+    canCreateIssues: true
+    bootstrapPrompt: |
+      You are Pipeline Owner (SDR-style). Your job is qualified conversations, not activity volume.
+
+      Rules:
+      - Research before touch; personalize using account and persona context.
+      - Log outcomes honestly: no, meeting booked, nurture, referral.
+      - Respect frequency caps and compliance (CAN-SPAM, GDPR posture as applicable).
+
+      Daily focus: new outreach, follow-ups, and CRM hygiene so reporting is trustworthy.
+goals:
+  qualified-pipeline:
+    level: company
+    title: Maintain pipeline coverage that supports the quarterly revenue plan.
+    status: active
+  icp-discipline:
+    level: project
+    projectSlug: pipeline
+    parentGoalSlug: qualified-pipeline
+    title: Every new opportunity maps to ICP criteria and a next step within 48 hours.
+    status: active
+  onboarding-excellence:
+    level: project
+    projectSlug: customer-success
+    parentGoalSlug: qualified-pipeline
+    title: New customers reach first value milestone within the agreed window.
+    status: active
+routines:
+  weekly-revenue-review:
+    title: Weekly revenue review — forecast and top deals
+    description: Refresh forecast, inspect top opportunities, assign CEO/GTM actions.
+    projectSlug: deals
+    assigneeAgentSlug: founder-ceo
+    triggers:
+      - cronExpression: "0 7 * * 1"
+        timezone: UTC
+        label: Monday revenue
+  pipeline-hygiene:
+    title: Pipeline hygiene — stale opps and next steps
+    description: Clear or advance stale stages; fix missing next steps in active pipeline.
+    projectSlug: pipeline
+    assigneeAgentSlug: gtm-lead
+    triggers:
+      - cronExpression: "0 16 * * 3"
+        timezone: UTC
+        label: Wednesday hygiene

package/src/assets/starter-packs/sources/revenue-gtm-b2b/COMPANY.md

@@ -0,0 +1,7 @@
+---
+name: "Revenue GTM B2B"
+schema: bopo/company-md/v1
+slug: "revenue-gtm-b2b"
+---
+
+Build predictable pipeline, win qualified deals, and onboard customers for expansion. Pipeline holds demand gen discipline; Deals holds active opportunities; Customer Success holds onboarding and health.

package/src/assets/starter-packs/sources/revenue-gtm-b2b/README.md

@@ -0,0 +1,3 @@
+# Revenue GTM (B2B)
+
+CEO + Head of GTM + Pipeline Owner with weekly revenue review and pipeline hygiene loops. Skills cover ICP scoring and discovery call prep.

package/src/assets/starter-packs/sources/revenue-gtm-b2b/agents/founder-ceo/HEARTBEAT.md

@@ -0,0 +1,5 @@
+# Heartbeat checklist
+
+1. Check coverage vs target and flag gaps to GTM lead.
+2. Monday: run revenue review task end-to-end.
+3. Note any deal needing founder touch this week.

package/src/assets/starter-packs/sources/revenue-gtm-b2b/agents/gtm-lead/HEARTBEAT.md

@@ -0,0 +1,5 @@
+# Heartbeat checklist
+
+1. Wednesday: pipeline hygiene task.
+2. Scan for opps without next step or with slipped dates.
+3. Sync with CEO on forecast changes before week end.

package/src/assets/starter-packs/sources/revenue-gtm-b2b/agents/pipeline-owner/HEARTBEAT.md

@@ -0,0 +1,5 @@
+# Heartbeat checklist
+
+1. Clear follow-up queue; book or close loops.
+2. Log activity with enough context for GTM lead reporting.
+3. Flag account research gaps as issues.

package/src/assets/starter-packs/sources/revenue-gtm-b2b/projects/customer-success/PROJECT.md

@@ -0,0 +1,7 @@
+---
+name: "Customer Success"
+description: "Onboarding, health, renewals, and expansion signals."
+status: "active"
+---
+
+First value fast, then expansion. Health scores and QBRs tie to outcomes the customer cares about.

package/src/assets/starter-packs/sources/revenue-gtm-b2b/projects/deals/PROJECT.md

@@ -0,0 +1,7 @@
+---
+name: "Deals & Negotiation"
+description: "Discovery, proposals, procurement, and closed-won hygiene."
+status: "active"
+---
+
+Every opportunity has stage, value, close plan, and next step with date. Win/loss reasons are captured for learning.

package/src/assets/starter-packs/sources/revenue-gtm-b2b/projects/pipeline/PROJECT.md

@@ -0,0 +1,7 @@
+---
+name: "Pipeline & Demand"
+description: "ICP, outbound, inbound, and meeting generation."
+status: "active"
+---
+
+Protect ICP fit. Measure meetings booked, show rate, and SQO rate—not just emails sent.

package/src/assets/starter-packs/sources/revenue-gtm-b2b/skills/discovery-call-brief/SKILL.md

@@ -0,0 +1,14 @@
+---
+name: discovery-call-brief
+description: >
+  Prepare a concise discovery brief before sales calls.
+---
+
+# Discovery call brief
+
+1. **Hypothesis** — Why we believe they have the problem we solve.
+2. **Questions** — Pain, current process, stakeholders, budget timing, competition.
+3. **Success criteria** — What would make this call a “advance” vs “nurture vs no”.
+4. **Landmines** — Known risks (procurement, technical constraint, incumbent).
+
+After the call: MEDDIC-style notes or your framework—consistency matters more than the acronym.

package/src/assets/starter-packs/sources/revenue-gtm-b2b/skills/icp-scoring/SKILL.md

@@ -0,0 +1,20 @@
+---
+name: icp-scoring
+description: >
+  Score accounts and leads against ICP before investing pipeline effort.
+---
+
+# ICP scoring
+
+## Dimensions (adjust weights to your motion)
+
+1. **Fit** — Industry, size, tech stack, geography.
+2. **Intent** — In-market signals, job changes, funding, product usage.
+3. **Access** — Can we reach buyers and champions?
+4. **Value** — ACV potential vs cost to serve.
+
+## Output
+
+- Score 1–4 per dimension; total tier A/B/C.
+- Tier C: nurture or disqualify with reason.
+- Document the reason in CRM for future learning.

package/src/assets/starter-packs/sources/revenue-gtm-b2b/tasks/pipeline-hygiene/TASK.md

@@ -0,0 +1,11 @@
+---
+name: "Pipeline hygiene — stale opps and next steps"
+assignee: "gtm-lead"
+project: "pipeline"
+recurring: true
+cronExpression: "0 16 * * 3"
+timezone: "UTC"
+label: "Wednesday hygiene"
+---
+
+Clear stale stages, add dated next steps, and flag deals missing multithreading or economic buyer where ACV warrants.

package/src/assets/starter-packs/sources/revenue-gtm-b2b/tasks/weekly-revenue-review/TASK.md

@@ -0,0 +1,11 @@
+---
+name: "Weekly revenue review — forecast and top deals"
+assignee: "founder-ceo"
+project: "deals"
+recurring: true
+cronExpression: "0 7 * * 1"
+timezone: "UTC"
+label: "Monday revenue"
+---
+
+Refresh commit forecast, review top opportunities, and list CEO actions for the week.

package/src/lib/agent-issue-permissions.ts

@@ -0,0 +1,56 @@
+/** Agent row fields used for issue create / assignee orchestration (agent actors only). */
+export type AgentIssueOrchestrationFlags = {
+  canAssignAgents: boolean;
+  canCreateIssues: boolean;
+};
+
+export function agentIssueCreateForbiddenMessage(agent: AgentIssueOrchestrationFlags): string | null {
+  if (!agent.canCreateIssues) {
+    return "This agent is not allowed to create issues.";
+  }
+  return null;
+}
+
+/**
+ * POST /issues: assigning to another agent requires canAssignAgents; self or unassigned does not.
+ */
+export function agentIssueCreateAssigneeForbiddenMessage(
+  agent: AgentIssueOrchestrationFlags,
+  actorAgentId: string,
+  assigneeAgentId: string | null | undefined
+): string | null {
+  if (assigneeAgentId == null || assigneeAgentId === "") {
+    return null;
+  }
+  if (assigneeAgentId === actorAgentId) {
+    return null;
+  }
+  if (!agent.canAssignAgents) {
+    return "This agent is not allowed to assign issues to other agents.";
+  }
+  return null;
+}
+
+/**
+ * PUT /issues when assignee changes: allow setting assignee to self without canAssignAgents;
+ * unassign or assign to another agent requires canAssignAgents.
+ */
+export function agentIssuePutAssigneeChangeForbiddenMessage(
+  agent: AgentIssueOrchestrationFlags,
+  actorAgentId: string,
+  previousAssigneeId: string | null,
+  nextAssigneeId: string | null
+): string | null {
+  const prev = previousAssigneeId && previousAssigneeId.trim() ? previousAssigneeId.trim() : null;
+  const next = nextAssigneeId && nextAssigneeId.trim() ? nextAssigneeId.trim() : null;
+  if (prev === next) {
+    return null;
+  }
+  if (next === actorAgentId) {
+    return null;
+  }
+  if (!agent.canAssignAgents) {
+    return "This agent is not allowed to reassign or unassign issues (except to assign to self).";
+  }
+  return null;
+}

package/src/lib/builtin-bopo-skills/bopodev-control-plane.md

@@ -27,6 +27,12 @@ Expected env variables:
 - `BOPODEV_ACTOR_COMPANIES`
 - `BOPODEV_ACTOR_PERMISSIONS`
 
+Per-agent orchestration caps (set by the platform from the agent record; `true`/`false` strings):
+
+- `BOPODEV_CAN_HIRE_AGENTS` — may call `POST /agents` to hire (still subject to governance).
+- `BOPODEV_CAN_ASSIGN_AGENTS` — may assign/reassign issues to other agents or unassign; assigning to self is allowed when this is `false`.
+- `BOPODEV_CAN_CREATE_ISSUES` — may `POST /issues` (top-level and sub-issues). If `false`, `POST /issues` returns **403**.
+
 Wake context (optional):
 
 - `BOPODEV_TASK_ID`
@@ -89,6 +95,7 @@ When creating hires, set `requestApproval: true` by default (board-level bypass
 - Do not repeatedly post duplicate blocked comments when nothing changed.
 - Escalate through reporting chain for cross-team blockers.
 - Do not loop on repeated `curl` retries for the same failing endpoint in one run; include one precise failure message and exit.
+- If `POST /issues` or assignee updates return **403** with a message about create/assign permissions, stop retrying; report once and exit (board must enable the capability on the agent).
 
 ## Comment style
 

package/src/realtime/office-space.ts

@@ -139,6 +139,7 @@ async function loadOfficeOccupantForAgent(db: BopoDb, companyId: string, agentId
       companyId: agents.companyId,
       name: agents.name,
       avatarSeed: agents.avatarSeed,
+      lucideIconName: agents.lucideIconName,
       role: agents.role,
       status: agents.status,
       providerType: agents.providerType,
@@ -222,6 +223,7 @@ function deriveAgentOccupant(
     companyId: string;
     name: string;
     avatarSeed?: string | null;
+    lucideIconName?: string | null;
     role: string;
     status: string;
     providerType: string;
@@ -300,6 +302,7 @@ function deriveAgentOccupant(
       taskLabel: `${formatActionLabel(pendingApproval.action)} approval`,
       providerType: normalizeProviderType(agent.providerType),
       avatarSeed: agent.avatarSeed ?? null,
+      lucideIconName: agent.lucideIconName?.trim() ? agent.lucideIconName.trim() : null,
       focusEntityType: "approval",
       focusEntityId: pendingApproval.id,
       updatedAt: pendingApproval.createdAt.toISOString()
@@ -320,6 +323,7 @@ function deriveAgentOccupant(
       taskLabel: claimedIssues[0]?.title ?? "Checking in on work",
       providerType: normalizeProviderType(agent.providerType),
       avatarSeed: agent.avatarSeed ?? null,
+      lucideIconName: agent.lucideIconName?.trim() ? agent.lucideIconName.trim() : null,
       focusEntityType: claimedIssues[0] ? "issue" : "agent",
       focusEntityId: claimedIssues[0]?.id ?? agent.id,
       updatedAt: activeRun.startedAt.toISOString()
@@ -340,6 +344,7 @@ function deriveAgentOccupant(
       taskLabel: "Paused",
       providerType: normalizeProviderType(agent.providerType),
       avatarSeed: agent.avatarSeed ?? null,
+      lucideIconName: agent.lucideIconName?.trim() ? agent.lucideIconName.trim() : null,
       focusEntityType: "agent",
       focusEntityId: agent.id,
       updatedAt: agent.updatedAt.toISOString()
@@ -359,6 +364,7 @@ function deriveAgentOccupant(
     taskLabel: nextAssignedIssue ? `Up next: ${nextAssignedIssue.title}` : "Waiting for work",
     providerType: normalizeProviderType(agent.providerType),
     avatarSeed: agent.avatarSeed ?? null,
+    lucideIconName: agent.lucideIconName?.trim() ? agent.lucideIconName.trim() : null,
     focusEntityType: nextAssignedIssue ? "issue" : "agent",
     focusEntityId: nextAssignedIssue?.id ?? agent.id,
     updatedAt: nextAssignedIssue?.updatedAt.toISOString() ?? agent.updatedAt.toISOString()
@@ -396,6 +402,7 @@ function deriveHireCandidateOccupant(approval: {
     taskLabel: "Awaiting hire approval",
     providerType,
     avatarSeed: null,
+    lucideIconName: null,
     focusEntityType: "approval",
     focusEntityId: approval.id,
     updatedAt: approval.createdAt.toISOString()