[briananderson1222]

Veritas 1.11.2 writes npx --no @kontourai/veritas readiness into the governance block. A bare veritas is on PATH only inside an npm script, and npx without --no can fetch the unscoped veritas package, which belongs to another project. This moves Dispatch to 1.11.2 and to the installed-only spelling.

Changes

• package.json, pnpm-lock.yaml: @kontourai/veritas devDependency ^1.7.4 (resolved 1.7.4) to exactly 1.11.2, via pnpm. The lockfile diff is the Veritas entry and its new transitive dependency only.
• AGENTS.md: governance block refreshed with npx --no @kontourai/veritas apply governance-blocks. Only the line between the markers changed. No files were created.
• .veritas/README.md: the five suggested commands now read npx --no @kontourai/veritas ..., matching what 1.11.2's README template emits. (apply governance-blocks does not touch this file; the Veritas migration guide says to edit it by hand.)
• .veritas/GOVERNANCE.md: the attestation command agents may prepare reads npx --no @kontourai/veritas attest ... --approval-ref <ref>, matching 1.11.2's template.

Not changed: the veritas:readiness package script (it runs inside npm, where the bin resolves), and the Protected Standards (.veritas/repo-map.json, repo-standards/, authority/).

Readiness (npx --no @kontourai/veritas readiness --working-tree)

Before, Veritas 1.11.2 against the unchanged instruction files:

WARN  ai-instruction-files-synced: AI instruction governance block mismatch: 1 stale canonical block content mismatch. ...
WARN  surface-status: claim "veritas.policy.dispatch.dispatch-default.ai-instruction-files-synced" is DISPUTED ...

(With the previously installed 1.7.4, ai-instruction-files-synced passed, because the old block matched the old canonical text.)

After:

PASS  evidence-check: npm run verify
WARN  policy-changes-require-attestation: No active attestation found; readiness is advisory until bootstrap attestation is recorded.
PASS  required-veritas-artifacts: All required repository artifacts are present.
PASS  ai-instruction-files-synced: All required AI instruction files contain the canonical Veritas governance block.
PASS  prefer-veritas-routed-delivery: All required repository artifacts are present.
WARN  surface-status: claim "dispatch.governance" is DISPUTED (Evidence explicitly reported a non-passing result.)
WARN  surface-status: claim "veritas.policy.dispatch.dispatch-default.policy-changes-require-attestation" is DISPUTED (Evidence explicitly reported a non-passing result.)

No FAIL. The remaining WARNs predate this change (no bootstrap attestation is recorded).

Other checks

• npm run docs:check passes (AGENTS.md is a published document).
• npm run verify passes (it is the readiness evidence check).
• pnpm install --frozen-lockfile passes on the new lockfile.

Dependabot #72 bumps Veritas to 1.7.6 in the same group; this supersedes that part of it.