10 keys, 0 of them read

ork’s plugin settings.json was discarded at load, every time, since v7.0.0.

The binary decides it, not the doc

Wmd = ["agent","subagentStatusLine"]
$_y = fullSettingsSchema.pick(Wmd).strip()
Jmd(e){ t=$_y().safeParse(e); r=t.data;
        if (Object.keys(r).length===0) return;   ◀ whole object discarded
        return r }

.strip() drops unknown keys silently and safeParse still succeeds, so the plugin loads clean with no diagnostic. An empty pick discards everything. ork declared neither supported key.

What was never loaded

key	size	status
env	14 vars	inert
permissions.deny	26 rules	inert — RETAINED
permissions.allow	6 rules	inert
sandbox	+19 domains	inert
keybindings, plansDirectory, respectGitignore, fileSuggestion, spinner×2	—	inert

The permissions block is kept byte-exact. Deleting an inert deny rule loses no enforcement, but it deletes the only written record that someone intended those paths denied. Inertness and coverage are independent arguments.

Adopting some of these would have been HARMFUL

key	what it would actually do
SUBPROCESS_ENV_SCRUB=1	forces permission mode to `default`, overriding --dangerously-skip-permissions and agent frontmatter
ORCHESTKIT_LOG_LEVEL=warn	read before CLAUDE_DEBUG ⇒ kills /debug
SCRIPT_CAPS="500"	malformed; CC wants an object ⇒ caps disabled
STREAM_IDLE_TIMEOUT_MS	180000 is below CC’s 300000 floor

The inertness has been protecting the estate, not merely wasting it.