intent-engine 0.11.1

A command-line database service for tracking strategic intent, tasks, and events
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128

# Phase 1 Focus Restoration - Integration Tests

This directory contains integration tests for Phase 1 of the Speckit Guardian Integration Protocol.

## Test Files

### 1. `test-session-restore-workflow.sh`
**Purpose**: Tests the complete session-restore workflow including task creation, focus management, and event recording.

**Test Scenarios**:
- ✅ Complete workflow with focus (parent task, subtasks, siblings, events)
- ✅ No focus scenario (returns stats and guidance)
- ✅ Error scenario (workspace not found)

**Key Validations**:
- Correct JSON structure
- Parent/sibling/child relationships
- Event history preservation
- Suggested commands generation

### 2. `test-session-start-hook.sh`
**Purpose**: Tests the SessionStart hook integration and output formatting.

**Test Scenarios**:
- ✅ Hook execution with focused task
- ✅ Spec preview truncation
- ✅ Event types (decision, blocker, note) display
- ✅ No focus scenario output
- ✅ Error handling (graceful degradation)

**Key Validations**:
- `<system-reminder>` formatting
- Minimal style output (concise, high information density)
- Correct emoji usage (⚠️ for blockers)
- Executable permissions (Unix)

### 3. `test-setup-claude-code.sh`
**Purpose**: Tests the automated hook installation command.

**Test Scenarios**:
- ✅ Fresh directory setup
- ✅ Existing .claude directory handling
- ✅ Hook already exists (should fail without --force)
- ✅ --force flag (overwrite existing)
- ✅ --dry-run mode (preview only)
- ✅ --claude-dir custom directory
- ✅ Hook functionality verification

**Key Validations**:
- Directory structure creation
- File permissions (executable on Unix)
- Hook content correctness
- Error handling

## Running the Tests

### Run All Tests
```bash
./run-all-tests.sh
```

### Run Individual Tests
```bash
./test-session-restore-workflow.sh
./test-session-start-hook.sh
./test-setup-claude-code.sh
```

## Prerequisites

- **jq**: JSON parsing in bash scripts
  ```bash
  # Ubuntu/Debian
  sudo apt-get install jq

  # macOS
  brew install jq
  ```

- **Intent-Engine**: Built and available in PATH
  ```bash
  cargo build --release
  export PATH="$PWD/target/release:$PATH"
  ```

## Test Environment

Each test creates a temporary directory and cleans up after completion. Tests are isolated and do not interfere with each other.

## Test Output Format

Tests use a clear assertion-based format:
```
✓ workspace init
✓ task add parent
✓ session-restore execution
✓ status is success
...
✅ Test 1 passed
```

Failed assertions show:
```
❌ FAILED: status is success
```

## Success Criteria

All tests must pass with:
- Exit code 0
- All assertions passing
- No errors in stderr (except intentional error tests)

## Coverage

These integration tests cover:
- ✅ CLI command execution
- ✅ JSON output parsing
- ✅ Hook script execution
- ✅ File system operations
- ✅ Error scenarios
- ✅ Cross-platform compatibility (Unix/Windows considerations)

## Related Documentation

- [Phase 1 Implementation Spec](../../docs/phase1-focus-restoration-spec.md)
- [Phase 1 Testing Spec](../../docs/phase1-testing-spec.md)
- [Speckit Guardian v2.0](../../docs/speckit-guardian.md)