l0ng-ai c396e85e0c docs(skill): launch workers interactively and wait on --changed ...

The taught loop started its worker with `claude -p`, but headless print
mode never stops to ask, so the `waiting` state steps 3-4 are built on
could not arrive. Step 2 now launches interactively.

Every wait after a send passes `--changed`, with the reason spelled out:
without it the loop re-reads the state it just walked in on. The exit-1
"worker died" branch is documented too, and both guards are asserted in
the skill-content test.

Also gives the install round-trip test a Drop guard, so a panic cannot
leave `CLAUDE_CONFIG_DIR` set for whatever runs next in the process.

2026-08-02 09:49:59 +08:00

..

features.md

docs(skill): launch workers interactively and wait on --changed

2026-08-02 09:49:59 +08:00

features.zh-CN.md

docs(skill): launch workers interactively and wait on --changed

2026-08-02 09:49:59 +08:00