FixThis v1.2.0

FixThis v1.2.0 focuses on source-trust accuracy, release evidence depth, and
maintainability after the v1.1 trust-loop release. The headline change for
external Android projects is configurable testTagConventions, which lets a
project teach FixThis its local Compose test-tag patterns without changing the
persisted MCP JSON contract.

Highlights

• Project-specific test-tag conventions. Android apps can declare custom
  testTagConventions through the Gradle DSL. The conventions are written into
  source-index schema 1.3 and used by MCP owner resolution and source matching
  so strict tags can map to the intended composable owner.
• Sharper edit-surface confidence. CALL_SITE hints can now reach HIGH
  confidence under strong unambiguous evidence, while COPY_OR_DATA,
  COMPONENT_DEFINITION, and LAYOUT_OR_STYLE confidence is promoted or demoted
  from exact literals, single-owner evidence, and call-site evidence. Shared
  component definitions remain capped at MEDIUM-or-lower.
• Recommended shared-component call sites. When a reused component has one
  clear usage to inspect, FixThis surfaces a ranked recommendedEditSite
  without claiming the shared definition is the exact edit target.
• Residual-risk release gate. Release readiness now maps ADB discovery,
  source/interop evidence, required-check observations, and healthy SSE fallback
  behavior to explicit local evidence commands.
• MCP maintainability cleanup. Session code is split across focused
  preview, source, connection, DTO, target, edit-surface, handoff, draft, store,
  and event packages, with dependency-direction tests guarding the layout.
• Release version sync hardening. The release-version sync helper now
  handles v1 FixThis install/plugin/CLI contexts while leaving unrelated
  dependency versions such as Compose artifacts untouched.

Compatibility

• V1 scope is unchanged. FixThis remains debug-only, local/ADB-only, and
  Compose-only. This release does not add PyPI, Docker, or a new package
  channel.
• Persisted MCP JSON: additive only. Existing sessions may omit
  testTagConventions, confidenceBasis, recommendedEditSite, and boundary
  context fields.
• Source-index schema: current assets use schema 1.3; older 1.2 assets
  still load.
• Bridge protocol: unchanged at 1.3.
• Gradle plugin: io.github.beyondwin.fixthis.compose version 1.2.0.
• CLI/MCP package: fixthis-cli-mcp-v1.2.0.tar.gz.
• npm wrapper: @beyondwin/fixthis@1.2.0.

Agent install

From a Jetpack Compose Android app repository:

# macOS
brew install beyondwin/tools/fixthis
# npm
npm install -g @beyondwin/fixthis@1.2.0
# macOS/Linux fallback without package managers
curl -fsSL https://raw.githubusercontent.com/beyondwin/FixThis/main/scripts/install-fixthis.sh \
 | bash -s -- --version v1.2.0
fixthis install-agent --project-dir . --target all
fixthis doctor --project-dir . --json

Manual Gradle plugin form:

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

Release evidence

The release commit should include passing or explicitly deferred evidence for
the v1 residual-risk closure, external trust matrix, release drift, and release
gate sections in
docs/contributing/release-readiness.md.
Connected Android evidence remains local-only; if no unlocked emulator is
available, record the runtime commands as deferred rather than claiming
device-level proof.

See also

• CHANGELOG.md — full v1.2.0 entry.
• docs/contributing/release-process.md —
  artifact and registry publication sequence.
• docs/contributing/release-readiness.md
  — claim manifests and evidence commands.

FixThis v1.1.0

FixThis v1.1.0 closes the post-v1 trust loop: release claims now have an
observable reality check, the external agent lifecycle has a strict local smoke
path, interop handoffs carry richer boundary evidence without exact-source
overclaiming, and maintainers get one release-gate report that classifies
pass/deferred/fail evidence before tagging.

Highlights

• Release reality check. npm run release:reality verifies the public
  GitHub Release, Homebrew, npm, MCP Registry, Maven Central, and Gradle Plugin
  Portal surfaces against the version being released. Missing network or
  device-backed evidence is reported as deferred instead of silently treated as
  success.
