opencodekit 0.14.5 → 0.15.0

package/dist/template/.opencode/memory/project/conventions.md

@@ -1,206 +1,68 @@
 ---
-purpose: Code patterns, commit style, PR process, team conventions
-updated: 2025-01-05
+purpose: Code patterns, commit style, team conventions
+updated: { { DATE } }
 ---
 
 # Project Conventions
 
 ## Code Style
 
-- **TypeScript**: ES2022, ESNext modules, strict disabled, forceConsistentCasing
-- **Python**: 3.10+, type hints required, dataclasses for config, pathlib for paths
-- **Imports**: Group stdlib, third-party, local imports
-- **Naming**: PascalCase classes, snake_case functions/variables, UPPER_CASE constants
+### TypeScript
 
-## Commit Messages
-
-<!-- Conventional commits? Prefix style? -->
-
-## PR Process
-
-<!-- Review requirements, CI checks, merge strategy -->
-
-## OpenCode Configuration Patterns (v1.1.2+)
-
-### Permission Structure Best Practice
-
-```jsonc
-{
-  "permission": {
-    "bash": {
-      "*": "allow", // 1. Base rule first (catch-all)
-      "git status*": "allow", // 2. Safe operations whitelisted
-      "git diff*": "allow",
-      "npm *": "allow",
-      "rm*": "deny", // 3. Dangerous operations denied
-      "sudo*": "deny",
-    },
-    "read": {
-      ".env": "deny", // 4. Protect secrets
-      ".env.example": "allow", //    But allow examples
-    },
-  },
-}
-```
-
-### LSP Tool Strategy
-
-**This project uses built-in experimental LSP** (`experimental.lsp: true`).
-
-| Tool                        | Purpose                      |
-| --------------------------- | ---------------------------- |
-| `lsp_lsp_hover`             | Type info and docs at cursor |
-| `lsp_lsp_goto_definition`   | Jump to symbol definition    |
-| `lsp_lsp_find_references`   | Find all usages              |
-| `lsp_lsp_rename`            | Rename across codebase       |
-| `lsp_lsp_code_actions`      | Get available refactorings   |
-| `lsp_lsp_code_action_apply` | Apply a code action          |
-| `lsp_lsp_diagnostics`       | Get errors/warnings          |
-| `lsp_lsp_document_symbols`  | File outline                 |
-| `lsp_lsp_workspace_symbols` | Search symbols               |
-| `lsp_lsp_organize_imports`  | Clean up imports             |
-
-### DCP Configuration Tiers
-
-| Tier             | Strategies         | nudgeFrequency | turnProtection | Use When                     |
-| ---------------- | ------------------ | -------------- | -------------- | ---------------------------- |
-| **Aggressive**   | All enabled        | 8              | 3              | Long sessions, context-heavy |
-| **Conservative** | Deduplication only | 12+            | 6+             | Safety-first, debugging      |
-| **Balanced**     | All enabled        | 10             | 4              | Default, general use         |
-
-### Protected Tools Pattern
-
-Always protect these tools from auto-pruning:
-
-```jsonc
-"protectedTools": [
-  // State-modifying
-  "write", "edit", "skill_mcp", "bd_sync",
-  // Metadata
-  "memory-search", "memory-update", "observation", "todowrite", "todoread",
-  // Task management
-  "task", "batch",
-  // LSP (if using plugin)
-  "lsp_lsp_find_references", "lsp_lsp_goto_definition"
-]
-```
+- **Module**: ESNext, bundler moduleResolution
+- **Strict**: Disabled
+- **Imports**: Group stdlib, third-party, local
 
-### Prompt Injection Pattern (Nudges)
+### Python
 
-Use `chat.message` hook to inject prompts (nudges) based on user triggers:
+- **Version**: 3.10+
+- **Style**: type hints required, dataclasses for config
 
-```typescript
-"chat.message": async (input, output) => {
-  const { message, parts } = output;
-  if (message.role !== "user") return;
-
-  // 1. Detect trigger keywords
-  const fullText = parts.map(p => p.text).join(" ");
-  if (!fullText.match(/trigger pattern/)) return;
-
-  // 2. Inject synthetic prompt
-  parts.push({
-    type: "text",
-    text: "━━━━━━━━\n[TRIGGER DETECTED]\nAction required: ...\n━━━━━━━━",
-    synthetic: true
-  });
-}
-```
+## Naming Conventions
 
