docs: the runtime runs in a process of its own

[dlipicar]

The developer guide follows the runtime into a process of its own. Stacked on #97 (docs/drop-legacy-mode).

logoscore and Basecamp now spawn logos_runtime, which holds capability_module and every module's credential (logos-co/logos-liblogos#229, logos-co/logos-logoscore-cli#148, logos-co/logos-basecamp#439). The guide said otherwise in four places:

• §6.1: the daemon's capability_module "runs in its process". It now runs in logos_runtime, and the daemon holds no credential but its own.
• §6.1, running plain modules in-process: this is now the runtime's process, not the daemon's. An in-process module shares the runtime's fate (a crash takes every module down), so the bar is trusting it as much as the runtime. The package modules never run there, whatever the policy says. logos_runtime is found beside logoscore or at LOGOS_RUNTIME_PATH.
• The CLI reference's comment on --placement.
• Troubleshooting: Basecamp's capability_module runs inside logos_runtime, not inside the app.

No executable spec pins any of this, so nothing is regenerated.

🤖 Generated with Claude Code