• Agent lifecycle smoke. The external Android agent loop now has a strict
  smoke path covering handoff through claim, resolution, persistence, and
  console reflection. The contract test stays local; the strict runtime command
  remains device/emulator-backed and should be recorded as deferred if no
  unlocked device is available.
• Interop boundary evidence. AndroidView/WebView-risk handoffs now expose
  ranked boundary host, ancestor, and context rows so agents can verify nearby
  Compose ownership without treating any one row as exact interop source
  ownership.
• SSE reliability reporting. Console reliability writes an SSE/fallback
  request-count report and preserves the fallback-only polling contract for
  healthy sessions.
• One release gate. npm run release:gate aggregates release reality,
  interop guidance, runtime trust, console reliability, docs, and whitespace
  evidence into one local release-decision report.

Compatibility

• V1 scope is unchanged. FixThis remains debug-only, local/ADB-only, and
  Compose-only. This release adds evidence, diagnostics, and conservative
  handoff context; it does not add PyPI, Docker, or a new package channel.
• Persisted MCP JSON: additive only. Boundary-context and release-evidence
  fields are optional on existing local sessions.
• Bridge protocol: unchanged at 1.3.
• Gradle plugin: io.github.beyondwin.fixthis.compose version 1.1.0.
• CLI/MCP package: fixthis-cli-mcp-v1.1.0.tar.gz.
• npm wrapper: @beyondwin/fixthis@1.1.0.

Agent install

From a Jetpack Compose Android app repository:

# macOS
brew install beyondwin/tools/fixthis
# npm
npm install -g @beyondwin/fixthis@1.1.0
# macOS/Linux fallback without package managers
curl -fsSL https://raw.githubusercontent.com/beyondwin/FixThis/main/scripts/install-fixthis.sh \
 | bash -s -- --version v1.1.0
fixthis install-agent --project-dir . --target all
fixthis doctor --project-dir . --json

Manual Gradle plugin form:

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

Release evidence

The release commit should include passing or explicitly deferred evidence for
the v1.1 Trust Loop manifest and the Release Gate / Interop / SSE manifest in
docs/contributing/release-readiness.md.
Connected Android evidence remains local-only; if no unlocked emulator is
available, record the runtime commands as deferred rather than claiming
device-level proof.

See also

• CHANGELOG.md — full v1.1.0 entry.
• docs/contributing/release-process.md —
  artifact and registry publication sequence.
• docs/contributing/release-readiness.md
  — claim manifests and evidence commands.

FixThis v0.7.0

FixThis v0.7.0 improves agent setup for flavored Android apps, strengthens
Compose source matching, and tightens release guardrails around the published
CLI, Homebrew, npm, MCP, Maven Central, and Gradle Plugin Portal surfaces.

Highlights

• Flavor-aware app setup. fixthis init, fixthis install-agent, and
  fixthis run now handle flavor- and build-type-suffixed application ids
  end-to-end, including combined suffixes such as .demo.debug.
• Stronger source matching. Source-index generation now scans the app
  module plus project dependencies on the active debug variant's classpath and
  records typed semantic signals for Compose text, content descriptions, roles,
  test tags, owner composables, and string resources.
• Lower minSdk support. The debug sidekick and sample app now document and
  validate minSdk 23 support while keeping the Android 14-compatible
  compileSdk 34 baseline.
• More reliable Homebrew setup. Generated MCP config uses the stable
  fixthis executable when available instead of pinning Homebrew installs to a
  versioned Cellar path.
• Release guardrails expanded. Release checks now cover the Homebrew tap
  and release helper fixtures so stale package coordinates are caught before
  publication.

Compatibility

• Gradle plugin: io.github.beyondwin.fixthis.compose version 0.7.0.
• CLI/MCP package: fixthis-cli-mcp-v0.7.0.tar.gz.
• npm wrapper: @beyondwin/fixthis@0.7.0.
• Bridge protocol: unchanged at 1.3.
• Source-index schema: 1.2, preserving legacy fields while adding typed
  signals.
• Persisted MCP JSON: unchanged.
• Android baseline: compileSdk 34, targetSdk 34, minSdk 23.

Agent install

From a Jetpack Compose Android app repository:

