aboutsummaryrefslogtreecommitdiff
path: root/scripts/systemd/roam-sync.timer
diff options
context:
space:
mode:
authorCraig Jennings <c@cjennings.net>2026-06-14 22:07:00 -0500
committerCraig Jennings <c@cjennings.net>2026-06-14 22:07:00 -0500
commite0f914d510c081db45cafaf4fe5c8f7b65e46fec (patch)
tree8ad851aea65e0e5fc1b6adbc70355b435a4dde0d /scripts/systemd/roam-sync.timer
parent16e64fb5f81bd8c3eaa2dc4c00a796ddbec01441 (diff)
downloadrulesets-e0f914d510c081db45cafaf4fe5c8f7b65e46fec.tar.gz
rulesets-e0f914d510c081db45cafaf4fe5c8f7b65e46fec.zip
docs(ai): require an epoch on the tail of helper-agent ids
A helper agent's session-context file is .ai/session-context.d/<id>.org. A bare, reused id like "codex" makes the next run resolve to the previous run's leftover anchor, which it then mistakes for a crash to recover or clobbers. That bit on 2026-06-13: a codex run left codex.org for the next session to clean up. The fix is a convention, not a resolver change. The spawner appends an epoch on the tail (host.project.runtime.<epoch>) so each run gets a fresh anchor. The epoch can't be minted inside session-context-path, since that resolver runs many times per session and must return the same path each call. I documented it in protocols.org, the wrap-up recommended-shape note, and the resolver header.
Diffstat (limited to 'scripts/systemd/roam-sync.timer')
0 files changed, 0 insertions, 0 deletions