slice-tournament-zoo 0.5.6

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 Robert Li
+
+   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,357 @@
+<div align="center">
+
+# Slice Tournament Zoo (STZ)
+
+<pre>
+  ██████╗  ████████╗ ███████╗
+ ██╔════╝  ╚══██╔══╝ ╚══███╔╝
+ ╚█████╗      ██║      ███╔╝ 
+  ╚═══██╗     ██║     ███╔╝  
+ ██████╔╝     ██║    ███████╗
+ ╚═════╝      ╚═╝    ╚══════╝
+</pre>
+
+[![CI](https://github.com/dr-robert-li/slice-tournament-zoo/actions/workflows/ci.yml/badge.svg)](https://github.com/dr-robert-li/slice-tournament-zoo/actions/workflows/ci.yml)
+[![License: Apache 2.0](https://img.shields.io/badge/License-Apache_2.0-blue.svg)](./LICENSE)
+[![Node](https://img.shields.io/badge/node-%3E%3D20-brightgreen.svg)](./package.json)
+
+</div>
+
+> An agentic-coding harness for "software-engineering dark factories with
+> auditable outputs." Each slice is one interface contract plus its
+> implementation plus its tests, implemented adversarially by N **specimens**.
+> Survivors are selected by an eval-gate and a pairwise LLM judge against a
+> **frozen, sealed** test suite the implementers never see. Every run leaves a
+> markdown audit trail a human can replay.
+
+## Contents
+
+- [Requirements](#requirements)
+- [Install](#install)
+- [Use](#use)
+- [Example commands and workflows](#example-commands-and-workflows)
+- [Uninstall](#uninstall)
+- [The pipeline](#the-pipeline-two-levels)
+- [The audit tree](#the-stz-audit-tree)
+- [Documentation](#documentation)
+- [License](#license)
+
+## Requirements
+
+- Node.js 20 or newer.
+- For the in-session harness: Claude Code (the CLI, desktop, or web app).
+- No database, no vector service, no API keys beyond what Claude Code already
+  uses for its subagents.
+
+## Install
+
+STZ installs two ways: as a global CLI via **npm**, or as a **Claude Code
+plugin**. They are complementary — the plugin drives the in-session `/stz:*`
+commands, and the npm CLI gives you `stz init`, `stz run`, and direct
+`stz bridge` access. Installing the npm CLI also satisfies the plugin's bridge
+dependency without any `${CLAUDE_PLUGIN_ROOT}` fallback.
+
+### Via npm (global CLI)
+
+```bash
+npm i -g slice-tournament-zoo               # from npm
+# or install straight from GitHub (no npm publish needed):
+npm i -g dr-robert-li/slice-tournament-zoo
+```
+
+This puts `stz` on your `PATH` (`stz`, `stz init`, `stz run`, `stz bridge …`)
+and bundles its `tsx` runtime, so it works offline after install. Requires
+Node.js 20+. Run `stz` with no arguments to see the banner and commands.
+
+### As a Claude Code plugin
+
+From inside Claude Code, add the marketplace and install the plugin:
+
+```text
+/plugin marketplace add dr-robert-li/slice-tournament-zoo
+/plugin install stz
+```
+
+This registers the project commands (`/stz:new`, `/stz:research`, `/stz:validate`,
+`/stz:standards`, `/stz:tests`, `/stz:slice`, `/stz:summary`, `/stz:pipeline`,
+`/stz:merge`) and `/stz:run`, the subagents (the per-slice specimen, judge,
+test-author, cross-reference, documenter plus the project-level researcher,
+validator, conventions, test-planner, slicer, summarizer), and a SessionStart hook
+that announces STZ when a project contains a `.stz/` tree. Restart the session (or
+reload) so the definitions load.
+
+The plugin calls a bundled `stz bridge` CLI for every deterministic decision. If
+you installed the npm CLI above, the commands use that `stz` directly. Otherwise
+they resolve the bundled copy via `${CLAUDE_PLUGIN_ROOT}`, with no `PATH` setup
+needed (Node.js 20+ is the only requirement; the bundled copy fetches `tsx` via
+`npx` on first use, so that first call needs network).
+
+> Developing STZ itself, or running the engine without Claude Code? See
+> [`docs/development/local-and-testing.md`](./docs/development/local-and-testing.md).
+
+## Use
+
+### Scaffold a project
+
+```bash
+stz init .          # create the .stz/ taxonomy + AGENTS.md in the current repo
+```
+
+This writes the tiered `.stz/` tree (`00-intent` through `90-audit`) and an
+`AGENTS.md` table of contents. Nothing else is required to start.
+
+### The full pipeline (in Claude Code)
+
+`/stz:run` handles one slice. The full pipeline takes a project from an idea to a
+completion report, one command per phase (a get-shit-done-style UX):
+
+```text
+/stz:new        elicit intent + done-predicates + run config (batched Q&A)
+/stz:research   external (docs, prior art) + internal (codebase) research
+/stz:validate   ground-truth: verify each claim against reality, not recall
+/stz:standards  style, architecture, naming conventions
+/stz:tests      test strategy + coverage targets, locked BEFORE implementation
+/stz:slice      collaborative breakdown into a DAG of vertical slices
+/stz:run <id>   the adversarial tournament, once per slice
+/stz:summary    aggregate every document into one completion report
+```
+
+`/stz:pipeline` is a dashboard: it shows project-phase and per-slice status (plus
+the run config), then dispatches the recommended next step (and can run
+independent slices in parallel).
+
+#### Run configuration (set once, applied everywhere)
+
+`/stz:new` batches its questions per area and, at the end, captures a **run
+config** the rest of the pipeline obeys — stored in `.stz/00-intent/run-config.json`
+and surfaced by `stz bridge project-status` so every later command reads it in one
+call:
+
+| Choice | Set in `/stz:new` | Consumed by |
+|---|---|---|
+| **Slicing granularity** (`coarse`/`balanced`/`fine`) | area E | `/stz:slice` |
+| **Specimen fan-out** (N, 2–16) | area E | `/stz:run` (the number of specimens) |
+| **Model per role** (planning, research, execution, testing, validation, judging) | area E | each phase's subagent `model` |
+| **Strictness** (coverage target, mutation policy, conventions) | area E | `/stz:standards`, `/stz:tests` |
+
+Model choices follow the get-shit-done "Other" pattern: pick a suggested combo
+(Balanced / Thrifty / Max quality) or type your own spawn alias
+(`opus`/`sonnet`/`haiku`/`fable`) or model id. Anything unset falls back to a
+balanced default, so the pipeline always has a complete config.
+
+`--auto` means different things by scope, so keep the mental model straight:
+
+- `/stz:run slice-01` runs that one slice's tournament and nothing else.
+- `/stz:run slice-01 --auto` runs that one slice with no approval pause (it skips
+  the human winner-approval gate). It does **not** cascade to other slices.
+- The project phase commands (`/stz:new --auto`, `/stz:research --auto`, …) each
+  chain to the next phase.
+- `/stz:pipeline --auto` runs everything: it walks the DAG in dependency order,
+  fires `/stz:run` for each runnable slice (independent slices in the frontier in
+  parallel), and continues through to `/stz:summary`. This is the entry point for
+  "do the whole project automatically."
+
+Two human gates remain even in full auto: confirming a done-predicate in
+`/stz:new`, and approving the slice breakdown in `/stz:slice`.
+
+#### Dark-factory mode (lights-out, fully autonomous)
+
+`--auto` still pauses at those two human gates. **Dark-factory mode** goes one
+step further: it skips *every* downstream human gate — the `/stz:slice` approval
+and the `/stz:run` winner-approval — and runs the whole pipeline lights-out to a
+final `/stz:summary` completion report. The only gate it cannot skip is the F2
+done-predicate confirmation in `/stz:new`; acceptance criteria are never
+auto-invented. Everything the run decides (DAG, winners, GRPO advantages, hack
+findings) still lands in the `.stz/` audit tree for after-the-fact review.
+
+It is offered once at the end of elicitation (after the predicate gate) and can be
+flipped at any point:
+
+```bash
+stz bridge project-dark-factory --root . --on    # engage; --off to disengage
+```
+
+The toggle only flips the `darkFactory` flag in the run config — it never resets
+your fan-out / models / strictness. `project-status` hoists the flag to the top
+level, so engaging it between phases takes effect immediately. See
+[`docs/development/dark-factory.md`](docs/development/dark-factory.md) for the full
+contract.
+
+The DAG ordering and per-slice seeding are backed by the deterministic
+`stz bridge project-status` (which computes the runnable frontier). The `--auto`
+chaining itself is orchestration the agent follows from the command markdown, not
+a hard-coded loop.
+
+Each project-level phase writes its own `.stz/` tier and is settled once, before
+any slice runs. When `/stz:slice` seeds the DAG, each slice inherits those early
+phases as done, leaving only the tournament half for `/stz:run`. Project status
+is derived from each slice's own `state.json`, so an interrupted pipeline resumes
+by re-reading state. A worked run of the front phases (a `slugify` library) lives
+in [`examples/full-pipeline/`](./examples/full-pipeline).
+
+### Run a slice as a tournament (in Claude Code)
+
+```text
+/stz:run slice-01
+```
+
+You, the session, become the orchestrator. The command:
+
+1. Reads or elicits the slice manifest (the contract plus at least one
+   machine-checkable done-predicate). It refuses prose-only acceptance.
+2. Spawns a frozen **test-author** subagent to write the sealed held-out suite.
+3. Spawns N **specimen** subagents in parallel, each implementing the contract
+   with a different strategy.
+4. Runs the real eval runner over each specimen with `stz bridge eval`
+   (executed sealed suite, V8 coverage, mutation survival, hack-pattern
+   detection), then gates them.
+5. Spawns **judge** subagents for pairwise votes across the survivors.
+6. Selects a winner with `stz bridge select` (two-stage selection plus GRPO).
+7. Pauses for your approval of the winner, then spawns a **documenter** and
+   writes the spec-diff, pressure log, and audit journal.
+
+Every exact decision is made by the CLI, never by the agent's own arithmetic.
+
+## Example commands and workflows
+
+### A whole project (the full pipeline)
+
+Run the project-level phases once, let `/stz:slice` break the work into a DAG and
+seed the slices, then let `/stz:pipeline` drive each slice's tournament in
+dependency order:
+
+```text
+/stz:new          # elicit intent + done-predicates
+/stz:research     # external + internal research
+/stz:validate     # ground-truth the research
+/stz:standards    # conventions
+/stz:tests        # test strategy, before any code
+/stz:slice        # co-design the slice DAG; seeds 40-slices/<id> manifests
+/stz:pipeline     # dashboard: dispatches /stz:run for each slice in dep order
+/stz:summary      # completion report once the slices are done
+```
+
+You do not hand-author slice manifests or run `/stz:run` by hand here. `/stz:slice`
+creates the manifests and `/stz:pipeline` sequences the tournaments. To run the
+whole thing automatically, `/stz:pipeline --auto` walks the DAG and dispatches
+each slice through to the summary. (Note: `/stz:run --auto` is single-slice only;
+it just skips that slice's winner-approval pause and does not cascade.)
+
+### A single slice, standalone (no project)
+
+For a one-off slice without the project pipeline, `/stz:run <name>` elicits its
+own contract and one done-predicate if no manifest exists, runs the tournament,
+then you read the result:
+
+```text
+/stz:run payment-validator
+```
+
+```bash
+cat .stz/40-slices/payment-validator/spec-diff.md      # intent vs as-built
+cat .stz/50-pressure/payment-validator/pressure.md     # why the losers lost
+cat .stz/90-audit/journal.md                           # the replayable event log
+```
+
+### Inspect a worked example without running anything
+
+```bash
+# a real tournament (one slice)
+cat examples/clamp-tournament/stz-tree/40-slices/slice-01/tournament.md
+# a real project front-pipeline (slugify)
+cat examples/full-pipeline/stz-tree/90-audit/SUMMARY.md
+```
+
+`clamp-tournament`: four specimens implement `clamp`; a planted network-bypass
+cheater passes all 304 sealed checks but is disqualified at the gate; the winner
+is chosen by six judge votes and the highest GRPO advantage. `full-pipeline`: the
+project phases run for a `slugify` library through to a seeded slice DAG.
+
+## Uninstall
+
+### Remove the plugin
+
+```text
+/plugin uninstall stz
+/plugin marketplace remove dr-robert-li/slice-tournament-zoo
+```
+
+### Remove the CLI
+
+```bash
+npm unlink -g stz       # if you used `npm link`
+```
+
+### Remove harness data from a project
+
+The `.stz/` tree is the only thing STZ writes into your repo. Delete it to
+remove all harness state:
+
+```bash
+rm -rf .stz AGENTS.md
+```
+
+Nothing else is touched. There is no external state to clean up.
+
+## The pipeline (two levels)
+
+The pipeline runs at two levels. The **project level** settles intent, research,
+conventions, and test strategy once for the whole project. **Slice
+disaggregation** then breaks the work into a DAG and seeds each slice, marking
+those early phases done so they are not repeated. Each slice then runs only the
+**tournament half**.
+
+```text
+PROJECT (once):
+  elicit (/stz:new) -> research (/stz:research) -> ground-truth (/stz:validate)
+    -> standards (/stz:standards) -> test strategy (/stz:tests)
+    -> slice disaggregation (/stz:slice)  [seeds each slice; early phases done]
+
+PER SLICE (/stz:run <id>, sequenced by /stz:pipeline over the DAG):
+  test-author (frozen, sealed held-out suite)
+    -> spawn N specimens in parallel
+    -> eval-gate (sealed suite + coverage + mutation + hack-pattern detect)
+    -> judge (pairwise votes, GRPO group-relative advantage)
+    -> winner -> as-built spec -> spec-diff -> state.json checkpoint
+
+FINISH:
+  /stz:summary  -> completion report across every slice
+
+failure (bounded): no passers -> 1 GRPO retry -> 1 replan -> halt + report
+```
+
+Note: the standalone mock demo (`stz run`, no Claude Code) runs all eight phases
+inside a single slice for a self-contained, no-network smoke test. The two-level
+split above is the real in-session flow.
+
+## The `.stz/` audit tree
+
+| Tier | Purpose |
+| ---- | ------- |
+| `00-intent/` | project + intent manifests, elicitation, done-predicates |
+| `10-research/` | external/internal research, ground-truth validation |
+| `20-standards/` | versioned conventions, ADRs |
+| `30-tests/` | test strategy, rubric, sealed held-out suite |
+| `40-slices/` | the slice DAG, manifests, specimen prototypes, tournament, spec-diff |
+| `50-pressure/` | culled specimens' diffs and critiques (the pressure log) |
+| `90-audit/` | project state, journal, call ledger, cost, completion report, SUMMARY |
+
+## Documentation
+
+For contributors and anyone going past day-to-day operation:
+
+- **Contributing** — setup, the architecture rule, the quality bar:
+  [`CONTRIBUTING.md`](./CONTRIBUTING.md).
+- **Source layout** — the `src/` module map: [`src/README.md`](./src/README.md).
+- **Local development & testing** — run the engine without Claude Code, the mock
+  pipeline, CI checks: [`docs/development/local-and-testing.md`](./docs/development/local-and-testing.md).
+- **The bridge CLI** — the deterministic `stz bridge` subcommands:
+  [`docs/development/bridge-cli.md`](./docs/development/bridge-cli.md).
+- **Sealed-suite integrity** — the guide-vs-sensor contract behind the frozen
+  held-out suite: [`docs/development/sealed-suite.md`](./docs/development/sealed-suite.md).
+- **Requirement-to-test mapping** — [`docs/TESTPLAN.md`](./docs/TESTPLAN.md).
+- **What is real versus deferred** — [`docs/AS-BUILT.md`](./docs/AS-BUILT.md).
+
+## License
+
+[Apache-2.0](./LICENSE).

package/bin/stz.mjs

@@ -0,0 +1,15 @@
+#!/usr/bin/env node
+// npx stz entrypoint. Runs the TS CLI via tsx so the package needs no build
+// step (N10: minimal toolchain). For a published build this would point at
+// compiled dist/cli.js; for the source-available template repo, tsx is fine.
+import { spawnSync } from "node:child_process";
+import { fileURLToPath } from "node:url";
+import { dirname, join } from "node:path";
+
+const here = dirname(fileURLToPath(import.meta.url));
+const cli = join(here, "..", "src", "cli.ts");
+const r = spawnSync("npx", ["tsx", cli, ...process.argv.slice(2)], {
+  stdio: "inherit",
+  shell: process.platform === "win32",
+});
+process.exit(r.status ?? 1);

package/package.json

@@ -0,0 +1,35 @@
+{
+  "name": "slice-tournament-zoo",
+  "version": "0.5.6",
+  "description": "STZ: a contract-bounded slice pipeline that implements each slice adversarially via an N-specimen tournament with frozen sealed tests, GRPO-style selection, layered anti-reward-hacking, and a replayable markdown audit trail.",
+  "license": "Apache-2.0",
+  "type": "module",
+  "bin": {
+    "stz": "bin/stz.mjs"
+  },
+  "exports": {
+    ".": "./src/index.ts"
+  },
+  "files": [
+    "src",
+    "bin"
+  ],
+  "scripts": {
+    "stz": "tsx src/cli.ts",
+    "test": "vitest run",
+    "test:watch": "vitest",
+    "typecheck": "tsc --noEmit",
+    "prepublishOnly": "npm run typecheck && npm test"
+  },
+  "engines": {
+    "node": ">=20"
+  },
+  "dependencies": {
+    "tsx": "^4.19.0"
+  },
+  "devDependencies": {
+    "@types/node": "^22.10.0",
+    "typescript": "^5.7.0",
+    "vitest": "^2.1.0"
+  }
+}

package/src/README.md

@@ -0,0 +1,19 @@
+# Module map (`src/`)
+
+Production spine: `types.ts` (schema), `taxonomy.ts` (tree and frontmatter),
+`state.ts` (checkpoint and recovery), `grpo.ts`, `selection.ts`,
+`hack-detector.ts`, `escalation.ts`, `budget.ts`, `cost-tracker.ts`,
+`pressure.ts`, `specdiff.ts`, `eval-runner.ts` (real tests, coverage, mutation),
+`project.ts` (the project DAG driver), and `bridge.ts` (the in-session CLI,
+per-slice and project subcommands).
+
+The `mock/` subfolder is the no-network testing harness (the `stz run` demo):
+its orchestrator, the model-layer seam, and the deterministic mock. Not part of
+the production path — see [`mock/`](./mock).
+
+## Further reading
+
+- The requirement-to-test mapping is in [`docs/TESTPLAN.md`](../docs/TESTPLAN.md).
+- What is real versus deferred is in [`docs/AS-BUILT.md`](../docs/AS-BUILT.md).
+- Running the engine locally / in CI: [`docs/development/local-and-testing.md`](../docs/development/local-and-testing.md).
+- The deterministic bridge CLI: [`docs/development/bridge-cli.md`](../docs/development/bridge-cli.md).