project-iris 0.0.1

package/src/iris_bundle/frameworks/iris-core/memory-bank/intents/011-vscode-extension/units/artifact-parser/stories/003-artifact-parsing.md

@@ -0,0 +1,57 @@
+---
+id: vscode-extension-story-ap-003
+unit: artifact-parser
+intent: 011-vscode-extension
+status: complete
+priority: must
+created: 2025-12-25T17:00:00Z
+assigned_bolt: bolt-artifact-parser-1
+implemented: true
+---
+
+# Story: Artifact Parsing
+
+## User Story
+
+**As a** sidebar-provider component
+**I want** to get a complete model of all memory-bank artifacts
+**So that** I can render them in the tree view
+
+## Acceptance Criteria
+
+- [ ] **Given** a memory-bank with intents, **When** scanMemoryBank() is called, **Then** return array of Intent objects with name, number, status
+- [ ] **Given** an intent with units, **When** parseIntent() is called, **Then** return Intent with nested Unit objects
+- [ ] **Given** a unit with stories, **When** parseUnit() is called, **Then** return Unit with nested Story objects
+- [ ] **Given** bolts in memory-bank/bolts/, **When** scanMemoryBank() is called, **Then** return array of Bolt objects with id, type, status, stages, stories
+- [ ] **Given** standards in memory-bank/standards/, **When** scanMemoryBank() is called, **Then** return array of Standard objects
+- [ ] **Given** a bolt with stages completed, **When** parseBolt() is called, **Then** return Bolt with stages array and currentStage
+
+## Technical Notes
+
+- Use MemoryBankSchema for all paths
+- Parse frontmatter using 004-frontmatter-parser
+- Create TypeScript interfaces: Intent, Unit, Story, Bolt, Stage, Standard
+- Handle missing folders gracefully (empty arrays)
+
+## Dependencies
+
+### Requires
+- 001-memory-bank-schema
+- 004-frontmatter-parser
+
+### Enables
+- sidebar-provider/002-intent-unit-story-tree
+
+## Edge Cases
+
+| Scenario | Expected Behavior |
+|----------|-------------------|
+| Empty intents folder | Return empty array |
+| Intent without units folder | Return intent with empty units array |
+| Malformed folder names | Skip folder, log warning |
+| Very deep nesting | Handle up to defined depth |
+
+## Out of Scope
+
+- Caching (future optimization)
+- Incremental parsing (future optimization)

package/src/iris_bundle/frameworks/iris-core/memory-bank/intents/011-vscode-extension/units/artifact-parser/stories/004-frontmatter-parser.md

@@ -0,0 +1,61 @@
+---
+id: vscode-extension-story-ap-004
+unit: artifact-parser
+intent: 011-vscode-extension
+status: complete
+priority: must
+created: 2025-12-25T17:00:00Z
+assigned_bolt: bolt-artifact-parser-1
+implemented: true
+---
+
+# Story: Frontmatter Parser
+
+## User Story
+
+**As a** artifact parser component
+**I want** to extract YAML frontmatter from markdown files
+**So that** I can determine artifact status and metadata
+
+## Acceptance Criteria
+
+- [ ] **Given** a markdown file with YAML frontmatter, **When** parseFrontmatter() is called, **Then** return parsed object with all fields
+- [ ] **Given** frontmatter with `status: draft`, **When** normalizeStatus() is called, **Then** return ArtifactStatus.Draft
+- [ ] **Given** frontmatter with `status: in-progress`, **When** normalizeStatus() is called, **Then** return ArtifactStatus.InProgress
+- [ ] **Given** frontmatter with `status: complete`, **When** normalizeStatus() is called, **Then** return ArtifactStatus.Complete
+- [ ] **Given** a file without frontmatter, **When** parseFrontmatter() is called, **Then** return null (not error)
+- [ ] **Given** invalid YAML in frontmatter, **When** parseFrontmatter() is called, **Then** return null and log warning
+- [ ] **Given** frontmatter with `status: completed`, **When** normalizeStatus() is called, **Then** return ArtifactStatus.Complete (handle variations)
+
+## Technical Notes
+
+- Use js-yaml or gray-matter for parsing
+- Frontmatter is delimited by `---` at start of file
+- Status normalization should handle common variations:
+  - draft, pending → Draft
+  - in-progress, in_progress, inprogress → InProgress
+  - complete, completed, done → Complete
+  - anything else → Unknown
+
+## Dependencies
+
+### Requires
+- None (utility function)
+
+### Enables
+- 003-artifact-parsing
+
+## Edge Cases
+
+| Scenario | Expected Behavior |
+|----------|-------------------|
+| Empty file | Return null |
+| Only frontmatter, no content | Return parsed frontmatter |
+| Nested YAML objects | Parse correctly |
+| Unicode in values | Handle correctly |
+| Very large frontmatter | Parse without issue |
+
+## Out of Scope
+
+- Frontmatter validation against schema
+- Writing/updating frontmatter

