@robbiesrobotics/alice-agents 1.5.10 → 1.5.13

package/templates/workspaces/devon/USER.md

@@ -1,13 +0,0 @@
-# USER.md - About Your Human
-
-- **Name:** Rob
-- **What to call them:** Rob
-- **Timezone:** America/New_York
-- **Notes:** Developer, entrepreneur, and creator of the A.L.I.C.E. framework.
-
-## Context
-
-- Rob is building a multi-agent orchestration platform (A.L.I.C.E.)
-- You are one of 28 agents in the A.L.I.C.E. system
-- Olivia is the orchestrator — she coordinates all specialists
-- Be helpful, competent, and slightly snarky when appropriate

package/templates/workspaces/devon/check_github.py

@@ -1,12 +0,0 @@
-#!/usr/bin/env python3
-import json, sys, urllib.request
-
-# GitHub API - check builderz-labs/mission-control git tree for runtime/nodes files
-url = 'https://api.github.com/repos/builderz-labs/mission-control/git/trees/HEAD?recursive=1'
-req = urllib.request.Request(url, headers={'Accept': 'application/vnd.github.v3+json', 'User-Agent': 'Devon'})
-with urllib.request.urlopen(req, timeout=15) as resp:
-    data = json.loads(resp.read())
-
-matches = [x for x in data.get('tree', []) if 'runtime' in x['path'] or 'heartbeat' in x['path'] or ('nodes' in x['path'] and 'heartbeat' in x.get('path', ''))]
-for x in matches:
-    print(x['path'])

package/templates/workspaces/devon/check_mc_env.py

@@ -1,30 +0,0 @@
-#!/usr/bin/env python3
-import json, subprocess
-
-token = json.load(open('/Users/aliceclaw/.vercel/auth'))['token']
-
-# Get mc-final project full config
-result = subprocess.run(
-    ['curl', '-s', f'https://api.vercel.com/v6/projects/mc-final?teamId=robbiesrobotics-7692s-projects',
-     '-H', f'Authorization: Bearer {token}'],
-    capture_output=True, text=True
-)
-data = json.loads(result.stdout)
-git = data.get('git', {})
-print(f"Git repo: {git.get('repo','?')}")
-print(f"Git type: {git.get('type','?')}")
-print(f"Git deployed约: {git.get('deployedDeployments',[])}")
-print(f"Build command: {data.get('buildCommand',{})}")
-print(f"Install command: {data.get('installCommand',{})}")
-print(f"Dev command: {data.get('devCommand',{})}")
-print(f"Framework: {data.get('framework','?')}")
-
-# Try to get deployments
-result2 = subprocess.run(
-    ['curl', '-s', f'https://api.vercel.com/v6/deployments?teamId=robbiesrobotics-7692s-projects&projectName=mc-final&limit=3',
-     '-H', f'Authorization: Bearer {token}'],
-    capture_output=True, text=True
-)
-data2 = json.loads(result2.stdout)
-for d in data2.get('deployments', []):
-    print(f"\nDeploy: {d['uid']} | {d['state']} | {d.get('meta',{}).get('githubCommitSha','?')[:12]} | {d.get('meta',{}).get('githubCommitMessage','?')[:60]}")

package/templates/workspaces/devon/check_sb.py

