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
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
//! [`Filesystem`] trait, its supporting value types, and the
//! [`FsError`] variant set every implementation produces.
use ;
use Snafu;
/// Failure modes shared by every [`Filesystem`] method.
///
/// Each variant prefixes its `Display` impl with strong-LTR ASCII
/// text before any path field, matching the path-rendering rule in
/// `docs/spec/06-paths.md`.
/// Kind of a filesystem entry.
///
/// Exhaustively enumerates the seven entry kinds POSIX defines (the
/// `S_IF*` bits in `st_mode`). Implementations targeting platforms
/// that cannot produce a given variant simply never return it; for
/// example, [`StdFilesystem`](crate::std_impl::StdFilesystem) on
/// Windows only produces [`EntryKind::Dir`], [`EntryKind::File`], and
/// [`EntryKind::Symlink`], and reports any non-symlink reparse point
/// as [`FsError::UnknownEntryKind`].
/// Lightweight metadata about a filesystem entry.
///
/// Carries the entry's kind and its byte size. Timestamps and
/// permissions remain out of scope for this trait; callers needing
/// permission bits for restoration use the manifest format
/// (`CACHE-011`) rather than re-querying the host.
///
/// `size` is the regular-file byte length on real filesystems
/// (`std::fs::Metadata::len()`). For non-file kinds the value is
/// implementation-defined on real filesystems (often the inode
/// size on Unix); the in-memory backend reports zero. Cache code
/// only consults `size` when [`Self::kind`] is
/// [`EntryKind::File`], so non-file values do not enter any
/// normative check.
/// One entry returned by [`Filesystem::read_dir`].
///
/// Carries both the absolute path of the entry and the entry's
/// metadata (without following symlinks), so callers can classify
/// directory contents without issuing a second `stat` per entry.
/// Abstract filesystem used by all of `haz-discovery`.
///
/// Implementations MUST require absolute paths on every method and
/// return [`FsError::NotAbsolute`] when given a relative one.
/// Implementations MUST follow the symlink semantics documented on
/// each method.
///
/// The trait is deliberately minimal. It exposes only the
/// operations that workspace-root walking, glob expansion, and
/// `*.yml` loading need. Future phases that require additional
/// operations (write access for the cache, file-watching for
/// incremental rebuilds) SHOULD introduce dedicated traits rather
/// than extending this one.
/// Mutating operations needed by callers that persist state on the
/// filesystem (today: the cache layer in `haz-cache`).
///
/// Kept as a sibling sub-trait of [`Filesystem`] rather than folded
/// into it: most callers (workspace discovery, configuration
/// parsing) only need reads, and a smaller surface is easier to
/// reason about. Implementations of this trait MUST also implement
/// [`Filesystem`], so a single handle covers both read and write
/// concerns for callers that need them.
///
/// Methods take `&self`, mirroring [`Filesystem`]. Implementations
/// that need to mutate internal state (e.g. an in-memory backend)
/// MUST use interior mutability.
///
/// Path semantics: every method requires absolute paths and returns
/// [`FsError::NotAbsolute`] for relative inputs, matching
/// [`Filesystem`]'s convention.
///
/// Overwrite semantics: [`Self::write_file`] and [`Self::rename`]
/// MAY replace an existing entry. Callers that need fail-on-exists
/// semantics are responsible for pre-checking; the trait does not
/// offer it because the cache's two-phase store (write fresh files
/// in a tmp dir, then [`Self::rename`] into place) does not need
/// it.
///
/// Durability semantics: [`Self::write_file`] and [`Self::rename`]
/// are NOT durable on their own. Callers that need durability
/// across power loss MUST follow them with [`Self::fsync_file`]
/// (for the written file) and/or [`Self::fsync_dir`] (for the
/// parent directory of a renamed entry). On in-memory backends the
/// fsync methods are no-ops.