package/src/iris_bundle/frameworks/iris-core/memory-bank/intents/011-vscode-extension/units/artifact-parser/stories/005-bolt-dependencies.md

@@ -0,0 +1,58 @@
+---
+id: vscode-extension-story-ap-005
+unit: artifact-parser
+intent: 011-vscode-extension
+status: complete
+priority: must
+created: 2025-12-26T10:00:00Z
+assigned_bolt: bolt-artifact-parser-2
+implemented: true
+---
+
+# Story: Bolt Dependency Parsing
+
+## User Story
+
+**As a** extension developer
+**I want** the parser to read and compute bolt dependencies
+**So that** the UI can display dependency-ordered queues and blocked bolt indicators
+
+## Acceptance Criteria
+
+- [ ] **Given** a bolt with `requires_bolts: [bolt-a, bolt-b]`, **When** parsed, **Then** bolt.requiresBolts equals `['bolt-a', 'bolt-b']`
+- [ ] **Given** a bolt with `enables_bolts: [bolt-c]`, **When** parsed, **Then** bolt.enablesBolts equals `['bolt-c']`
+- [ ] **Given** a pending bolt where all requires_bolts are complete, **When** computed, **Then** bolt.isBlocked equals `false`
+- [ ] **Given** a pending bolt where some requires_bolts are incomplete, **When** computed, **Then** bolt.isBlocked equals `true`
+- [ ] **Given** a blocked bolt, **When** computed, **Then** bolt.blockedBy contains IDs of incomplete required bolts
+- [ ] **Given** a bolt that enables 3 other bolts, **When** computed, **Then** bolt.unblocksCount equals `3`
+- [ ] **Given** a bolt with no requires_bolts, **When** computed, **Then** bolt.isBlocked equals `false`
+
+## Technical Notes
+
+- Add `requiresBolts`, `enablesBolts`, `isBlocked`, `blockedBy`, `unblocksCount` to Bolt interface
+- Dependency computation requires access to all bolts (pass full bolt list)
+- Use O(n) algorithm for computing unblocksCount
+- Handle missing/malformed dependency fields gracefully (treat as empty array)
+
+## Dependencies
+
+### Requires
+- 003-artifact-parsing (bolt parsing)
+- 004-frontmatter-parser
+
+### Enables
+- sidebar-provider/009-up-next-queue
+
+## Edge Cases
+
+| Scenario | Expected Behavior |
+|----------|-------------------|
+| Circular dependencies | Detect and mark both as blocked |
+| Non-existent bolt in requires_bolts | Treat as incomplete (blocked) |
+| Empty requires_bolts array | Not blocked |
+| Missing requires_bolts field | Treat as empty (not blocked) |
+
+## Out of Scope
+
+- Dependency cycle detection warning UI
+- Auto-reordering of bolts based on dependencies

package/src/iris_bundle/frameworks/iris-core/memory-bank/intents/011-vscode-extension/units/artifact-parser/stories/006-activity-feed-derivation.md

