headlesscode 1.0.2

package/ATTRIBUTION.md

@@ -0,0 +1,53 @@
+# ATTRIBUTION
+
+The following material in this repository is derived from
+**[Zoo Code](https://github.com/Zoo-Code-Org/Zoo-Code)** —
+`Zoo-Code-Org/Zoo-Code`, a Roo Code fork — and is used under the
+**Apache License, Version 2.0**:
+
+- **Prompt text** — the system prompt builder
+  (`src/vendor/zoo-code/src/core/prompts/system.ts`) and every prompt section
+  under `src/vendor/zoo-code/src/core/prompts/sections/` (TOOL USE, RULES,
+  OBJECTIVE, CAPABILITIES, MODES, SYSTEM INFORMATION, USER'S CUSTOM
+  INSTRUCTIONS, etc.), plus the built-in mode role definitions in
+  `src/vendor/zoo-code/types/mode.ts`.
+- **Tool schemas** — the OpenAI `ChatCompletionTool` JSON schema definitions in
+  `src/vendor/zoo-code/src/core/prompts/tools/native-tools/` (21 tools) and the
+  OpenAI ↔ Anthropic converters (`converters.ts`).
+- **Mode/rules loading logic** — `.roomodes` parsing/merging
+  (`src/vendor/zoo-code/src/core/config/CustomModesManager.ts`),
+  `.roo/rules-<slug>/`, `.roo/rules/`, and `AGENTS.md` splicing
+  (`src/vendor/zoo-code/src/core/prompts/sections/custom-instructions.ts`),
+  and the `.roo` directory discovery service
+  (`src/vendor/zoo-code/src/services/roo-config/`).
+- **Types and constants** — `ModeConfig`/`DEFAULT_MODES` and the tool/group
+  type definitions under `src/vendor/zoo-code/types/`.
+- **Checkpoints** — the shadow-git auto-commit mechanism
+  (`src/vendor/zoo-code/src/services/checkpoints/ShadowCheckpointService.ts`,
+  `RepoPerTaskCheckpointService.ts`, `types.ts`, `excludes.ts`, `index.ts`),
+  which snapshots the workspace into a hidden git repo (via `simple-git`)
+  after every tool-executing turn so edits can be reverted; see
+  `docs/checkpoints.md`.
+- **Diff-based editing** — the multi-search-replace fuzzy diff engine
+  (`src/vendor/zoo-code/src/core/diff/strategies/multi-search-replace.ts`,
+  a verbatim copy of `zoo-code/src/core/diff/strategies/multi-search-replace.ts`),
+  plus its pure helpers `zoo-code/src/utils/text-normalization.ts` and the
+  line-number helpers extracted from
+  `zoo-code/src/integrations/misc/extract-text.ts`, and the
+  `DEFAULT_DIFF_FUZZY_THRESHOLD` constant from
+  `zoo-code/packages/types/src/global-settings.ts`. These back the headless
+  harness's `apply_diff` tool (the tool schemas for `apply_diff` /
+  `search_replace` / `edit_file` were already vendored under
+  `src/vendor/zoo-code/src/core/prompts/tools/native-tools/`).
+
+Source: **https://github.com/Zoo-Code-Org/Zoo-Code**
+License: **Apache-2.0** · Copyright **2026 Zoo Code**.
+Inspection commit: `ca9b60fbc7b72a27352b0e2084271c28f2419f94`.
+
+A verbatim copy of the Apache License 2.0 is provided in
+[`LICENSE`](./LICENSE). The full inventory of vendored files, local shims, and
+excluded files is in
+[`src/vendor/zoo-code/VENDOR-NOTES.md`](./src/vendor/zoo-code/VENDOR-NOTES.md).
+
+This notice is provided in addition to — and does not modify — the terms of the
+Apache License 2.0.

package/CODE_OF_CONDUCT.md