@@ -1,34 +0,0 @@
-#!/usr/bin/env python3
-"""Direct Supabase gateway_connections heartbeat update + file search."""
-import json, subprocess
-
-SB_URL = 'https://xxxgvtwnlbtdgmlgccee.supabase.co'
-SB_KEY = 'eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJzdXBhYmFzZSIsInJlZiI6Inh4eGd2dHdubGJ0ZGdtbGdjY2VlIiwicm9sZSI6InNlcnZpY2Vfcm9sZSIsImlhdCI6MTc3NDU4MjI5MCwiZXhwIjoyMDkwMTU4MjkwfQ.TM_CDuPsuHZK6HeK_pzc5NHCT-peVr16l0qUNWufXqw'
-
-# Test: check if gateway_connections table exists and has the Mac.fios-router.home row
-query = {
-    "query": "SELECT id, gateway_name, last_heartbeat, status FROM public.gateway_connections WHERE gateway_name = 'Mac.fios-router.home' LIMIT 5;"
-}
-result = subprocess.run(
-    ['curl', '-s', f'{SB_URL}/rest/v1/rpc/exec_sql',
-     '-H', f'apikey: {SB_KEY}',
-     '-H', f'Authorization: Bearer {SB_KEY}',
-     '-H', 'Content-Type: application/json',
-     '-d', json.dumps(query)],
-    capture_output=True, text=True
-)
-print("Query result:", result.stdout[:500])
-
-# Also check all gateway_connections rows
-query2 = {
-    "query": "SELECT id, gateway_name, last_heartbeat, status FROM public.gateway_connections LIMIT 10;"
-}
-result2 = subprocess.run(
-    ['curl', '-s', f'{SB_URL}/rest/v1/rpc/exec_sql',
-     '-H', f'apikey: {SB_KEY}',
-     '-H', f'Authorization: Bearer {SB_KEY}',
-     '-H', 'Content-Type: application/json',
-     '-d', json.dumps(query2)],
-    capture_output=True, text=True
-)
-print("All rows:", result2.stdout[:500])

package/templates/workspaces/devon/check_vercel.py

@@ -1,12 +0,0 @@
-#!/usr/bin/env python3
-import json, subprocess
-
-token = json.load(open('/Users/aliceclaw/.vercel/auth'))['token']
-
-result = subprocess.run(
-    ['curl', '-s', f'https://api.vercel.com/v6/projects/mc-final?teamId=robbiesrobotics-7692s-projects',
-     '-H', f'Authorization: Bearer {token}'],
-    capture_output=True, text=True
-)
-data = json.loads(result.stdout)
-print(json.dumps(data, indent=2)[:2000])

package/templates/workspaces/devon/get_mc_files.py

@@ -1,17 +0,0 @@
-#!/usr/bin/env python3
-"""Download Vercel deployment file tree for mc-final."""
-import json, subprocess
-
-token = json.load(open('/Users/aliceclaw/.vercel/auth'))['token']
-uid = 'dpl_FaYDF8KSdg9qnGrC99kfSSf4WxCN'
-team = 'robbiesrobotics-7692s-projects'
-
-# Get file list
-result = subprocess.run(
-    ['curl', '-s', f'https://api.vercel.com/v6/deployments/{uid}/files?teamId={team}',
-     '-H', f'Authorization: Bearer {token}'],
-    capture_output=True, text=True
-)
-raw = result.stdout
-print(f"Length: {len(raw)}")
-print(f"First 200: {repr(raw[:200])}")

package/templates/workspaces/devon/write_heartbeat.py

@@ -1,67 +0,0 @@
-import os
-
-content = """import { NextRequest, NextResponse } from 'next/server'
-
-const SUPABASE_URL = process.env.NEXT_PUBLIC_SUPABASE_URL!
-const SERVICE_KEY = process.env.SUPABASE_SERVICE_ROLE_KEY!
-const AUTH_TOKEN = 'mc_worker_164bb779164a780da36df4f5272dc38c784f6f1e'
-
-async function supabaseRequest(method: string, path: string, body?: unknown) {
-  const url = `${SUPABASE_URL}/rest/v1/${path}`
-  const res = await fetch(url, {
-    method,
-    headers: {
-      'Content-Type': 'application/json',
-      'apikey': SERVICE_KEY,
-      'Authorization': `Bearer ${SERVICE_KEY}`,
-      'Prefer': method === 'GET' ? 'return=representation' : 'return=minimal',
-    },
-    body: body ? JSON.stringify(body) : undefined,
-  })
-  const data = await res.text()
-  return { ok: res.ok, status: res.status, data }
-}
-
-export async function GET() {
-  return NextResponse.json({ ok: true, commands: [] })
-}
-
-export async function POST(request: NextRequest) {
-  const authHeader = request.headers.get('authorization')
-  if (authHeader !== `Bearer ${AUTH_TOKEN}`) {
-    return NextResponse.json({ error: 'Unauthorized' }, { status: 401 })
-  }
-
-  let body: { nodeId?: string; status?: string }
-  try {
-    body = await request.json()
-  } catch {
-    return NextResponse.json({ error: 'Invalid request body' }, { status: 400 })
-  }
-
-  const { nodeId, status } = body
-  if (!nodeId) {
-    return NextResponse.json({ error: 'nodeId is required' }, { status: 400 })
-  }
-
-  const { ok, data } = await supabaseRequest(
-    'PATCH',
-    `gateway_connections?gateway_name=eq.${nodeId}`,
-    {
-      last_heartbeat: new Date().toISOString(),
-      status: status === 'offline' ? 'disconnected' : 'connected',
-    }
-  )
-
-  if (!ok) {
-    return NextResponse.json({ error: 'Failed to update heartbeat', detail: data }, { status: 500 })
-  }
-
-  return NextResponse.json({ ok: true })
-}
-"""
-
-path = '/Users/aliceclaw/.openclaw/workspace/apps/mission-control-web/src/app/api/v1/runtime/nodes/heartbeat/route.ts'
-with open(path, 'w') as f:
-    f.write(content)
-print(f"Written to {path}")

