fix: retain resolved component paths

docs/wasm-runtime-architecture.md

@@ -375,6 +375,11 @@ header free-functions are `inline`. The wasm backend exposes only declarations
   old mutation handler, and verifies demand-priority convergence. A CLI request
   still waits and returns only the current dependency result after rebuild
   completion.
+  The component page also calls a parent once without its optional relative
+  child and again with that child activated. This guards the component-slot
+  cache invariant that a cache hit must restore both the function-table slot
+  and the resolved unit path; otherwise nested relative targets resolve from
+  the caller after a repeated parent invocation.
 
 - **WebSocket end-to-end**: a headless client performs a raw WS handshake to
   `:HTTP_PORT` with path `/site/tests/websockets.ws.uce` (self-resolving