-This transforms passive detection into active agent behavior (e.g., Memory plugin triggers).
+| Type      | Convention | Example           |
+| --------- | ---------- | ----------------- |
+| Classes   | PascalCase | `UserService`     |
+| Functions | snake_case | `get_user_data()` |
+| Variables | snake_case | `user_data`       |
+| Constants | UPPER_CASE | `MAX_RETRIES`     |
+| Files     | kebab-case | `user-service.ts` |
 
-## Agent Behavior Rules
+## Import Order
 
-### MANDATORY LSP-First Workflow
+```typescript
+// 1. Node.js stdlib
+import fs from "node:fs/promises";
+import path from "node:path";
 
-**HARD RULE**: Before editing ANY code file, you MUST use LSP tools first.
+// 2. Third-party
+import { cli } from "cac";
+import { log } from "@clack/prompts";
 
+// 3. Local
+import { initCommand } from "./commands/init.js";
 ```
-grep/read → LSP → understand → THEN edit
-```
-
-**After EVERY grep/glob/read that returns code files:**
 
-1. **IMMEDIATELY** call `lsp` with `documentSymbol` to understand file structure
-2. **IMMEDIATELY** call `lsp` with `findReferences` on symbols you'll modify
-3. **IMMEDIATELY** call `lsp` with `goToDefinition` to trace dependencies
-4. **USE** additional LSP operations as needed:
-   - `hover` - Get type info and documentation
-   - `goToImplementation` - Find implementations of interface/abstract
-   - `workspaceSymbol` - Search symbols across entire workspace
-   - `prepareCallHierarchy` - Get call hierarchy item at position
-   - `incomingCalls` - Find what calls this function
-   - `outgoingCalls` - Find what this function calls
-5. **ONLY THEN** proceed with edits
-
-**Example - The Correct Flow:**
+## Commit Messages
 
 ```
-User: "Fix the auth bug in src/auth.ts"
-
-# Step 1: Read the file
-read({ filePath: "src/auth.ts" })
+type(scope): subject
 
-# Step 2: MANDATORY LSP (before ANY edit) - use ALL relevant operations
-lsp({ operation: "documentSymbol", filePath: "src/auth.ts", line: 1, character: 1 })
-lsp({ operation: "findReferences", filePath: "src/auth.ts", line: 42, character: 10 })
-lsp({ operation: "goToDefinition", filePath: "src/auth.ts", line: 42, character: 10 })
-lsp({ operation: "hover", filePath: "src/auth.ts", line: 42, character: 10 })
-lsp({ operation: "incomingCalls", filePath: "src/auth.ts", line: 42, character: 10 })
-lsp({ operation: "outgoingCalls", filePath: "src/auth.ts", line: 42, character: 10 })
+body (optional)
 