package/templates/workspaces/dylan/.env.example

@@ -1,33 +0,0 @@
-# A.L.I.C.E. Stripe Webhook Handler — Environment Variables
-# Copy to ~/alice-observability/.env and fill in Rob's values
-# Then: source ~/alice-observability/.env  (or restart the service)
-
-# ── Stripe ─────────────────────────────────────────────────────────────────────
-# Get from: Stripe Dashboard → Developers → API Keys
-STRIPE_SECRET_KEY=sk_live_...           # Live secret key (swap from sk_test_ for dev)
-
-# Get from: Stripe Dashboard → Developers → Webhooks → your endpoint → Signing secret
-STRIPE_WEBHOOK_SECRET=whsec_...
-
-# Price IDs — get from: Stripe Dashboard → Products → Pro/Cloud → Price → API ID
-STRIPE_PRO_PRICE_ID=price_...
-STRIPE_CLOUD_PRICE_ID=price_...
-
-# ── Supabase ───────────────────────────────────────────────────────────────────
-# URL: https://tfodkdtknoaodavakajg.supabase.co (known)
-# Service role key: Supabase Dashboard → Project Settings → API → service_role key
-SUPABASE_URL=https://tfodkdtknoaodavakajg.supabase.co
-SUPABASE_SERVICE_ROLE_KEY=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9...
-
-# ── n8n ────────────────────────────────────────────────────────────────────────
-# URL for the n8n welcome email webhook trigger
-# Format: http://<ubuntu-desktop-ip>:5678/webhook/stripe-checkout-completed
-N8N_WEBHOOK_URL=http://100.106.110.119:5678/webhook/stripe-checkout-completed
-
-# ── Resend (email delivery) ────────────────────────────────────────────────────
-# Get from: https://resend.com/api-keys
-RESEND_API_KEY=re_...
-
-# ── Flask Server ───────────────────────────────────────────────────────────────
-FLASK_HOST=0.0.0.0
-FLASK_PORT=5001

package/templates/workspaces/dylan/00007_verify_licenses_table.sql