@@ -0,0 +1,70 @@
+---
+id: vscode-extension-story-ap-006
+unit: artifact-parser
+intent: 011-vscode-extension
+status: complete
+priority: must
+created: 2025-12-26T10:00:00Z
+assigned_bolt: bolt-artifact-parser-2
+implemented: true
+---
+
+# Story: Activity Feed Derivation
+
+## User Story
+
+**As a** extension developer
+**I want** activity events derived from bolt timestamps
+**So that** the UI can display a recent activity feed without maintaining a separate log
+
+## Acceptance Criteria
+
+- [ ] **Given** a bolt with `created: 2025-12-26T09:00:00Z`, **When** buildActivityFeed called, **Then** result includes `bolt-created` event with that timestamp
+- [ ] **Given** a bolt with `started: 2025-12-26T10:00:00Z`, **When** buildActivityFeed called, **Then** result includes `bolt-start` event
+- [ ] **Given** a bolt with `stages_completed: [{name: model, completed: ...}]`, **When** buildActivityFeed called, **Then** result includes `stage-complete` event for each entry
+- [ ] **Given** a bolt with `completed: 2025-12-26T12:00:00Z`, **When** buildActivityFeed called, **Then** result includes `bolt-complete` event
+- [ ] **Given** multiple bolts with various timestamps, **When** buildActivityFeed called, **Then** result is sorted by timestamp descending
+- [ ] **Given** an activity event, **When** accessed, **Then** it has: id, type, timestamp, icon, iconClass, text, targetId, targetName, tag
+
+## Technical Notes
+
+- ActivityEvent interface:
+  ```typescript
+  interface ActivityEvent {
+    id: string;           // e.g., "bolt-x-started"
+    type: 'bolt-created' | 'bolt-start' | 'stage-complete' | 'bolt-complete';
+    timestamp: Date;
+    icon: string;         // e.g., "▶", "✓", "✔", "+"
+    iconClass: string;    // e.g., "bolt-start", "stage-complete"
+    text: string;         // e.g., "Started <strong>bolt-x</strong>"
+    targetId: string;     // Bolt ID
+    targetName: string;   // Bolt name
+    tag: 'bolt' | 'stage';
+  }
+  ```
+- Parse ISO 8601 timestamps from frontmatter
+- Handle missing/null timestamps gracefully (skip event)
+
+## Dependencies
+
+### Requires
+- 003-artifact-parsing (bolt parsing)
+- 004-frontmatter-parser
+
+### Enables
+- sidebar-provider/010-activity-feed-ui
+
+## Edge Cases
+
+| Scenario | Expected Behavior |
+|----------|-------------------|
+| Bolt with null timestamps | Skip those events |
+| Invalid timestamp format | Skip that event, log warning |
+| Empty bolts array | Return empty activity feed |
+| Bolt with only created timestamp | Only bolt-created event |
+
+## Out of Scope
+
+- Persisting activity to separate file
+- Activity for non-bolt events (stories, intents)
+- Activity pruning/limiting at parser level

package/src/iris_bundle/frameworks/iris-core/memory-bank/intents/011-vscode-extension/units/artifact-parser/unit-brief.md

