@pimmesz/afterburner 1.0.1

package/.env.example

@@ -0,0 +1,16 @@
+# Afterburner reads secrets from the environment only. Never commit a real .env.
+
+# Required ONLY for the 'api-key' backend. Bills your Anthropic API account per
+# token at API rates, so every run costs real money.
+#
+# IMPORTANT: with the 'claude-code' backend, leave this UNSET. In headless mode
+# (`claude -p`) a present ANTHROPIC_API_KEY is ALWAYS used and silently takes
+# precedence over your subscription login, so runs would bill the API instead
+# of spending subscription quota. Afterburner strips it from the child process
+# environment as a defense, but don't rely on that alone.
+ANTHROPIC_API_KEY=
+
+# Optional, 'claude-code' backend in CI/headless environments without an
+# interactive `claude /login`: generate a long-lived subscription OAuth token
+# with `claude setup-token` and put it here. Scoped to inference only.
+CLAUDE_CODE_OAUTH_TOKEN=

package/LICENSE

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright 2026 Afterburner contributors
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

package/README.md

@@ -0,0 +1,294 @@
+<p align="center">
+  <img src="assets/afterburner-logo.png" alt="Afterburner logo" width="150" />
+</p>
+
+<h1 align="center">Afterburner</h1>
+
+<p align="center">
+  <strong>Turn unused Claude subscription quota into small, reviewed pull requests.</strong>
+</p>
+
+<p align="center">
+  <a href="https://github.com/pimmesz/afterburner/actions/workflows/ci.yml">
+    <img src="https://github.com/pimmesz/afterburner/actions/workflows/ci.yml/badge.svg" alt="CI status" />
+  </a>
+  <a href="./LICENSE">
+    <img src="https://img.shields.io/badge/license-Apache--2.0-blue" alt="Apache-2.0 license" />
+  </a>
+  <img src="https://img.shields.io/badge/dry--run-default-2ea44f" alt="Dry-run by default" />
+  <img src="https://img.shields.io/badge/output-PR--only-f97316" alt="PR-only output" />
+</p>
+
+<p align="center">
+  <code>budget-aware</code> · <code>one bounded task</code> · <code>dry-run first</code> ·
+  <code>no telemetry</code>
+</p>
+
+Afterburner watches how much of your Claude budget is left. When there's enough headroom, it
+picks one small, checkable coding task against a repo you've allowlisted and shows exactly
+what it would do.
+
+The coding agent isn't the interesting part; that already exists. What Afterburner adds is
+the decision layer: working out when it's safe to spend, and what's worth spending on.
+
+> Current status: the dry-run path works end to end. Live Claude Code/API execution and real
+> PR creation are still interface stubs in this version.
+
+| What it does       | Why it matters                                                          |
+| ------------------ | ----------------------------------------------------------------------- |
+| Checks both caps   | Uses weekly headroom and 5-hour session availability before doing work. |
+| Keeps work bounded | Runs one task per ignition cycle, sized to fit your configured budget.  |
+| Stays review-first | Plans a `claude/` branch and PR; live output stays away from default.   |
+| Starts safe        | Dry-run is the default, and live runs require a two-part opt-in.        |
+
+> Fair use: Afterburner is for spending your own subscription quota on your own repos. It
+> doesn't get around provider limits; it keeps capacity you've already paid for from going to
+> waste.
+
+## The economics
+
+Flat-rate Claude plans are use-it-or-lose-it. Whatever you don't use each week is gone, with
+no rollover. The `claude-code` backend is designed to run tasks through your local Claude
+Code login, so it spends quota you're already paying for and costs nothing extra. The
+`api-key` backend is the alternative: it works anywhere, but it bills your Anthropic API
+account per token, so every run costs real money.
+
+Two billing details worth knowing (checked against the official docs on 2026-06-11):
+
+- From June 15, 2026, headless `claude -p` usage on subscription plans comes out of a
+  separate monthly "Agent SDK credit" (Pro $20/mo, Max 5x/20x $100/$200) rather than your
+  interactive weekly limits. Afterburner's budget model tracks the interactive limits you can
+  see yourself with `/usage` in Claude Code. Think of the SDK credit as the pool that live
+  `claude-code` runs actually draw from.
+- Fable-family models cost real money. Outside promotional windows they're excluded from
+  subscription plan limits and bill usage credits at API rates. That's why Afterburner blocks
+  them by default (see [Safety model](#safety-model)).
+
+## Use at your own risk
+
+Afterburner runs on your machine, under your accounts, against your repositories. Whatever it
+uses is yours to pay for: it spends your Claude subscription quota, and with the `api-key`
+backend or a Fable/Mythos model it can spend real money billed to your own Anthropic account.
+The maintainers don't run it for you and don't cover anything it does.
+
+You're responsible for what it does on your behalf, including the budgets you set, the repos
+you allowlist, the backend you choose, and reviewing any pull request before you merge it.
+Dry-run is the default and live runs need an explicit opt-in precisely so nothing costs you
+anything until you decide it should. The software is provided "as is", without warranty of any
+kind, as set out in the [Apache-2.0 license](./LICENSE).
+
+## Safety model
+
+These rules live in the code, not just in this README:
+
+- Dry-run is the default. A live run needs both the `--live` flag and a live engine
+  (`agent.backend`) in the config. Miss either one and you get a dry run.
+- PR-only. Live work is designed to land on a `claude/`-prefixed branch and become a pull
+  request. It never merges and never pushes to your default branch.
+- One task per run. The task has to fit inside the budget or be abandoned cleanly. A killed
+  run leaves a resumable `claude/` branch, never a half-broken state.
+- Both caps are checked. A run only fires when a 5-hour session window is available and the
+  estimated cost plus a safety margin fits inside the remaining weekly budget.
+- Idempotent. Each task gets a deterministic fingerprint, and a fingerprint that already has
+  an open or merged PR won't run again.
+- Fable is gated. Any Fable/Mythos-tier model is refused unless you explicitly set
+  `agent.allowFable: true`, so an unattended scheduler can't quietly spend at API rates.
+- Untrusted input stays data. Repo contents, issue titles, and PR text never get interpolated
+  into shell commands. They go through stdin and environment variables instead.
+- No telemetry, and no repos configured out of the box. The only network call the CLI makes
+  on its own is a once-daily npm version check (skipped off-TTY and in CI; disable with
+  `NO_UPDATE_NOTIFIER=1`).
+
+## Quickstart (60 seconds)
+
+Needs Node.js 22.12 or newer and `git` on your PATH.
+
+Heads up before you copy-paste: the first release isn't on npm yet, so install from source —
+clone the repo, then `pnpm install && pnpm build && npm install -g .`. Once published, the
+install line below works; the unscoped `afterburner` name on npm is a different, unrelated
+package, so always use the scoped `@pimmesz/afterburner`.
+
+```sh
+npm install -g @pimmesz/afterburner   # once published; until then see above
+afterburner init             # interactive setup, writes afterburner.config.mjs
+afterburner doctor           # checks prerequisites and prints fixes
+afterburner run-once --dry-run
+```
+
+Point `init` at a repo (or add one to `repos` in the config later), and a dry run shows
+exactly what a live run would do:
+
+```text
+Mode: DRY-RUN (no side effects)
+Budget (manual: budget.manual / flags): session=available weekly=100% (~3,000,000 Sonnet-eq tokens remaining)
+
+repo /path/to/repo
+  [tests] Add tests for src/math.ts
+  branch   claude/tests-c615710cd153
+  PR title Add tests for src/math.ts [afterburner:c615710cd153]
+  est cost 90,000 Sonnet-equivalent tokens
+  [dry-run] Would check out …, create branch claude/tests-c615710cd153, … No side effects were performed.
+
+Next
+  This was a preview. Live execution ships in a future release; once it does,
+  set agent.backend: 'claude-code' in afterburner.config.mjs, then: afterburner run-once --live
+```
+
+### Claude Code skill
+
+```sh
+afterburner skill install   # copies the skill to ~/.claude/skills/afterburner/
+```
+
+Then you can ask Claude Code to "run an afterburner dry run", or use `/afterburner`. Both
+drive the same CLI.
+
+### MCP server (stub)
+
+`afterburner mcp` is a placeholder for exposing run-once, log, and doctor as MCP tools. It's
+documented but not built yet. The CLI and the skill are the supported front-ends.
+
+## Scheduling
+
+```sh
+afterburner schedule install   # recommended: native launchd / systemd / schtasks entry
+afterburner watch              # foreground daemon, useful for dev or temporary runs
+afterburner schedule uninstall
+```
+
+Use `schedule install` for normal unattended use. It lets the OS restart the cadence after
+login/reboot and is more reliable than keeping a terminal process alive. It figures out your
+platform, writes the unit or plist files, and prints the command to activate them.
+
+`watch` is still there for foreground runs and for cron expressions that native schedulers
+can't express. If your cron expression is too complex for the native scheduler, `schedule
+install` says so and points you at `watch`.
+
+## Configuration
+
+`afterburner init` writes `afterburner.config.mjs`. cosmiconfig loads it, and `.js`, `.cjs`,
+and `.ts` variants of `afterburner.config.*` work too (JSON only as `.afterburnerrc.json`).
+A `.ts` config also needs the `typescript` package available at runtime, which is why `init`
+writes `.mjs` by default. There's a commented example in
+[afterburner.config.example.ts](./afterburner.config.example.ts).
+
+| Key                                   | Default                | What it does                                                                                                                        |
+| ------------------------------------- | ---------------------- | ----------------------------------------------------------------------------------------------------------------------------------- |
+| `repos[]`                             | `[]`                   | Allowlist: `url` (remote or local path), `defaultBranch` (`main`), `branchPrefix` (must stay in `claude/`), `enabledTaskCategories` |
+| `budget.provider`                     | `manual`               | `manual`, `claude-code-transcripts`, or `claude-usage` (the automatic ones are described below)                                     |
+| `budget.weeklyAllowanceSonnetTokens`  | `5_000_000`            | Your plan's weekly capacity estimate, used by the automatic providers                                                               |
+| `budget.usageCacheMaxAgeHours`        | `12`                   | `claude-usage` only: a cache older than this falls back to the transcript estimate                                                  |
+| `budget.minWeeklyHeadroomPct`         | `20`                   | Don't fire below this much of the weekly cap remaining                                                                              |
+| `budget.safetyMarginTokens`           | `200_000`              | Sonnet-equivalent tokens kept untouched on every decision                                                                           |
+| `budget.requireSessionAvailable`      | `true`                 | Also require a 5-hour session window                                                                                                |
+| `budget.manual`                       | session ✓ / 100% / 3M  | Inputs for the manual provider; you can override them per run with flags                                                            |
+| `schedule.cron` / `schedule.timezone` | `17 */4 * * *` / `UTC` | When `watch` and native schedules fire                                                                                              |
+| `agent.backend`                       | `dry-run`              | `dry-run`, `claude-code`, or `api-key`                                                                                              |
+| `agent.modelByCategory`               | sonnet/opus/haiku mix  | Per-category model routing. Plain strings, so a new model never breaks the config.                                                  |
+| `agent.maxTaskTokens`                 | `200_000`              | Hard per-task ceiling in Sonnet-equivalent tokens                                                                                   |
+| `agent.allowFable`                    | `false`                | Explicit opt-in for Fable-family models                                                                                             |
+| `taskCategories`                      | all enabled, weighted  | Per-category enable/disable plus a ranking weight                                                                                   |
+
+Task categories are `security`, `tests`, `types-lint`, `dead-code`, `perf`, `infra`, and
+`docs`. Each one comes with a built-in note on how a reviewer confirms it's done.
+
+### The budget model
+
+Everything is measured in Sonnet-equivalent tokens, normalized through one cost table built
+from published API price ratios (Haiku 1/3x, Sonnet 1x, Opus 1.67x, Fable 3.33x). There's no
+official API for how much subscription quota you have left, so there are three
+estimate-driven providers:
+
+- `claude-usage` (automatic, most accurate). Reads the same numbers the `/usage` panel shows:
+  your real 5-hour and 7-day usage percentages and the exact reset times. Claude Code hands
+  these to its statusLine feature, and `afterburner statusline install` adds a hook that
+  caches them. This provider reads that cache. The reset timestamps let a slightly-stale cache
+  correct itself (a 5-hour window that has already reset reads as available again), and it
+  falls back to the transcript estimate if the cache is missing or older than
+  `budget.usageCacheMaxAgeHours`. Setup:
+
+  ```sh
+  afterburner statusline install     # wraps any existing status line without clobbering it
+  # use Claude Code once so it reports usage after the first API response
+  # then set budget.provider: 'claude-usage' in your config
+  ```
+
+  You still set `budget.weeklyAllowanceSonnetTokens` once. The percentage is authoritative,
+  but turning it into a token figure needs to know your plan's size. The cache refreshes
+  whenever you use Claude Code interactively.
+
+- `claude-code-transcripts` (automatic). Reads your local Claude Code session transcripts
+  (`~/.claude/projects/**/*.jsonl`, written live by every session), adds up what you actually
+  spent over the last rolling 7 days, converts it through the cost table, and subtracts it
+  from `budget.weeklyAllowanceSonnetTokens`. Set the allowance once against `/usage`, and
+  after that the remaining budget tracks itself. Session availability stays a manual input,
+  since the 5-hour cap isn't exposed locally.
+
+- `manual`. You supply the `budget.manual` numbers (check `/usage`), or override them per run:
+
+```sh
+afterburner run-once --weekly-remaining-pct 45 --weekly-remaining-tokens 1500000 --session-available true
+```
+
+Flags override whichever provider you've configured, so you can spot-check the automatic
+numbers whenever you want.
+
+## Live execution status
+
+1. Pick an engine in `afterburner init` (it explains the cost of each one inline), or set
+   `agent.backend` in the config.
+2. For `claude-code`: install Claude Code, log in with `claude /login`, and make sure
+   `ANTHROPIC_API_KEY` is unset. In headless mode a present API key quietly takes priority
+   over your subscription and bills the API instead. `afterburner doctor` checks for exactly
+   this, including which auth method is actually in use. On headless machines, generate a
+   token with `claude setup-token` and set `CLAUDE_CODE_OAUTH_TOKEN`.
+3. For `api-key`: export `ANTHROPIC_API_KEY` (see `.env.example`, which ships with the
+   package) and accept that runs bill per token.
+4. Arm a run explicitly with `afterburner run-once --live` (or `watch --live`).
+
+The live backends are interface stubs in this version. They validate, gate, and then refuse
+with a single clear message (no stack traces). The dry-run path works end to end.
+
+## Uninstall
+
+```sh
+afterburner schedule uninstall            # remove native scheduler entries first
+rm -rf ~/.claude/skills/afterburner       # remove the skill if you installed it
+npm uninstall -g @pimmesz/afterburner     # also how a source install (`npm install -g .`) is removed
+```
+
+The run store lives in your OS data directory; `afterburner doctor` prints the exact path.
+Delete that directory to clear the audit trail.
+
+## Threat model
+
+- Prompt injection. Repo contents, issue titles, PR bodies, and comments are all untrusted.
+  Afterburner never drops them into shell command strings or CI `run:` blocks. They go through
+  stdin and environment variables and get read via `process.env`. The invocation builder has
+  unit tests that feed it hostile input.
+- Blast radius. PR-only output, the `claude/` branch namespace, one task per run, and a repo
+  allowlist. The default branch can't be reached by design.
+- Spending. Dry-run default, a two-part opt-in for live runs, the both-caps budget gate with a
+  safety margin, a hard per-task token ceiling, and the Fable gate. The run store
+  (`afterburner log`) is an append-only record of what happened.
+- Secrets. Environment variables only (`.env.example` documents them). For subscription runs
+  the child process environment has API-key auth stripped out, so billing can't be quietly
+  hijacked.
+
+## Naming
+
+The short alias is `abr`, not `ab`. On most macOS and Linux systems `ab` is ApacheBench, and
+shadowing it would break benchmarking setups.
+
+## Roadmap (out of scope for now)
+
+Real PR creation and live `claude-code` execution, the live `api-key` backend, an OpenAI
+provider, prebuilt single binaries and a Homebrew tap (the build is set up so these are easy
+to add later), the MCP server beyond its stub, and any web dashboard or vendor notification
+integration. The `Notifier` interface is the seam for that last one.
+
+## Contributing and license
+
+See [CONTRIBUTING.md](./CONTRIBUTING.md) (and [DECISIONS.md](./DECISIONS.md) for the reasoning
+behind the less obvious choices), [SECURITY.md](./SECURITY.md), and
+[CODE_OF_CONDUCT.md](./CODE_OF_CONDUCT.md). Licensed under [Apache-2.0](./LICENSE).

package/afterburner.config.example.ts

@@ -0,0 +1,94 @@
+// Afterburner example configuration.
+//
+// Copy this to `afterburner.config.mjs` (gitignored, since your repo allowlist
+// is private) and adjust it. The contents are plain JS, so .mjs loads
+// everywhere, which is also why `afterburner init` writes .mjs. A .ts config
+// works too, but only where the `typescript` package is resolvable at runtime
+// (a project with typescript installed, not a bare global install).
+//
+// This file is deliberately dependency-free. With a local install of
+// afterburner you can get full type checking instead:
+//   import { defineConfig } from '@pimmesz/afterburner';
+//   export default defineConfig({ ... });
+const config = {
+  // Allowlist of repositories Afterburner may work on. Local paths work too;
+  // the built-in deterministic selector only scans local checkouts.
+  repos: [
+    {
+      url: 'https://github.com/your-name/your-repo',
+      defaultBranch: 'main',
+      // Must stay in the claude/ namespace so automation branches are
+      // unmistakable and the default branch is never touched.
+      branchPrefix: 'claude/',
+      enabledTaskCategories: ['docs', 'tests', 'dead-code'],
+    },
+  ],
+
+  budget: {
+    // How remaining budget is determined:
+    //   'manual':                  the manual block below.
+    //   'claude-code-transcripts': spend computed from local Claude Code
+    //                              sessions (~/.claude/projects), subtracted
+    //                              from the weekly allowance.
+    //   'claude-usage':            the real 5h/7d usage % and reset times
+    //                              Claude Code reports, captured via the
+    //                              statusLine hook (run `afterburner statusline
+    //                              install`). Most accurate; falls back to the
+    //                              transcript estimate when the cache is stale.
+    provider: 'manual',
+    // Your plan's total weekly capacity in Sonnet-equivalent tokens. Calibrate
+    // it once against /usage in Claude Code. Both automatic providers use it to
+    // turn a percentage into a token figure.
+    weeklyAllowanceSonnetTokens: 5_000_000,
+    // 'claude-usage' only: a cache older than this (hours) falls back to transcripts.
+    usageCacheMaxAgeHours: 12,
+    // Don't fire below this much of the weekly cap remaining.
+    minWeeklyHeadroomPct: 20,
+    // Keep this many Sonnet-equivalent tokens untouched on every decision.
+    safetyMarginTokens: 200_000,
+    // Also require a 5-hour session window to be available.
+    requireSessionAvailable: true,
+    // Inputs for the manual provider. There is no official API for remaining
+    // subscription quota, so check /usage in Claude Code and keep these roughly
+    // current (or override them per run with CLI flags). sessionAvailable is
+    // read here by the manual and claude-code-transcripts providers;
+    // claude-usage reads the real 5-hour window from its cache instead.
+    manual: {
+      sessionAvailable: true,
+      weeklyRemainingPct: 60,
+      weeklyRemainingTokensEst: 3_000_000,
+    },
+  },
+
+  schedule: {
+    cron: '17 */4 * * *',
+    timezone: 'UTC',
+  },
+
+  agent: {
+    // 'dry-run' (default, simulates everything), 'claude-code' (spends the
+    // subscription quota you already pay for), or 'api-key' (bills per token,
+    // real money). A live run also needs the --live flag (the two-part opt-in).
+    backend: 'dry-run',
+    // Per-category model routing. Plain strings on purpose, so a new model
+    // can't break the config. Omitted categories use the built-in defaults
+    // (sonnet for most, opus for perf and infra, haiku for the simple end).
+    modelByCategory: {
+      perf: 'claude-opus-4-8',
+      docs: 'claude-haiku-4-5',
+    },
+    // Upper bound for a single task, in Sonnet-equivalent tokens.
+    maxTaskTokens: 200_000,
+    // Fable-family models are gated: roughly 2x Opus against your limits, and
+    // outside promotional windows they bill usage credits at API rates.
+    allowFable: false,
+  },
+
+  // Per-category enable/disable plus a ranking weight (higher is more valuable).
+  taskCategories: {
+    docs: { enabled: true, weight: 1 },
+    tests: { enabled: true, weight: 4 },
+  },
+};
+
+export default config;

package/dist/chunk-2NSOEZWY.js

@@ -0,0 +1,11 @@
+// src/mcp/server.ts
+var MCP_STUB_MESSAGE = "The MCP server front-end is not implemented yet.\nUse the CLI (afterburner run-once / log / doctor) or the Claude Code skill (afterburner skill install).\nPlanned: an `afterburner mcp` stdio server exposing run-once, log, and doctor as MCP tools.";
+function startMcpServer() {
+  console.error(MCP_STUB_MESSAGE);
+  process.exit(1);
+}
+
+export {
+  MCP_STUB_MESSAGE,
+  startMcpServer
+};