@lovelybunch/core 1.0.54 → 1.0.56

package/dist/schema-templates.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"schema-templates.d.ts","sourceRoot":"","sources":["../src/schema-templates.ts"],"names":[],"mappings":"AAQA,QAAA,MAAM,eAAe,EAAE,MAAM,CAAC,MAAM,EAAE,MAAM,CAS3C,CAAC;AAEF,OAAO,EAAE,eAAe,EAAE,CAAC"}
+{"version":3,"file":"schema-templates.d.ts","sourceRoot":"","sources":["../src/schema-templates.ts"],"names":[],"mappings":"AAgBA,QAAA,MAAM,eAAe,EAAE,MAAM,CAAC,MAAM,EAAE,MAAM,CAS3C,CAAC;AAEF,OAAO,EAAE,eAAe,EAAE,CAAC"}

package/dist/schema-templates.js

@@ -1,9 +1,14 @@
-import { readFileSync, readdirSync } from 'fs';
+import { existsSync, readFileSync, readdirSync } from 'fs';
 import path from 'path';
 import { fileURLToPath } from 'url';
 const currentFile = fileURLToPath(import.meta.url);
 const currentDir = path.dirname(currentFile);
-const schemaDir = path.resolve(currentDir, '../../shared/system-prompts/schema');
+const packagedSchemaDir = path.resolve(currentDir, 'system-prompts', 'schema');
+const workspaceSchemaDir = path.resolve(currentDir, '..', '..', 'shared', 'system-prompts', 'schema');
+const schemaDir = existsSync(packagedSchemaDir) ? packagedSchemaDir : workspaceSchemaDir;
+if (!existsSync(schemaDir)) {
+    throw new Error(`Schema templates directory not found. Looked in: ${packagedSchemaDir} or ${workspaceSchemaDir}`);
+}
 const schemaTemplates = Object.fromEntries(readdirSync(schemaDir)
     .filter((file) => file.endsWith('.md'))
     .sort()

package/dist/schema-templates.js.map

@@ -1 +1 @@
-{"version":3,"file":"schema-templates.js","sourceRoot":"","sources":["../src/schema-templates.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,YAAY,EAAE,WAAW,EAAE,MAAM,IAAI,CAAC;AAC/C,OAAO,IAAI,MAAM,MAAM,CAAC;AACxB,OAAO,EAAE,aAAa,EAAE,MAAM,KAAK,CAAC;AAEpC,MAAM,WAAW,GAAG,aAAa,CAAC,MAAM,CAAC,IAAI,CAAC,GAAG,CAAC,CAAC;AACnD,MAAM,UAAU,GAAG,IAAI,CAAC,OAAO,CAAC,WAAW,CAAC,CAAC;AAC7C,MAAM,SAAS,GAAG,IAAI,CAAC,OAAO,CAAC,UAAU,EAAE,oCAAoC,CAAC,CAAC;AAEjF,MAAM,eAAe,GAA2B,MAAM,CAAC,WAAW,CAChE,WAAW,CAAC,SAAS,CAAC;KACnB,MAAM,CAAC,CAAC,IAAI,EAAE,EAAE,CAAC,IAAI,CAAC,QAAQ,CAAC,KAAK,CAAC,CAAC;KACtC,IAAI,EAAE;KACN,GAAG,CAAC,CAAC,IAAI,EAAE,EAAE;IACZ,MAAM,YAAY,GAAG,IAAI,CAAC,IAAI,CAAC,SAAS,EAAE,IAAI,CAAC,CAAC;IAChD,MAAM,OAAO,GAAG,YAAY,CAAC,YAAY,EAAE,OAAO,CAAC,CAAC;IACpD,OAAO,CAAC,IAAI,EAAE,OAAO,CAAC,CAAC;AACzB,CAAC,CAAC,CACL,CAAC;AAEF,OAAO,EAAE,eAAe,EAAE,CAAC"}
+{"version":3,"file":"schema-templates.js","sourceRoot":"","sources":["../src/schema-templates.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,UAAU,EAAE,YAAY,EAAE,WAAW,EAAE,MAAM,IAAI,CAAC;AAC3D,OAAO,IAAI,MAAM,MAAM,CAAC;AACxB,OAAO,EAAE,aAAa,EAAE,MAAM,KAAK,CAAC;AAEpC,MAAM,WAAW,GAAG,aAAa,CAAC,MAAM,CAAC,IAAI,CAAC,GAAG,CAAC,CAAC;AACnD,MAAM,UAAU,GAAG,IAAI,CAAC,OAAO,CAAC,WAAW,CAAC,CAAC;AAE7C,MAAM,iBAAiB,GAAG,IAAI,CAAC,OAAO,CAAC,UAAU,EAAE,gBAAgB,EAAE,QAAQ,CAAC,CAAC;AAC/E,MAAM,kBAAkB,GAAG,IAAI,CAAC,OAAO,CAAC,UAAU,EAAE,IAAI,EAAE,IAAI,EAAE,QAAQ,EAAE,gBAAgB,EAAE,QAAQ,CAAC,CAAC;AAEtG,MAAM,SAAS,GAAG,UAAU,CAAC,iBAAiB,CAAC,CAAC,CAAC,CAAC,iBAAiB,CAAC,CAAC,CAAC,kBAAkB,CAAC;AAEzF,IAAI,CAAC,UAAU,CAAC,SAAS,CAAC,EAAE,CAAC;IAC3B,MAAM,IAAI,KAAK,CAAC,oDAAoD,iBAAiB,OAAO,kBAAkB,EAAE,CAAC,CAAC;AACpH,CAAC;AAED,MAAM,eAAe,GAA2B,MAAM,CAAC,WAAW,CAChE,WAAW,CAAC,SAAS,CAAC;KACnB,MAAM,CAAC,CAAC,IAAI,EAAE,EAAE,CAAC,IAAI,CAAC,QAAQ,CAAC,KAAK,CAAC,CAAC;KACtC,IAAI,EAAE;KACN,GAAG,CAAC,CAAC,IAAI,EAAE,EAAE;IACZ,MAAM,YAAY,GAAG,IAAI,CAAC,IAAI,CAAC,SAAS,EAAE,IAAI,CAAC,CAAC;IAChD,MAAM,OAAO,GAAG,YAAY,CAAC,YAAY,EAAE,OAAO,CAAC,CAAC;IACpD,OAAO,CAAC,IAAI,EAAE,OAAO,CAAC,CAAC;AACzB,CAAC,CAAC,CACL,CAAC;AAEF,OAAO,EAAE,eAAe,EAAE,CAAC"}

package/dist/system-prompts/coconut-assistant.md

@@ -0,0 +1,25 @@
+You are the Coconut 🥥 AI assistant for agent‑native development workflows.
+
+Goals
+- Help developers with proposals, architecture decisions, planning, and execution.
+- Be precise, actionable, and concise; favor stepwise guidance over essays.
+- Respect repository context and any user‑provided documents.
+- Ask clarifying questions when requirements are ambiguous.
+
+Style
+- Use monospace for commands, paths, and code identifiers.
+- Prefer short, direct sentences; avoid filler.
+- Offer succinct next-step options when helpful.
+
+Knowledge Base
+- Proactively notice when the conversation surfaces durable knowledge (research summaries, improved docs, reusable insights) and offer to save it into `.nut/context/knowledge`.
+- When you have a knowledge document ready to review, respond with a short natural-language summary followed by a fenced code block tagged `knowledge_action` containing JSON:
+  - `action`: `"create"` or `"update"`
+  - `title`: human-readable title for the document
+  - `filename`: existing file name for updates (include the `.md` suffix)
+  - `summary`: concise description of what changed and why it matters
+  - `content`: complete markdown body that follows the guidance in `.nut/.schema/knowledge.schema.md`
+  - `metadata`: optional object (`category`, `tags`, `sources`, `related`, `owner`, `audience`, etc.) with arrays expanded, not left undefined
+- Use this pattern when refining user-supplied documents (e.g., `project.md`) so the UI can show “View diff” and “Update knowledge.md” actions.
+- Only execute the `knowledge_documents` MCP tool automatically after the user confirms they want the change; otherwise provide the structured payload so they can approve or adjust it.
+- When system messages include context documents, assume you already have the full text—do not ask the user to reshare it; instead, propose revisions or actions directly.

package/dist/system-prompts/schema/agent.schema.md

@@ -0,0 +1,36 @@
+---
+name: design-quality-specialist
+description: |
+  Example agent profile that reviews UI changes for adherence to brand and accessibility guidelines.
+color: teal
+tools:
+  - Read
+  - Write
+  - MultiEdit
+  - Bash
+  - Git
+createdAt: '2025-09-20T15:00:00.000Z'
+updatedAt: '2025-09-21T09:00:00.000Z'
+version: '1.0.0'
+focusAreas:
+  - Flag unintended visual regressions before release.
+  - Coach contributors on meeting accessibility targets.
+contextPreferences:
+  - .nut/context/project.md
+  - .nut/.schema/proposal.schema.md
+---
+# Agent Schema Example
+
+Spell out the responsibilities, decision-making guidance, and success criteria for the agent.
+
+## Responsibilities
+
+Explain the situations where this agent should be invoked and how it collaborates with humans.
+
+## Playbooks
+
+Outline repeatable steps the agent should follow when executing its responsibilities.
+
+## Escalation
+
+Clarify when the agent should raise issues or hand back to a human teammate.

package/dist/system-prompts/schema/architecture.schema.md

@@ -0,0 +1,57 @@
+---
+version: '1.0'
+updated: '2025-09-21'
+type: architecture
+tags:
+  - reference
+  - engineering
+stack:
+  runtime: node
+  framework: hono
+  language: typescript
+  database: postgres
+  deployment: vercel
+  repository: https://github.com/lovelybunch/coconut
+commands:
+  install: pnpm install
+  dev: pnpm dev
+  test: pnpm test
+  build: pnpm build
+  deploy: pnpm --filter @lovelybunch/api deploy
+systems:
+  frontend: packages/frontend
+  api: packages/api
+  cli: packages/cli
+  shared: packages/shared
+integrationPoints:
+  - name: Claude MCP server
+    description: Provides remote tool access for the AI assistant.
+    protocol: http
+    url: https://mcp.lovelybunch.dev
+observability:
+  logging: pino
+  metrics: prometheus
+  tracing: opentelemetry
+---
+# Architecture Schema Example
+
+Describe the high-level system, directory layout, major data flows, and operational considerations.
+
+## System Diagram
+
+Capture the primary components and how they interact.
+
+## Data Flow
+
+Document how information moves between services, including ingress, processing, and persistence.
+
+## Operational Notes
+
+Track deployment strategy, scaling thresholds, and recovery procedures.
+
+## Development Conventions
+
+- **File Naming:** kebab-case for files, camelCase for variables.
+- **Code Style:** ESLint + Prettier enforced via CI.
+- **Branch Strategy:** Trunk-based with short-lived feature branches.
+- **Commit Format:** Conventional Commits (`feat:`, `fix:`, etc.).

package/dist/system-prompts/schema/knowledge.schema.md

@@ -0,0 +1,37 @@
+---
+version: '1.0'
+updated: '2025-09-21'
+type: knowledge
+category: design-system
+tags:
+  - branding
+  - iconography
+sources:
+  - Design System Audit 2025-09-15
+  - Customer feedback triage 2025-09-18
+related:
+  - .nut/context/project.md
+  - .nut/.schema/proposal.schema.md
+owner:
+  name: Kevin Bluer
+  email: kevin@bluer.com
+audience:
+  - Designers
+  - Frontend Engineers
+status: active
+---
+# Knowledge Schema Example
+
+Document durable learnings, guidelines, and references that support the team.
+
+## Key Takeaways
+
+List the most important facts, decisions, and rationales.
+
+## References
+
+Link to designs, proposals, experiments, and conversations that informed the knowledge.
+
+## Follow-ups
+
+Capture open questions or next steps for the team to investigate.

package/dist/system-prompts/schema/project.schema.md

@@ -0,0 +1,71 @@
+---
+version: '1.0'
+updated: '2025-09-21'
+type: project
+status: active
+category: overview
+tags:
+  - palm-tree-refresh
+  - ui
+project:
+  name: Coconut Palm Refresh
+  description: Align shared branding assets with the neutral palette across all surfaces.
+  website: https://coconut.dev
+  version: '2.3.0'
+  stage: production
+owners:
+  product:
+    name: Steve Jobs
+    email: steve@apple.com
+  engineering:
+    name: Coconut AI
+    email: coconut.ai@lovelybunch.com
+roadmap:
+  milestones:
+    - name: Palette audit complete
+      targetDate: '2025-09-18'
+      owners:
+        - design-team
+    - name: Updated assets shipped
+      targetDate: '2025-09-28'
+      owners:
+        - frontend-team
+dependencies:
+  repositories:
+    - https://github.com/lovelybunch/coconut-design-system
+  stakeholders:
+    - Marketing
+    - Customer Support
+communication:
+  standups:
+    cadence: weekly
+    channel: '#coconut-brand-refresh'
+  statusReports:
+    frequency: bi-weekly
+    audience:
+      - leadership
+      - design
+---
+# Project Schema Example
+
+Use this structure to capture project identity, goals, roadmap, and coordination details.
+
+## Overview
+
+Summarize the mission, scope boundaries, and target customers.
+
+## Current Status
+
+Highlight what is complete, in progress, blocked, and upcoming.
+
+## Goals & Success Metrics
+
+Document the primary project ambition, the key metrics used to assess success, and any explicit non-goals in markdown. For example:
+
+- **Primary Goal:** Introduce automated moderation to reduce manual review load.
+- **Success Metrics:** Time-to-triage under 5 minutes, 95% precision on high-risk flags.
+- **Non-Goals:** Real-time interventions, policy redesign.
+
+## Resources
+
+List repositories, docs, dashboards, and any external references the team relies on.

package/dist/system-prompts/schema/proposal.schema.md

@@ -0,0 +1,179 @@
+---
+id: cp-1758376921669
+intent: Remove the green color for the palm tree icon in the top left header
+createdAt: '2025-09-20T14:02:01.669Z'
+updatedAt: '2025-09-21T09:05:45.123Z'
+status: draft
+priority: medium
+productSpecRef: specs/ui-refresh.md
+author:
+  id: current-user
+  name: Steve Jobs
+  email: apple@apple.com
+  role: engineer
+  type: human
+plan:
+  estimatedDuration: 'P2D'
+  dependencies:
+    - .nut/context/architecture.md
+    - packages/frontend/src/components/AppLogo.tsx
+  steps:
+    - id: step-01
+      description: Audit every usage of the palm tree icon across the frontend.
+      status: completed
+      expectedOutcome: Inventory of components with the hard-coded fill.
+      command: pnpm --filter @lovelybunch/frontend lint
+      executedAt: '2025-09-20T17:45:00.000Z'
+    - id: step-02
+      description: Replace hard-coded green fills with the neutral brand token.
+      status: in-progress
+      expectedOutcome: All icons inherit shared theme tokens.
+    - id: step-03
+      description: Update visual regression tests and document changes.
+      status: pending
+      expectedOutcome: Screenshots reflect the new neutral color.
+tags:
+  - branding
+  - accessibility
+labels:
+  - ui-refresh
+  - iteration-21
+comments:
+  - id: cmt-01
+    author: design-review@lovelybunch.com
+    content: Confirm alignment with the design system palette before merging.
+    createdAt: '2025-09-20T19:10:00.000Z'
+  - id: cmt-02
+    author: qa-team@lovelybunch.com
+    content: Please include snapshots from the regression suite in evidence.
+    createdAt: '2025-09-21T08:30:00.000Z'
+evidence:
+  - type: screenshot
+    description: Before and after comparison exported from Storybook.
+    data: artifacts/screenshots/logo-before-after.png
+    timestamp: '2025-09-21T08:45:00.000Z'
+  - type: test
+    description: Jest snapshot update for the header logo.
+    data:
+      command: pnpm --filter @lovelybunch/frontend test -- Logo
+      result: passed
+    timestamp: '2025-09-21T08:50:00.000Z'
+policies:
+  - id: policy-brand
+    name: Brand consistency
+    description: Any palette change must be approved by design.
+    status: passed
+    message: Confirmed by Design Systems lead.
+    checkedAt: '2025-09-21T08:55:00.000Z'
+featureFlags:
+  - id: flag-ui-logo-color
+    version: v1
+    name: ui-logo-neutral
+    description: Gradually roll out the neutral palm tree icon.
+    type: boolean
+    defaultValue: false
+    scopes:
+      - web
+      - desktop
+    targets:
+      - audience: internal
+        value: true
+        percentage: 100
+    killSwitch: true
+    dependencies: []
+    createdAt: '2025-09-20T14:05:00.000Z'
+    updatedAt: '2025-09-21T08:45:00.000Z'
+experiments:
+  - id: exp-logo-sentiment
+    name: Logo sentiment experiment
+    hypothesis: A neutral logo improves trust without reducing recognition.
+    variants:
+      - id: control
+        name: current-logo
+        description: Maintains the green fill.
+        allocation: 50
+        config:
+          asset: logo-green.svg
+      - id: treatment
+        name: neutral-logo
+        description: Uses the neutral brand token.
+        allocation: 50
+        config:
+          asset: logo-neutral.svg
+    allocation:
+      method: random
+      totalAllocation: 20
+    successMetrics:
+      - trust_score
+      - click_through_header
+    guardrailMetrics:
+      - name: bounce_rate
+        threshold: 5
+        comparison: greater
+        action: alert
+    stopRules:
+      - metric: trust_score
+        condition: treatment <= control
+        action: pause
+    analysisConfig:
+      confidenceLevel: 0.95
+      minimumSampleSize: 500
+      testType: two-tailed
+    status: draft
+telemetryContracts:
+  - eventName: header_logo_rendered
+    version: '2025-09-20'
+    schema:
+      iconFill: string
+      theme: string
+    piiFields: []
+    samplingRate: 1
+    retentionPolicy:
+      duration: 30
+      deleteAfter: 90
+    approvals: []
+releasePlan:
+  strategy: gradual
+  stages:
+    - name: design-review
+      percentage: 10
+      duration: 4
+      criteria:
+        - Design approval recorded in comments.
+    - name: staging
+      percentage: 30
+      duration: 12
+      criteria:
+        - No visual diffs detected.
+    - name: production
+      percentage: 60
+      duration: 24
+      criteria:
+        - Support team informed.
+  schedule: '2025-09-25T09:00:00.000Z'
+  rollbackPlan: Revert to the previous SVG asset and restore original theme tokens.
+aiInteractions:
+  - id: ai-01
+    timestamp: '2025-09-20T14:10:00.000Z'
+    model: claude-3.5
+    prompt: Suggest implementation plan for updating the shared logo asset.
+    response: Validate the SVG once shared tokens are in place and run visual regression tests.
+    tokens:
+      prompt: 820
+      completion: 260
+      total: 1080
+---
+# Proposal Schema Example
+
+This file demonstrates the full front matter and content structure Coconut expects for change proposals.
+- Keep arrays populated with meaningful objects, not empty lists.
+- Update timestamps using ISO 8601 format.
+- Maintain sections below the front matter for narrative context and status updates.
+
+## Problem Statement
+
+Document why the change is needed, who benefits, and which constraints apply.
+
+## Implementation Notes
+
+Summarize critical decisions, risks, follow-up work, and any files that must be touched.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@lovelybunch/core",
-  "version": "1.0.54",
+  "version": "1.0.56",
   "description": "Core Coconut functionality",
   "type": "module",
   "main": "./dist/index.js",
@@ -24,13 +24,14 @@
   },
   "scripts": {
     "build": "tsc",
+    "postbuild": "node ./scripts/copy-schema.mjs",
     "dev": "tsc --watch",
     "clean": "rm -rf dist tsconfig.tsbuildinfo",
     "type-check": "tsc --noEmit",
     "test": "vitest run"
   },
   "dependencies": {
-    "@lovelybunch/types": "^1.0.54",
+    "@lovelybunch/types": "^1.0.56",
     "gray-matter": "^4.0.3",
     "fuse.js": "^7.0.0",
     "nanoid": "^5.0.6"