@@ -0,0 +1,223 @@
+---
+unit: artifact-parser
+intent: 011-vscode-extension
+phase: construction
+status: complete
+created: 2025-12-25T17:00:00Z
+updated: 2025-12-27T16:30:00Z
+default_bolt_type: simple-construction-bolt
+---
+
+# Unit Brief: Artifact Parser
+
+## Purpose
+
+Parse memory-bank directory structure and artifact files to build a model of AI-DLC artifacts with their statuses. This is the foundation unit that other units depend on for understanding the memory-bank content.
+
+## Scope
+
+### In Scope
+
+- Central `MemoryBankSchema` class with hardcoded paths (future: dynamic from memory-bank.yaml)
+- Directory scanning for intents, units, stories, bolts, standards
+- YAML frontmatter parsing from markdown files
+- Status extraction and normalization
+- Project detection (is this a irismd project?)
+- Graceful handling of missing/malformed files
+
+### Out of Scope
+
+- File system watching (handled by file-watcher unit)
+- Tree view rendering (handled by sidebar-provider unit)
+- File modification/creation
+
+---
+
+## Assigned Requirements
+
+| FR | Requirement | Priority |
+|----|-------------|----------|
+| FR-1.4 | Auto-detect irismd projects (presence of `memory-bank/` or `.irismd/`) | Must |
+| FR-3.1 | Parse intent status (draft, in-progress, complete) | Must |
+| FR-3.2 | Calculate unit completion status | Must |
+| FR-3.3 | Parse story status (pending, in-progress, done) | Must |
+| FR-3.4 | Parse bolt status, type, stages, stories | Must |
+| FR-6.1 | Central `MemoryBankSchema` class for path definitions | Must |
+| FR-6.2 | Hardcoded paths for Phase 1 | Must |
+| FR-6.3 | Design for future dynamic discovery | Should |
+| FR-6.4 | Parse artifact frontmatter for status | Must |
+| FR-6.5 | Handle missing/malformed frontmatter gracefully | Must |
+| FR-6.6 | Support standard memory-bank directory structure | Must |
+| FR-10.1 | Parse `requires_bolts` field from bolt frontmatter | Must |
+| FR-10.2 | Parse `enables_bolts` field from bolt frontmatter | Must |
+| FR-10.3 | Compute `isBlocked` for pending bolts | Must |
+| FR-10.4 | Compute `blockedBy` list for blocked bolts | Must |
+| FR-10.5 | Compute `unblocksCount` for prioritization | Must |
+| FR-10.6 | Distinguish "blocked" from "pending" status | Must |
+| FR-11.1 | Derive activity feed from bolt timestamps | Must |
+| FR-11.2 | Support activity event types (created, start, stage-complete, complete) | Must |
+| FR-11.3 | Sort activity feed by timestamp descending | Must |
+
+---
+
+## Domain Concepts
+
+### Key Entities
+
+| Entity | Description | Attributes |
+|--------|-------------|------------|
+| MemoryBankSchema | Central path/structure definitions | paths, patterns, getIntentsPath(), getBoltsPath() |
+| Intent | Feature/capability container | name, number, status, units[] |
+| Unit | Deployable work unit | name, intent, status, stories[], dependencies |
+| Story | User story | id, title, status, unit |
+| Bolt | Construction session | id, type, status, currentStage, stages[], stories[], requiresBolts[], enablesBolts[], isBlocked, blockedBy[], unblocksCount |
+| Stage | Bolt execution stage | name, status, order, completed (timestamp) |
+| Standard | Project standard | name, path |
+| ArtifactStatus | Normalized status | draft/pending, in-progress, complete/done, blocked, unknown |
+| ActivityEvent | Derived activity item | id, type, timestamp, icon, text, targetId, targetName, tag |
+
+### Key Operations
+
+| Operation | Description | Inputs | Outputs |
+|-----------|-------------|--------|---------|
+| detectProject | Check if workspace is irismd project | workspacePath | boolean |
+| scanMemoryBank | Scan and parse all artifacts | workspacePath | MemoryBankModel |
+| parseIntent | Parse single intent folder | intentPath | Intent |
+| parseUnit | Parse single unit folder | unitPath | Unit |
+| parseBolt | Parse single bolt folder | boltPath | Bolt |
+| parseFrontmatter | Extract YAML frontmatter | fileContent | FrontmatterData |
+| normalizeStatus | Convert status string to enum | rawStatus | ArtifactStatus |
+| computeBoltDependencies | Calculate isBlocked, blockedBy, unblocksCount | Bolt, allBolts | Bolt (enriched) |
+| isBoltBlocked | Check if bolt's requires_bolts are complete | Bolt, allBolts | boolean |
+| getBlockingBolts | Get list of incomplete required bolts | Bolt, allBolts | string[] |
+| countUnblocks | Count bolts this bolt enables | boltId, allBolts | number |
+| buildActivityFeed | Derive activity events from bolts | Bolt[] | ActivityEvent[] |
+| getUpNextBolts | Get pending bolts ordered by priority | Bolt[] | Bolt[] |
+
+---
+
+## Story Summary
+
+| Metric | Count |
+|--------|-------|
+| Total Stories | 6 |
+| Must Have | 6 |
+| Should Have | 0 |
+| Could Have | 0 |
+
+### Stories
+
+| Story ID | Title | Priority | Status | Bolt |
+|----------|-------|----------|--------|------|
+| 001 | Memory Bank Schema Class | Must | Complete | bolt-1 |
+| 002 | Project Detection | Must | Complete | bolt-1 |
+| 003 | Artifact Parsing | Must | Complete | bolt-1 |
+| 004 | Frontmatter Parser | Must | Complete | bolt-1 |
+| 005 | Bolt Dependency Parsing | Must | Complete | bolt-2 |
+| 006 | Activity Feed Derivation | Must | Complete | bolt-2 |
+
+---
+
+## Dependencies
+
+### Depends On
+
+| Unit | Reason |
+|------|--------|
+| None | Foundation unit |
+
+### Depended By
+
+| Unit | Reason |
+|------|--------|
+| sidebar-provider | Needs parsed artifact data |
+| file-watcher | Needs to re-parse on changes |
+| welcome-view | Needs project detection |
+
+### External Dependencies
+
+| System | Purpose | Risk |
+|--------|---------|------|
+| Node.js fs | File system access | Low |
+| js-yaml | YAML frontmatter parsing | Low |
+
+---
+
+## Technical Context
+
+### Suggested Technology
+
+- TypeScript classes for models
+- js-yaml for frontmatter parsing
+- VS Code workspace API for paths
+- Glob patterns for file discovery
+
+### Integration Points
+
+| Integration | Type | Protocol |
+|-------------|------|----------|
+| VS Code workspace | API | vscode.workspace |
+| File System | API | Node.js fs/promises |
+
+### Data Storage
+
+| Data | Type | Volume | Retention |
+|------|------|--------|-----------|
+| In-memory models | TypeScript objects | Small (<1MB) | Session |
+
+---
+
+## Constraints
+
+- Must be synchronous-friendly for initial load (or fast async)
+- Must handle 100+ artifacts without performance issues
+- Must not throw on malformed files (graceful degradation)
+
+---
+
+## Success Criteria
+
+### Functional
+
+- [ ] MemoryBankSchema defines all paths in one place
+- [ ] detectProject correctly identifies irismd projects
+- [ ] All artifact types parsed correctly (intents, units, stories, bolts, standards)
+- [ ] Frontmatter parsing extracts status fields
+- [ ] Malformed files return "unknown" status, not errors
+- [ ] Bolt dependencies parsed (requires_bolts, enables_bolts)
+- [ ] isBlocked computed correctly for pending bolts
+- [ ] blockedBy list computed for blocked bolts
+- [ ] unblocksCount computed for queue prioritization
+- [ ] Activity feed derived from bolt timestamps
+- [ ] Activity events sorted by timestamp descending
+
+### Non-Functional
+
+- [ ] Parse 100 artifacts in < 200ms
+- [ ] No memory leaks from repeated parsing
+- [ ] Dependency computation O(n) complexity
+
+### Quality
+
+- [ ] Unit tests for all parsing functions
+- [ ] Unit tests for dependency computation
+- [ ] Unit tests for activity feed derivation
+- [ ] Test fixtures for valid/invalid frontmatter
+- [ ] Code coverage > 80%
+
+---
+
+## Bolt Suggestions
+
+| Bolt | Type | Stories | Objective | Status |
+|------|------|---------|-----------|--------|
+| bolt-artifact-parser-1 | Simple | 001, 002, 003, 004 | Core parsing functionality | Complete |
+| bolt-artifact-parser-2 | Simple | 005, 006 | Dependency parsing and activity derivation | Complete |
+
+---
+
+## Notes
+
+- MemoryBankSchema should be designed with dependency injection in mind for future dynamic loading
+- Consider caching parsed results to avoid re-parsing unchanged files
+- Status normalization should handle variations (e.g., "completed" vs "complete")

