opencode-starterkit 1.0.1

package/baseline/dcp.jsonc

@@ -0,0 +1,72 @@
+{
+	"$schema": "https://raw.githubusercontent.com/Opencode-DCP/opencode-dynamic-context-pruning/master/dcp.schema.json",
+	"enabled": true,
+	"debug": false,
+	// "minimal" shows prune activity without noise; "detailed" shows token counts
+	"pruneNotification": "detailed",
+	// "chat" (in-conversation) or "toast" (system notification)
+	"pruneNotificationType": "toast",
+	// Commands: /dcp context, /dcp stats, /dcp sweep, /dcp compress, /dcp decompress, /dcp recompress
+	"commands": {
+		"enabled": true,
+		// Protect these from /dcp sweep
+		"protectedTools": ["observation", "memory-update", "memory-search"]
+	},
+	// Manual mode: disables autonomous context management
+	"manualMode": {
+		"enabled": false,
+		"automaticStrategies": true
+	},
+	"turnProtection": {
+		"enabled": true,
+		"turns": 4
+	},
+	// Protected file patterns - never auto-prune reads of these files
+	"protectedFilePatterns": [
+		"**/.env*",
+		"**/AGENTS.md",
+		"**/.opencode/**",
+		"**/.beads/**",
+		"**/package.json",
+		"**/tsconfig.json",
+		"**/biome.json"
+	],
+	"compress": {
+		// v3.0.0: single compress tool replaces the old 3-tool system
+		"permission": "allow",
+		"showCompression": false,
+		"maxContextLimit": "80%",
+		"minContextLimit": 30000,
+		"nudgeFrequency": 5,
+		"iterationNudgeThreshold": 15,
+		"nudgeForce": "soft",
+		"flatSchema": false,
+		"protectUserMessages": true,
+		// v3.0.0 auto-protects: task, skill, todowrite, todoread, compress, batch, plan_enter, plan_exit
+		// Only list additional tools here
+		"protectedTools": ["write", "edit", "memory-*", "observation", "tilth_*"]
+	},
+	// Experimental features
+	"experimental": {
+		"allowSubAgents": true,
+		"customPrompts": false
+	},
+	// Auto strategies
+	"strategies": {
+		// Dedup = zero LLM cost, high impact - always enable
+		"deduplication": {
+			"enabled": true,
+			"protectedTools": []
+		},
+		// Supersede writes = zero cost, removes redundant write inputs after read
+		"supersedeWrites": {
+			"enabled": true
+		},
+		// Purge error inputs after N turns
+		"purgeErrors": {
+			"enabled": true,
+			"turns": 4,
+			"protectedTools": []
+		}
+	}
+}

package/baseline/memory/README.md

