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
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
//! App-level effects for pre-pipeline operations.
//!
//! This module defines effects that represent side effects in the CLI layer
//! before the pipeline reducer takes over. Effects are data describing what
//! should happen, not the execution itself.
//!
//! # Architecture
//!
//! Effects follow the functional core / imperative shell pattern:
//! - Pure functions produce [`AppEffect`] values describing desired operations
//! - An [`AppEffectHandler`] executes the effects, performing actual I/O
//! - This separation enables testing without real filesystem or git operations
//!
//! # Example
//!
//! ```ignore
//! // Pure function returns effects (testable)
//! fn setup_workspace() -> Vec<AppEffect> {
//! vec![
//! AppEffect::CreateDir { path: PathBuf::from(".agent") },
//! AppEffect::WriteFile {
//! path: PathBuf::from(".agent/config.toml"),
//! content: "key = value".to_string(),
//! },
//! ]
//! }
//!
//! // Handler executes effects (I/O boundary)
//! for effect in setup_workspace() {
//! handler.execute(effect);
//! }
//! ```
use ;
use PathBuf;
/// Result of a git commit operation.
///
/// Indicates whether a commit was successfully created or if there were
/// no changes to commit.
/// Result of a rebase operation.
///
/// Captures the various outcomes possible when rebasing a branch onto
/// an upstream branch, including success, conflicts, and failures.
/// App-level effects for CLI operations.
///
/// Each variant represents a side effect that can occur during CLI
/// operations. Effects are data structures that describe what should
/// happen without actually performing the operation.
///
/// # Categories
///
/// Effects are organized into logical categories:
/// - **Working Directory**: Process working directory management
/// - **Filesystem**: File and directory operations
/// - **Git**: Version control operations
/// - **Environment**: Environment variable access
/// - **Logging**: User-facing output
/// Result of executing an [`AppEffect`].
///
/// Each effect execution produces a result that either indicates success
/// (with optional return data) or an error. The variant used depends on
/// what data the effect produces.
/// Trait for executing app-level effects.
///
/// Implementors of this trait perform the actual I/O operations described
/// by [`AppEffect`] values. This separation enables:
/// - **Testing**: Mock handlers can record effects without performing I/O
/// - **Batching**: Handlers can optimize by batching similar operations
/// - **Logging**: Handlers can log all operations for debugging
///
/// # Example
///
/// ```ignore
/// struct MockHandler {
/// effects: Vec<AppEffect>,
/// }
///
/// impl AppEffectHandler for MockHandler {
/// fn execute(&mut self, effect: AppEffect) -> AppEffectResult {
/// self.effects.push(effect.clone());
/// AppEffectResult::Ok
/// }
/// }
/// ```