-# Step 3: NOW you can edit
-edit({ filePath: "src/auth.ts", ... })
+footer (optional)
 ```
 
-**Why This Matters:**
+**Types**: `feat`, `fix`, `docs`, `style`, `refactor`, `test`, `chore`
 
-- LSP gives you semantic understanding (types, references, call hierarchy)
-- grep/read only gives you text (no understanding of relationships)
-- Editing without LSP context leads to broken refactors
+## Code Review
 
-**Violations:**
-
-- ❌ `read → edit` (WRONG - no LSP)
-- ❌ `grep → edit` (WRONG - no LSP)
-- ✅ `read → LSP → edit` (CORRECT)
-- ✅ `grep → read → LSP → edit` (CORRECT)
+- **Self-review**: Run lint/typecheck before PR
+- **Test coverage**: Add tests for new features
+- **Docs**: Update README for user-facing changes
 
 ## Patterns to Avoid
 
-### Anti-Pattern: Mixing LSP Systems
-
-```jsonc
-// DON'T: Causes tool duplication and naming confusion
-{
-  "experimental": { "lsp": true },  // Built-in: lsp_lsp_*
-  // AND .opencode/tool/lsp.ts      // Custom: lsp_*
-}
-
-// DO: Use built-in only (recommended for this project)
-{
-  "experimental": { "lsp": true }
-}
-// Delete any custom .opencode/tool/lsp.ts
-```
-
-### Anti-Pattern: Over-Restrictive Permissions
-
-```jsonc
-// DON'T: Blocks legitimate workflow
-{
-  "bash": { "git *": "ask" }  // Every git command asks
-}
-
-// DO: Whitelist safe, ask dangerous
-{
-  "bash": {
-    "git status*": "allow",
-    "git diff*": "allow",
-    "git log*": "allow",
-    "git commit*": "ask",
-    "git push*": "ask",
-    "git reset*": "ask"
-  }
-}
-```
+- Premature abstraction
+- Circular dependencies
+- Magic numbers/strings

package/dist/template/.opencode/memory/project/gotchas.md

@@ -1,197 +1,41 @@
 ---
 purpose: Footguns, edge cases, and "don't forget this" warnings
-updated: 2025-01-09
+updated: { { DATE } }
 ---
 
 # Project Gotchas
 
 ## Configuration Quirks
 
-### OpenCode v1.1.7 → v1.1.8 Changes
+### Field Name
 
-**v1.1.7 Features:**
+**Issue**: What goes wrong
+**Fix**: How to handle it
 
-- **Question tool**: New interactive tool for gathering user preferences/clarifying instructions
-- **Config precedence fix**: Local `.opencode/opencode.json` now correctly overrides remote/global config
-- **`.claude` loading toggle**: Can disable via `--no-claude-prompts` / `--no-claude-skills` flags
-- **Task tool filtering**: Simplified subagent filtering
+## Dependencies
 
-**v1.1.8 Features:**
+### Package Name
 
-- **Multi-select questions**: Question tool now supports `multiple: true` for multi-select
-- **Performance**: Chunked message loading, lazy diff rendering
-- **Full path fuzzy matching**: Autocomplete uses full file paths
-- **OpenTUI v0.1.70**: UI improvements
-
-**Plugin SDK Update Required:**
-
-```json
-"@opencode-ai/plugin": "^1.1.8"  // Was ^1.1.2
-```
-
-### DCP Protected Tools (v1.1.8)
-
-Legacy `bd_*` tool names don't exist - use actual custom tool names:
-
-| Old (Wrong)       | New (Correct) |
-| ----------------- | ------------- |
-| `bd_init`         | N/A (use CLI) |
-| `bd_claim`        | N/A (use CLI) |
-| `bd_reserve`      | `bd-reserve`  |
-| `bd_reservations` | `bd-release`  |
-| `bd_sync`         | N/A (use CLI) |
-
-### DCP v1.1.3 Schema Breaking Changes
-
-1. **Legacy `strategies.onIdle` removed**: v1.1.2+ no longer supports this field
-   - Error: `Unknown keys: strategies.onIdle`
-   - Fix: Remove the entire `onIdle` block from `dcp.jsonc`
-
-2. **Permission model changed**: v1.1.1+ deprecated legacy `tools: { write: true }` boolean syntax
-   - Old: Global `tools: {}` with booleans
-   - New: `permission: {}` with `"allow"` / `"ask"` / `"deny"` actions
-   - Both still work for backwards compatibility, but new syntax preferred
-
-### OpenCode v1.1.2 New Features
-
-- `compaction.auto` and `compaction.prune` are NEW - enable both for long sessions
-- `experimental.continue_loop_on_deny` - controls agent behavior after permission denial
-- `cargo-fmt` formatter support added for Rust projects
-
-## Non-Obvious Dependencies
-
-### LSP Tool Naming Convention
-
-- OpenCode built-in LSP uses `lsp_lsp_*` prefix (e.g., `lsp_lsp_rename`, `lsp_lsp_hover`)
-- Requires `experimental.lsp: true` in opencode.json
-- **This project uses built-in LSP** (custom plugin removed for simplicity)
-- Custom plugins would use `lsp_*` prefix - avoid mixing both
-
-### Protected Tools in DCP
-
-v1.1.8 recognizes more tool variants. Ensure these are protected:
-
-```jsonc
-"protectedTools": [
-  // State-modifying
-  "write", "edit", "question",
-  // Memory/observation
-  "memory-read", "memory-update", "memory-search", "observation",
-  // Skills/tasks
-  "skill", "skill_mcp", "task", "batch", "todowrite", "todoread",
-  // LSP
-  "lsp", "lsp_lsp_rename", "lsp_lsp_find_references", "lsp_lsp_goto_definition",
-  "lsp_lsp_code_actions", "lsp_lsp_code_action_apply", "lsp_lsp_organize_imports",
-  // Beads (custom tools only - CLI uses bash)
-  "bd-reserve", "bd-release", "bd-msg", "bd-inbox"
-]
-```
+**Version**: x.y.z
+**Why Required**: Purpose
+**Gotcha**: Edge case or limitation
 
 ## Time Wasters
 
-### Debugging DCP Errors
-
-If DCP plugin throws "Unknown keys" errors:
-
-1. Check OpenCode version (`opencode --version`)
-2. Compare against [DCP schema](https://github.com/opencode/dcp) for your version
-3. Remove deprecated fields - don't try to "fix" them
-
-### Permission Debugging
-
-If tools are unexpectedly blocked:
-
-1. Check global config: `~/.config/opencode/opencode.json`
-2. Check project config: `.opencode/opencode.json`
-3. Project config takes precedence
-4. Use `"*": "ask"` as base rule to debug which pattern is matching
-
-## Beads Gotchas
-
-### Architecture: CLI + Custom Tools
-
-**Beads CLI** (`bd`) handles all issue tracking natively with `--json` output.
-
-**Custom Tools** (`.opencode/tool/bd-*.ts`) provide agent-specific features NOT in CLI:
-
-| Tool         | Purpose                           |
-| ------------ | --------------------------------- |
-| `bd-reserve` | Atomic file locking (mkdir-based) |
-| `bd-release` | Release locks / list active locks |
-| `bd-msg`     | Send messages to other agents     |
-| `bd-inbox`   | Read messages, mark as read       |
-
-### CLI for Everything Else
-
-Use bash tool with `bd` CLI directly:
-
-```bash
-bd ready --json              # Find unblocked tasks
-bd create "Title" -p 2       # Create task
-bd update bd-xxx --status in_progress  # Claim
-bd close bd-xxx --reason "Done"        # Complete
-bd sync                      # Push to git
-```
-
-### Agent Workflow Pattern
-
-```bash
-# 1. Find work
-bd ready --json
-
-# 2. Claim task
-bd update bd-xxx --status in_progress
-
-# 3. Lock files (custom tool)
-bd-reserve({ paths: ["src/foo.ts"] })
-
-# 4. Do work...
-
-# 5. Release + close + sync
-bd-release({ paths: ["src/foo.ts"] })
-bd close bd-xxx --reason "Completed: description"
-bd sync
-```
-
-### Hash-Based IDs Prevent Collisions
-
-Beads uses hash IDs (`bd-a3f8`) not sequential IDs (`bd-1`, `bd-2`). This eliminates merge conflicts when multiple agents create issues on different branches.
-
-Don't assume sequential IDs. Always use `bd show` to get exact IDs.
-
-### `bd ready` Is Your Friend
-
-`bd ready` shows tasks with NO unresolved blockers. Use it to find work instead of `bd list`.
-
-### Dependencies Block Work
-
-```bash
-bd dep add bd-child bd-parent --type blocks
-```
-
-Now `bd-child` won't appear in `bd ready` until `bd-parent` closes. Check `bd blocked` to see what's waiting.
-
-### Git Is The Coordination Layer
-
-No central server. Agents coordinate via:
-
-1. Issue status (in_progress = claimed)
-2. Git branches
-3. `bd sync` to push/pull changes
-
-### Sandbox Environments (Claude Code, etc.)
+### Issue Description
 
-Daemon can't be killed by sandbox. Use:
+**Symptoms**: What you'll see
+**Cause**: Root cause
+**Fix**: Solution
 
-```bash
-bd --sandbox ready
-# Or: bd --no-daemon --no-auto-flush --no-auto-import list
-```
+## Common Errors
 
-### 30-Second Debounce
+| Error Message | Cause  | Fix       |
+| ------------- | ------ | --------- |
+| "Error: ..."  | Reason | Fix steps |
 
-Rapid operations get batched into single JSONL flush after 30s. Force immediate sync:
+## TODO
 
-```bash
-bd sync
-```
+- [ ] Document more edge cases
+- [ ] Add troubleshooting section
+- [ ] List known issues

package/dist/template/.opencode/memory/user.example.md

@@ -6,16 +6,21 @@ updated: 2024-12-21
 # User Profile
 
 ## Identity
+
 <!-- Name, role, git contributor identity -->
 
 ## Communication Preferences
+
 <!-- Concise vs detailed, tone preferences -->
 
 ## Workflow Preferences
+
 <!-- Preferred tools, testing habits, review style -->
 
 ## Technical Preferences
+
 <!-- Languages, frameworks, patterns they favor -->
 
 ## Things to Remember
+
 <!-- Personal quirks, pet peeves, preferences learned -->