# macOS
brew install beyondwin/tools/fixthis
# npm
npm install -g @beyondwin/fixthis
# macOS/Linux fallback without package managers
curl -fsSL https://raw.githubusercontent.com/beyondwin/FixThis/main/scripts/install-fixthis.sh \
 | bash -s -- --version v0.7.0
fixthis install-agent --project-dir . --target all
fixthis doctor --project-dir . --json

Manual Gradle plugin form:

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

Release evidence

The release-prep commit includes version synchronization, documentation
consistency, release-readiness, Android compatibility, and local packaging
validation. Connected device smoke was not run locally for this release; the
release keeps the existing debug-only bridge protocol and records this as a
release-note limitation rather than claiming device-level evidence.

See also

• CHANGELOG.md — full [0.7.0] entry.
• docs/contributing/release-process.md —
  artifact and registry publication sequence.
• docs/reference/compatibility.md —
  Android SDK compatibility contract.

FixThis v0.6.1

FixThis v0.6.1 is a compatibility patch for external Android projects using
the published agent-first install path.

Highlights

• Android compileSdk compatibility restored. The 0.6.1 sidekick AAR is
  built and release-gated with minCompileSdk=34, so apps compiling with
  Android 14 or 15 can consume FixThis without raising their project-wide
  compileSdk just for the debug sidekick.
• Published versions are aligned. CLI, Gradle plugin, sidekick, npm
  wrapper, MCP Registry metadata, and public install docs now all point at
  0.6.1.
• Safer agent install. fixthis install-agent preflights Gradle app-module
  matching before writing agent config, avoiding partial global Codex / Claude
  writes when a flavor-suffixed application id cannot be mapped.
• Cleaner ADB device handling. If one ready device is present alongside
  offline emulators, bridge requests scope to the ready device instead of
  failing with ADB's ambiguous-device error.
• Release packaging guardrails. Central Portal bundle creation validates
  sidekick AAR minCompileSdk against the shared catalog and now works with
  the documented relative output paths.

Compatibility

• Bridge protocol is unchanged at 1.3.
• External Android apps should apply the Gradle plugin
  io.github.beyondwin.fixthis.compose at version 0.6.1.
• Android compileSdk minimum for the 0.6.1 sidekick artifact is 34.
• Persisted MCP JSON is unchanged.

Agent install

From a Jetpack Compose Android app repository:

# macOS
brew install beyondwin/tools/fixthis
# npm
npm install -g @beyondwin/fixthis
# macOS/Linux fallback without package managers
curl -fsSL https://raw.githubusercontent.com/beyondwin/FixThis/main/scripts/install-fixthis.sh \
 | bash -s -- --version v0.6.1
fixthis install-agent --project-dir . --target all
fixthis doctor --project-dir . --json

Manual Gradle plugin form:

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

Release evidence

The release-prep commit includes local Gradle, release version, Android
compatibility, and Central Portal bundle validation. Connected-emulator smoke
should be recorded separately if this tag's release issue needs device-level
evidence.

See also

• CHANGELOG.md — full [0.6.1] entry.
• docs/contributing/release-process.md —
  artifact and registry publication sequence.
• docs/reference/compatibility.md —
  Android SDK compatibility contract.

FixThis v0.6.0

FixThis v0.6.0 is a rollup release that lands every initiative since v0.3.0
on a single tag. It covers v0.4 maintainability (pre-v0.4 compatibility
purge plus risk burn-down), v0.5 trustworthy onboarding (README-first
agent install with machine-readable readiness), and the three v0.6 tracks —
Handoff Intelligence, Studio Reliability, and Release Grade.

Version-skip note. There is no v0.4.0 or v0.5.0 tag. Each of those
programs is included verbatim in v0.6.0; consumers upgrading from v0.3.0
jump straight to v0.6.0. CHANGELOG.md keeps the full per-entry detail
under the [0.6.0] heading.

Highlights

v0.4 maintainability

• Legacy purge. Pre-v0.4 local compatibility paths are removed: schema-v1
  browser pending mirrors (localStorage["fixthis.pending.<sessionId>"]),
  the .fixthis/artifacts screenshot fallback, keyless semantic draft
  dedupe, and the deprecated no-item sendDraftToAgent(sessionId) overload.
  Draft recovery is now schema-v2 fixthis.workspace.* only.
