Distillation

Date: Sep 9, 2026

• 🔴 (10:10) User stated the fetch interceptor must never intercept requests already going to the gateway; /home/byk/Code/opencode-lore/packages/core/src/fetch-interceptor.ts lines 471-481 still pass their headers to observeRequestHeaders() so in-process extensions can scope side-channel requests, then call the original fetch.
• 🔴 (10:10) User stated the fetch interceptor must never intercept local requests because they could target a local LLM or the gateway itself; /home/byk/Code/opencode-lore/packages/core/src/fetch-interceptor.ts lines 484-493 bypass hosts localhost, 127.0.0.1, 0.0.0.0, ::1, and [::1].
• 🔴 (10:10) /home/byk/Code/opencode-lore/packages/core/src/fetch-interceptor.ts’s installFetchInterceptor(config) uses a process-shared original-fetch slot to prevent double installation across multiple copies of the module; if the slot is non-null, it returns a no-op cleanup to avoid interceptor-chain corruption and the infinite-loop shape guarded by issue #1027.
• 🔴 (10:10) installFetchInterceptor() stores globalThis.fetch, pre-parses config.gatewayBase, and fast-bypasses URL parsing unless the URL contains /messages, /completions, or /responses; malformed URLs also use the original fetch.
• 🔴 (10:11) For an LLM-looking path that cannot be intercepted because its body is absent or unrecognized, /home/byk/Code/opencode-lore/packages/core/src/fetch-interceptor.ts warns only once per ${upstream.host}${upstream.pathname} via warnedPaths, then bypasses the Lore gateway.
• 🔴 (10:11) installFetchInterceptor() preserves extra properties from the original fetch, such as newer Node.js preconnect, by assigning globalThis.fetch = Object.assign(interceptor, originalFetch); cleanup restores originalFetch and clears the shared slot with writeOriginalFetchSlot(null).
• 🔴 (10:12) /home/byk/Code/opencode-lore/packages/gateway/src/portfile.ts stores runtime gateway discovery data in ~/.local/share/lore/gateway.port; clean shutdown removes it, while stale crash artifacts are harmless because plugins probe /health and ignore unresponsive ports.
• 🔴 (10:12) GatewayPortRecord has exact fields version: 1, port: number, and token: string; valid ports are safe integers from 1 through 65535, and valid tokens have lengths from 32 through 256.
• 🔴 (10:12) writePortFile(port, token?) supports a legacy plain-port format when token === undefined; with a token it validates both fields and atomically writes ${JSON.stringify({ version: 1, port, token })}\n, throwing Invalid gateway port record for invalid data.
• 🔴 (10:12) removePortFile(expectedPort, expectedToken?) atomically claims gateway.port by renaming it to .gateway.port.cleanup-${process.pid}-${randomBytes(8).toString("hex")}; it deletes only a matching generation, supports matching legacy plain-port records when no token is expected, and otherwise attempts to restore the displaced record with linkSync(). If restoration encounters EEXIST, it retains the displaced unknown generation as a recovery artifact.
• 🔴 (10:12) readPortFile() accepts either valid versioned JSON or a valid legacy integer port and returns null on invalid or unreadable data; strict inspectPortFile(runtimeName = PORTFILE_NAME) instead distinguishes { state: "absent" }, { state: "valid", record }, and { state: "invalid", reason }, reading with { ownerOnly: true }.
• 🔴 (10:12) /home/byk/Code/opencode-lore/packages/gateway/test/shutdown-active-stream.test.ts verifies that authenticated shutdown remains bounded when a socket sends incomplete HTTP headers: the test uses shutdownDeadlineMs: 75, calls requestGatewayShutdown(record, 500), expects "accepted", requires shutdown settlement within 500 ms, confirms the socket is destroyed and the process record removed, and confirms handle.shutdown() resolves.
• 🔴 (10:12) The non-settling authenticated-control teardown test starts the gateway with { port: 0, local: true, quiet: true, processBoundary: true }, uses both server and process-controller deadlines of 20 ms, blocks resetPipelineState, and expects forced exit code 1; forcedExit(1) runs, safeExit does not run, and reset is invoked exactly once.
• 🔴 (10:12) User stated teardown in the forced-exit test never reached safe closure; therefore live-generation evidence remains and processRecord must still equal the original record rather than being removed.
• 🔴 (10:12) /home/byk/Code/opencode-lore/packages/gateway/test/shutdown-active-stream.test.ts asserts that a concurrent signal/control shutdown request shares the existing teardown attempt: handle.processShutdown?.(143) must not cause resetPipelineState to run more than once.