package/src/iris_bundle/frameworks/iris-core/memory-bank/intents/011-vscode-extension/units/extension-core/construction-log.md

@@ -0,0 +1,59 @@
+---
+unit: extension-core
+intent: 011-vscode-extension
+created: 2025-12-25
+last_updated: 2025-12-25
+---
+
+# Construction Log: extension-core
+
+## Original Plan
+
+**From Inception**: 1 bolt planned
+**Planned Date**: 2025-12-25
+
+| Bolt ID | Stories | Type |
+|---------|---------|------|
+| bolt-extension-core-1 | 001, 002, 003 | simple-construction-bolt |
+
+## Replanning History
+
+| Date | Action | Change | Reason | Approved |
+|------|--------|--------|--------|----------|
+
+## Current Bolt Structure
+
+| Bolt ID | Stories | Status | Changed |
+|---------|---------|--------|---------|
+| bolt-extension-core-1 | 001, 002, 003 | completed | - |
+
+## Execution History
+
+| Date | Bolt | Event | Details |
+|------|------|-------|---------|
+| 2025-12-25T22:30:00Z | bolt-extension-core-1 | started | Stage 1: Plan |
+| 2025-12-25T22:30:00Z | bolt-extension-core-1 | stage-complete | Plan -> Implement |
+| 2025-12-25T22:45:00Z | bolt-extension-core-1 | stage-complete | Implement -> Test |
+| 2025-12-25T22:50:00Z | bolt-extension-core-1 | completed | All 3 stages done |
+
+## Execution Summary
+
+| Metric | Value |
+|--------|-------|
+| Original bolts planned | 1 |
+| Current bolt count | 1 |
+| Bolts completed | 1 |
+| Bolts in progress | 0 |
+| Bolts remaining | 0 |
+| Replanning events | 0 |
+
+## Notes
+
+Bolt complete. extension-core unit is fully implemented with:
+- Main extension.ts entry point
+- activate() and deactivate() functions
+- TreeDataProvider and WebviewViewProvider registration
+- All commands registered (refresh, openFile, revealInExplorer, copyPath)
+- File watcher integration for auto-refresh
+- Installation watcher for post-install detection
+- favicon.png activity bar icon

