[edgehero]

Part 4 of 4 for #712. Parts 1 to 3 (#722, #724 and #723) are merged.

What changes

• OpenShell facts on the run record. On the two openshell venues, the record gains openshell: { mode, ruleHosts, ruleHostCount, providers, placeholders }.

  • The rule hosts are the generated policy's endpoints: the egress allowlist, the model endpoints and the fixed forge host. That is operator config, never repository or payload text, so the record stays PII-free.
  • Hosts must fit a host-name charset. At most 32 are listed, and the total is always kept.
  • No values appear.

• The secrets profile on the run record. The record gains secretsProfile: the name of the profile a run's secrets resolved through.

• Run views. The console run page and the panel's run detail show the sandbox policy, its rule hosts and the secrets profile.

• MCP connection state. It is recorded nowhere, so no row claims it.

• A "Secret profiles in use" view, in the console, the panel and /dispatch secrets list. For each profile it shows:

  • its source;
  • where an overlay resolver stands against PI_SECRET_RESOLVER_ROOTS;
  • the triggers and projects that use it;
  • its last resolve;
  • the live hosts that advertise it.

  The view never shows a path. A refusal whose reason the project bundle's read shares is worded as either read.

• One rule for resolver roots. resolverRootsStatus is the single roots rule. The add's pre-confirm check reads it and stays strict on a bad seam.

• Model context. dispatch_runs carries the openshell counts, plus host names only for a run read by id. It never carries resolver paths.

• Conformance lanes. Through buildRecord, they check the exact facts of a real bundle run:

  • copy mode: 2 providers and 4 placeholders;
  • bind mode: 2 and 2;
  • the host set as networkPolicyFor derives it.

Specs

• Amended: INT-RUN-HISTORY-FILE-CONTRACT (openshell and secretsProfile), DES-OPENSHELL-VENUE, DES-OPERATOR-CONSOLE, REQ-TRIGGER-SECRETS and REQ-OPERATOR-CONSOLE-SCREENS (g).

Residuals

• One realpathSync per overlay profile per snapshot. Bounded by the size of the overlay.
• The bundles view still judges resolver roots lexically. It comes from Project secret bundles: grant a project's env once, shared by every job, any manager or none #704 and feat(admin): project secret bundles in the console, the panel and /dispatch secrets (#704) #721; this view uses the realpath, so a follow-up is needed.

Verification

• Review: two adversarial rounds, with every finding fixed.
• Full suite with Valkey: 9658 tests; only the known macOS mcp test and two timing tests failed.
• Build and checks: node admin/build.mjs succeeds. The revision-row, test-count, temp-dir and dated-fixture checks pass.