@songyang0603/dsh-codex-execpolicy

Codex execpolicy semantics as a stateful DeepSeek Harness Cordis service, pinned to OpenAI Codex commit 086396f7f60347b74c82784d5dfaf4fb2d3bda12.

Status: 0.1.0 is parity_verified for the macOS arm64 source-component boundary. Runtime, config-stack, host-discovery, and persistence corpora match their independently built upstream oracles 68/68, 6/6, 11/11, and 16/16 respectively. This is not a whole-agent or multi-platform claim.

What this component owns

• Extended Starlark execpolicy parsing and rule ordering;
• Bash/sh/zsh lowering, compound-command splitting, safe/dangerous heuristics, and the pinned Windows PowerShell path;
• ExecApprovalRequirement derivation, including bypassSandbox, forbidden reasons, and transparent execpolicy amendment payloads;
• materialized ConfigLayerStack composition, requirements overlays, provenance, sorted rules/*.rules discovery, and parse-warning fallback;
• canonical local Codex host discovery through the pinned public config loader;
• startup banned-prefix migration before policy load;
• canonical $CODEX_HOME/rules/default.rules prefix/network persistence, locking, exact-line deduplication, and same-manager in-memory updates;
• compiled network allow/deny domain output.

The TypeScript layer does not interpret policy. It owns the DSH service lifecycle, a versioned JSONL process boundary, cancellation, strict response validation, backpressure, fail-closed teardown, and provenance handshake.

Install from this checkout

At repository root:

pnpm install
pnpm native:stage
pnpm --filter @songyang0603/dsh-codex-execpolicy build

Then add the package's DSH bundle to a profile:

dsh plugin --profile codex-dev add ./packages/execpolicy
dsh --profile codex-dev --dump-config

The shipped cordis.patch.yml mounts the package with canonical local host discovery: discovered CODEX_HOME, current cwd, no CLI overrides, and no online cloud bootstrap. Service activation performs the same pinned ordering as Codex: discover config, attempt the one-shot migration when applicable, then load policy and retain ownership of the canonical update path.