@@ -1,100 +0,0 @@
--- Migration: 00007_verify_licenses_table.sql
--- Purpose: Verify/create the licenses table for Stripe webhook fulfillment
--- Project: tfodkdtknoaodavakajg.supabase.co
--- Run: psql $SUPABASE_DB_URL -f 00007_verify_licenses_table.sql
-
--- The licenses table was created by migration 00006_licenses.sql (v1.4.8).
--- This migration adds missing indexes and verifies the table is properly configured.
-
--- ─── Licenses Table ────────────────────────────────────────────────────────────
-
-CREATE TABLE IF NOT EXISTS public.licenses (
-    id                  TEXT PRIMARY KEY DEFAULT 'lic-' || substr(md5(random()::text), 1, 12),
-    key                 TEXT NOT NULL UNIQUE DEFAULT
-        'ALICE-' || upper(substr(md5(random()::text), 1, 4))
-        || '-'    || upper(substr(md5(random()::text), 1, 4))
-        || '-'    || upper(substr(md5(random()::text), 1, 4)),
-    email               TEXT NOT NULL,
-    plan                TEXT NOT NULL DEFAULT 'pro',
-    stripe_session_id   TEXT,
-    stripe_customer_id  TEXT,
-    purchased_at        TIMESTAMPTZ NOT NULL DEFAULT now(),
-    revoked             BOOLEAN NOT NULL DEFAULT false,
-    revoked_at          TIMESTAMPTZ,
-    metadata            JSONB DEFAULT '{}'::jsonb
-);
-
--- Unique index on stripe_session_id (deduplication key for webhooks)
-CREATE UNIQUE INDEX IF NOT EXISTS idx_licenses_stripe_session_id
-    ON public.licenses(stripe_session_id)
-    WHERE stripe_session_id IS NOT NULL;
-
--- Index on key (license validation lookups)
-CREATE UNIQUE INDEX IF NOT EXISTS idx_licenses_key
-    ON public.licenses(key);
-
--- Index on email
-CREATE INDEX IF NOT EXISTS idx_licenses_email
-    ON public.licenses(email);
-
--- ─── Teams Table ───────────────────────────────────────────────────────────────
-
-CREATE TABLE IF NOT EXISTS public.teams (
-    id           BIGSERIAL PRIMARY KEY,
-    name         TEXT NOT NULL,
-    slug         TEXT NOT NULL UNIQUE,
-    plan         TEXT NOT NULL DEFAULT 'pro',
-    owner_email  TEXT NOT NULL,
-    created_at   TIMESTAMPTZ NOT NULL DEFAULT now(),
-    metadata     JSONB DEFAULT '{}'::jsonb
-);
-
-CREATE INDEX IF NOT EXISTS idx_teams_slug ON public.teams(slug);
-CREATE INDEX IF NOT EXISTS idx_teams_owner_email ON public.teams(owner_email);
-
--- ─── Team Tokens Table ─────────────────────────────────────────────────────────
-
-CREATE TABLE IF NOT EXISTS public.team_tokens (
-    id           BIGSERIAL PRIMARY KEY,
-    team_id      BIGINT REFERENCES public.teams(id) ON DELETE CASCADE,
-    license_key  TEXT NOT NULL,
-    ingest_token TEXT NOT NULL UNIQUE,
-    worker_token TEXT NOT NULL UNIQUE,
-    created_at   TIMESTAMPTZ NOT NULL DEFAULT now(),
-    metadata     JSONB DEFAULT '{}'::jsonb
-);
-
-CREATE INDEX IF NOT EXISTS idx_team_tokens_team_id ON public.team_tokens(team_id);
-CREATE INDEX IF NOT EXISTS idx_team_tokens_license_key ON public.team_tokens(license_key);
-CREATE UNIQUE INDEX IF NOT EXISTS idx_team_tokens_ingest ON public.team_tokens(ingest_token);
-
--- ─── Row Level Security ────────────────────────────────────────────────────────
--- For service role (webhook handler): full access
--- For anon: read-only by key only
-
-ALTER TABLE public.licenses ENABLE ROW LEVEL SECURITY;
-ALTER TABLE public.teams ENABLE ROW LEVEL SECURITY;
-ALTER TABLE public.team_tokens ENABLE ROW LEVEL SECURITY;
-
--- Service role has full access by default (no policy needed).
--- Allow anon to validate licenses by key:
-DROP POLICY IF EXISTS "licenses_anon_validate" ON public.licenses;
-CREATE POLICY "licenses_anon_validate" ON public.licenses
-    FOR SELECT USING (true);
-
--- Allow anon to find team by slug (for Mission Control):
-DROP POLICY IF EXISTS "teams_anon_read" ON public.teams;
-CREATE POLICY "teams_anon_read" ON public.teams
-    FOR SELECT USING (true);
-
-DROP POLICY IF EXISTS "team_tokens_anon_read" ON public.team_tokens;
-CREATE POLICY "team_tokens_anon_read" ON public.team_tokens
-    FOR SELECT USING (true);
-
--- ─── Verify ────────────────────────────────────────────────────────────────────
-
-SELECT 'licenses'     AS table_name, COUNT(*) AS row_count FROM public.licenses
-UNION ALL
-SELECT 'teams',                       COUNT(*)          FROM public.teams
-UNION ALL
-SELECT 'team_tokens',                COUNT(*)          FROM public.team_tokens;

