nx_chat_demo_api.nx

nx_chat_demo_api.nx -- the SAFE public front for a testable persistent-chat UI backed by C1's store. v2 (2026-08-16): does the append/fetch IN-PROCESS on the seg-store, NOT by forking nx_chat_store. WHY: MEASURED via curl to /mcp -- a list (read) returned in 44ms, but a post that FORKED nx_chat_store to write hung to the tools-daemon exec deadline (~14s) and returned empty (exit -5), because the write-path grandchild orphaned under the daemon's capture. A read fork was fine; a write fork was not. In-process removes the fork entirely: this organ takes the plane lock, appends, and releases in its own process -- the exact code path nx_chat_store's gate proves, just linked instead of exec'd. Fast + no orphan. SECURITY BOUNDARY unchanged: only post/list, rooms forced into demo_, inputs sanitized + capped, budgets from C1's conf refuse loudly. Destructive verbs do not exist here. REFEREE: nx_chat_demo_api_gate. DEBT (named, not a silent twin): the append/fetch logic is duplicated from nx_chat_store; the consolidation is to extract nx_chat_store_lib that BOTH this front and the CLI import (comms.plan chatstore-lib-extract). license_tier: ORIGINAL No hw writes (Rule 26).