Merge branch 'main' of git.arirex.me:iris/ai-app

This commit is contained in:
iris committed 2026-08-30 18:41:25 -04:00
commit 28b2e67a38
1 file changed
+11
+11
View File
@@ -238,6 +238,17 @@ first if a remote spawn ever mangles an argument.
faults live entirely in what the app does *while* one is outstanding. On faults live entirely in what the app does *while* one is outstanding. On
a loopback server those windows close before anything can be observed, a loopback server those windows close before anything can be observed,
so the bug looks like it is not there. so the bug looks like it is not there.
- **A fake CLI exercises the process lifecycle without a token.** Point a
`claude_cli` provider's `command` at a two-line script — `#!/bin/sh` and
`cat > /dev/null` — and it behaves the way the lifecycle code cares
about: it holds the fifo open, records a real pid, writes nothing, and
dies on a signal. So adopt, stop, restart and start are all drivable
without a real `--resume` and without spending a turn on somebody's
account. Sibling to `debug-transcript.sh`, and the two cover different
halves: reach for this when what is under test is *whether a process is
running*, and for the script when it is *what the transcript draws*.
(From the ai-app-2 session, 2026-08-30, which found a clock bug with it
that the tests did not have.)
- Prefer exercising the server directly over going through the UI: - Prefer exercising the server directly over going through the UI:
`curl --cacert ~/.config/ai-app/certs/ca.pem -H "Authorization: Bearer …" https://127.0.0.1:8443/sessions`. `curl --cacert ~/.config/ai-app/certs/ca.pem -H "Authorization: Bearer …" https://127.0.0.1:8443/sessions`.
The CA is wherever `--certs` put it — by default under The CA is wherever `--certs` put it — by default under