@slycode/slycode 0.1.19 → 0.2.0

package/dist/store/.backups/context-priming/references/areas/web-frontend.md

@@ -1,252 +0,0 @@
-# Web Frontend
-
-Updated: 2026-02-14
-
-## Overview
-
-Next.js 16 command center for project management. Features project cards with health scoring, kanban boards with drag-drop, card modals, command configuration, system health monitoring, cross-project toolkit/asset management, global search, activity feed, project scaffolding, and graceful reconnection handling. Neon-minimalist theme (SlyCode Neon) with Tailwind CSS v4, featuring lane-colored gradients, SVG noise textures, and theme-aware terminal styling.
-
-## Key Files
-
-### Pages & Layout
-- `web/src/app/page.tsx` - Home dashboard, lists projects from registry
-- `web/src/app/project/[id]/page.tsx` - Project detail page with kanban
-- `web/src/components/ProjectPageClient.tsx` - Client wrapper for project pages, global terminal activity polling
-- `web/src/components/ProjectView.tsx` - Project view wrapper, manages archive toggle state
-
-### Core Components
-- `web/src/components/Dashboard.tsx` - Project card grid + Toolkit tab, global search, number-key shortcuts
-- `web/src/components/ProjectKanban.tsx` - Kanban board container, drag-drop logic
-- `web/src/components/KanbanColumn.tsx` - Stage columns (backlog, design, impl, testing, done)
-- `web/src/components/KanbanCardItem.tsx` - Individual card, status indicators, active glow effect
-- `web/src/components/CardModal.tsx` - Full card editor with dynamic tabs, edit session protection
-- `web/src/components/ProjectHeader.tsx` - Header with Commands, Archive toggle, HealthMonitor
-
-### Project Management
-- `web/src/components/ProjectCard.tsx` - Enhanced project card with health dot, platform badges, edit/delete
-- `web/src/components/AddProjectModal.tsx` - Multi-phase project creation wizard (details → analysis → scaffold → done)
-- `web/src/components/HealthDot.tsx` - Health score indicator with tooltip (green/amber/red)
-- `web/src/components/PlatformBadges.tsx` - Detected AI platform badges (Claude, Gemini, Codex)
-- `web/src/components/SearchBar.tsx` - Global/contextual search across all kanban cards
-
-### Terminal & Commands
-- `web/src/components/ClaudeTerminalPanel.tsx` - Reusable terminal with provider selector, startupCommands/activeCommands, card area filtering
-- `web/src/components/Terminal.tsx` - xterm.js terminal with ConnectionManager integration
-- `web/src/components/CommandConfigModal.tsx` - Command configuration UI with Command Assistant terminal
-- `web/src/components/GlobalClaudePanel.tsx` - Floating panel for project-wide session, supports session/CWD/class overrides
-
-### Toolkit & Assets
-- `web/src/components/ToolkitTab.tsx` - Asset management tab with matrix view and pending changes
-- `web/src/components/AssetMatrix.tsx` - Cross-project asset deployment matrix with click-to-deploy/remove
-- `web/src/components/AssetViewer.tsx` - Modal viewer for asset content with frontmatter display
-
-### Activity & Content
-- `web/src/components/ActivityFeed.tsx` - Collapsible event log with day grouping and stage indicators
-- `web/src/components/MarkdownContent.tsx` - Markdown renderer using react-markdown with GFM support
-
-### Health & Connection
-- `web/src/components/HealthMonitor.tsx` - System stats widget (CPU, memory, terminals)
-- `web/src/components/ConnectionStatusIndicator.tsx` - Reconnection toast indicator
-- `web/src/lib/connection-manager.ts` - Centralized SSE reconnection with Page Visibility API
-
-### Hooks
-- `web/src/hooks/useConnectionStatus.ts` - Hook for connection state subscription
-- `web/src/hooks/useKeyboardShortcuts.ts` - Keyboard navigation (1-9 project jump, Escape)
-- `web/src/hooks/useCommandsConfig.ts` - Polling-based commands config loader (30s intervals)
-- `web/src/hooks/usePolling.ts` - Generic polling hook
-
-### Utilities
-- `web/src/lib/types.ts` - All shared types (see Data Models)
-- `web/src/lib/claude-actions.ts` - getStartupCommands(), getActiveCommands(), renderTemplate()
-- `web/src/lib/registry.ts` - Project registry loader with kanban, health scoring, platform detection
-- `web/src/lib/paths.ts` - Dynamic path resolution for SlyCode root and project directories
-- `web/src/lib/kanban-paths.ts` - Project-aware kanban file path resolution with tiered backup
-- `web/src/lib/asset-scanner.ts` - Asset scanning, frontmatter parsing, version comparison, platform detection
-- `web/src/lib/event-log.ts` - Append-only activity log with filtering/querying (500 event cap)
-- `web/src/lib/health-score.ts` - Health score calculator with configurable weights
-- `web/src/lib/tab-sync.ts` - Cross-tab synchronization using BroadcastChannel API
-
-### API Routes
-- `web/src/app/api/kanban/route.ts` - Kanban CRUD
-- `web/src/app/api/bridge/[...path]/route.ts` - Bridge proxy
-- `web/src/app/api/commands/route.ts` - Commands CRUD
-- `web/src/app/api/commands/stream/route.ts` - SSE for command file changes
-- `web/src/app/api/system-stats/route.ts` - CPU/memory metrics
-- `web/src/app/api/areas/route.ts` - Available areas list
-- `web/src/app/api/terminal-classes/route.ts` - Terminal class definitions
-- `web/src/app/api/claude-actions/route.ts` - Commands in ClaudeActionsConfig format
-- `web/src/app/api/toolkit/route.ts` - Scan all project assets, build matrix
-- `web/src/app/api/toolkit/sync/route.ts` - Batch deploy/remove assets
-- `web/src/app/api/toolkit/import/route.ts` - Import asset from project to workspace
-- `web/src/app/api/events/route.ts` - Query activity log with filters
-- `web/src/app/api/search/route.ts` - Cross-project card search
-- `web/src/app/api/projects/route.ts` - List/create projects
-- `web/src/app/api/projects/[id]/route.ts` - GET/PUT/DELETE individual project
-- `web/src/app/api/projects/analyze/route.ts` - Analyze directory before scaffolding
-- `web/src/app/api/providers/route.ts` - GET/PUT for providers.json (provider list + stage defaults)
-- `web/src/app/api/file/route.ts` - Read files from approved directories
-- `web/src/app/api/git-status/route.ts` - Git status for projects
-
-## Key Functions
-
-- `ProjectKanban.handleDragEnd()` - Reorders cards, handles cross-column moves
-- `ConnectionManager.createManagedEventSource()` - Auto-reconnecting SSE with backoff
-- `getStartupCommands(commands, terminalClass, hasHistory)` - Filter commands for session start
-- `getActiveCommands(commands, terminalClass)` - Filter commands for running session toolbar
-- `scanProjectAssets()` - Scan commands/skills/agents across projects, build matrix
-- `calculateHealthScore()` - Score 0-100 based on configurable weighted factors
-
-## CardModal Tabs
-
-- **Details** - Edit fields, dropdowns for stage/priority, editable areas/tags chips, delete button
-- **Design** - Shows if `design_ref` exists, renders markdown with copy path button
-- **Feature** - Shows if `feature_ref` exists, renders markdown
-- **Test** - Shows if `test_ref` exists, renders markdown
-- **Checklist** - Interactive checkboxes with progress bar (uses ref-based state for rapid clicks)
-- **Terminal** - AI session with provider selector, auto-connect, startupCommands/activeCommands
-
-CardModal uses edit session protection: last-known-value tracking, 2000ms grace period for field editing, prevents overwriting active edits from external updates.
-
-## Health Scoring
-
-- **Factors**: outdated assets, stale cards, unresolved problems, missing CLAUDE.md, non-compliant frontmatter
-- **Levels**: green (≥80), amber (≥50), red (<50)
-- **Display**: HealthDot component with tooltip showing score breakdown
-- Located on ProjectCard in Dashboard
-
-## Toolkit (Asset Management)
-
-- Scans commands/skills/agents across all projects
-- Frontmatter validation: name, version, updated, description required
-- Version comparison for detecting outdated assets
-- Matrix view: rows=assets, columns=projects, cells=status
-- Batch operations: deploy to / remove from projects
-- Import from project back to workspace
-
-## Connection Management
-
-- `ConnectionManager` - Singleton managing all SSE connections
-- Page Visibility API detection for sleep/wake cycles
-- Exponential backoff with jitter (1s initial, 30s max)
-- `ConnectionStatusIndicator` - Toast showing "Reconnecting..." during recovery
-
-## Data Models
-
-- `KanbanCard` - id, title, description, type, priority, order, areas[], tags[], problems[], checklist[], archived?, design_ref?, feature_ref?, test_ref?, claude_session?
-- `Command` - label, description, group, cardTypes[], prompt, visibleIn, scope, sessionState
-- `BridgeStats` - bridgeTerminals, connectedClients, activelyWorking, sessions[]
-- `SystemStats` - cpu (0-100), memory {used, total}, swap {used, total}
-- `SessionActivity` - name, status, lastOutputAt, isActive
-- `AssetInfo` - name, type, version, updated, description, filePath, frontmatter
-- `AssetCell` - status (present|outdated|missing|extra), masterVersion?, projectVersion?
-- `ToolkitData` - rows (AssetRow[]), projects (string[])
-- `HealthScore` - score (0-100), level (green|amber|red), factors[]
-- `ActivityEvent` - type, timestamp, project, detail, cardId?
-- `SearchResult` - card, project, matchedFields[]
-- `ProjectWithBacklog` - extends Project with assets, gitUncommitted, healthScore, platforms, lastActivity, activeSessions
-- `ProvidersData` - providers (Record<id, ProviderConfig>), defaults (stages, global, projects)
-- `ProviderConfig` - id, displayName, command, permissions, resume, prompt
-
-## Design System — SlyCode Neon Theme
-
-### Philosophy
-Neon-minimalist aesthetic. Clean surfaces with subtle texture for life and depth. Never sterile/flat, never over-the-top. The theme should feel like a premium tool — atmospheric but professional. Light mode is clean with color; dark mode is moody with glow.
-
-### Color Palette
-- **Neon Blue** (`--neon-blue: #00bfff`) — Primary accent, design/implementation lanes, links, active states
-- **Neon Orange** (`--neon-orange: #ff8c00`) — Global/project terminal headers, warnings
-- **Red-Orange** (`#ff6a33`) — Testing lane (NOT standard orange, which looks brown in dark mode)
-- **Green** — Done lane, success states, running indicators
-- **Void** — Neutral grey scale for backgrounds, borders, muted text
-- **Red** (`#ff3b5c`) — Critical/bug indicators, stop buttons
-
-### Critical Color Lesson
-Dark-end scale colors (e.g. `neon-orange-950 = #2b1700`) are inherently brown. For vibrant dark mode colors, use the BRIGHT color at LOW OPACITY (e.g. `neon-orange-400/15`) instead of dark scale values.
-
-### Texture System (globals.css)
-Three-layer texture approach for gradient surfaces:
-
-1. **Fine grain** (`.grain`) — High-frequency SVG feTurbulence noise (`baseFrequency: 0.65`), overlay blend. Desaturate with `feColorMatrix type='saturate' values='0'` when color neutrality matters.
-2. **Perlin noise** (`.depth-glow`) — Low-frequency organic texture (`baseFrequency: 0.015` light, `0.012` dark), large 400px tiles. Light mode uses `screen` blend (lightens), dark mode uses `soft-light`. Masked with left-to-right gradient fade.
-3. **Terminal texture** (`.terminal-texture`) — CRT-like grain + vignette + lane-colored tint via `--terminal-tint` CSS variable. Box-shaped mask (edges visible, centre clear). Light: `soft-light` blend. Dark: `screen` blend (avoids warm/red cast from `soft-light` on dark backgrounds).
-
-### Blend Mode Rules
-- `soft-light` on dark backgrounds produces warm/red cast — avoid for dark mode textures
-- `overlay` is neutral but can be invisible on very dark surfaces
-- `screen` always adds light — use for dark mode when you need visible texture
-- `mix-blend-multiply` makes white backgrounds transparent (light mode logos)
-- `mix-blend-lighten` makes black backgrounds transparent (dark mode logos)
-- `filter: drop-shadow()` traces the ALPHA boundary — creates rectangular glow on images with opaque backgrounds. Incompatible with blend-mode logo transparency.
-
-### Logo Handling
-Logos have opaque backgrounds (white for light, black for dark). Two `<img>` tags per location:
-- Light: `mix-blend-multiply dark:hidden`
-- Dark: `mix-blend-lighten hidden dark:block`
-- All CSS drop-shadow/filter glow DISABLED (creates rectangular artifacts with blend modes). Logos have baked-in glow.
-- Files: `slycode_light.png` / `slycode.png` (hero), `slycode_logo_light.png` / `slycode_logo.png` (nav)
-
-### Lane-Colored Theming
-Stage colors flow through multiple layers:
-- **KanbanColumn headers** — `colorClasses` map with header gradient, text, count badge, border
-- **CardModal header/tabs** — `stageModalStyles` map with gradients, borders per stage. Uses transparency (85% → 50%) for subtle glass quality
-- **CardModal footer** — `stageTerminalColors` with colored top border
-- **Terminal tint** — `stageTerminalTint` map provides rgba color → passed as `tintColor` prop → sets `--terminal-tint` CSS variable on terminal overlay
-
-### Gradient Direction Convention
-Left-to-right, vibrant-to-soft. The left/start side is always the stronger color, fading lighter toward the right. Never center-out fades (looks artificial).
-
-### Button Aesthetic — Neon Glass
-Terminal/action buttons use semi-transparent backgrounds with colored borders and hover glow:
-```
-border border-{color}-400/40 bg-{color}-400/15 text-{color}-400
-hover:bg-{color}-400/25 hover:shadow-[0_0_12px_rgba(...,0.3)]
-```
-
-### Health Monitor
-Uses inline gradient fills + glow shadows (not flat CSS classes):
-- Normal: `linear-gradient(90deg, #00e676, #00bfff)` + blue glow
-- Warning: `linear-gradient(90deg, #ff8c00, #ffaa00)` + orange glow
-- Critical: `linear-gradient(90deg, #ff3b5c, #ff6b81)` + red glow
-
-### Terminal Background
-Theme-aware: `#222228` (light mode, slightly lighter) / `#1a1a1a` (dark mode). Detected at xterm mount via `document.documentElement.classList.contains('dark')`. Wrapper divs use `bg-[#222228] dark:bg-[#1a1a1a]`.
-
-### Dark Mode Borders
-Card modals get colored outer borders in dark mode (`dark:border dark:border-{color}/25-30`). Section dividers (header/tabs/terminal) use lane colors in both modes.
-
-## Patterns & Invariants
-
-- Cards auto-save on changes via `/api/kanban` PUT
-- Kanban data stored in `documentation/kanban.json` per project
-- Stage order: backlog → design → implementation → testing → done
-- Active glow: `active-glow-card` CSS class with pulse animation (2s activity threshold)
-- Commands use `startupCommands` (session start) and `activeCommands` (running toolbar)
-- SSE connections managed centrally via ConnectionManager for reconnection
-- Dynamic path resolution via paths.ts (no hardcoded paths)
-- Cross-tab sync via BroadcastChannel API
-- Number keys 1-9 jump to projects, Escape closes modals
-- Event log capped at 500 entries, append-only
-- Session names include provider segment: `{projectId}:{provider}:card:{cardId}`
-- Provider selector shown on no-session screen, pre-filled from stage defaults
-- CardModal detects existing session's provider from session name for pre-selection
-- ProjectKanban/ProjectPageClient use regex patterns to match both new and legacy session names
-
-## When to Expand
-
-- Editing card behavior → CardModal.tsx
-- Kanban drag/drop issues → ProjectKanban.tsx, KanbanColumn.tsx
-- Adding new card fields → types.ts, CardModal.tsx
-- Command configuration → CommandConfigModal.tsx, data/commands.json
-- Health monitoring → HealthMonitor.tsx, /api/system-stats
-- Connection issues → connection-manager.ts, ConnectionStatusIndicator.tsx
-- Terminal panel behavior → ClaudeTerminalPanel.tsx
-- Provider selection → ClaudeTerminalPanel.tsx, /api/providers, data/providers.json
-- Provider detection for existing sessions → CardModal.tsx (session name parsing)
-- Asset management → asset-scanner.ts, ToolkitTab.tsx, AssetMatrix.tsx
-- Health scoring → health-score.ts, HealthDot.tsx
-- Activity feed → event-log.ts, ActivityFeed.tsx
-- Project scaffolding → AddProjectModal.tsx, /api/projects
-- Search → SearchBar.tsx, /api/search
-- Path resolution → paths.ts, kanban-paths.ts
-- Keyboard shortcuts → useKeyboardShortcuts.ts
-- Theme/design system → globals.css (texture classes), CardModal.tsx (stageModalStyles), KanbanColumn.tsx (colorClasses), GlobalClaudePanel.tsx (terminal header), Terminal.tsx (tintColor, terminal-texture)

