docs: name the two daemon-spawning forms in update-felis #174

Merged

natsukium merged 1 commit from docs/update-felis-autospawn-160 into main

2026-09-07 15:18:07 +09:00

natsukium commented

2026-09-07 13:24:52 +09:00

Owner

Fixes #160.

docs/how-to/update-felis.md claimed that "the next window launch or headless command (such as felis sessions spawn)" restarts the daemon after felis daemon stop. Under the auto-spawn policy, only two forms spawn a daemon: a
window launch and felis sessions spawn. The sentence now names those two forms, states what the other headless verbs
do instead (unreachable vs. "not running"), and links the full table in docs/reference/cli.md#auto-spawning.

Doc cascade: how-to only. The normative table already lives in docs/reference/cli.md#auto-spawning (landed by #141),
so the how-to links it rather than restating it; no explanation, skill, or code mirror states the old claim.

Verified: just check green (fmt, clippy, nextest, deny, proto-compat); reviewed by pi sol + pi luna; docs proofread by
Gemini gemini-3.8-flash-high

Deferred

Spelling out that felis version and felis doctor report the daemon as "not running" rather than exiting 2 — the
how-to only needs the spawn/no-spawn distinction; the exact non-spawning outcomes are reference material already
tabulated in docs/reference/cli.md#auto-spawning, which the sentence now links.

Fixes #160. `docs/how-to/update-felis.md` claimed that "the next window launch or headless command (such as `felis sessions spawn`)" restarts the daemon after `felis daemon stop`. Under the auto-spawn policy, only two forms spawn a daemon: a window launch and `felis sessions spawn`. The sentence now names those two forms, states what the other headless verbs do instead (unreachable vs. "not running"), and links the full table in `docs/reference/cli.md#auto-spawning`. Doc cascade: how-to only. The normative table already lives in `docs/reference/cli.md#auto-spawning` (landed by #141), so the how-to links it rather than restating it; no explanation, skill, or code mirror states the old claim. Verified: just check green (fmt, clippy, nextest, deny, proto-compat); reviewed by pi sol + pi luna; docs proofread by Gemini gemini-3.8-flash-high ## Deferred - Spelling out that `felis version` and `felis doctor` report the daemon as "not running" rather than exiting 2 — the how-to only needs the spawn/no-spawn distinction; the exact non-spawning outcomes are reference material already tabulated in `docs/reference/cli.md#auto-spawning`, which the sentence now links.

natsukium added 1 commit

2026-09-07 13:24:52 +09:00

docs: name the two daemon-spawning forms in update-felis

pr / nix flake check (pull_request) Successful in 23s

Details

pr / cargo build / clippy / test / deny (pull_request) Successful in 1m34s

Details

pr / wire schema is compatible with the base (pull_request) Successful in 13s

Details

pr / frontend smoke (x86_64-linux) (pull_request) Successful in 50s

Details

pr / publish felis (x86_64-linux) (pull_request) Has been skipped

Details

c4b7501318

The restart section claimed that any headless command starts a stopped
daemon, with `sessions spawn` as one example. Only `sessions spawn` and
window launches spawn; the rest report the daemon unreachable, or, for
`version` and `doctor`, not running, so a reader following the old
wording would expect `daemon status` to resurrect the daemon after
`daemon stop`.

Refs #160

natsukium merged commit af9d98d79f into main

2026-09-07 15:18:07 +09:00

natsukium deleted branch docs/update-felis-autospawn-160

2026-09-07 15:18:08 +09:00

natsukium referenced this pull request from a commit

2026-09-07 15:18:08 +09:00

docs: name the two daemon-spawning forms in update-felis (#174)