Mighty Mouse v0.2.6

Mighty Mouse v0.2.6

Mighty Mouse v0.2.6 completes architecture seam deepening across Agent
Execution, response application, and Signal telemetry while preserving public
compatibility paths.

Release changes

• Established response application as authoritative for supported Agent and
  non-Agent callers.
• Routed supported loop callers through canonical SignalTelemetry while
  retaining compatibility facades.
• Contracted legacy parser ownership at response application boundary.
• Added characterization, inventory, and compatibility coverage for migrated
  seams.

Limits

Compatibility facades remain intentionally in place until retirement evidence
proves removal safe. Original local-model orchestration and evaluation-only
boundaries remain separately classified.

Mighty Mouse v0.2.4

Mighty Mouse v0.2.4

Mighty Mouse v0.2.4 establishes canonical architecture seams behind existing
public and runtime contracts.

Release changes

• Established PolicyEngine as the canonical policy-selection seam and added
  canonical status projection.
• Added PolicyMutationEngine as the typed mutation-generation seam.
• Added SignalTelemetry as the canonical v2 Signal construction and emission
  seam.
• Added an explicit AutoresearchCycle boundary for bounded cycle execution.
• Completed the expand-contract compatibility migration while preserving public
  APIs, persistence behavior, evaluator boundaries, and runner-lock semantics.
• Restored the missing Scope import so CI collection succeeds across Python
  3.10–3.13.

Limits

Legacy mutation orchestration still couples filesystem, replay, and log
behavior. The evaluator metric_telemetry.json remains separate from v2
Signal telemetry. Runner-lock scope remains outside the individual cycle.
Compatibility adapters remain intentionally in place where contraction would
change behavior.

Mighty Mouse v0.2.3

Mighty Mouse v0.2.3

Mighty Mouse v0.2.3 makes local learning collection a default MCP capability.

Release changes

• Added setup_workspace, which derives a pinned Ollama model-layer digest or
  accepts an exact host-supplied digest, plus a verified host execution profile
  without hand-written workspace JSON.
• Added verify_and_record as the standard post-edit MCP path, with local,
  content-free Signal receipts partitioned by exact model and profile.
• Added recording_audit and the mighty-mouse-signal-audit command for
  optional fail-closed host completion hooks.
• Updated all shipped host rules to use setup plus recorded verification, while
  keeping one portable MCP core rather than separate learning systems.
• Aligned the core and MCP packages at 0.2.3; the MCP package requires
  mighty-mouse>=0.2.3,<0.3.

Limits

Routine use now accumulates local Signals automatically after workspace setup.
Background Research, candidate evaluation, and promotion remain separately
machine-gated; the adapter never edits code autonomously or promotes a policy.

Mighty Mouse v0.2.2

Mighty Mouse v0.2.2

Mighty Mouse v0.2.2 delivers the local-first v2 improvement control plane and
its release qualification: bounded Policy research, immutable state and
provenance, exact compatibility, controlled evaluation, promotion and recovery,
migration, quarantined Improvement Bundles, and expiring evidence-backed claim
receipts.

Release changes

• Added v2 routing, durable Hybrid handoffs, privacy-safe Signal lifecycle, and
  operator history controls.
• Added bounded Background Research, isolated Candidate evaluation, fresh
  holdout nomination, machine-gated promotion, and automatic recovery records.
• Added v1 migration, signed data-only Improvement Bundle export/import, and
  fail-closed claim receipts.
• Made invalid CLI input actionable: console users receive a concise error and
  exit code instead of a traceback; Signal help documents its controlled values.
• Aligned the core and MCP package versions at 0.2.2; the MCP package requires
  mighty-mouse>=0.2.2,<0.3.

Claims and limits

This release establishes executable implementation facts only. It does not make
comparative performance claims: any such claim still requires the separately
versioned prospective protocol and an unexpired claim receipt at the evidence
tier it supports.

Mighty Mouse v0.2.1

Mighty Mouse v0.2.1

Mighty Mouse v0.2.1 packages the completed real-project evaluation and the portability work needed to demonstrate the core library and MCP transport from clean environments.

Evidence update

The prospective study completed 10 paired real-project tasks. Both the control and Mighty Mouse passed 6 of 10 tasks on the first attempt, with no scope violations. Mighty Mouse used 4 retry rounds versus 6 for the control and received a higher mean blind-review quality score, 4.60 versus 4.30. It was slower by both mean and median duration.

No generalized reliability or speed improvement was demonstrated. The result is mixed and should not be generalized beyond this sample. The full paired evidence and limitations are recorded in data/evidence/real_project_report.md.

Release changes

• Completed and preserved the ten-pair prospective study, including unfavorable results and per-trial manifests.
• Added source-distribution filtering and archive tests that reject AppleDouble metadata.
• Repaired editable-install behavior and verified the supported CPython 3.10–3.13 matrix.
• Verified the documented MCP stdio configuration with isolated Antigravity IDE and Codex profiles, including tool discovery and calls to both protocol and verify.
• Aligned the core and MCP package versions at 0.2.1; the MCP package requires mighty-mouse>=0.2.1,<0.3.

The platform smoke proves configuration compatibility, server startup, discovery, and tool calls. It does not claim a model-quality result. See data/evidence/platform_smoke_report.md.