• Risk burn-down. Console draft holders left state.js for selector-owned
  paths, MCP session handoff and event-log payload builders were split into
  focused collaborators, and CLI setup write-plan construction is now a
  side-effect-free planner shared by setup, init, and install-agent.
• Contract test. scripts/v04LegacyPurgeContract-test.mjs (canonical
  group) guards against reintroducing the removed paths.

v0.5 trustworthy onboarding

• README-first agent path is canonical:
  fixthis install-agent --project-dir . --target all followed by
  fixthis doctor --project-dir . --json. install-agent writes
  .fixthis/project.json, .fixthis/agent-setup.md,
  .fixthis/agent-setup.json, and .fixthis/mcp.json.template.
• Machine-readable readiness. install-agent --json reports
  readiness, nextAction, and restartRequired alongside applied,
  skipped, errors, and next. fixthis doctor --json,
  .fixthis/agent-setup.json, and the feedback console share that
  vocabulary, so agents can drive the bootstrap from a single contract.
• Evidence commands. npm run docs:agent-bootstrap:test,
  npm run first-run:smoke, and npm run first-run:smoke:test guard the
  README-first path.

v0.6 Handoff Intelligence

• Feedback items may now include editSurfaceCandidates[].role, an optional
  role token distinguishing call sites, reusable component definitions,
  copy/data origins, layout/style surfaces, visual-area targets, and
  interop-risk targets.
• Compact handoff Markdown renders the role token as
  editSurface: <kind> role=<role> -> <file>:<line> ..., so agents can
  inspect the likely edit surface before following source-origin candidates.
• New evaluation corpus and regression gate: npm run handoff:eval:test.

v0.6 Studio Reliability

• New grouped reliability harness: npm run console:reliability:test covers
  reducer, use-case, polling, stale-session fencing, and idempotency
  contracts.
• Duplicate-save idempotency, Studio stale-session fences, and the draft
  recovery matrix are strengthened so repeated saves, reload recovery,
  session switching, and blocked-device states stay tied to the correct
  feedback workspace.
• Browser-level proof via Playwright: npm run console:browser:reliability
  covers two-tab SSE sync, stale-preview isolation, EventSource reconnect
  recovery, stale-save confirmation, repeated Save to MCP idempotency, and
  closed-session mutation rejection.

v0.6 Studio workflow hardening

• Studio actions route through a centralized workflow policy. Safe automatic
  paths (heartbeat retry, app foreground recovery, preview refresh) stay
  automatic; dirty drafts, stale previews, activity drift, server draft
  conflicts, and stale force-save now require an explicit boundary decision.
• Durable session mutations are rejected for closed sessions at the MCP
  server boundary (screen, item, handoff, claim, resolve, draft mutation
  paths) and surface as a mapped session_closed conflict.
• Live preview delivery is push-first: preview-ready SSE events and
  fallback preview polling share the preview-application path and session
  fence; polling runs only when the event stream is unavailable.
• Draft recovery now classifies ownership for active, closed, and
  mismatched sessions; unsupported local recovery asks the user to recapture
  instead of silently mutating the wrong workspace.
• Annotate / session edge cases tightened: annotate can launch the app when
  needed, preserves saved-focus and capture-in-flight cases, refreshes
  session counts after returning from detail, avoids entry dead-ends, and
  keeps the annotate badge layout stable at zoomed preview sizes.

v0.6 Release Grade

• Release claims are now evidence-gated. Handoff Intelligence, Studio
  Reliability, or Release Grade claims require the evidence commands in
  docs/contributing/release-readiness.md
  and the release issue must record their results.
• New release-gate checks: npm run release:v06:evidence:test,
  node scripts/check-release-readiness.mjs, with local-check wiring that
  guards CLI/docs/MCP/output-schema drift before tagging.

Compatibility

• Bridge protocol is unchanged at 1.3.
• External Android apps should apply the Gradle plugin
  io.github.beyondwin.fixthis.compose at version 0.6.0.
• Persisted JSON changes are additive. editSurfaceCandidates[].role
  is optional; sessions written by older builds omit it and are read as-is.
