Place the trust checks before the command can change a record

Edit boundary-plan.json. trustedKeys is the current key-pin set. steps is a unique ordered subset of schema, signature, scope, permission, dispatch. failureMode stop halts immediately on ANY failed step; continue records failures and proceeds. Each frame starts with all four gate flags false and no parsed body. schema parses exact raw body bytes as JSON and retains the untrusted parsed value even when invalid; its gate requires EXACTLY seven fields [subject,audience,action,target,value,notBefore,expiresAt], valid IDs, known target/verb, integer value0..1000 and integer0<=notBefore<expiresAt<=1000. signature uses the frame key only if pinned and verifies its exact UTF-8 body with native Ed25519; it works before parsing. scope requires parsed audience and notBefore<=at<expiresAt. permission requires an exact subject/action/target grant with from<=at<until. Scope/permission can inspect a parsed prefix even when schema failed. dispatchRequires lists the gate flags required at dispatch (ALL listed flags must already be true). Without a guard it can apply a bounded set-limit or delete effect from a parseable prefix even after a failed gate. Dispatch before checks leaves an effect that later denial cannot undo. stop can enforce mediation by halting before dispatch; continue needs a conjunctive four-gate guard. No dispatch or a check before its input exists can deny legitimate work. Report accepted/denied FINAL verdicts, signatureChecks/decodeAttempts actually executed, writes actually applied and unsafeWrites lacking all four fresh successful flags AT dispatch. verdicts maps EVERY frame to allow iff a write occurred and no executed step failed; otherwise deny. Reconcile every counter and verdict. Preserve working program fields while repairing one missing guard or report field, without Reset.