@@ -0,0 +1,89 @@
+---
+purpose: PARA-organized memory system with SQLite backing
+updated: 2026-02-04
+---
+
+# Project Memory
+
+Multi-layer memory system combining PARA organization with SQLite + FTS5 search.
+
+## Directory Structure
+
+```
+memory/
+├── project/           # Tacit knowledge (always-injected context)
+│   ├── user.md        # User preferences, identity
+│   ├── tech-stack.md  # Framework, dependencies, constraints
+│   └── gotchas.md     # Footguns, edge cases, warnings
+├── knowledge/         # PARA-organized reference (curated)
+│   ├── projects/      # Active work with deadlines
+│   ├── areas/         # Ongoing responsibilities
+│   ├── resources/     # Reference material
+│   └── archives/      # Completed/inactive items
+├── daily/             # Chronological session logs
+├── research/          # Deep-dive analysis documents
+├── handoffs/          # Session handoff context
+└── _templates/        # File templates
+```
+
+## Memory Layers (3-Layer Architecture)
+
+| Layer               | Location      | Purpose                 | Access                             |
+| ------------------- | ------------- | ----------------------- | ---------------------------------- |
+| **Knowledge Graph** | SQLite + FTS5 | Searchable observations | `memory-search()`, `observation()` |
+| **Daily Notes**     | `daily/`      | Chronological narrative | Manual review                      |
+| **Tacit Knowledge** | `project/`    | Always-present context  | Auto-injected                      |
+
+## SQLite Memory Tools
+
+| Tool                | Purpose                                       |
+| ------------------- | --------------------------------------------- |
+| `observation()`     | Write structured observations to SQLite       |
+| `memory-search()`   | FTS5 full-text search (returns compact index) |
+| `memory-get()`      | Fetch full observation details by ID          |
+| `memory-timeline()` | Get chronological context around anchor       |
+| `memory-update()`   | Update markdown files in memory               |
+
+## PARA Categories
+
+- **Projects**: Active work with deadlines → `knowledge/projects/`
+- **Areas**: Ongoing responsibilities → `knowledge/areas/`
+- **Resources**: Reference material → `knowledge/resources/`
+- **Archives**: Completed/inactive → `knowledge/archives/`
+
+## Memory Tiers (Decay-based)
+
+| Tier     | Access Pattern | Location                   |
+| -------- | -------------- | -------------------------- |
+| **Hot**  | Daily/Weekly   | Active SQLite + `project/` |
+| **Warm** | Monthly        | `knowledge/` directories   |
+| **Cold** | Rarely         | `knowledge/archives/`      |
+
+## Workflow
+
+### Session Start
+
+1. `memory-search()` - Find relevant context
+2. Read `project/` files (auto-injected)
+3. Check `daily/` for recent sessions if needed
+
+### During Work
+
+1. Use `observation()` for decisions, patterns, gotchas
+2. Update `project/gotchas.md` for footguns
+3. Add to `knowledge/` for curated reference
+
+### Session End
+
+1. Summary appended to `daily/YYYY-MM-DD.md`
+2. Sync beads: `br sync --flush-only`
+
+## Philosophy
+
+**Three-layer memory beats single-layer:**
+
+- SQLite for searchability (Knowledge Graph)
+- Daily notes for context (Chronological)
+- Project files for presence (Tacit Knowledge)
+
+Each layer serves a different retrieval pattern.

package/baseline/memory/_templates/design.md

@@ -0,0 +1,59 @@
+# Design Document
+
+**Bead ID:** [bead-id]
+**Created:** [date]
+**Status:** Draft | Validated
+
+## Problem Statement
+
+What we're solving and why it matters:
+
+## Approaches Considered
+
+### Option A: [Name]
+
+- **Pros:** [advantages]
+- **Cons:** [drawbacks]
+
+### Option B: [Name]
+
+- **Pros:** [advantages]
+- **Cons:** [drawbacks]
+
+### Chosen Approach
+
+[Which option and why]
+
+## Architecture
+
+High-level structure and how components fit together:
+
+### Components
+
+- [Component 1]: [purpose]
+- [Component 2]: [purpose]
+
+### Data Flow
+
+[How data moves through the system]
+
+## Error Handling
+
+How the design handles failure cases:
+
+- [Error scenario 1]: [handling approach]
+- [Error scenario 2]: [handling approach]
+
+## Testing Strategy
+
+How we'll validate this design works:
+
+- [Testing approach 1]
+- [Testing approach 2]
+
+## Open Questions
+
+Unresolved items to address during implementation:
+
+- [ ] [Question 1]
+- [ ] [Question 2]

package/baseline/memory/_templates/prd.md