package/src/iris_bundle/frameworks/iris-core/memory-bank/intents/011-vscode-extension/units/extension-core/stories/001-extension-activation.md

@@ -0,0 +1,55 @@
+---
+id: vscode-extension-story-ec-001
+unit: extension-core
+intent: 011-vscode-extension
+status: draft
+priority: must
+created: 2025-12-25
+assigned_bolt: null
+implemented: false
+---
+
+# Story: Extension Activation and View Registration
+
+## User Story
+
+**As a** VS Code user
+**I want** the irismd extension to activate and show in the activity bar
+**So that** I can access the memory-bank dashboard
+
+## Acceptance Criteria
+
+- [ ] **Given** VS Code starts with extension installed, **When** workspace opens, **Then** extension activates
+- [ ] **Given** extension activates, **When** activation completes, **Then** "irismd" icon appears in activity bar
+- [ ] **Given** activity bar icon, **When** clicked, **Then** sidebar panel opens
+- [ ] **Given** extension activates, **When** checking project state, **Then** shows welcome view OR tree view appropriately
+- [ ] **Given** extension, **When** VS Code closes, **Then** deactivate function cleans up resources
+- [ ] **Given** extension, **When** checking icon, **Then** uses favicon.png from resources
+
+## Technical Notes
+
+- Export activate(context: ExtensionContext) and deactivate()
+- Register TreeDataProvider in activate
+- Add all disposables to context.subscriptions
+- Use vscode.window.registerWebviewViewProvider for welcome view
+
+## Dependencies
+
+### Requires
+- All other units (coordinates them)
+
+### Enables
+- All extension functionality
+
+## Edge Cases
+
+| Scenario | Expected Behavior |
+|----------|-------------------|
+| Activation error | Log error, show notification |
+| No workspace | Extension activates, shows "no workspace" state |
+| Slow file system | Activation completes, tree loads async |
+
+## Out of Scope
+
+- Lazy activation optimization
+- Remote workspace support

package/src/iris_bundle/frameworks/iris-core/memory-bank/intents/011-vscode-extension/units/extension-core/stories/002-command-registration.md

@@ -0,0 +1,54 @@
+---
+id: vscode-extension-story-ec-002
+unit: extension-core
+intent: 011-vscode-extension
+status: draft
+priority: must
+created: 2025-12-25
+assigned_bolt: null
+implemented: false
+---
+
+# Story: Command Registration
+
+## User Story
+
+**As a** VS Code user
+**I want** extension commands to be available
+**So that** I can interact with the sidebar via commands and shortcuts
+
+## Acceptance Criteria
+
+- [ ] **Given** extension activates, **When** commands registered, **Then** "irismd.refresh" command is available
+- [ ] **Given** refresh command, **When** executed, **Then** tree view refreshes
+- [ ] **Given** sidebar title bar, **When** rendered, **Then** refresh icon button is visible
+- [ ] **Given** refresh button, **When** clicked, **Then** irismd.refresh command executes
+- [ ] **Given** command palette, **When** searching "irismd", **Then** relevant commands appear
+
+## Technical Notes
+
+- Use vscode.commands.registerCommand
+- Commands in package.json contributes.commands
+- Refresh button via contributes.menus["view/title"]
+- Command IDs: irismd.refresh, irismd.revealInExplorer, irismd.copyPath
+
+## Dependencies
+
+### Requires
+- 001-extension-activation
+- sidebar-provider (for refresh target)
+
+### Enables
+- 003-file-operation-commands
+
+## Edge Cases
+
+| Scenario | Expected Behavior |
+|----------|-------------------|
+| Command called without tree | No-op or show message |
+| Rapid refresh clicks | Debounced by file-watcher |
+
+## Out of Scope
+
+- Custom keyboard shortcuts
+- Command arguments