# `smart-commit-host-agent` 0.1.2 Release Notes

## Summary

`smart-commit-host-agent` 0.1.2 is a patch release that aligns PR/MR content generation with `pull-request create` and with `smart-commit-cli`, lets local-only commands load config without a platform token, and ships first-use documentation.

## Highlights

- `bridge` generates PR/MR title and description via a Host-Agent `pr-content` turn (same path as `pull-request create`)
- when the branch range has exactly one commit, the PR/MR title reuses that commit subject (parity with `smart-commit-cli`); multiple commits still use the Host-Agent generated title
- explicit `--title` / `--description` are not overwritten
- `bridge` create payload includes `description` when an MR/PR is created
- branch diff for PR content falls back to `origin/<targetBranch>` when the local target ref is missing
- `pullRequest.authToken` `env:` refs resolve to `""` when the variable is missing or empty, so `config resolve` / `bridge --review-only` / `commit-message generate` no longer fail at config load; platform commands still require a non-empty token
- README leads with product features and links to shipped user docs: `docs/getting-started.md`, `docs/configuration.md`, `docs/integrations.md`, and `docs/contracts.md`

## Why This Release Matters

In 0.1.0 / 0.1.1, full `bridge` reused the git commit message as the PR/MR description. That diverged from `pull-request create` and produced weaker review context. 0.1.2 uses the same `pr-content` turn for both paths, and matches CLI title behavior for single-commit branches.

Local-only skill loops can now ship a config that references `env:SMART_COMMIT_PULL_REQUEST_AUTH_TOKEN` without forcing every developer to export that variable before `config resolve` or `bridge --review-only`.

First-use and skill integration now start from the four user docs above. Publish, release, and parity pages stay in-repo for maintainers.

## Available Commands

Same surface as 0.1.0 — see [`docs/releases/0.1.0-draft.md`](./0.1.0-draft.md). `bridge` now includes a `pr-content` turn before platform create (unless `--title` and `--description` are both provided).

## Stability Notes

- still no LLM HTTP transport; exit `10` still means pause for Host-Agent turn response
- full `bridge` may emit one extra `needs_host_agent` pause (`purpose: "pr-content"`) after push, before create
- additive command surface growth remains preferred during `0.1.x`

## Suggested Upgrade Path

1. install or bump to `smart-commit-host-agent@0.1.2`
2. skill loops that run full `bridge` should handle an additional `pr-content` turn after commit/push (same `needs_host_agent` → write response → `--session` loop)
3. no config schema changes; `--title` / `--description` still skip the turn when both are provided
4. `bridge --review-only` / `config resolve` no longer require `SMART_COMMIT_PULL_REQUEST_AUTH_TOKEN` even when config uses `env:` for `pullRequest.authToken`
5. platform commands (`pull-request create` / `review`, `my-pull-request list` / `batch-review`) still fail if the token is empty
6. first-use and skill integration now start at `docs/getting-started.md`; publish / parity docs stay in-repo for maintainers

## Verification

Before publish:

1. run `npm test`
2. run `npm run pack:dry-run`
3. review [`CHANGELOG.md`](../../CHANGELOG.md)
4. review this note against the intended release scope
5. confirm `node out/cli.js --version` prints `0.1.2`

## Known Follow-Up Areas

- no chunked / hybrid review; no correction repair turns
- optional smoke-test script for common skill loops
- keep `package.json` free of private Git remote URLs (npm consumers use the published package / jsDelivr docs)