@@ -0,0 +1,130 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our
+community a harassment-free experience for everyone, regardless of age, body
+size, visible or invisible disability, ethnicity, sex characteristics, gender
+identity and expression, level of experience, education, socio-economic
+status, nationality, personal appearance, race, religion, or sexual identity
+and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming,
+diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our
+community include:
+
+- Demonstrating empathy and kindness toward other people
+- Being respectful of differing opinions, viewpoints, and experiences
+- Giving and gracefully accepting constructive feedback
+- Accepting responsibility and apologizing to those affected by our mistakes,
+  and learning from the experience
+- Focusing on what is best not just for us as individuals, but for the
+  overall community
+
+Examples of unacceptable behavior include:
+
+- The use of sexualized language or imagery, and sexual attention or
+  advances of any kind
+- Trolling, insulting or derogatory comments, and personal or political
+  attacks
+- Public or private harassment
+- Publishing others' private information, such as a physical or email
+  address, without their explicit permission
+- Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards
+of acceptable behavior and will take appropriate and fair corrective action in
+response to any behavior that they deem inappropriate, threatening, offensive,
+or harmful.
+
+Community leaders have the right and responsibility to remove, edit, or reject
+comments, commits, code, wiki edits, issues, and other contributions that are
+not aligned to this Code of Conduct, and will communicate reasons for
+moderation decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies
+when an individual is officially representing the community in public spaces.
+Examples of representing our community include using an official e-mail
+address, posting via an official social media account, or acting as an
+appointed representative at an online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported to the community leaders responsible for enforcement at the
+repository maintainers (reachable via the email address on the
+[Capsize-Games/headlesscode](https://github.com/Capsize-Games/headlesscode)
+repository profile). All complaints will be reviewed and investigated promptly
+and fairly.
+
+All community leaders are obligated to respect the privacy and security of the
+reporter of any incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining
+the consequences for any action they deem in violation of this Code of
+Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed
+unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders, providing
+clarity around the nature of the violation and an explanation of why the
+behavior was inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series of
+actions.
+
+**Consequence**: A warning with consequences for continued behavior. No
+interaction with the people involved, including unsolicited interaction with
+those enforcing the Code of Conduct, for a specified period of time. This
+includes avoiding interactions in community spaces as well as external
+channels like social media. Violating these terms may lead to a temporary or
+permanent ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including
+sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public
+communication with the community for a specified period of time. No public or
+private interaction with the people involved, including unsolicited
+interaction with those enforcing the Code of Conduct, is allowed during this
+period. Violating these terms may lead to a permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community
+standards, including sustained inappropriate behavior, harassment of an
+individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within
+the community.
+
+## Attribution
+
+This Code of Conduct is adapted from the
+[Contributor Covenant](https://www.contributor-covenant.org), version 2.1,
+available at
+<https://www.contributor-covenant.org/version/2/1/code_of_conduct.html>.
+
+Community Impact Guidelines were inspired by
+[Mozilla's code of conduct enforcement ladder](https://github.com/mozilla/diversity).
+
+For answers to common questions about this Code of Conduct, see the FAQ at
+<https://www.contributor-covenant.org/faq>.

package/CONTRIBUTING.md

@@ -0,0 +1,107 @@
+# Contributing to headlesscode
+
+Thanks for contributing! This file covers how this repository is set up, how
+to run the verification bar, and what a merge-ready change looks like.
+
+## What this project is
+
+`headlesscode` is a standalone Node/TypeScript CLI that runs a headless
+coding-agent loop, ported from a VS Code extension (vendored verbatim under
+`src/vendor/zoo-code/`, Apache-2.0 — see `ATTRIBUTION.md`). There is **no
+build step**: everything runs directly via `tsx`. Read the docs in `docs/`
+before diving into a subsystem.
+
+## Security first
+
+This agent **executes arbitrary shell commands as the invoking user** — that
+is its core function. Read [`SECURITY.md`](./SECURITY.md) before running it
+unattended or pointing it at untrusted repositories, and never weaken the
+permission layer without a very explicit reason. If you are adding a feature
+that executes commands or reads secrets, think about the least-privilege
+story as part of the design, not after.
+
+## Setup
+
+```bash
+npm install          # tsx + typescript + deps; no build step needed
+npm test             # full suite (see "Test conventions" below)
+npm run typecheck    # npx tsc --noEmit
+```
+
+`node >= 18` is required (see `engines` in `package.json`).
+
+**Optional: the `browser_action` tool's tests.** `src/tools/__tests__/browser-action.test.ts`
+launches a real headless Chromium via Playwright. `npm install` only installs
+the `playwright` npm package, not the browser binary itself — run
+`npx playwright install chromium` once to enable those tests. Without it, the
+suite detects the missing binary, prints a clear skip message, and exits 0
+(this is treated as an environment gap, not a test failure — the rest of
+`npm test` still runs and still gates your change).
+
+## Test conventions
+
+- **No test framework.** The project deliberately uses no jest/mocha/vitest.
+  Tests are plain `.test.ts` files run directly via `tsx` with hand-rolled
+  assertions, and the file ends with an `All N tests passed` trailer line.
+  Look at any existing file under `src/*/__tests__/` for the exact style
+  before writing a new one.
+- **Discovery is automatic.** `npm test` runs `scripts/run-tests.mjs`, which
+  globs every `*.test.ts` under `src/` (plus a short explicit list of
+  non-test-suffixed check scripts) and runs them sequentially, fail-fast. A
+  new test file needs **zero** edits outside the file itself — do not add it
+  to `package.json` by hand.
+- **Verification bar for any change to `src/`:**
+  1. `npx tsc --noEmit` is clean (respect the strictness `tsconfig.json`
+     actually configures — no `any`, `@ts-ignore`, or `!` escapes).
+  2. `npm test` passes in full. A targeted run (`npm test -- <substring>` or
+     `npx tsx <test-file>`) is fine while iterating, but the full suite is
+     the gate.
+- **Orchestrator / watcher / spawn / worker changes** also re-run the
+  relevant suites under `scripts/e2e*/run.sh` — these exercise real
+  spawn/watch/review flows against a local mock LLM server, not just
+  unit-level logic.
+
+## Repository conventions
+
+- **No new runtime dependencies without a real reason.** The project
+  deliberately avoids frameworks and schema libraries for its own
+  state/JSON handling (plain `node:fs`/`node:http`, loose JSON validation).
+  Prefer the smallest dependency footprint that does the job; ask in the
+  issue/PR if you think a dependency is genuinely warranted.
+- **Non-fatal failure pattern for auxiliary subsystems.** Memory recording,
+  checkpoint saving, and usage/cost recording all follow the same idiom:
+  wrap in try/catch, log a warning via the session's logger, and never let a
+  failure in an auxiliary subsystem abort or corrupt the coding session.
+  Match that pattern when adding a new auxiliary write path.
+- **Vendoring convention.** Code ported from the upstream VS Code extension
+  lives under `src/vendor/zoo-code/`, copied verbatim wherever practical,
+  with a corresponding entry in `ATTRIBUTION.md`. VS Code API calls the
+  vendored code makes are satisfied by no-op shims under
+  `src/vendor/zoo-code/shim/`, wired via `tsconfig.json`'s `paths` — check
+  there before assuming something needs a new shim.
+- **Comments are minimal.** Only when the WHY is genuinely non-obvious.
+- **Docs vs. plans.** `docs/*.md` describes how a shipped subsystem works.
+  `plans/*.md` are standalone work orders for an external agent to execute —
+  each must be fully self-contained and must not reference internal-only
+  planning artifacts.
+- **Plan docs cite verified locations.** Every code reference in a
+  `plans/*.md` doc must include the real file path AND line
+  number/range (e.g. `src/checkpoints/cli.ts:12-30`), verified by actually
+  reading or grepping the file at writing time — never recalled from memory.
+
+## Working with issues
+
+- This repo is developed primarily through **headless workers in parallel git
+  worktrees** (see `scripts/spawn-parallel-worktrees.sh`). If you're
+  submitting a PR the normal way, the same conventions apply: one logical
+  change per commit, reference the issue number in the commit message and PR
+  body.
+- **Commit before you're done.** Real, working changes should be committed in
+  logical units; a PR is a series of reviewed, individually sensible commits,
+  not one giant diff.
+
+## Code of conduct
+
+All contributors and maintainers are expected to follow our
+[Code of Conduct](./CODE_OF_CONDUCT.md). Be respectful, be constructive, and
+assume good faith — this project is small and every contribution matters.

package/LICENSE

@@ -0,0 +1,202 @@
+                                 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 Zoo Code.
+   Copyright 2026 Capsize Games, Inc. and the headlesscode 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.