v0.27.2

Changes

• Add harnessme providers doctor to check CLI installation, authentication, model discovery, and an optional live structured-output probe (--probe).
• Show model stage start, completion time, and a 30-second still-running signal during initialization and refresh.
• Store per-call inference durations in .harnessme/facts/harness-generation.json without prompts or model responses.

Verification

• TypeScript lint, 155 tests, and the package smoke test passed locally. One Windows-only test was skipped on macOS.
• Live structured-output probes passed with Cursor (auto, 20.6 seconds) and Codex (3.7 seconds).

HarnessME v0.27.1

HarnessME v0.27.1 improves reliability for Cursor and the other inference providers.

• Verify CLI login status before selecting Codex, Claude Code, or Cursor; ignore unrelated programs named agent.
• Report Cursor and Claude error envelopes even when their process exits successfully, and give provider-specific invalid JSON and timeout errors.
• Parse structured results surrounded by CLI notices, preserve useful early-exit diagnostics, and handle Windows npm .cmd shims safely.
• Add regression coverage for Cursor, Codex, Claude, HTTP, and Windows process launch behavior.

Verification: 151 tests passed locally; lint and package smoke passed; macOS, Ubuntu, Windows, and package CI passed. Live Codex and Cursor probes passed. A full Cursor-assisted initialization and drift check passed on an isolated fixture; the multi-stage run took about 20 minutes, mostly in Cursor model review.

HarnessME v0.27.0

HarnessME v0.27.0 closes gaps found by generating a fresh harness for Corey without its existing agent instructions.

• Always load the canonical agent contract and require explicit developer confirmation for foundational entry methods and core infrastructure contracts.
• Ask the model to cover startup, runtime configuration, prompt/model resolution, and other foundational owners; allow up to 12 focused references.
• Keep deterministic source citations separate from verified behavioral invariants.
• Score cited, actionable guide content and whether leading critical paths resolve to an owner and guide.
• Cap quality below “excellent” until critical-path proposals are reviewed.

Verification: 140 tests passed locally; lint and package smoke passed; macOS, Ubuntu, Windows, and package CI passed. A fresh Corey cold-start run produced guides for prompt/model and startup contracts; harnessme check passed after sync.

HarnessME v0.26.0

HarnessME 0.26.0 stages the remaining multi-file harness updates before applying them. Directive, critical-path, feature, and MCP directive changes now commit their stored settings and generated integrations together. Critical approval commits its record, index, and manifest together. Dashboard provider changes, gate batches, and quality remediation also use a shared commit boundary.

Failure tests verify that late rendering, manifest, and dashboard batch errors leave repository state unchanged. Verified by 138 local tests, package smoke, and CI on Ubuntu, macOS, and Windows.

HarnessME v0.25.0

HarnessME 0.25.0 stages generation rollback and its before/after history snapshots before applying any repository changes. A restore conflict leaves the current generated documents and generation history unchanged.

Verified by 134 local tests, package smoke, and CI on Ubuntu, macOS, and Windows.

HarnessME v0.24.0

HarnessME 0.24.0 stages the complete init and refresh operations before applying changes. A late analysis or rendering failure now leaves imported instructions, stored facts, quality history, and generated files unchanged. Successful updates retain the concurrent-edit checks and rollback behavior introduced in 0.23.0.

Verified by 133 local tests, package smoke, and CI on Ubuntu, macOS, and Windows.

HarnessME v0.23.0

HarnessME 0.23.0 stages sync and validate updates before applying them to the repository. A late rendering or validation failure now leaves generated instructions, facts, and generation history untouched. The commit checks for concurrent edits and restores earlier writes if an update fails.

The release also covers linked Git worktrees and keeps generation previews isolated. Verified by 131 local tests, package smoke, and CI on Ubuntu, macOS, and Windows.

HarnessME v0.22.0

What changed

• Root instructions keep maintainer directives and active protected paths visible while routing local fixes through nearby source and tests.
• Agent-pack, focused references, and harnessme context are used when ownership, invariants, or extension seams need more context.
• Correcting an outdated reference no longer automatically requires a root pending note and harnessme validate; new reusable rules still do.
• The optional detailed contract follows the same maintenance rule.

Verified with 128 tests, lint, package smoke, and cross-platform CI. Historical task verifiers passed, but the pilot showed variable token use; this release makes no cross-repository efficiency guarantee.

HarnessME v0.21.0

What changed

• Generate concise agent guidance grounded in repository files and documentation.
• Keep scoped AGENTS.md files focused on relevant references and active gates.
• Check generated guidance links and include link integrity in quality scoring.
• Add an opt-in private historical task benchmark runner.

Verified with 128 tests, lint, package smoke, and cross-platform CI. The six-task pilot showed mixed efficiency results; token savings are not guaranteed across repositories.

HarnessME v0.20.0

HarnessME 0.20.0 gives generated harnesses a shorter entrypoint and a canonical agent pack, following the pattern proven in Corey's authored harness.

• Root AGENTS.md keeps imported maintainer directives and critical approval rules close to the agent.
• .harnessme/agent-pack/agent.md routes changes to focused references and lists when those references must be maintained.
• Detailed generated instructions move to .harnessme/agent-pack/contract.md.
• MCP preflight includes the canonical agent contract, and drift checks cover the generated pack.
• Generated links resolve from their new location; missing AI-suggested reference links render as plain text.
• Quality commands retain compatibility with existing harnesses until they are synchronized.

To adopt the new layout in an existing repository, update HarnessME and run harnessme sync. The tool preserves imported maintainer directives and pending notes.

Verified against the Corey evaluation clone: drift check passes, quality is 99/100, and all links in the root and agent pack resolve. The remaining point reflects an existing Python version conflict in Corey documentation.