Host session registers its tools without borrowing an app peer's token #146

The system agent's terminal.run (ADR 0004 §12, #132's command-execution switch, wired in #145) is registered on the host's own session with peer/tools/register without peer (octos#2567). Today the shell has no host credential of its own for that call, so it borrows an existing app peer's host token. Until any app peer exists, terminal.run can't be registered, and the system chat says so.

Wanted: the host session registers its tools with its own credential, independent of app peers.

• Either the kernel accepts the host token itself for host-session registration, or the shell keeps a host-session credential from serve --host-managed / its kernel start.
• Registration happens at kernel start and after every reconnect, like the app peers' registration in Shell side of octos#2567: host tools, relay, peer/input, terminal.run on #system (ADR 0004) #145.
• Register only while the command-execution switch is on, withdraw when it turns off, and never offer it on external (Talk to Octos) sessions.

Where:

• crates/shell/src/host_tools/: the system-session registration from Shell side of octos#2567: host tools, relay, peer/input, terminal.run on #system (ADR 0004) #145;
• crates/kernel (system_tools, launch);
• octos UPCR-2026-035's host-session registration.

Test: with no app peer running, turning the switch on registers terminal.run on _main:api:octosense#system, and a system-agent turn is offered it.

🤖 Generated with Claude Code