JC·HARNESS

Known Gaps

Honest current-state disclosure from code-backed capability review, runtime credentials, and trust-boundary controls.

No Fake Completion

These gaps are not hidden behind optimistic UI states. A stage or integration is labeled implemented, server configured, operator checkpoint, unconfigured, missing, not executed, or planned based on real code and available configuration.

Consolidated findings.jsonl

implemented

The runner writes deterministic per-model findings.jsonl files and a top-level run findings.jsonl after report compilation.

Comparative scorecard rubric

implemented

lib/scoring.js implements vulnerability priority scoring. Web real-runs also persist scorecards derived from actual Hunt/Validate findings and token-cost evidence.

LLM router in runner loop

implemented

The web real-run path executes bounded passive recon plus AI Gateway Hunt/Validate work. The original CLI still supports supervised prompt-package operation.

Web/API trust boundary enforcement

implemented

validateScope rejects mismatched base URLs, disallowed hosts, private/link-local/metadata hosts outside lab mode, and non-http(s) targets before web dry-runs, real-runs, and reruns proceed.

CLI trust boundary preflight

operator checkpoint

The original CLI remains a supervised local operator workflow. It validates config and warns on trust boundaries, while active network controls stay in web/API scope validation and approved sandbox/job policy.

Docs, Sheets, Files publishing

server configured

Docs, Sheets, and Files publishing can use the server-side PLATPHORM_API_KEY only as a downstream credential. Browser-triggered delivery still needs explicit operator auth and downstream confirmation before it claims success.

Server PlatPhorm key

server configured

PLATPHORM_API_KEY is configured server-side. It enables protected downstream sends from the deployment without exposing the raw key to the browser.

Real-run automation

implemented

Real run creation is gated by PLATPHORM_API_KEY, responsible-use acceptance, scope validation, and typed AUTHORIZED confirmation. With AI Gateway credentials present, the run performs bounded passive recon, model Hunt/Validate work, finding persistence, and scorecard derivation.

Trust Boundary Controls

implemented

Blocked hosts

localhost, 127.0.0.1, 0.0.0.0, ::1, metadata.google.internal

Blocked ranges

10.0.0.0/8, 127.0.0.0/8, 169.254.0.0/16, 172.16.0.0/12, 192.168.0.0/16, 100.64.0.0/10

Enforced in

scope validation API, web dry-run creation, web real-run creation, rerun scope reconstruction

Web/API guarantee

Browser-created dry-runs, real-runs, reruns, and handoff payloads validate base URL, allowed hosts, protocol, and private-network exclusions before work is persisted or sent. Sandbox and BrowserOps handoffs use fixed PlatPhorm endpoints rather than arbitrary user-supplied fetch targets.

CLI boundary

The original Jean-Claude CLI remains a supervised local operator workflow. The web cockpit does not claim unattended CLI network enforcement beyond config validation, warnings, and the web/API scope controls.

Localhost, private, link-local, and metadata hosts are blocked unless labMode is explicitly true.