package/templates/workspaces/dylan/FEEDBACK.md

@@ -1,28 +0,0 @@
-# FEEDBACK.md — User Feedback Log
-
-_Olivia writes here when Rob provides feedback about your work._
-_Read this at session startup. Incorporate active items into your approach._
-
-## Active Feedback
-
-_No feedback yet._
-
-## Resolved
-
-_Items that have been addressed and incorporated into PLAYBOOK.md._
-
-## 2026-03-17 — Architecture brief failures
-When asked to write a technical brief:
-- Your output MUST be original analysis — never return file contents you read
-- Read files silently, then write your analysis from scratch
-- If you find yourself copy-pasting code from files, stop and write prose instead
-- Complete the ENTIRE document before finishing — partial outputs are not acceptable
-- Test: before you finish, check "did I write original content, or just return file contents?" If the latter, rewrite.
-echo "✅ Dylan feedback logged"
-## 2026-03-17 — Architecture brief task failures
-When asked to write a technical/architecture brief:
-- Your output MUST be original analysis in prose — NEVER return raw file contents
-- Read files silently, synthesize, then write your analysis from scratch  
-- If asked to write a brief, your entire response should be the written document
-- Complete the ENTIRE document before finishing — partial outputs ("Let me read the files...") are failures
-- Self-check before finishing: "Is my output original analysis or just file contents?" If the latter, rewrite.

package/templates/workspaces/dylan/HEARTBEAT.md

@@ -1,5 +0,0 @@
-# HEARTBEAT.md
-
-# Keep this file empty (or with only comments) to skip heartbeat API calls.
-
-# Add tasks below when you want the agent to check something periodically.

package/templates/workspaces/dylan/IDENTITY.md

@@ -1,6 +0,0 @@
-# IDENTITY.md
-
-- **Name:** Dylan
-- **Creature:** Development specialist in the A.L.I.C.E. team
-- **Vibe:** Focused, competent, domain-expert
-- **Emoji:** 💻

package/templates/workspaces/dylan/LEARNINGS.md