package/dist/store/.backups/context-priming/references/maintenance.md

@@ -1,128 +0,0 @@
-# Maintenance Doctrine
-
-Rules for maintaining context-priming references. Changes to this file require user approval.
-
-## Area File Structure
-
-Area files should be as lean as the area requires. Include sections that add value; omit those that don't.
-
-**Always include:**
-```markdown
-# [Area Name]
-
-Updated: YYYY-MM-DD
-
-## Overview
-What this area does, boundaries. 2-3 sentences.
-
-## Key Files
-- `file.py` - purpose
-[Most important files/modules]
-
-## When to Expand
-- [task] → [files to open]
-```
-
-**Include when relevant:**
-
-| Section | When to include |
-|---------|-----------------|
-| Key Functions | Area has important entry points, APIs, or non-obvious control flow |
-| Data Models | Area defines data structures used internally or externally |
-| Shared Objects | Area defines or consumes objects used across multiple areas |
-| Patterns & Invariants | Area has critical rules that must hold |
-| Interfaces | Area connects to other areas with data flow |
-
-**Section formats (when used):**
-
-```markdown
-## Key Functions
-- `process_message()` in handlers.py - entry point for incoming messages
-
-## Data Models
-- `Message` (models.py) - id, content, sender_id, timestamp | core envelope
-
-## Shared Objects
-- `Message` - DEFINED HERE, used by: frontend, api, workers
-- `Config` - defined in core, IMPORTED HERE
-
-## Patterns & Invariants
-- Auth middleware runs before handlers
-
-## Interfaces
-- → frontend: sends Message via WebSocket
-- ← api: receives Request, returns Response
-```
-
-Keep area files under 200 lines. Simple areas may be 20-30 lines; complex areas will be longer.
-
-**Shared Objects note**: When present, prevents duplicate definitions. Mark canonical location.
-
-## Defragmentation
-
-**When to defrag an area:**
-- Information is scattered/duplicated within the file
-- Sections contain outdated content mixed with current
-- File has grown beyond 200 lines
-- Reading the file doesn't quickly answer "what do I need to know?"
-
-**Defrag process:**
-1. Read the entire area file
-2. Identify: duplicates, outdated info, poor organization
-3. Consolidate related information
-4. Remove obsolete content (don't comment it out - delete)
-5. Verify remaining content is accurate against current code
-6. Update the `Updated` date
-
-**Consult user before defragging if:**
-- Multiple areas need simultaneous restructuring
-- Unsure whether information is obsolete or still relevant
-- Defrag would take significant time
-
-## Area Separation
-
-**Heuristics for deciding areas:**
-- Group by logical module/subsystem, not by file type
-- An area should be loadable and useful independently
-- If two areas are always loaded together, consider merging
-- If an area covers unrelated concerns, consider splitting
-
-**When to split an area:**
-- File exceeds 200 lines despite being concise
-- Contains distinct subsystems that don't interact
-- Load-when triggers have diverged (some tasks need part A, others need part B)
-
-**When to merge areas:**
-- Two areas are nearly always loaded together
-- Combined size would still be under 150 lines
-- Separation creates artificial boundaries
-
-**Cross-references:**
-- Areas can note "see also: [other-area]" for related context
-- Don't auto-load chains - let the index's load-when guide loading
-- If area A heavily depends on area B, note this in A's Interfaces section
-
-## Note Pruning
-
-Notes in area-index.md capture learnings. Prune when:
-- Note contradicts newer information (keep newer)
-- Code changed and note no longer applies
-- Note is vague or not actionable
-- Area exceeds 10 notes
-
-**Pruning is lightweight** - remove stale notes during routine updates, don't treat as separate task.
-
-## New Project Initialization
-
-When skill is introduced to a new codebase:
-
-1. Clear `areas/` directory
-2. Reset area-index.md to template state
-3. Keep SKILL.md and maintenance.md intact
-4. Scan project structure:
-   - Look for obvious module boundaries (directories, packages)
-   - Check build configs (package.json, pyproject.toml, etc.)
-   - Read CLAUDE.md for existing documentation pointers
-5. Propose 3-6 initial areas to user
-6. After approval, create area files with initial discovery
-7. Mark all as freshly created - validate through actual use

package/dist/store/.ignored-updates.json

@@ -1,37 +0,0 @@
-{
-  "skills/kanban": "1.3.0",
-  "skills/code-review": "1.0.0",
-  "actions/onboard": "d2a2dd1bcb97",
-  "actions/show-card": "185ccdc4beb0",
-  "actions/approve": "0d1097e72a69",
-  "actions/archive": "44999be606ab",
-  "actions/checkpoint": "1b87d19a1c22",
-  "actions/clear": "b3f1a7a21337",
-  "actions/configure-commands": "778d11c6df39",
-  "actions/context": "830cf4fc47d4",
-  "actions/continue": "a808fa97513e",
-  "actions/convert-asset": "47d33ad765a1",
-  "actions/create-card": "3aa7f18c0807",
-  "actions/explore": "d67b7785deb0",
-  "actions/organise-backlog": "28e9fb9bd19c",
-  "actions/summarize": "6ce55b060254",
-  "actions/test-review": "baa161179c9d",
-  "actions/update-priming": "685464a284c2",
-  "actions/analyse-implementation": "f380bedf7c60",
-  "actions/chore": "da6c88ff5a07",
-  "actions/complete": "4da58630f469",
-  "actions/debug": "721c9ce48ed3",
-  "actions/deep-design": "02146223d052",
-  "actions/design-requirements": "c214c49eb284",
-  "actions/implement": "0793a438b277",
-  "actions/make-feature": "b4c2763bc890",
-  "actions/quick-fix": "a93f3ce3123d",
-  "actions/review": "29c6fbf1448f",
-  "skills/checkpoint": "0d72f0dc3b87",
-  "skills/context-priming": "4979c7d2ff4f",
-  "skills/design": "c2cba0b138f4",
-  "skills/feature": "aeff2aad7309",
-  "skills/implement": "f6dca53805ab",
-  "skills/messaging": "1fbb11161959",
-  "skills/chore": "dc1fb83dbeca"
-}

package/dist/store/actions/analyse-implementation.md

@@ -1,72 +0,0 @@
----
-name: analyse-implementation
-version: 1.0.0
-label: "Analyse"
-description: "Analyse the implementation for consistency, bugs, bloat, and card alignment"
-group: "Card Actions"
-placement: both
-scope: global
-classes:
-  implementation: 20
-  testing: 80
----
-
-{{cardContext}}
-
----
-
-## Your Task
-
-Perform a **thorough analysis** of the implementation for this card.
-
-> Card details are provided above. If you need checklist status, notes from prior sessions, or problem IDs, run `sly-kanban show {{card.id}}` before proceeding.
-
-**Step 1 - Gather context:**
-Read the card description, acceptance criteria, design_ref and feature_ref (if they exist) to understand what was expected.
-
-**Step 2 - Prime context:**
-Use `/context-priming` with the card's **Areas** to load the relevant codebase patterns, conventions, and architecture.
-
-**Step 3 - Identify changed files:**
-Use git history, the feature spec, and the card areas to identify all files that were added or modified as part of this implementation. Read every one of them thoroughly.
-
-**Step 4 - Analyse against these criteria:**
-
-| Category | What to look for |
-|---|---|
-| **Pattern Consistency** | Does the new code follow the same patterns, naming conventions, file organization, and idioms as the existing codebase? Flag deviations. |
-| **Bugs & Logic Errors** | Off-by-one errors, null/undefined handling, missing error handling, incorrect conditionals, type mismatches, silent failures. |
-| **Race Conditions & Timing** | Async operations without proper awaiting, shared mutable state, event ordering assumptions, missing locks or guards, stale closures. |
-| **Card Alignment** | Does the implementation actually deliver what the card description and acceptance criteria specify? Is anything missing, incomplete, or going beyond scope? |
-| **Bloat & Complexity** | Over-engineering, unnecessary abstractions, dead code, premature generalisation, things that could be simpler. Flag anything that adds complexity without clear justification. |
-| **Edge Cases** | Untested boundaries - empty inputs, large inputs, concurrent access, network failures, permission errors, malformed data. |
-| **Security** | Injection risks, missing input validation at boundaries, exposed secrets, unsafe defaults. |
-
-**Step 5 - Produce the findings report:**
-
-Present a structured table of findings:
-
-| # | Severity | Category | File:Line | Finding | Recommendation |
-|---|----------|----------|-----------|---------|----------------|
-| 1 | critical/major/minor | Category from above | path:line | Detailed description of the issue | What should be done to fix it |
-
-Severity guide:
-- **critical** - Will cause bugs, data loss, or security issues in production
-- **major** - Significant quality issue, deviation from patterns, or missing card requirement
-- **minor** - Style inconsistency, minor improvement opportunity, or nitpick
-
-After the table, provide a brief **overall assessment** - is this implementation solid, or does it need work before approval?
-
-**Step 6 - Log issues on the card:**
-
-For every **critical** and **major** finding, log it as a problem on the card:
-```bash
-sly-kanban problem {{card.id}} add "[Category] Finding description — Recommendation" --severity <major|critical>
-```
-
-For **minor** findings, log them as minor:
-```bash
-sly-kanban problem {{card.id}} add "[Category] Finding description" --severity minor
-```
-
-Summarize how many issues were logged at each severity level.

package/dist/store/actions/archive.md

@@ -1,36 +0,0 @@
----
-name: archive
-version: 1.0.0
-label: "Archive"
-description: "Archive a completed card"
-group: "Card Actions"
-placement: toolbar
-scope: global
-classes:
-  done: 10
----
-
-{{cardContext}}
-
----
-
-## Your Task
-
-Archive this completed card.
-
-**First, verify it's truly complete:**
-```bash
-sly-kanban show {{card.id}}
-```
-
-**Check:**
-- All work is complete
-- No unresolved problems
-- Ready to be archived for record-keeping
-
-**If ready to archive:**
-```bash
-sly-kanban archive {{card.id}}
-```
-
-This removes the card from active view but preserves it in history.

package/dist/store/actions/clear.md

@@ -1,13 +0,0 @@
----
-name: clear
-version: 1.0.0
-label: "Clear"
-description: "Clear conversation history"
-group: "Utilities"
-placement: toolbar
-scope: global
-classes:
-  global-terminal: 20
----
-
-/clear

package/dist/store/actions/complete.md

@@ -1,34 +0,0 @@
----
-name: complete
-version: 1.0.0
-label: "Complete"
-description: "Wrap up implementation and move to testing"
-group: "Card Actions"
-placement: toolbar
-scope: global
-classes:
-  implementation: 40
----
-
-{{cardContext}}
-
----
-
-## Your Task
-
-Complete the implementation phase for this card.
-
-> Card details are provided above. If you need checklist status, notes from prior sessions, or problem IDs, run `sly-kanban show {{card.id}}` before proceeding.
-
-**Checklist before moving to testing:**
-1. All planned work is done
-2. Code is committed (use /checkpoint if needed)
-3. No critical issues remain (check problems list)
-4. Basic functionality verified
-
-**If ready:**
-```bash
-sly-kanban move {{card.id}} testing
-```
-
-**If not ready**, explain what's still needed.

package/dist/store/actions/continue.md

@@ -1,20 +0,0 @@
----
-name: continue
-version: 1.0.0
-label: "Continue"
-description: "Continue working from where we left off"
-group: "Session"
-placement: startup
-scope: global
-classes:
-  project-terminal: 10
-  testing: 40
----
-
-{{cardContext}}
-
----
-
-## Your Task
-
-Continue from where we left off. Briefly recap what was happening and what's next.