diff options
| author | Craig Jennings <c@cjennings.net> | 2026-07-02 01:20:17 -0400 |
|---|---|---|
| committer | Craig Jennings <c@cjennings.net> | 2026-07-02 01:20:17 -0400 |
| commit | 8d790c0f5fd8d7841c92b6a4a9b56b64d945a795 (patch) | |
| tree | bb814338bdffecd2344e779e46a21b3d2276692f /scripts | |
| parent | 263138a696a62f8b4b81867f1fdb49f84dc79f02 (diff) | |
| download | rulesets-8d790c0f5fd8d7841c92b6a4a9b56b64d945a795.tar.gz rulesets-8d790c0f5fd8d7841c92b6a4a9b56b64d945a795.zip | |
feat(backlog): pin the commit-autonomy waiver and its degrade contract
The waiver is now a machine-read marker: ":COMMIT_AUTONOMY: yes" in notes.org's Workflow State, with ":LOOP_MAY_COMMIT: yes" as the separate grant for the unattended loop. An absent or non-yes marker reads as no, and the read is a fresh grep each run, never memory. A caller requesting autonomous-commit without the marker degrades to file-only, surfaced in both the run intro and the summary.
I stamped rulesets' own :COMMIT_AUTONOMY: and left :LOOP_MAY_COMMIT: ungranted. Letting the recurring loop commit unattended is a separate trust decision.
Diffstat (limited to 'scripts')
0 files changed, 0 insertions, 0 deletions