@@ -1,70 +0,0 @@
-# LEARNINGS.md — Task Reflections
-
-_After completing non-trivial tasks, append a structured reflection here._
-_Olivia periodically reviews these and promotes the best patterns into PLAYBOOK.md._
-
-<!-- Entries below, newest first -->
-
-### 2026-03-20 — Mission Control overnight backend status check from repo state
-- **Outcome:** success
-- **What worked:** verifying the current branch state before touching code avoided unnecessary edits; `npm run build` and the expanded focused test suite were enough to validate the in-progress backend changes quickly
-- **What to improve:** add a lightweight schema inventory doc for tables like `session_messages` so migration gaps are obvious during backend work instead of being discovered by grep
-- **Reusable pattern:** when inheriting uncommitted backend work, first prove whether the repo is already green locally, then separate runtime-schema risks from build/test risks before deciding to patch code
-
-
-### 2026-03-20 — Mission Control overnight reconciliation check confirmed no DB change needed
-- **Outcome:** success
-- **What worked:** reading the runbook first, then verifying live table and column availability over PostgREST with the repo’s service-role key, established the effective remote schema state without risky write attempts
-- **What to improve:** expose migration-history visibility (for example `supabase_migrations.schema_migrations`) through a documented read-only path so checks can confirm exact migration IDs instead of inferring from schema effects
-- **Reusable pattern:** for additive Supabase migrations, when DB credentials or CLI link state are incomplete, confirm the live presence of migration-specific tables and columns via service-role REST probes before deciding to apply anything
-
-
-### 2026-03-20 — Mission Control MCP discovery fallback from runtime config and persisted catalog
-- **Outcome:** success
-- **What worked:** replacing the stub with a layered discovery path that first inspects local OpenClaw MCP config metadata and then falls back to persisted `ah_mcp_tools` rows kept the implementation useful without inventing an unproven remote MCP HTTP contract
-- **What to improve:** add an explicit Mission Control ⇄ OpenClaw tool-discovery contract or gateway endpoint so remote live discovery can be implemented intentionally instead of inferred from config snapshots
-- **Reusable pattern:** for partially-defined integrations, prefer supported local/runtime metadata plus persisted catalog data, normalize a few common shapes, and return soft-empty results rather than probing speculative network endpoints
-
-
-### 2026-03-20 — Mission Control safe session/message persistence fallback
-- **Outcome:** success
-- **What worked:** read the existing `memory-service`, transcript/session routes, and Supabase helpers first, then aligned the implementation to already-used `sessions` and `session_messages` tables with payload fallbacks instead of inventing a new schema contract
-- **What to improve:** centralize PostgREST schema/table error detection in a shared helper so graceful fallback behavior is consistent across the codebase
-- **Reusable pattern:** for optional Supabase-backed persistence in mixed local/hosted setups, attempt writes with a small ordered set of payload shapes, treat missing-table/missing-column errors as feature detection, cache unsupported tables in-process, and only warn on non-schema failures
-
-### 2026-03-20 — Mission Control backend/build and Supabase migration status check
-- **Outcome:** success
-- **What worked:** combined local verification (`git status`, `npm run build`, `npm test`) with direct Supabase REST probes using the service-role key to confirm cloud table presence when CLI linking/Docker status were unavailable
-- **What to improve:** add a checked-in Supabase project link/config or a documented read-only remote schema check so migration state can be verified without relying on Docker or ad hoc REST probing
-- **Reusable pattern:** when `supabase status`/`migration list` are blocked, confirm critical migration effects by querying expected tables over PostgREST with the service-role key before deciding whether any DB change is safe or necessary
-
-### 2026-03-20 — Verified Mission Control cloud reconciliation schema state
-- **Outcome:** success
-- **What worked:** using the configured Supabase URL plus service-role key to query the live PostgREST API gave a safe, direct read of remote schema/table availability without needing destructive DB access
-- **What to improve:** if exact migration-history proof matters, add a lightweight verification path for `supabase_migrations.schema_migrations` or a dedicated healthcheck RPC
-- **Reusable pattern:** when direct DB credentials are unavailable but service-role API access exists, verify migration effects by checking live tables/columns/endpoints that uniquely distinguish the target migration
-
-### 2026-03-20 — Verified Mission Control remote Supabase migration state
-- **Outcome:** success
-- **What worked:** Using repo env + service-role-backed REST probes to verify remote table presence when Supabase CLI lacked a linked project and access token.
-- **What to improve:** Keep a lightweight project-link/auth note in the repo so migration history can be checked via CLI without fallback probing.
-- **Reusable pattern:** When CLI auth/link is missing, verify additive Supabase migrations by probing expected tables/endpoints over PostgREST with the service role key before attempting any schema change.
-
-### 2026-03-24 — Stripe Pipeline build (webhook handler + n8n welcome email)
-- **Outcome:** success
-- **What worked:** reading the existing Vercel webhook handler to understand the exact flow before writing the Python version; querying the n8n SQLite database directly to extract the API key; using the n8n REST API (POST /api/v1/workflows) to import and activate the workflow programmatically.
-- **What to improve:** n8n v2.12 requires `name`, `nodes`, `connections`, and `settings` fields on create — `staticData` must be `null` not absent, and extra fields like `triggerCount` and `versionId` cause "must NOT have additional properties" errors. The `settings` field must include `executionOrder`, `saveManualExecutions`, `callerPolicy`, and `errorWorkflow`.
-- **Reusable pattern:** n8n API workflow import needs exactly `{name, nodes, connections, settings}` at minimum — any extra top-level fields cause schema validation errors.
-- **Reusable pattern:** when n8n API key is not in env vars, it can be extracted from the SQLite database at `/home/node/.n8n/database.sqlite` in the `user_api_keys` table.
-
-### 2026-03-29 — KidSpark Phase 3: Stripe v21 fixes + remaining route wiring
-- **Outcome:** success
-- **What worked:** Reading the Stripe v21 type definitions directly from node_modules to understand what changed. The task description listed 9 routes to wire but most were already complete from the previous session — careful review avoided duplicate work.
-- **What to improve:** Stripe v21 (npm stripe@21) uses API version `2026-03-25.dahlia` and made breaking type changes: `Subscription.current_period_start/end` moved to `SubscriptionItem.current_period_start/end`, `Invoice.subscription` moved to `Invoice.parent.subscription_details.subscription`. Best to drop the explicit `apiVersion` param entirely and let the SDK use its built-in default.
-- **Reusable pattern:** When Stripe SDK major version bumps, always check `node_modules/stripe/types/apiVersion.d.ts` for the expected API version, and grep changed type definitions rather than guessing.
-
-### 2026-03-23 — Architected three-product AI coding service for Rob
-- **Outcome:** success
-- **What worked:** Led with model routing table first — everyone (Rob, Devon, future devs) immediately understands where work happens. Layered architecture (n8n = orchestrator, Qdrant = brain, Langfuse = observability) kept the three offerings from becoming spaghetti.
-- **What to improve:** Should have spec'd the per-client namespace isolation in Qdrant more formally before writing the rest — it touches security and billing.
-- **Reusable pattern:** "Infrastructure first, then offerings" — always anchor model routing + node mapping before describing agent flows.

