docs: linking runtimes (peering) and the remote caller

[dlipicar]

Stacked on #98 (docs/runtime-process). Documents cross-instance module calls: logos-co/logos-peering, logos-co/logos-liblogos#230 and logos-co/logos-logoscore-cli (feat/peering).

• New §9.6 "Linking runtimes (peering)":

  • the peering section;
  • pairing by code, invite or local invite;
  • export, import and policy;
  • facades and their state;
  • what a provider module sees;
  • the provider's capability_module deciding every route from the remote policy (feat(engine): remote access decisions and caller scopes, for peering logos-capability-module#35);
  • Basecamp accepting pairing requests (Accept pairing for 5 min and its consent dialog, feat: Settings → Peering, linking Basecamp with other Logos runtimes logos-basecamp#440);
  • operating a daemon from another computer, on the spec's Remote Runtime Control (logos-lips runtime §9): runtime_control: true, peer invite --runtime-control, logosctl remote pair, and a remote policy that grants the client's logosctl consumer each core_service method (and the target method of a forwarded call); "*" covers user modules only and never core_service.

• Caller identity: the Remote{peer, name} arm, in C++ (isRemote()) and Rust; the operator @peer:<runtime id>:<consumer> a remote client's forwarded call arrives as.

• §6.1: logos_host_remote and LOGOS_HOST_REMOTE_PATH.

• CLI summary: logosctl peer. peer and remote exist only in the logosctl binary, so §9.6 uses logosctl throughout.

• §6.1, placement: "single_process": true, for a deployment with no other processes: every module runs in the runtime's process or does not load, and peering_module, peering_identity and each import's facade run there too (feat: peering — imports as facades, exports on tls_tcp logos-liblogos#230).

🤖 Generated with Claude Code