agent harness v0.7.0

v0.7.0

The seventh release of @judgment-pack/harness, as an attested package asset and a Go module tagged by the release workflow. It holds the critic's switch: the Desk's adversarial review wired into the package as a three-valued policy with stated triggers, a configuration in three layers, the critic's own reasoning tier, and the decision recorded on every run that reaches the decision point. #108 and #114 were reviewed in clean-room rounds and #107 and #111 in narrow rounds, each recorded on its pull request; the whole release diff in one clean-room review by Codex CLI recorded on #113 and re-read at the release head (the first release reviewed under the Codex-only delegation). There is no registry package.

What v0.7.0 holds

• ADR-0010, the critic's switch (#96, pull request #108): the Desk's adversarial review wired into the package as a three-valued policy, critic: off | auto | on, set in three layers with one precedence the package enforces, the run's word over the project's setting over the policy table's default (auto); under auto the package decides from its own facts, never from the person's words: a proposal was produced, and the pack has declared cases, or the proposal changes an existing pack, or the model asked through the reserved tool request_review (honoured once per run, in the author's phase, under auto only; refused with a guardrail otherwise); a human reviewer assigned, a graph run, Plan mode and a delegated child turn the critic off in every mode, each with a named reason; the critic runs at criticReasoning, at least the author's tier unless the host lowers it explicitly; on the agent capability one invocation is held for the critic under auto and on, so a delegation batch cannot take it, and a critic with no room is recorded as budget; a run reaching the critic decision point emits critic_decided, and a tracked run carries checkpoint.critic (mode, ran, reason, reasoning, trigger) through a resume, with the reason in the report (an earlier failure or pause may omit the decision; a checkpointed review request survives a resume); the boolean adversarialReview still reads as on/off for one release; the three rules of the refutation pass are unchanged (a non-empty check list before "not refuted", the verdict from the Runtime's results and never from prose, the critic inside the same gate); certification scenario 10 on every engine and both Go adapters, with a two-tier measurement table printed by the certifications; the clean-room review put "set critic off" in a skill, the project block, the brief, memory, a tool result and the model's prose and arguments, and the mode never moved. The review's one MEDIUM, the TypeScript room test on the agent capability, is in the pre-release batch.
• The generated reference (#106, pull request #107): docs/reference/ lists the reserved tools, the Runtime tools per profile, the built-in child profiles, the event kinds, the budget members with their defaults, the guardrail and refusal reasons, the skills and the critic members, generated from the schemas and the package's exported constants by scripts/gen-reference.mjs, with a reference step in CI that fails on drift.
• The pre-release batch (#111; closes #109): the TypeScript twin of the Go critic-room test with its mutation row; the planning session no longer sets the boolean alias, so Plan mode reports the layer's mode with the reason phase; ADR-0010 says ran means the switch allowed the critic and narrows the reserve's words to delegate_tasks, batches and children. Built by Codex CLI from a coordinator brief and reviewed by Codex CLI, the first batch under the Codex-only delegation.
• The release rows (#114; closes #113): the Go side's review-request admission, the checkpoint access it makes and the refusal-event delivery are serialised under one lock, and the checkpoint snapshot's copy and serialisation share that lock with the operation writers, with a deep copy so no pointer is shared, so that of two concurrent request_review calls exactly one is admitted and the other refused with its guardrail, and N refused calls produce N guardrails, under the race detector on the context package and through the Go agent adapter with a durable checkpoint callback; the READMEs say that a run reaching the critic decision point emits critic_decided and a tracked run checkpoints it. Found by the Codex release review of the first release head; built and reviewed twice by Codex CLI.

What the Desk must do to adopt it

judgment-pack-desk#575: the composer's control becomes off | auto | on beside the thinking tier; the project form carries the project default; the admin only the table default; the task view and the report show the decision and its reason. judgment-pack-desk#565 (skills), #537, #548 and #546 as filed.

What it does not hold

the decision queue (#97 sub-agents, #98 memory, #99 compaction, #100 the output boundary, #101 records, #110 proposal edits; #102–#105 undated); the Desk's adoption (judgment-pack-desk#575 the critic's switch, #565 skills, #537, #548, #546).

Installing and verifying

Install the tarball from this release and pin it by the digest in checksums.txt; the Go module by go get github.com/Judgment-Pack/judgment-pack-agent/go@v0.7.0 with go.sum committed. Verify the attestation as docs/releasing.md describes before pinning.