Files
OmniRoute/tests/unit/route-guard-private-lan.test.ts
KooshaPari f657c7865a feat(issue-agent): surface RecordedTriageTimeoutError as 504 (#7315)
* chore(ci): add .mergify.yml to main — Mergify only reads config from the default branch (#7168)

* feat: scaffold issue agent and router eval provenance

* feat: wire recorded issue triage runner

* feat: ingest recorded issue context

* feat: persist issue agent audit log

* feat: import recorded github issue exports

* docs: document issue agent env toggle

* fix(issue-agent): validate run requests

* fix(ci): add the auto-enqueue pull_request_rule to the Mergify config (queue_conditions alone are eligibility-only) (#7179)

* fix: validate issue agent run requests

* docs: add issue agent execution traceability

* feat(issue-agent): route recorded triage through chat

* test(issue-agent): verify recorded triage through chat route

* docs(issue-agent): add executable triage session artifacts

* fix(ci): migrate Mergify auto-enqueue to merge_protections_settings.auto_merge_conditions (rules-based path is EOL 2026-07-16) (#7216)

* fix(ci): drop Mergify batch settings (batching is a paid-tier feature; free plan queue is serial) (#7220)

* feat(issue-agent): surface RecordedTriageTimeoutError as 504

When the recorded-triage chat completion times out, the AbortController
fires an AbortError that previously surfaced as a generic 400 to the
caller. This change:

  * Adds a `RecordedTriageTimeoutError` that wraps the AbortError
    with the timeoutMs context.
  * Re-throws it from `executeRecordedTriageChatCompletion` so the
    caller can distinguish timeouts from other failures.
  * In the runs route, catches it and returns a 504 with code
    `ISSUE_AGENT_TIMEOUT` so clients can render a useful error.

Tests:
  * issue-agent-execution.test.ts        — verifies the typed error
  * issue-agent-route-execution.test.ts  — covers timeout path
  * issue-agent-runs-route.test.ts       — verifies 504 mapping

* fix(ci): merge queue tolerates the advisory dast-smoke failure (its GH-hosted build hang dequeued every attempt) (#7225)

* test(ci): make the #6634 selfref guard hermetic — main's copy hard-fails every PR (#7341)

main's copy of this test still does git I/O inside a unit test:

    const baseSrc = git(['show', 'origin/main:' + FILE]);

Runners check out a shallow single ref, so origin/main does not resolve and the
test dies with 'fatal: invalid object name origin/main'. Every PR into main
fails Unit Tests (7/8) on it — today that is #7313, #7315, #7316, #7334, #7336
and #7337, six PRs red on a defect none of them introduced. #7313 has no other
red at all.

release/v3.8.49 already carries a fix (2e42b8efc, #7174: try/catch, fetch
origin/main on demand, t.skip() when unreachable), but it only reaches main at
release time — so main stays broken for the whole cycle. Cherry-picking it would
also import a new problem: PR Test Policy classifies t.skip() as a silenced
assertion, which we watched it correctly catch on #7300 today.

This is the hermetic version instead (ported from #7327, which does the same for
the release branch): read the file straight off disk, compare against an empty
base so baseTaut/baseExtTaut are 0 — the strictest possible comparison point —
and call evaluateMasking() directly. No git ref, no fetch, no skip, nothing the
runner's checkout depth can break.

The #6634 regression stays covered: the guard's logic lives in
SELF_TEST_FIXTURE_RE (check-test-masking.mjs:337), not in the test. Proven both
ways on main before committing — neutralise SELF_TEST_FIXTURE_RE to /$^/ and
the test FAILS; restore it and it passes 2/2, with check-test-masking.mjs left
byte-identical.

Co-authored-by: growab <nekron@icloud.com>

* chore(quality): tighten main's coverage baseline to the CI's real numbers (#7347)

main's ratchet had been failing --require-tighten on every PR: 11 metrics
improved but the baseline was never tightened. Same class as the #6634
selfref guard — an infra fix that lands only on the release branch leaves
main red for the whole cycle, and every PR into main pays for it.

Values are the merged-coverage numbers from a run on main itself (a local
run measures ~68% vs CI's ~80%; the baseline's own note warns about that
gap). Only the 11 coverage values change — gitleaks and semgrepFindings
keep main's own state.

No changelog fragment: #7326 carries it on release/v3.8.49, and a second
one here would double the entry at release time.

* fix(issue-agent): dryRun-explicit test fixture + sanitize the generic error catch

Two independent Hard Rule #12/#18 fixes on the recorded-triage runs route:

1. tests/unit/issue-agent-route-execution.test.ts's "preserves the normal
   chat route provider failure response" test omitted dryRun from its
   request body. createRecordedTriageRun() computes `dryRun: input.dryRun
   !== false`, so an omitted dryRun defaults to true (dry-run mode) and the
   route returns the deterministic dry-run summary WITHOUT ever calling
   executeRecordedTriageChatCompletion() -- the mocked 429 fetch was never
   invoked, so the test always observed the 200 dry-run response instead.
   Add the missing `dryRun: false`, matching the sibling test above it. The
   normal chat-completions route also enriches upstream errors with a
   "[provider/model] [status]:" prefix and a connection-cooldown hint
   (RESILIENCE_GUIDE.md) rather than passing them through byte-for-byte, so
   the assertion now checks the original message survives (status +
   substring) instead of exact-matching the mocked JSON shape.

2. src/app/api/issue-agent/runs/route.ts's generic (non-timeout) catch
   returned raw `error.message` straight to the client. Validation failures
   thrown by this module (bad issue URL, malformed GitHub export) are safe,
   curated messages -- but appendIssueAgentAuditRecord()'s mkdir/appendFile
   under DATA_DIR can throw a real Node fs error (ENOENT/EACCES/EEXIST, ...)
   whose raw `.message` embeds the server's absolute filesystem path. Add
   isNodeSystemError() (keys off NodeJS.ErrnoException's `.code`, which only
   Node's own fs/system errors set) to replace that class of error with a
   generic message, and route everything else through sanitizeErrorMessage()
   per Hard Rule #12. Add a regression test that forces a real audit-write
   failure (pre-creating a file where audit.ts expects to mkdir) and asserts
   the response contains neither the errno code nor the DATA_DIR path.

Co-authored-by: diegosouzapw <8016841+diegosouzapw@users.noreply.github.com>

---------

Co-authored-by: Diego Rodrigues de Sa e Souza <8016841+diegosouzapw@users.noreply.github.com>
Co-authored-by: KooshaPari <koosha@example.com>
Co-authored-by: growab <nekron@icloud.com>
2026-07-18 15:13:35 -03:00

136 lines
5.4 KiB
TypeScript

import test from "node:test";
import assert from "node:assert/strict";
import { readFileSync } from "node:fs";
import { join } from "node:path";
import {
isPrivateLanHost,
isLoopbackHost,
isLocalOnlyPath,
classifyHostLocality,
} from "../../src/server/authz/routeGuard.ts";
import { resolveStampedPeer } from "../../src/server/authz/peerStamp.ts";
test("isPrivateLanHost: accepts RFC1918 IPv4 (incl. :port and ::ffff: mapped)", () => {
for (const h of [
"192.168.0.15",
"192.168.0.15:54321",
"10.0.0.5",
"172.16.0.9",
"172.31.255.254",
"::ffff:192.168.1.20",
]) {
assert.equal(isPrivateLanHost(h), true, `expected private-LAN: ${h}`);
}
});
test("isPrivateLanHost: accepts Tailscale CGNAT IPv4 range", () => {
for (const h of [
"100.64.0.1",
"100.96.135.160",
"100.127.255.254",
"100.96.135.160:20128",
"::ffff:100.96.135.160",
]) {
assert.equal(isPrivateLanHost(h), true, `expected Tailscale LAN: ${h}`);
}
});
test("isPrivateLanHost: accepts IPv6 ULA / link-local", () => {
assert.equal(isPrivateLanHost("fd12:3456::1"), true);
assert.equal(isPrivateLanHost("fe80::1"), true);
});
test("isPrivateLanHost: rejects public IPs, loopback and junk", () => {
for (const h of [
"8.8.8.8",
"69.164.221.35", // public VPS
"100.63.255.255", // just outside Tailscale 100.64/10
"100.128.0.1", // just outside Tailscale 100.64/10
"172.32.0.1", // just outside 172.16/12
"127.0.0.1",
"::1",
"example.com",
"",
null,
]) {
assert.equal(isPrivateLanHost(h), false, `expected NOT private-LAN: ${h}`);
}
});
test("isLoopbackHost: IPv4, hostname:port, bracketed + bare IPv6, ::ffff: mapped", () => {
assert.equal(isLoopbackHost("127.0.0.1"), true);
assert.equal(isLoopbackHost("localhost:20128"), true);
// Bare IPv6 loopback forms that socket.remoteAddress produces on dual-stack
// (regression: split(":")[0] previously mangled these to "" → false → DoS).
assert.equal(isLoopbackHost("::1"), true);
assert.equal(isLoopbackHost("::ffff:127.0.0.1"), true);
assert.equal(isLoopbackHost("[::1]:20128"), true);
assert.equal(isLoopbackHost("192.168.0.15"), false);
assert.equal(isLoopbackHost("8.8.8.8"), false);
});
test("classifyHostLocality: loopback / lan / remote, with fail-closed null", () => {
assert.equal(classifyHostLocality("127.0.0.1"), "loopback");
assert.equal(classifyHostLocality("::1"), "loopback");
assert.equal(classifyHostLocality("::ffff:127.0.0.1"), "loopback");
assert.equal(classifyHostLocality("192.168.0.15"), "lan");
assert.equal(classifyHostLocality("::ffff:192.168.1.20"), "lan");
assert.equal(classifyHostLocality("8.8.8.8"), "remote");
assert.equal(classifyHostLocality("69.164.221.35"), "remote");
assert.equal(classifyHostLocality(null), "remote", "unknown peer must fail closed");
});
test("services + traffic-inspector remain LOCAL_ONLY paths", () => {
assert.equal(isLocalOnlyPath("/api/services/9router/status"), true);
assert.equal(isLocalOnlyPath("/api/tools/traffic-inspector/sessions"), true);
});
test("issue-agent routes are LOCAL_ONLY by default", () => {
assert.equal(isLocalOnlyPath("/api/issue-agent/runs"), true);
assert.equal(isLocalOnlyPath("/api/issue-agent/runs/recorded-triage"), true);
});
test("management policy must NOT derive locality from the spoofable Host header", () => {
const src = readFileSync(
join(import.meta.dirname, "../../src/server/authz/policies/management.ts"),
"utf8"
);
// Regression guard: a prior fix read the client-controlled Host header for the
// LOCAL_ONLY decision, letting `Host: 127.0.0.1` bypass the gate. Locality must
// come from the token-stamped peer IP instead.
assert.ok(
!src.includes('get?.("host")') && !src.includes('get("host")'),
"requestPeerAddress must NOT read the Host header"
);
assert.ok(
src.includes("resolveStampedPeer") && src.includes("PEER_IP_HEADER"),
"requestPeerAddress must resolve the trusted token-stamped peer IP"
);
});
// ── resolveStampedPeer: the auth boundary that replaces Host-header trust ──
const TOK = "process-secret-token-abc";
test("resolveStampedPeer: returns the IP only for a correctly-tokened stamp", () => {
assert.equal(resolveStampedPeer(`${TOK}|127.0.0.1`, TOK), "127.0.0.1");
assert.equal(resolveStampedPeer(`${TOK}|192.168.0.15`, TOK), "192.168.0.15");
assert.equal(resolveStampedPeer(`${TOK}|::1`, TOK), "::1");
assert.equal(resolveStampedPeer(`${TOK}|::ffff:192.168.1.20`, TOK), "::ffff:192.168.1.20");
});
test("resolveStampedPeer: rejects forged token, missing token, no separator, empty ip", () => {
assert.equal(resolveStampedPeer("wrong-token|127.0.0.1", TOK), null, "forged token");
assert.equal(resolveStampedPeer(`${TOK}|127.0.0.1`, undefined), null, "no process token");
assert.equal(resolveStampedPeer("127.0.0.1", TOK), null, "no separator (raw client value)");
assert.equal(resolveStampedPeer(`${TOK}|`, TOK), null, "empty ip");
assert.equal(resolveStampedPeer("|127.0.0.1", TOK), null, "empty token segment");
assert.equal(resolveStampedPeer(null, TOK), null, "absent header");
assert.equal(resolveStampedPeer("", TOK), null, "empty header");
});
test("resolveStampedPeer: a spoofed Host-style value cannot pass without the token", () => {
// Simulates a remote attacker who knows the header name but not the secret.
assert.equal(resolveStampedPeer("127.0.0.1|127.0.0.1", TOK), null);
assert.equal(resolveStampedPeer("anything|127.0.0.1", TOK), null);
});