v2.7.2

Codex Autoresearch 2.7.2

This patch closes several places where a session could look ready before its evidence was actually ready. Fresh sessions now point to a runnable baseline, qualitative research has durable decisions, Git-private state has one owner, and finalization rejects ambiguous state before it mutates the repository.

Highlights

• One honest next action. State, Doctor, Recommend Next, and the dashboard now agree when a session still needs a baseline. Nonzero quality_gap values no longer look complete, and finalization requires current accepted evidence.
• Qualitative research that survives the chat. Every gap gets a stable ID. gap-decide records implemented or rejected decisions in append-only quality-gap-decisions.jsonl; checking a Markdown box alone remains provisional. Starting a research round also preserves an existing executable outcome metric instead of replacing it with quality_gap.
• Safer resume and recovery. Last-run, progress, and pending-log state share one Git-private resolver and preflight. Conflicting stores fail closed with actionable diagnostics, and setup no longer adds .gitattributes just to hide its own state.
• Finalization for real-world paths. Files containing spaces, brackets, wildcard characters, and Unicode are treated literally. Generated and supplied branch refs are validated before mutation, and nested finalization decisions are accepted correctly.
• Smaller routine output. Onboarding and research commands return bounded operator snapshots by default, while --json-full keeps the complete diagnostic view available when needed.

Maintainer cleanup

The repository agent contract is shorter and now points to the actual owners for workflow, architecture, command, dashboard, and release behavior. The release evidence also includes a dedicated end-to-end session-friction journey, with the canonical action reasons captured when surfaces disagree.

Verified

2.7.2 passed the full package gate and seven portable operator journeys on Ubuntu, macOS, and Windows, plus the Chrome and Chromium/Firefox/WebKit dashboard gates, workflow-policy checks, CodeQL, package extraction smoke, checksum verification, and post-publish artifact verification.

No migration is required from 2.7.1.

Read the changelog or view the full comparison.