FixThis v1.5.0

FixThis v1.5.0

FixThis v1.5.0 makes runtime diagnostics part of the normal agent handoff
without turning FixThis into a remote telemetry service. Save to MCP can collect
a bounded, redacted local baseline before feedback becomes agent-visible, while
Copy Prompt remains side-effect free and every session can choose Auto, Manual,
or Off.

Highlights

• Auto runtime diagnostics. New feedback sessions default to Auto, so Save
  to MCP collects the configured baseline before exposing the batch to agents.
  Legacy sessions remain Manual, and policy choices survive restart and event
  replay.
• Fixed-preset MCP collection. Agents can call
  fixthis_collect_runtime_evidence with baseline, logs, memory, or
  performance. Arbitrary host commands are not accepted.
• Bounded local evidence bundles. Raw collector output is redacted and kept
  under .fixthis/runtime-evidence/<session-id>/<capture-id>/ with per-file,
  bundle, and project quotas. MCP JSON and compact Markdown contain bounded
  summaries and status metadata rather than raw output.
• Fail-closed ownership checks. Collection and handoff linkage reject stale
  device, install, package, session, item, and screen ownership. Closed,
  deleted, or replaced feedback contexts cannot receive late evidence.
• Connected product-path proof. The strict Android proof now drives the real
  MCP collector, Auto Save-to-MCP, artifact containment and redaction, item
  linkage, and restart replay before the release can claim connected delivery.
• Stable performance reporting. Scheduled performance comparisons combine
  baseline and current-run variance. Results from a different runner
  environment remain visible as advisory instead of failing the workflow.
• Hardened release recovery. Publication jobs verify immutable tag commits,
  keep manual inputs out of generated shell source, pin and checksum the MCP
  publisher, serialize duplicate version dispatches, skip already-public
  immutable packages, and persist Maven Central deployment IDs for
  interrupted-run recovery.

Compatibility

• V1 scope is unchanged. FixThis remains debug-only, local/ADB-only, and
  Jetpack Compose-only. Runtime evidence is not uploaded by FixThis.
• Persisted MCP JSON: additive only. Existing compatibility fields such as
  items, screens, itemId, screenId, targetEvidence,
  targetReliability, and sourceCandidates retain their names and shapes.
  Runtime-evidence policy and summaries decode with legacy-safe defaults.
• MCP tools: fixthis_collect_runtime_evidence is additive. The legacy
  manual-summary runtime-evidence tool remains available.
• Agent setup JSON: unchanged from the v1.4 line.
• Source-index schema: unchanged.
• Bridge protocol: unchanged at 1.3; collection remains a host CLI/MCP
  capability over ADB and adds no app-side Bridge method.
• Gradle plugin: io.github.beyondwin.fixthis.compose version 1.5.0.
• CLI/MCP package: fixthis-cli-mcp-v1.5.0.tar.gz.
• npm wrapper: @beyondwin/fixthis@1.5.0.

Agent install

From a Jetpack Compose Android app repository:

# macOS
brew install beyondwin/tools/fixthis

# npm
npm install -g @beyondwin/fixthis@1.5.0

# macOS/Linux fallback without package managers
curl -fsSL https://raw.githubusercontent.com/beyondwin/FixThis/main/scripts/install-fixthis.sh \
  | bash -s -- --version v1.5.0

fixthis install-agent --project-dir . --target all --verify --json
fixthis doctor --project-dir . --json

Manual Gradle plugin form:

plugins {
    id("io.github.beyondwin.fixthis.compose") version "1.5.0"
}

Release evidence

Runtime Evidence Autopilot is claimed only when the focused and aggregate
connected product-path reports both pass from the release commit:

npm run runtime-evidence:smoke:test
npm run runtime-evidence:smoke -- --strict
npm run android:proof:test
npm run android:proof -- --strict
npm run external-fixture:matrix -- --strict
npm run release:check

The focused report is written under
build/reports/fixthis-runtime-evidence/; the aggregate proof is under
build/reports/fixthis-android-proof/. Both are ignored local artifacts. A
deferred host-only result is not described as connected proof.

After GitHub, Maven Central, the Gradle Plugin Portal, npm, MCP Registry, and
Homebrew are updated, the all-channel gate must also pass:

npm run release:gate -- --strict
npm run release:reality -- --strict

The GitHub row requires a non-draft, non-prerelease release whose public
fixthis-cli-mcp-v1.5.0.tar.gz download hashes to the SHA-256 declared by its
sidecar. Maven Central verification covers core, sidekick, Gradle plugin
implementation, and plugin marker POMs.

See also

• CHANGELOG.md — full v1.5.0 entry.
• MCP tools — collector signature and fixed presets.
• Output schema — policy, summary, quota, and
  artifact layout contracts.
• Privacy and threat model
  — local storage, redaction, and trust boundaries.
• Release readiness — claim manifests
  and required evidence.
• Release process — GitHub, Maven, Gradle,
  npm, MCP Registry, and Homebrew publication sequence.