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
//! The register of verbs that destroy, and the one rule they all obey.
//!
//! # Why a register instead of two guards
//!
//! `cache clear` learned Explicit Target Designation on 2026-08-10 and the same
//! plan said `config init --force` would learn it too. Only the first was built.
//! The gap was not the missing guard — it was that nothing could tell the guard
//! was missing, because the rule lived inside one `match` arm and could not be
//! asked a question. A second destructive verb shipped without a waiver and every
//! gate agreed with the tree.
//!
//! So the rule moved here. The runtime reads this list to decide whether to
//! refuse, and `tests/policy/etd.rs` reads the same list to demand a waiver flag,
//! a `target_source` in the schema, and a line in both configuration references.
//! A third verb that destroys is either in this list or the class gate fails; it
//! cannot be quietly correct the way `config init --force` was.
//!
//! # What counts as designation
//!
//! Naming the directory in argv designates it. Passing the waiver accepts an
//! ambient one on purpose. Passing neither means the caller never saw the path
//! about to be destroyed, which is the confused-deputy shape: the caller names
//! the verb, the environment names the victim, and nothing compares the two.
use cratePathSource;
use crate;
/// One verb that destroys, with everything needed to refuse it safely.
/// `cache clear` empties every cached body under the resolved cache root.
pub const CACHE_CLEAR: DestructiveVerb = DestructiveVerb ;
/// `config init --force` replaces an existing `config.toml` in place.
///
/// The waiver is required whenever the target is ambient, even where no file
/// exists yet. The caller cannot know in advance whether a directory they never
/// named holds a file, and that uncertainty is precisely the risk: a rule whose
/// answer depends on the state of the disk gives the same argv two behaviours.
pub const CONFIG_INIT_FORCE: DestructiveVerb = DestructiveVerb ;
/// Every verb in this binary that destroys something it did not create.
///
/// This is the list the class gate reads. Adding a destructive verb without
/// adding it here fails `no_verb_that_destroys_escapes_the_register`.
pub const