aboutsummaryrefslogtreecommitdiff
path: root/.ai
diff options
context:
space:
mode:
authorCraig Jennings <c@cjennings.net>2026-08-20 11:54:13 -0700
committerCraig Jennings <c@cjennings.net>2026-08-20 11:54:13 -0700
commitaa1660111f1073c52a0646e9e7e03987bddaa6c5 (patch)
treebe3314647a830f517f297254eeb71dc463d35003 /.ai
parent84b558ae0988ee0646c40a3f3020878fafbd2c63 (diff)
downloadrulesets-aa1660111f1073c52a0646e9e7e03987bddaa6c5.tar.gz
rulesets-aa1660111f1073c52a0646e9e7e03987bddaa6c5.zip
docs: file the PROCESSED sweep and two cross-project proposals
The sweep task carries the closing condition for the ladder change: when the fleet count reaches zero, the three transitional PROCESSED-* exclusions come out together. Left unwritten they become permanent, which rebuilds the hiding place the ladder change removed. Two proposals arrived while that work was in flight. Both are filed rather than applied, because each restructures a rules file rather than fixing a defect. One consolidates the shell gotchas under a single heading and adds the ssh BatchMode PATH case. The other names a class: a claim recorded while some condition holds, still reading as fact after the condition lapses. Three projects hit it in one day. My read is that it widens the host-identity rule rather than earning a second rule beside it. I also repaired a task whose source line pointed at an inbox file swept a month ago. That dangling reference is the worked example in the ladder commit.
Diffstat (limited to '.ai')
0 files changed, 0 insertions, 0 deletions