bopodev-api 0.1.34 → 0.1.36

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "bopodev-api",
-  "version": "0.1.34",
+  "version": "0.1.36",
   "license": "MIT",
   "type": "module",
   "files": [
@@ -21,9 +21,9 @@
     "ws": "^8.19.0",
     "yaml": "^2.8.3",
     "zod": "^4.1.5",
-    "bopodev-agent-sdk": "0.1.34",
-    "bopodev-db": "0.1.34",
-    "bopodev-contracts": "0.1.34"
+    "bopodev-contracts": "0.1.36",
+    "bopodev-db": "0.1.36",
+    "bopodev-agent-sdk": "0.1.36"
   },
   "devDependencies": {
     "@types/archiver": "^7.0.0",
@@ -40,7 +40,7 @@
     "db:init": "tsx src/scripts/db-init.ts",
     "onboard:seed": "tsx src/scripts/onboard-seed.ts",
     "workspaces:backfill": "tsx src/scripts/backfill-project-workspaces.ts",
-    "build": "tsc -p tsconfig.json",
+    "build": "tsc -p tsconfig.json && node ./scripts/copy-assets.mjs",
     "lint": "tsc -p tsconfig.json --noEmit",
     "typecheck": "tsc -p tsconfig.json --noEmit"
   }

package/src/app.ts

@@ -11,7 +11,7 @@ import { createGoalsRouter } from "./routes/goals";
 import { createGovernanceRouter } from "./routes/governance";
 import { createHeartbeatRouter } from "./routes/heartbeats";
 import { createIssuesRouter } from "./routes/issues";
-import { createLoopsRouter } from "./routes/loops";
+import { createRoutinesRouter } from "./routes/routines";
 import { createObservabilityRouter } from "./routes/observability";
 import { createProjectsRouter } from "./routes/projects";
 import { createPluginsRouter } from "./routes/plugins";
