v0.16.0

Minor Changes

• #237 717468a Thanks @lucasbraum! - npx uptide fix gets the Agent SDK executor. The package stays as small as before: @anthropic-ai/claude-agent-sdk is not installed with Uptide. An SDK installed next to Uptide is used as it is; otherwise the first fix that needs it installs the version Uptide is tested with into Uptide's cache (~/.cache/uptide/agent-sdk/<version>), says so in one line with its size, and later runs reuse it. When that install fails (offline, a proxy) or the SDK cannot run, fix runs the patch executor and says so on the first line of its output and at the top of the PR body, with the reason and how to get the SDK executor. report.json records llm.executor and, after a fallback, the reason in llm.sdkMissing. The privacy notice names the SDK only when the SDK will run, and the LLM line names the executor. --agent sdk without a usable SDK stops before any work instead of failing mid-run.

• #239 e1e8c40 Thanks @lucasbraum! - uptide fix runs only with the Claude Agent SDK; if it can't, it doesn't run. Before the first download, an interactive terminal asks once: uptide fix needs the Claude Agent SDK (about 300 MB, downloaded once to <cache>). Download now? [Y/n] (default yes). With --yes, or without a terminal, it downloads and says so in one line. Once cached, it never asks again. Answering n, an SDK that can't be fetched or loaded (offline, a proxy, no binary for the platform), a missing ANTHROPIC_API_KEY, another provider, or llm.enabled: false / executor: patch in uptide.yml all stop fix with exit 2 before any clone or spending. The run prints one message with the reason and the fix, and --json returns it as error.code: "SDK_UNAVAILABLE". There is no fallback to the patch executor anywhere: the Uptide Action stops the run with the same message. --no-llm, --agent and --provider are gone from help and docs. llm.sdkMissing is gone from report.json, and uptide init no longer writes executor.

Patch Changes

• #236 9b35b9d Thanks @lucasbraum! - A repository build that fails on the final head is no longer published as a ready PR. When it fails, fix builds the parent commit in the same clone to compare. If the parent fails too, the build line says "already failing before this upgrade" and nothing is blocked. If the parent passes, the upgrade broke the build: verification fails, and the PR opens only as a draft with "Build broken by this upgrade" at the top. If the parent can't be checked out, installed or built, verification still fails and the PR says "Build fails on this upgrade; the parent build could not be checked" with the reason, never that the parent passed. The GitHub Action opens these runs as draft PRs, the same way it opens agent-led runs. The head build also skips workspaces already built on that head, so a workspace whose output a consumer reads is no longer built twice.

• #233 1ad8071 Thanks @lucasbraum! - The PR description's build check now gives the build's actual result: passed, failed with its first error, or not run and why. When a migration pack doesn't require a build, fix still runs the repository's build once on the final head, and uptide verify runs it again, and reports what happened. "Not required by the pack" now appears next to that result instead of replacing it. Before, the line read "build not required" even when the repository's build failed. A build the pack doesn't require still doesn't block verification or publishing.

• #238 6f07d3f Thanks @lucasbraum! - An SDK session's edits are no longer thrown away because of one flaky test. Before the gate rejects a session on test failures, it runs the failing test files once more, alone, with their runner and the same isolation as the full run. A file that passes then is recorded as flaky (llm.tasks[].flaky in report.json, and a line in the PR body's review list) and the edits stay. A file that fails twice still rejects them, and a failure that names no test file (a build, a timeout) is never rerun. Final verification keeps its full gate: it runs the flaky files again, and if one fails there, verification fails and the PR body says so. fix also stops starting verification feedback sessions when what is left of --max-cost is below the mean cost of the run's sessions so far, so it no longer starts a session it can't afford; the PR's feedback line says when this happened.

• #234 066deab Thanks @lucasbraum! - fix on npm no longer loses a package the repo imports without declaring it when the ERESOLVE retry re-resolves the lockfile. If the retry drops such a package from the top of node_modules, it runs again keeping that package and the locked packages that require it at their old versions; if that conflicts, the first retry stands. Either way the summary and the PR body name the package under "Imported but not declared" and suggest adding it to package.json. fix never adds it for you.