package/templates/workspaces/dylan/MEMORY.md

@@ -1,22 +0,0 @@
-# MEMORY.md — Dylan
-
-> Persistent memory for Dylan, Development specialist.
-> This file is yours — add notes, context, and learnings that should persist across sessions.
-
-## Identity
-
-- **Name:** Dylan
-- **Domain:** Development
-- **Team:** A.L.I.C.E.
-
-## Active Projects
-
-<!-- Add ongoing projects and their current status here -->
-
-## Key Notes
-
-<!-- Jot down anything important to remember across sessions -->
-
-## Decisions Made
-
-<!-- Record significant decisions and their rationale -->

package/templates/workspaces/dylan/PLAYBOOK.md

@@ -1,16 +0,0 @@
-# PLAYBOOK.md — Evolved Domain Expertise
-
-_This file is your accumulated wisdom. Olivia curates it from your LEARNINGS.md and FEEDBACK.md._
-_Consult this before starting any task. It contains proven patterns, anti-patterns, and preferences._
-
-## Patterns
-
-_Nothing yet — complete tasks and reflect to build your playbook._
-
-## Anti-Patterns
-
-_Approaches to avoid, learned from experience._
-
-## Preferences
-
-_User preferences and standards relevant to your domain._

package/templates/workspaces/dylan/SOUL.md

@@ -1,42 +0,0 @@
-# SOUL.md - Dylan, Senior Full-Stack Software Engineer
-
-_You are Dylan, part of the A.L.I.C.E. multi-agent team._
-
-## Core Truths
-
-**You are Dylan, a disciplined full-stack engineer.** You design and build backend services, APIs, and full-stack systems. You diagnose bugs from stack traces. You review PRs for correctness, not just style.
-
-**Code is a liability until proven otherwise.** Every line you add is something to maintain. Write the minimum correct implementation, then stop.
-
-**Read the codebase before writing a single line.** Understand existing patterns, conventions, and constraints before proposing changes. Don't introduce a third way of doing something that already has two.
-
-**For multi-file tasks, use Claude Code.** Don't hand-edit patches file by file when the coding agent can navigate the full codebase faster and more reliably. Delegate implementation; own the plan and verification.
-
-**Debug from evidence, not intuition.** Read the stack trace. Check the logs. Form a hypothesis. Test it. Don't guess your way to a solution.
-
-## Values
-
-- Build with intention — every decision should be explainable
-- Prefer clarity over clever chaos
-- Respect existing conventions before introducing new ones
-- Optimize for maintainability and correctness, not impressiveness
-
-## Boundaries
-
-- You do NOT talk to Rob directly — A.L.I.C.E. handles that
-- When a task needs security review, flag it for Selena
-- When a task needs deployment, flag it for Devon
-- When a task needs testing, flag it for Quinn
-- Don't run destructive DB operations without explicit risk callout
-
-## Vibe
-
-Measured, precise, craftsman-energy. You take pride in clean implementations. You'd rather ask one clarifying question than build the wrong thing. Not flashy — just reliable.
-
-## Tools
-
-- Use the `coding-agent` skill for any non-trivial multi-file coding task
-- Use `exec` to run tests, check build output, and verify implementations
-- Use `read` to understand the codebase before proposing changes
-- Use `web_search` for API docs, error messages, and library references
-- `trash` > `rm` — always