@@ -67,7 +67,9 @@ export function createApp(ctx: AppContext) {
   app.use("/companies", createCompaniesRouter(ctx));
   app.use("/projects", createProjectsRouter(ctx));
   app.use("/issues", createIssuesRouter(ctx));
-  app.use("/loops", createLoopsRouter(ctx));
+  const routinesRouter = createRoutinesRouter(ctx);
+  app.use("/routines", routinesRouter);
+  app.use("/loops", routinesRouter);
   app.use("/goals", createGoalsRouter(ctx));
   app.use("/agents", createAgentsRouter(ctx));
   app.use("/governance", createGovernanceRouter(ctx));

package/src/assets/starter-packs/sources/customer-support-excellence/.bopo.yaml

@@ -0,0 +1,129 @@
+schema: bopo/company-export/v1
+exportedAt: "2026-03-31T12:00:00.000Z"
+company:
+  name: Customer Support Excellence
+  mission: Resolve issues fast, grow self-serve, and protect customer trust.
+  slug: customer-support-excellence
+projects:
+  queue:
+    name: Support Queue
+    description: Triage, SLA, escalation, and case quality.
+    status: active
+  knowledge-base:
+    name: Knowledge Base
+    description: Help articles, macros, and searchable answers.
+    status: active
+  quality:
+    name: Quality & Coaching
+    description: QA, rubrics, training, and voice consistency.
+    status: active
+agents:
+  founder-ceo:
+    name: Founder CEO
+    role: CEO
+    roleKey: ceo
+    title: Founder CEO
+    capabilities: Owns customer trust, staffing trade-offs, and policy exceptions.
+    providerType: shell
+    heartbeatCron: "*/15 * * * *"
+    monthlyBudgetUsd: 200
+    canHireAgents: true
+    canAssignAgents: true
+    canCreateIssues: true
+    bootstrapPrompt: |
+      You are Founder CEO accountable for customer experience.
+
+      Principles:
+      - Support is a product surface: speed, clarity, and empathy matter.
+      - Deflect with docs only when accuracy is high; never optimize metrics by hiding humans behind bad KB.
+
+      Cadence:
+      - Review SLA breaches, top drivers of contact, and churn-risk tickets weekly.
+      - Align Support Lead on hiring, tooling, and policy (refunds, credits, edge cases).
+
+      Escalate: legal threats, security incidents, press-risk situations—immediate routing.
+
+      Output: volume trend, customer impact decision, owner, due date, risks.
+  support-lead:
+    name: Support Lead
+    role: Support Manager
+    roleKey: general
+    title: Support Lead
+    capabilities: Runs queue health, staffing, escalations, and KB roadmap with Support Specialist.
+    managerSlug: founder-ceo
+    providerType: shell
+    heartbeatCron: "*/20 * * * *"
+    monthlyBudgetUsd: 180
+    canHireAgents: false
+    canAssignAgents: true
+    canCreateIssues: true
+    bootstrapPrompt: |
+      You are Support Lead.
+
+      Operating rules:
+      - Queue discipline: oldest critical first; no ticket without owner and status.
+      - Escalation path to engineering includes repro, impact, and customer expectation.
+      - Weekly: categorize reasons for contact; feed top three into KB or product issues.
+
+      Coaching:
+      - Sample tickets against rubric; give specific feedback tied to customer outcome.
+
+      Metrics: SLA hit rate, first response time, reopen rate, CSAT if available.
+  support-specialist:
+    name: Support Specialist
+    role: Support Specialist
+    roleKey: general
+    title: Support Specialist
+    capabilities: Resolves tier-1/2 tickets, drafts KB articles, and flags product bugs.
+    managerSlug: support-lead
+    providerType: shell
+    heartbeatCron: "*/15 * * * *"
+    monthlyBudgetUsd: 160
+    canHireAgents: false
+    canAssignAgents: true
+    canCreateIssues: true
+    bootstrapPrompt: |
+      You are Support Specialist.
+
+      Standards:
+      - Acknowledge quickly; solve or set clear expectation for next update.
+      - One issue per ticket when possible; link related cases.
+      - KB drafts: problem, steps, screenshots or examples, when to escalate.
+
+      Tone: calm, specific, no jargon unless the customer used it first.
+goals:
+  customer-trust:
+    level: company
+    title: Meet response and resolution commitments while improving self-serve accuracy.
+    status: active
+  queue-sla:
+    level: project
+    projectSlug: queue
+    parentGoalSlug: customer-trust
+    title: Critical and high-priority SLAs met with transparent customer communication.
+    status: active
+  kb-coverage:
+    level: project
+    projectSlug: knowledge-base
+    parentGoalSlug: customer-trust
+    title: Top volume drivers have maintained articles linked from replies.
+    status: active
+routines:
+  daily-queue-standup:
+    title: Daily queue standup — volume, SLA risk, escalations
+    description: Review backlog age, SLA clocks, and stuck tickets; assign swarms if needed.
+    projectSlug: queue
+    assigneeAgentSlug: support-lead
+    triggers:
+      - cronExpression: "0 13 * * 1-5"
+        timezone: UTC
+        label: Weekday standup
+  kb-gap-sweep:
+    title: KB gap sweep — top reasons for contact
+    description: Identify missing or stale articles for top drivers; open KB issues with outlines.
+    projectSlug: knowledge-base
+    assigneeAgentSlug: support-specialist
+    triggers:
+      - cronExpression: "0 10 * * 2"
+        timezone: UTC
+        label: Tuesday KB

package/src/assets/starter-packs/sources/customer-support-excellence/COMPANY.md

@@ -0,0 +1,7 @@
+---
+name: "Customer Support Excellence"
+schema: bopo/company-md/v1
+slug: "customer-support-excellence"
+---
+
+Resolve issues fast, grow self-serve, and protect customer trust. Queue for live workload; Knowledge Base for deflection; Quality for coaching and consistency.

package/src/assets/starter-packs/sources/customer-support-excellence/README.md

@@ -0,0 +1,3 @@
+# Customer Support Excellence
+
+CEO + Support Lead + Support Specialist with weekday queue standup and weekly KB gap sweep. Skills for ticket responses and KB article structure.

package/src/assets/starter-packs/sources/customer-support-excellence/agents/founder-ceo/HEARTBEAT.md

@@ -0,0 +1,5 @@
+# Heartbeat checklist
+
+1. Scan for churn-risk or legal-sensitive threads.
+2. Unblock Support Lead on policy or headcount trade-offs.
+3. Connect top product bugs from support to roadmap conversation.

package/src/assets/starter-packs/sources/customer-support-excellence/agents/support-lead/HEARTBEAT.md

@@ -0,0 +1,5 @@
+# Heartbeat checklist
+
+1. Weekdays: standup task at scheduled time.
+2. Sample tickets for QA; note rubric updates.
+3. Weekly summary to CEO: volume, themes, product asks.

package/src/assets/starter-packs/sources/customer-support-excellence/agents/support-specialist/HEARTBEAT.md

@@ -0,0 +1,5 @@
+# Heartbeat checklist
+
+1. Work queue in priority order; update status honestly.
+2. Tuesday: KB gap sweep task.
+3. File product bugs with repro when pattern emerges.

package/src/assets/starter-packs/sources/customer-support-excellence/projects/knowledge-base/PROJECT.md

@@ -0,0 +1,7 @@
+---
+name: "Knowledge Base"
+description: "Help articles, macros, and searchable answers."
+status: "active"
+---
+
+Articles are owned, dated, and linked from tickets when they solve the case.

package/src/assets/starter-packs/sources/customer-support-excellence/projects/quality/PROJECT.md

@@ -0,0 +1,7 @@
+---
+name: "Quality & Coaching"
+description: "QA, rubrics, training, and voice consistency."
+status: "active"
+---
+
+Quality is sampled continuously; feedback is specific and tied to customer outcomes.

package/src/assets/starter-packs/sources/customer-support-excellence/projects/queue/PROJECT.md

@@ -0,0 +1,7 @@
+---
+name: "Support Queue"
+description: "Triage, SLA, escalation, and case quality."
+status: "active"
+---
+
+Age and priority drive order. Every escalation to engineering carries repro, impact, and customer expectation.

package/src/assets/starter-packs/sources/customer-support-excellence/skills/kb-article-skeleton/SKILL.md

@@ -0,0 +1,17 @@
+---
+name: kb-article-skeleton
+description: >
+  Skeleton for a help-center article that deflects repeat tickets.
+---
+
+# KB article skeleton
+
+**Title** — How to [verb] [object] (user language)
+
+1. **Who this is for** — Plan, role, or scenario.
+2. **Before you start** — Prereqs, permissions.
+3. **Steps** — Numbered, one action per step, screenshots where UI-heavy.
+4. **Troubleshooting** — Top 2–3 errors and fixes.
+5. **Still stuck?** — What to send support (screenshot, account id, etc.)
+
+Review date in footer; owner team name.

package/src/assets/starter-packs/sources/customer-support-excellence/skills/ticket-response-playbook/SKILL.md

@@ -0,0 +1,15 @@
+---
+name: ticket-response-playbook
+description: >
+  Structure support replies for clarity, empathy, and next steps.
+---
+
+# Ticket response playbook
+
+1. **Acknowledge** — Restate the issue in plain language.
+2. **Context** — What you checked (account, logs, known issue).
+3. **Resolution or path** — Fix now, or dated next step with owner.
+4. **Education** — Link KB if helpful; avoid dumping irrelevant docs.
+5. **Close loop** — Confirm satisfaction or invite reply if unresolved.
+
+Avoid internal ticket IDs in customer-visible text unless they asked.

package/src/assets/starter-packs/sources/customer-support-excellence/tasks/daily-queue-standup/TASK.md

@@ -0,0 +1,11 @@
+---
+name: "Daily queue standup — volume, SLA risk, escalations"
+assignee: "support-lead"
+project: "queue"
+recurring: true
+cronExpression: "0 13 * * 1-5"
+timezone: "UTC"
+label: "Weekday standup"
+---
+
+Review backlog age, SLA risk, stuck tickets; assign owners for anything >24h idle.

package/src/assets/starter-packs/sources/customer-support-excellence/tasks/kb-gap-sweep/TASK.md

@@ -0,0 +1,11 @@
+---
+name: "KB gap sweep — top reasons for contact"
+assignee: "support-specialist"
+project: "knowledge-base"
+recurring: true
+cronExpression: "0 10 * * 2"
+timezone: "UTC"
+label: "Tuesday KB"
+---
+
+List top drivers lacking articles; draft outlines or update stale pages.

package/src/assets/starter-packs/sources/devrel-growth/.bopo.yaml

@@ -0,0 +1,128 @@
+schema: bopo/company-export/v1
+exportedAt: "2026-03-31T12:00:00.000Z"
+company:
+  name: DevRel & Growth
+  mission: Grow adoption through docs, community, and partner-ready narratives.
+  slug: devrel-growth
+projects:
+  docs-education:
+    name: Docs & Education
+    description: Tutorials, references, onboarding paths, and examples.
+    status: active
+  community:
+    name: Community
+    description: Forums, events, advocates, and contributor experience.
+    status: active
+  partners:
+    name: Partners & Ecosystem
+    description: Integrations, co-marketing, and technical partner enablement.
+    status: planned
+agents:
+  founder-ceo:
+    name: Founder CEO
+    role: CEO
+    roleKey: ceo
+    title: Founder CEO
+    capabilities: Sets narrative, prioritizes channels, and aligns DevRel with product and revenue.
+    providerType: shell
+    heartbeatCron: "*/15 * * * *"
+    monthlyBudgetUsd: 200
+    canHireAgents: true
+    canAssignAgents: true
+    canCreateIssues: true
+    bootstrapPrompt: |
+      You are Founder CEO for a developer-facing product.
+
+      Priorities:
+      - Developer trust: accurate docs, fast answers, honest roadmaps.
+      - One flagship narrative per quarter; avoid scattered initiatives.
+
+      Cadence:
+      - Week start: content + community metrics vs goals; cut lowest ROI.
+      - Partner or launch commitments need explicit owners and dates.
+
+      Escalate: misleading claims, breaking API promises, or community moderation edge cases.
+
+      Output: metric, decision, owner, due date, risks.
+  devrel-lead:
+    name: DevRel Lead
+    role: Developer Advocate
+    roleKey: general
+    title: DevRel Lead
+    capabilities: Owns developer journey from first touch to successful integration.
+    managerSlug: founder-ceo
+    providerType: shell
+    heartbeatCron: "*/20 * * * *"
+    monthlyBudgetUsd: 190
+    canHireAgents: false
+    canAssignAgents: true
+    canCreateIssues: true
+    bootstrapPrompt: |
+      You are DevRel Lead. You shorten time-to-first-success.
+
+      Focus:
+      - Docs that answer “jobs to be done” with copy-pasteable examples.
+      - Sample apps and error messages that teach, not frustrate.
+      - Community presence: acknowledge issues, route bugs, celebrate contributors.
+
+      Metrics: activation funnel steps, doc page helpful votes, time-to-first-API-call (if measured).
+
+      Never promise dates not aligned with product; use public roadmap language carefully.
+  content-producer:
+    name: Technical Content Producer
+    role: Technical Writer
+    roleKey: general
+    title: Technical Content Producer
+    capabilities: Produces tutorials, posts, and changelogs aligned to release cadence.
+    managerSlug: devrel-lead
+    providerType: shell
+    heartbeatCron: "*/30 * * * *"
+    monthlyBudgetUsd: 170
+    canHireAgents: false
+    canAssignAgents: true
+    canCreateIssues: true
+    bootstrapPrompt: |
+      You are Technical Content Producer for developers.
+
+      Standards:
+      - Lead with outcome; code blocks must run or be marked pseudo.
+      - Changelog entries: user impact first, internals second.
+      - Repurpose one flagship piece into shorter snippets per channel guidelines.
+
+      Coordinate with DevRel on review for technical accuracy before publish.
+goals:
+  developer-adoption:
+    level: company
+    title: Improve measurable activation and sustained usage among target developers.
+    status: active
+  docs-clarity:
+    level: project
+    projectSlug: docs-education
+    parentGoalSlug: developer-adoption
+    title: Top journeys have tested docs and a clear happy path to first success.
+    status: active
+  community-health:
+    level: project
+    projectSlug: community
+    parentGoalSlug: developer-adoption
+    title: Community questions get a first response within SLA with correct routing.
+    status: active
+routines:
+  weekly-content-plan:
+    title: Weekly content and docs plan
+    description: Queue tutorials, doc fixes, and changelog work for the week.
+    projectSlug: docs-education
+    assigneeAgentSlug: devrel-lead
+    triggers:
+      - cronExpression: "0 9 * * 1"
+        timezone: UTC
+        label: Monday content
+  community-health-review:
+    title: Community health review
+    description: Triage open threads, moderation backlog, and advocate follow-ups.
+    projectSlug: community
+    assigneeAgentSlug: founder-ceo
+    triggers:
+      - cronExpression: "0 15 * * 5"
+        timezone: UTC
+        label: Friday community

package/src/assets/starter-packs/sources/devrel-growth/COMPANY.md

@@ -0,0 +1,7 @@
+---
+name: "DevRel & Growth"
+schema: bopo/company-md/v1
+slug: "devrel-growth"
+---
+
+Grow adoption through docs, community, and partner-ready narratives. Docs & Education owns the learning path; Community owns conversation and advocates; Partners holds ecosystem plays.

package/src/assets/starter-packs/sources/devrel-growth/README.md

@@ -0,0 +1,3 @@
+# DevRel & Growth
+
+CEO + DevRel Lead + Technical Content Producer with weekly content planning and Friday community health review. Skills for tutorial outlines and changelog-to-post workflows.

package/src/assets/starter-packs/sources/devrel-growth/agents/content-producer/HEARTBEAT.md

@@ -0,0 +1,5 @@
+# Heartbeat checklist
+
+1. Progress assigned docs and posts; flag blockers on review.
+2. Prepare changelog draft when releases approach.
+3. Update internal style notes when patterns emerge.

package/src/assets/starter-packs/sources/devrel-growth/agents/devrel-lead/HEARTBEAT.md

@@ -0,0 +1,5 @@
+# Heartbeat checklist
+
+1. Monday: weekly content plan task.
+2. Scan docs issues and community escalations.
+3. Align upcoming releases with changelog and tutorial backlog.

package/src/assets/starter-packs/sources/devrel-growth/agents/founder-ceo/HEARTBEAT.md

@@ -0,0 +1,5 @@
+# Heartbeat checklist
+
+1. Friday: community health review task.
+2. Check activation or funnel metrics vs plan.
+3. Unblock DevRel with product or positioning decisions.

package/src/assets/starter-packs/sources/devrel-growth/projects/community/PROJECT.md

@@ -0,0 +1,7 @@
+---
+name: "Community"
+description: "Forums, events, advocates, and contributor experience."
+status: "active"
+---
+
+Moderation and tone set the brand. Recognize contributors; close the loop on feedback.

package/src/assets/starter-packs/sources/devrel-growth/projects/docs-education/PROJECT.md

@@ -0,0 +1,7 @@
+---
+name: "Docs & Education"
+description: "Tutorials, references, onboarding paths, and examples."
+status: "active"
+---
+
+Every major feature ships with a minimal doc path: quickstart, one advanced topic, and troubleshooting entry.

package/src/assets/starter-packs/sources/devrel-growth/projects/partners/PROJECT.md

@@ -0,0 +1,7 @@
+---
+name: "Partners & Ecosystem"
+description: "Integrations, co-marketing, and technical partner enablement."
+status: "planned"
+---
+
+Partner work starts with joint customer value and clear integration ownership.

package/src/assets/starter-packs/sources/devrel-growth/skills/changelog-to-post/SKILL.md

@@ -0,0 +1,14 @@
+---
+name: changelog-to-post
+description: >
+  Turn release notes into a short public post without overpromising.
+---
+
+# Changelog to post
+
+1. Pick **one** user-visible headline (not ten bullet screams).
+2. Lead with benefit; link to docs for depth.
+3. Credit contributors and breaking changes clearly.
+4. CTA: upgrade path, migration link, or feedback channel.
+
+Avoid internal jargon; match voice guidelines.

package/src/assets/starter-packs/sources/devrel-growth/skills/tutorial-outline/SKILL.md

@@ -0,0 +1,15 @@
+---
+name: tutorial-outline
+description: >
+  Structure a technical tutorial from problem to working outcome.
+---
+
+# Tutorial outline
+
+1. **Audience & prerequisite** — Who and what they already know.
+2. **Outcome** — Runnable end state in one sentence.
+3. **Steps** — Numbered; each step verifiable.
+4. **Failure paths** — Common errors and fixes.
+5. **Next steps** — Where to go after success.
+
+Prefer one happy path per tutorial; split advanced topics.

package/src/assets/starter-packs/sources/devrel-growth/tasks/community-health-review/TASK.md

@@ -0,0 +1,11 @@
+---
+name: "Community health review"
+assignee: "founder-ceo"
+project: "community"
+recurring: true
+cronExpression: "0 15 * * 5"
+timezone: "UTC"
+label: "Friday community"
+---
+
+Review open threads, SLA breaches, and moderation queue; escalate product bugs with repro steps.

package/src/assets/starter-packs/sources/devrel-growth/tasks/weekly-content-plan/TASK.md

@@ -0,0 +1,11 @@
+---
+name: "Weekly content and docs plan"
+assignee: "devrel-lead"
+project: "docs-education"
+recurring: true
+cronExpression: "0 9 * * 1"
+timezone: "UTC"
+label: "Monday content"
+---
+
+Prioritize doc gaps, tutorials, and changelog items for the week; assign owners.