@@ -0,0 +1,192 @@
+# Beads PRD Template
+
+**Bead:** br-[id]  
+**Created:** [date]  
+**Status:** Draft | In Review | Approved
+
+## Bead Metadata
+
+```yaml
+depends_on: [] # Bead IDs that must complete before this one
+parallel: true # Can run concurrently with other parallel beads
+conflicts_with: [] # Bead IDs that modify same files (cannot parallelize)
+blocks: [] # Bead IDs waiting on this one
+estimated_hours: 2 # Time estimate for planning
+```
+
+---
+
+## Problem Statement
+
+### What problem are we solving?
+
+[Clear description of the problem. Include user impact and business impact.]
+
+### Why now?
+
+[What triggered this work? Cost of inaction?]
+
+### Who is affected?
+
+- **Primary users:** [Description]
+- **Secondary users:** [Description]
+
+---
+
+## Scope
+
+### In-Scope
+
+- [List what's allowed]
+
+### Out-of-Scope
+
+- [List what's explicitly off-limits]
+- [Deferred to future iterations]
+
+---
+
+## Proposed Solution
+
+### Overview
+
+[One paragraph describing what this feature does when complete.]
+
+### User Flow (if user-facing)
+
+1. [Step 1]
+2. [Step 2]
+3. [Step 3]
+
+---
+
+## Requirements
+
+### Functional Requirements
+
+#### [Requirement Name]
+
+Brief description of what must be true.
+
+**Scenarios:**
+
+- **WHEN** [precondition or trigger] **THEN** [expected outcome]
+- **WHEN** [edge case condition] **THEN** [expected behavior]
+
+### Non-Functional Requirements
+
+- **Performance:** [constraint if applicable]
+- **Security:** [constraint if applicable]
+- **Accessibility:** [WCAG level if applicable]
+- **Compatibility:** [constraint if applicable]
+
+---
+
+## Success Criteria
+
+- [ ] [Specific, measurable criterion 1]
+  - Verify: `[command or manual check]`
+- [ ] [Specific, measurable criterion 2]
+  - Verify: `[command or manual check]`
+
+---
+
+## Technical Context
+
+### Existing Patterns
+
+- Pattern 1: `src/path/to/example.ts` - Why relevant
+
+### Key Files
+
+- `src/relevant/file.ts` - Why relevant
+
+### Affected Files
+
+Files this bead will modify (for conflict detection):
+
+```yaml
+files:
+  - src/path/to/file.ts # Why
+  - src/path/to/other.ts # Why
+```
+
+---
+
+## Risks & Mitigations
+
+| Risk   | Likelihood   | Impact       | Mitigation      |
+| ------ | ------------ | ------------ | --------------- |
+| Risk 1 | High/Med/Low | High/Med/Low | How to mitigate |
+
+---
+
+## Open Questions
+
+| Question   | Owner | Due Date | Status        |
+| ---------- | ----- | -------- | ------------- |
+| Question 1 | Name  | Date     | Open/Resolved |
+
+---
+
+## Tasks
+
+Write tasks in a machine-convertible format for `prd-task` skill.
+
+**Rules:**
+
+- Each task is a `### <Title> [category]` heading
+- Provide one sentence describing the end state
+- Include `**Metadata:**` with dependency info
+- Include `**Verification:**` with bullet steps proving it works
+
+### <Task Title> [category]
+
+<One sentence describing the end state>
+
+**Metadata:**
+
+```yaml
+depends_on: [] # Task titles that must complete first
+parallel: true # Can run with other parallel tasks
+conflicts_with: [] # Task titles modifying same files
+files: [] # Files this task will modify
+```
+
+**Verification:**
+
+- [Command or check]
+- [Command or check]
+
+### <Task Title> [category]
+
+<One sentence describing the end state>
+
+**Metadata:**
+
+```yaml
+depends_on: ["<Previous Task Title>"]
+parallel: false
+files: []
+```
+
+**Verification:**
+
+- [Command or check]
+
+---
+
+## Dependency Legend
+
+| Field            | Purpose                                           | Example                                    |
+| ---------------- | ------------------------------------------------- | ------------------------------------------ |
+| `depends_on`     | Must complete before this task starts             | `["Setup database", "Create schema"]`      |
+| `parallel`       | Can run concurrently with other parallel tasks    | `true` / `false`                           |
+| `conflicts_with` | Cannot run in parallel (same files)               | `["Update config"]`                        |
+| `files`          | Files this task modifies (for conflict detection) | `["src/db/schema.ts", "src/db/client.ts"]` |
+
+---
+
+## Notes
+
+[Additional context, constraints, or decisions]

package/baseline/memory/_templates/project.md

@@ -0,0 +1,58 @@
+---
+purpose: Project vision, goals, and success criteria (loaded into all AI contexts)
+updated: 2024-12-21
+---
+
+# Project Vision
+
+## The Goal
+
+<!-- One sentence: What does this project achieve? Outcome-shaped, not task-shaped. -->
+<!-- Good: "A real-time chat application with persistent message history" -->
+<!-- Bad: "Build chat components and API endpoints" -->
+
+## Success Criteria
+
+<!-- How do we know the project is successful? List 3-7 observable outcomes. -->
+<!-- Each should be verifiable by using the application, not by checking code. -->
+
+1. **[Criterion 1]** - [Specific, measurable outcome]
+2. **[Criterion 2]** - [Specific, measurable outcome]
+3. **[Criterion 3]** - [Specific, measurable outcome]
+
+## Target Users
+
+<!-- Who will use this? What do they need? -->
+
+- **Primary:** [User type and their core need]
+- **Secondary:** [User type and their core need]
+
+## Core Principles
+
+<!-- Non-negotiable principles that guide all decisions -->
+
+1. **[Principle 1]** - [Explanation]
+2. **[Principle 2]** - [Explanation]
+3. **[Principle 3]** - [Explanation]
+
+## Current Phase
+
+<!-- Where are we in the project lifecycle? -->
+
+- **Status:** [Discovery / Planning / Implementation / Polish / Maintenance]
+- **Milestone:** [Current milestone name]
+- **Next Milestone:** [Next milestone name]
+
+## Key Links
+
+<!-- Important references -->
+
+- **Repository:** [URL]
+- **Documentation:** [URL]
+- **Staging:** [URL]
+- **Production:** [URL]
+
+---
+
+_Update this file when project direction or phase changes._
+_AI uses this to maintain context across sessions and make decisions aligned with project goals._

package/baseline/memory/_templates/proposal.md

@@ -0,0 +1,38 @@
+# Proposal
+
+**Bead:** [bead-id]
+**Author:** [author]
+**Date:** [YYYY-MM-DD]
+
+## Why
+
+<!-- What problem does this solve? Why now? -->
+
+## What Changes
+
+<!-- High-level description of the proposed changes -->
+
+## Capabilities
+
+### New Capabilities
+
+- `capability-name`: Brief description of what it enables
+
+### Modified Capabilities
+
+- `capability-name`: How existing behavior changes
+
+## Impact
+
+### Users Affected
+
+- [User type or system]
+
+### Migration Required
+
+- [ ] Yes / No
+- If yes: [brief migration notes]
+
+## Open Questions
+
+- [ ] [Question that needs answering before proceeding]

package/baseline/memory/_templates/roadmap.md

@@ -0,0 +1,93 @@
+---
+purpose: Project roadmap with phases, milestones, and bead organization
+updated: 2024-12-21
+---
+
+# Roadmap
+
+## Overview
+
+<!-- High-level project breakdown -->
+
+| Phase     | Goal                | Status        | Beads |
+| --------- | ------------------- | ------------- | ----- |
+| [Phase 1] | [One-sentence goal] | [Not Started] | [#]   |
+| [Phase 2] | [One-sentence goal] | [Not Started] | [#]   |
+| [Phase 3] | [One-sentence goal] | [Not Started] | [#]   |
+
+## Phase 1: [Name]
+
+**Goal:** [Outcome-shaped description]
+
+**Success Criteria:**
+
+- [ ] [Criterion 1]
+- [ ] [Criterion 2]
+- [ ] [Criterion 3]
+
+**Beads:**
+| ID | Title | Type | Status | Depends On |
+|----|-------|------|--------|------------|
+| br-xxx | [Title] | task | open | - |
+| br-xxx | [Title] | task | open | br-xxx |
+
+**Out of Scope:**
+
+- [What's explicitly deferred to later phases]
+
+---
+
+## Phase 2: [Name]
+
+**Goal:** [Outcome-shaped description]
+
+**Success Criteria:**
+
+- [ ] [Criterion 1]
+- [ ] [Criterion 2]
+
+**Beads:**
+| ID | Title | Type | Status | Depends On |
+|----|-------|------|--------|------------|
+| br-xxx | [Title] | feature | open | Phase 1 |
+
+**Dependencies:**
+
+- Requires Phase 1 completion
+
+---
+
+## Phase 3: [Name]
+
+**Goal:** [Outcome-shaped description]
+
+**Success Criteria:**
+
+- [ ] [Criterion 1]
+
+**Beads:**
+| ID | Title | Type | Status | Depends On |
+|----|-------|------|--------|------------|
+| br-xxx | [Title] | epic | open | Phase 2 |
+
+---
+
+## Legend
+
+**Status:**
+
+- `Not Started` - No work begun
+- `In Progress` - Active development
+- `Complete` - All beads closed
+
+**Type:**
+
+- `task` - Tactical, single-session work
+- `feature` - New capability, multi-session
+- `epic` - Cross-domain, significant scope
+- `bug` - Fix for broken behavior
+
+---
+
+_Update this file when phases complete or roadmap changes._
+_Use `/plan` command to create detailed plans for active phases._

package/baseline/memory/_templates/state.md

@@ -0,0 +1,89 @@
+---
+purpose: Current project state, active decisions, blockers, and position tracking
+updated: 2024-12-21
+---
+
+# State
+
+## Current Position
+
+<!-- Where are we right now? What just happened? -->
+
+**Active Bead:** br-xxx - [Title]
+**Status:** [In Progress / Blocked / Review]
+**Started:** [Date]
+**Phase:** [Phase name from roadmap.md]
+
+## Recent Completed Work
+
+<!-- Last 3-5 completed beads -->
+
+| Bead   | Title   | Completed | Summary            |
+| ------ | ------- | --------- | ------------------ |
+| br-xxx | [Title] | [Date]    | [One-line summary] |
+| br-xxx | [Title] | [Date]    | [One-line summary] |
+
+## Active Decisions
+
+<!-- Decisions made that affect current and future work -->
+
+| Date   | Decision           | Rationale | Impact            |
+| ------ | ------------------ | --------- | ----------------- |
+| [Date] | [What was decided] | [Why]     | [What it affects] |
+
+## Blockers
+
+<!-- What's preventing progress? -->
+
+| Bead   | Blocker                  | Since  | Owner               |
+| ------ | ------------------------ | ------ | ------------------- |
+| br-xxx | [Description of blocker] | [Date] | [Who's responsible] |
+
+## Open Questions
+
+<!-- Questions that need answers before proceeding -->
+
+| Question   | Context            | Blocking | Priority       |
+| ---------- | ------------------ | -------- | -------------- |
+| [Question] | [Where it came up] | [Yes/No] | [High/Med/Low] |
+
+## Context Notes
+
+<!-- Important context that doesn't fit elsewhere -->
+
+### Technical
+
+- [Technical decision or constraint]
+- [Pattern or convention established]
+
+### Product
+
+- [Product decision or direction]
+- [User feedback or requirement]
+
+### Process
+
+- [Workflow change or improvement]
+- [Team agreement or process]
+
+## Next Actions
+
+<!-- Immediate next steps -->
+
+1. [ ] [Action item with owner if applicable]
+2. [ ] [Action item]
+3. [ ] [Action item]
+
+## Session Handoff
+
+<!-- For multi-session work, what's the state for the next session? -->
+
+**Last Session:** [Date]
+**Next Session Priority:** [What's most important to do next]
+**Known Issues:** [Any issues to be aware of]
+**Context Links:** [Relevant files, PRs, docs]
+
+---
+
+_Update this file at the end of each significant session or when state changes._
+_This file is the "you are here" marker for the project._