@defrex/autobuild 0.8.0

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 Aron Jones
+
+   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,192 @@
+<div align="center">
+
+# Autobuild
+
+**Tickets in, PRs out. No babysitting required.**
+
+</div>
+
+Every build runs headless, so ten tickets in flight cost the same 
+attention as one. You groom tickets in, you review pull requests out. 
+Agents do the work, and deterministic code keeps them honest.
+
+![The autobuild dispatch dashboard with four builds in flight, each partway
+through the pipeline](docs/assets/headline-wide.png)
+
+## Groomed ticket in, reviewed PR out
+
+Running several coding agents by hand doesn't scale well. Every session wants
+prompts, permissions, and attention, and your focus becomes the ceiling.
+With Autobuild, each build runs the whole loop headlessly and escalates only
+when it is truly blocked. With attention off the critical path, throughput
+is only limited by how fast you can write good tickets.
+
+Headless is safe because the pipeline is deterministic code, not model
+judgment. State lives in a typed, append-only event log, phase transitions
+are owned by tested code, and every build leaves a queryable paper trail. Your
+merge gates are never bypassed: a PR lands when your required checks and your
+consent say it lands.
+
+The loop also feeds itself. While building, agents record observations —
+latent bugs, worthwhile refactors, follow-ups they noticed but rightly left
+alone. A harvester distills them into proposed tickets and files them for
+triage; approve one and it runs the same loop.
+
+Every seam is an adapter: ticket sources (the hosted service with database or
+Linear backend, direct Linear, local files, or a configured plugin), agent runtimes (Claude, Codex, Pi, or a configured plugin), the forge
+(GitHub via `gh`, credential-free local Git, or a configured plugin), workspaces,
+and the build store all sit behind
+narrow interfaces. Trusted Bun plugins declared in `autobuild.toml` can register
+third-party ticket, runtime, workspace, and forge adapters against the versioned
+`@defrex/autobuild/plugin-sdk` surface. Repositories may also opt into the shipped
+`vercel-sandbox` workspace provider: the complete build runs in an isolated
+Vercel VM while the local supervisor retains credentialed branch/PR publication.
+The default remains a local Git worktree. See the [workspace configuration and
+security contract](docs/configuration.md#vercel-sandbox).
+Teams that need one durable store across hosts
+can deploy the optional [hosted service](packages/hosted-store-service/README.md),
+which also serves a GitHub-authenticated browser dashboard, can own ticket
+persistence and external tracker credentials, and can run the dispatcher itself on a schedule (see [the hosted dispatcher](docs/hosted-dispatcher.md)). Repository identity across the
+Store, dispatcher, query commands, and that dashboard is the repository's
+normalized origin URL (e.g. `https://github.com/defrex/autobuild`), never a
+checkout path; pre-origin records are not migrated. The web UI uses a server-managed
+session; automation clients can use the versioned [operator API](docs/operator-api.md)
+for the same controls and projections without exposing service credentials, and
+external MCP agents connect through the [hosted MCP server](docs/mcp.md).
+
+## Quickstart
+
+You need [Bun](https://bun.sh), `git`, and the local prerequisites for the
+agent runtime you select: Claude Code, Codex CLI, or Pi. Choosing the GitHub
+forge also requires an authenticated [`gh` CLI](https://cli.github.com)
+(`gh auth login`) or an exported `GITHUB_TOKEN`/`GH_TOKEN`; the local-git forge needs no
+account or remote.
+Init suggests only runtimes whose executable and/or provider authentication is
+usable on your machine.
+
+<!-- release-install:start -->
+
+```sh
+bun add -g @defrex/autobuild@0.8.0
+```
+
+<!-- release-install:end -->
+
+Then, from the repository you want built:
+
+```sh
+ab init
+```
+
+Vendors the editable `ab-*` skills, writes a stack-neutral config, and hands
+repository-aware setup to a coding agent. Follow the canonical
+[installation and setup procedure](docs/setup.md) to keep local worktrees or
+explicitly configure Vercel, then commit the setup and check its real execution
+environment without creating build history:
+
+```sh
+ab init --validate
+```
+
+See the [configuration reference](docs/configuration.md) for every field. Only
+a clean readiness result should be followed by:
+
+```sh
+ab dispatch
+```
+
+Starts the dispatcher, with the live dashboard on a TTY.
+
+In your selected coding agent, invoke the ticket-grooming skill:
+
+```text
+/ab-spec I want to build a feature!
+```
+
+The agent asks the questions needed to produce a quality ticket and adds it
+directly to your ticketing system. Using the skill to create tickets then
+largely becomes your input workflow.
+
+## How it works
+
+Every build moves through the same fixed pipeline:
+
+```text
+spec → plan ⇄ plan-review → implement ⇄ code-review → verify:* → finalize
+      epilogue: (pr.conflicted → reconcile → verify:*)* → merged or closed
+```
+
+1. **spec** — the dispatcher claims a ready ticket, establishes the final
+   spec, and cuts a branch. The spec is the contract for everything after.
+2. **plan ⇄ plan-review** — a planner writes an implementation plan; an
+   independent reviewer approves it or sends it back with findings.
+3. **implement ⇄ code-review** — the same shape over commits: implement,
+   review, revise. A finding that survives round after round escalates to
+   you instead of looping forever.
+4. **verify:\*** — your verification steps, in the order you declare them:
+   shell commands judged by exit code, or agent verifiers that return a
+   verdict.
+5. **finalize** — the PR opens with an agent-written description and a summary
+   of explicitly attached evidence, then any post-PR steps you've configured
+   (changelogs, release notes) run failure-tolerant. A content-producing step
+   commits selected files locally; the runner extends the open PR branch with
+   a regular push. A no-op adds no commit, and a publication failure becomes a
+   follow-up observation rather than failing the green build. Agent verifiers
+   attach an exact screenshot, trace, or other artifact with
+   `ab artifact put <kind> <file> --attach`; the PR always gets a pinned
+   retrieval command, and configured public image hosting can also render
+   images inline.
+6. **epilogue** — the dispatcher watches the open PR. Conflicts route back
+   through reconcile and re-verify; the build ends `merged` or `closed`.
+
+Each phase is an agent session, but the pipeline itself is not agentic:
+agents never decide what phase comes next, and outcomes are never inferred
+from what a model printed. Every phase reports through a typed CLI into an
+append-only event log, and tested code decides the transition. That log is
+the build — kill the process at any point and the dispatcher resumes from
+durable state, and every decision along the way stays queryable after the
+fact.
+
+The pipeline grammar is fixed on purpose; `verify:*` and `finalize:*` are the
+extension points, declared per-repo in `autobuild.toml`. Post-step agents may
+commit locally but never push or call the forge; publication stays
+kernel-owned. For the seams and the reasoning behind them, see
+[`docs/architecture.md`](docs/architecture.md) and [`SPEC.md`](SPEC.md).
+
+### Observation harvesting
+
+Builds notice things they shouldn't fix. An implementer that spots a latent
+bug, a worthwhile refactor, or a missing follow-up outside its spec records a
+structured observation (`ab observe`) and moves on — the insight is kept, and
+scope creep stays out of the PR.
+
+Observations accumulate per repository, and once enough pile up the
+dispatcher runs a separate outer workflow — scan → synthesize ⇄ review →
+file — that distills them into proposed tickets, deduplicated against work
+already filed. By default, proposals land in triage with the reserved
+`autobuild:proposal` label and never dispatch themselves: the label means
+observation harvest created the ticket for human triage, not that Autobuild has
+groomed or claimed it. Autobuild does not use this label as a readiness gate or
+remove it; it is distinct from any configured or historical `autobuild` ready
+label. You groom and ready proposals like any ticket you wrote yourself. Agents
+propose; humans dispatch.
+
+## Learn more
+
+- [`docs/spec-standard.md`](docs/spec-standard.md) — what makes a ticket
+  buildable: the standard every dispatched spec must meet.
+- [`docs/configuration.md`](docs/configuration.md) — the complete strict
+  `autobuild.toml` schema and examples.
+- [`autobuild.toml`](autobuild.toml) — this repository's own pipeline
+  configuration, as a worked example of the config surface.
+- [`docs/architecture.md`](docs/architecture.md) — how the design maps to the
+  codebase: kernel, ports, processes, and stores.
+- [`packages/postgres-store/README.md`](packages/postgres-store/README.md) — serverless PostgreSQL persistence with S3-compatible or Vercel Blob storage.
+- [`docs/remote-store-protocol.md`](docs/remote-store-protocol.md) — the
+  complete HTTP server contract and BuildStore conformance instructions.
+- [`SPEC.md`](SPEC.md) — the source of truth for the design and its
+  terminology.
+
+## License
+
+[Apache License 2.0](LICENSE).