Repository navigation
Commit 321baf5
committed
docs(agents): narrow lookup rule to copied state
The staleness problem is specific to a lookup that carries another
object's content into the rendered output; a lookup whose repeated
render is identical, such as a guard or keeping a generated Secret,
cannot go stale, and banning it pushed agents toward nothing better.
The testing caveat held only for runs without a kubernetesProvider
mock, and the alternatives now name the mechanisms the tree already
has, so an agent can reach for them instead of a new lookup.
Assisted-by: LLM
Signed-off-by: Timofei Larkin <[email protected]>1 parent 648dcd2 commit 321baf5
2 files changed
Lines changed: 4 additions & 4 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
28 | 28 | | |
29 | 29 | | |
30 | 30 | | |
31 | | - | |
| 31 | + | |
32 | 32 | | |
33 | 33 | | |
34 | 34 | | |
| |||
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
118 | 118 | | |
119 | 119 | | |
120 | 120 | | |
121 | | - | |
| 121 | + | |
122 | 122 | | |
123 | | - | |
| 123 | + | |
124 | 124 | | |
125 | | - | |
| 125 | + | |
126 | 126 | | |
127 | 127 | | |
128 | 128 | | |
| |||
0 commit comments