fix(cli): drop manual CHANGELOG.md edit and stray closing tag in auggie docs

CI added a no-manual-changelog guard: release-please generates CHANGELOG.md
from the Conventional Commit PR title, so a hand-written entry fails the
gate. Removed it; the auggie feature entry will appear automatically in the
next release PR.

docs/content/docs/auggie.mdx also had a stray trailing `</content>` line
with no matching opening tag, which fumadocs-mdx rejects as invalid MDX and
fails the Next.js docs build. Removed it.

Author: rNoz

CHANGELOG.md

@@ -9,7 +9,6 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 ## Unreleased
 
 ### Features
-- **cli:** `headroom wrap auggie` routes an AugmentCode Auggie session through the local proxy. Auggie reads its tenant URL from its OAuth session, so the wrapper rewrites ONLY that `tenantURL` to the local proxy (the access token is preserved byte-for-byte), passes it via `AUGMENT_SESSION_AUTH`, and forwards every tenant path verbatim to the real tenant, tagging the `POST /chat-stream` inference call as the `augment` provider in `/stats`. All models (including Prism routing) stay on the user's Augment subscription with no API keys and no persistent config edits. Auggie's tenant wire is proprietary, so v1 forwards inference bodies unchanged (redirect + telemetry); request compression and output-shaping for the Augment shape are follow-ups. New `--augment-api-url` proxy option (env `AUGMENT_TARGET_API_URL`) registers the passthrough only when configured, so all other proxy behavior is unchanged.
 - **proxy:** opt-in cost-aware model routing ([#1706](https://github.com/headroomlabs-ai/headroom/issues/1706)). Set `HEADROOM_MODEL_ROUTER_ENABLED=1` and `HEADROOM_MODEL_ROUTES` (a JSON array of ordered rules) to rewrite the upstream model based on estimated input size and tool presence, complementary to content compression, e.g. send small, tool-free requests to a cheaper model. First matching rule wins, and each decision is logged with a reason so routing stays observable. Malformed rules fail open (the rule is skipped, never silently widened). Disabled by default so behavior is unchanged, skipped under `x-headroom-bypass`/passthrough, and currently applied on the Anthropic `/v1/messages` path.
 - **install:** `headroom install apply` now accepts `--code-aware/--no-code-aware`, `--intercept-tool-results`, `--protect-tool-results`, and `--bedrock-profile`, mirroring the equivalent flags already on `headroom proxy`. Previously the only way to run a persistent deployment with these settings was to hand-edit `manifest.json` after the fact, which silently reverts on the next `install apply`.
 - **install:** `headroom install apply --env KEY=VALUE` (repeatable) passes environment variables into supervised runners (macOS launchd, Linux systemd/cron, Windows services/tasks). These runners previously started with a bare environment and did not inherit the interactive shell's exports — e.g. a custom `HEADROOM_WORKSPACE_DIR` never reached the supervised process, so `headroom install agent run` looked for its manifest in the wrong location and failed outright even though `install apply` itself succeeded. `--env` values are merged into `DeploymentManifest.base_env` last, so they can override auto-derived defaults, and are threaded into the generated `run-headroom.sh`/`ensure-headroom.sh` (and Windows equivalents) as `export`/`$env:` lines before the `exec`.

docs/content/docs/auggie.mdx

@@ -51,4 +51,3 @@ Auggie's tenant wire is Augment-proprietary (the inference call `POST /chat-stre
 - Proxy dashboards bucket the inference traffic under the `augment` provider. (The real model id and token counts live in Auggie's proprietary response and are not yet parsed, so a v1 session shows the `augment` provider with a generic passthrough model label.)
 - If the target port already runs a Headroom proxy that is NOT in Auggie mode (for example a shared `headroom wrap claude` on the default `8787`), `wrap auggie` cannot serve Auggie's `/chat-stream` from it and stops with an error. Run Auggie on a dedicated port instead, e.g. `headroom wrap auggie --port 8790`.
 - Nothing durable is written (only the launched process's environment is set), so there is no `headroom unwrap auggie`: ending the session fully undoes the redirect. Your on-disk `~/.augment/session.json` is never modified.
-</content>