• Pre-v0.4 local data is not migrated. Clear browser storage or run
  fixthis clean if old localStorage["fixthis.pending.<sessionId>"]
  mirrors or .fixthis/artifacts screenshot roots confuse the console.

Agent install

From a Jetpack Compose Android app repository:

# macOS
brew install beyondwin/tools/fixthis
# npm
npm install -g @beyondwin/fixthis
# macOS/Linux fallback without package managers
curl -fsSL https://raw.githubusercontent.com/beyondwin/FixThis/main/scripts/install-fixthis.sh \
 | bash -s -- --version v0.6.0
fixthis install-agent --project-dir . --target all
./gradlew fixthisSetup # only if doctor reports NEEDS_INSTALL
fixthis doctor --project-dir . --json

Restart Claude Code or Codex after MCP config is written, then call
fixthis_open_feedback_console.

Release evidence

The v0.6 release-readiness checklist
(docs/contributing/release-readiness.md)
was run on the release commit. Connected-emulator smoke was not executed on
this release machine; the unit, integration, console reliability, browser
reliability, and v0.6 evidence harnesses cover the same surfaces and are the
substituted evidence for this tag.

See also

• CHANGELOG.md — full [0.6.0] entry.
• docs/contributing/release-readiness.md —
  release-claim manifest and required evidence.
• docs/reference/bridge-protocol.md —
  bridge protocol stayed at 1.3.

FixThis v0.3.0

FixThis v0.3.0 closes the v0.3 first-run trust program, lands the
project-risk-closure build/release hardening, and rolls up a wave of console
UX fixes for the saved-annotation flow, boundary dialog, and silent-return
dead-ends.

Highlights

• v0.3 first-run trust — follow-up complete. Six deferred items plus the
  pre-existing console:smoke failure are closed: a 403 reload CTA banner, a
  clipboard fallback that no longer marks items handed off, the new
  CAPTURE_UNAVAILABLE readiness state for screenshot 404 / semantics-only
  captures, late-SSE / preview-poll drop on session mismatch, a stale-draft
  conflict policy with ETag / If-Match plus a new staleDraftConflict
  boundary variant, and the previewStaleBadge regression fix that gated
  console:smoke.
• Project risk closure (2026年05月17日). Detekt baseline ratchet,
  preserved compare-perf exit code in the perf-report workflow, release
  tarball SHA-256 verification on both shell and npm installers, a release
  consumer minify fixture (ReleaseConsumerFixtureTest), and auditable
  scheduled-gate promotion via npm run checks:observation --json --require-ready.
• Console UX repairs. Boundary dialog 3-button layout fix and gated
  "Start annotating" entry, session-delete dialog wiring, toasts for the
  silent-return dead-ends (context drift, recovery block, undo empty stack,
  device picker change ignored, capture/annotate preconditions), real
  Cmd+Z / Cmd+Shift+Z undo/redo, saved-annotation actions consolidated into
  the inspector footer, and data-boundary-action preserved on hidden
  dialog buttons.
• Build / perf. Console bundle minified via esbuild with explicit
  // @requires source resolution; reproducible build/test performance
  harness under scripts/perf/ with a committed baseline and nightly
  perf-report workflow.

Compatibility

• Bridge protocol version is unchanged at 1.3.
• External Android apps should bump the Gradle plugin to
  io.github.beyondwin.fixthis.compose version 0.3.0.
• Persisted JSON contract is unchanged.
• The new /api/items/batch ETag / If-Match flow is backward-compatible:
  the legacy client path still works when the header is omitted.

Agent install

From a Jetpack Compose Android app repository:

# macOS
brew install beyondwin/fixthis/fixthis
# npm
npm install -g @beyondwin/fixthis
# macOS/Linux fallback without package managers
curl -fsSL https://raw.githubusercontent.com/beyondwin/FixThis/main/scripts/install-fixthis.sh \
 | bash -s -- --version v0.3.0
fixthis install-agent --project-dir . --target all
./gradlew fixthisSetup
fixthis doctor --project-dir . --json

Restart Claude Code or Codex after MCP config is written, then use
fixthis_open_feedback_console.

See also

• CHANGELOG.md — full [0.3.0] entry.
• docs/contributing/release-readiness.md —
  current channel status.
• docs/reference/bridge-protocol.md —
  bridge protocol version stayed at 1.3.

FixThis v0.2.3

FixThis v0.2.3 is the first verified agent-first public install release across
GitHub Releases, Maven Central, and the Gradle Plugin Portal.

What changed

• Maven Central publication now includes:
  • io.github.beyondwin:fixthis-compose-core
  • io.github.beyondwin:fixthis-compose-sidekick
  • io.github.beyondwin:fixthis-gradle-plugin
  • io.github.beyondwin.fixthis.compose:io.github.beyondwin.fixthis.compose.gradle.plugin
• The release workflow uses the Central Portal Publisher API and waits for the
  deployment to reach PUBLISHED.
• Public docs and CLI defaults now point agents at 0.2.3.

Agent install

From a Jetpack Compose Android app repository:

curl -fsSL https://raw.githubusercontent.com/beyondwin/FixThis/main/scripts/install-fixthis.sh \
 | bash -s -- --version v0.2.3
fixthis install-agent --project-dir . --target all
./gradlew fixthisSetup
fixthis doctor --project-dir . --json

Restart Claude Code or Codex after MCP config is written, then use
fixthis_open_feedback_console.

FixThis v0.2.1

FixThis v0.2.1 is a patch release for the first public agent-first install
path.

What changed

• fixthis install-agent now defaults to Gradle plugin
  io.github.beyondwin.fixthis.compose version 0.2.1.
• The Gradle plugin now defaults its debug sidekick runtime to
  io.github.beyondwin:fixthis-compose-sidekick:0.2.1.
• Generated .fixthis/agent-setup.* files now tell agents to continue with
  ./gradlew fixthisSetup, fixthis init --agent --project-dir ., and
  fixthis doctor --project-dir . --json instead of re-running
  fixthis install-agent.
• Public docs now describe the GitHub Release + Gradle Plugin Portal + Maven
  Central install path.

Agent install

From a Jetpack Compose Android app repository:

curl -fsSL https://raw.githubusercontent.com/beyondwin/FixThis/main/scripts/install-fixthis.sh \
 | bash -s -- --version v0.2.1
fixthis install-agent --project-dir . --target all
./gradlew fixthisSetup
fixthis doctor --project-dir . --json

Restart Claude Code or Codex after MCP config is written, then use
fixthis_open_feedback_console.

Notes

FixThis is debug-build-only and Jetpack Compose-only. It runs locally over ADB
and localhost; generated .fixthis/ feedback artifacts should stay out of
version control.

FixThis v0.1.0

Released: 2026年05月11日

FixThis v0.1.0 is the first GitHub source release. It is ready for local
debug-build evaluation in Jetpack Compose apps and for AI-agent handoff through
the browser feedback console and MCP server.

Highlights

• Browser-first feedback console for selecting Compose UI targets, adding
  annotations, and handing structured context to coding agents.
• Claude Code and Codex bootstrap via ./scripts/bootstrap-mcp.sh --package <applicationId>, plus manual CLI setup documentation.
• MCP feedback workflow with fixthis_list_feedback,
  fixthis_read_feedback, fixthis_claim_feedback, and
  fixthis_resolve_feedback.
• Compact handoff prompts with source candidates, target evidence, overlap
  hints, stale-source warnings, and stable item ids.
• Debug-only Android sidekick with local socket bridge, localhost console token
  checks, screenshot containment hardening, and release-build guardrails.
• CI, security, compatibility, and release-readiness documentation for
  contributors.

Distribution Status

This release is published as a GitHub source release only. The Gradle plugin and
Android sidekick artifacts are not on Maven Central or the Gradle Plugin Portal
yet. Use the repository directly with a Gradle composite build for now.

Verification

Release validation follows the checks documented in
docs/contributing/release-process.md:

• Host unit tests for core, CLI, MCP, sidekick, and Gradle plugin modules.
• Sample debug build.
• CLI and MCP install distributions.
• Console JavaScript syntax check.
• Whitespace check.
• Connected smoke on a Pixel 9 Android 16 emulator.

Connected-device smoke testing remains manual for contributors and depends on a
locally available device or emulator.

Full Changelog

See CHANGELOG.md.