codex-harness-kit 0.1.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 [yyyy] [name of copyright owner]
+
+   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,279 @@
+# codex-harness-kit
+
+`codex-harness-kit` is a lightweight CLI plus scaffold for making any repository easier to run with a harness-style Codex workflow.
+
+It does not try to become a new agent platform. v1 is intentionally small and only helps with five things:
+
+1. state recovery
+2. project memory
+3. decision logging
+4. task contracts
+5. a minimal validation entrypoint
+
+## What Problem It Solves
+
+Long Codex tasks break down when context lives only in chat history. New threads lose the current goal, scope drifts mid-task, repeated failures trigger more guessing, and important decisions disappear.
+
+This toolkit moves the durable parts of the workflow into repository files so a new thread can recover context from the repo itself before writing code.
+
+## Why It Fits Long Tasks and Multi-Thread Collaboration
+
+The harness files make the repo readable by both humans and Codex:
+
+- `docs/harness-state.json` stores the current goal, status, blockers, contract, and last verification result.
+- `docs/project-memory.md` stores durable preferences and recurring pitfalls.
+- `docs/decisions.md` stores explicit trade-offs and decisions.
+- `docs/contracts/` stores task contracts with acceptance and validation notes.
+- `AGENTS.md` is the active instruction source. In repos that already have a custom `AGENTS.md`, the tool adds a small activation bridge there and writes the detailed harness rules to `AGENTS.harness.md`.
+
+That means a new thread can start with repository context instead of trying to reconstruct intent from old messages.
+
+## Non-Goals
+
+v1 deliberately does not include:
+
+- multi-agent orchestration
+- a background daemon
+- a web UI
+- a database
+- cloud services
+- automatic file watching
+- plugin or MCP ecosystems
+- a new chat interface
+
+## Install and Run
+
+This repository is npm-ready. If you are using the source repo directly, use the local development path below. After the package is published, the npm install path becomes available.
+
+Published package, after release:
+
+```bash
+npx codex-harness-kit init
+```
+
+Local development from this repository:
+
+```bash
+npm install
+npm run build
+node dist/src/cli.js --help
+```
+
+Or link the local checkout:
+
+```bash
+npm link
+codex-harness-kit --help
+```
+
+## CLI Commands
+
+```bash
+codex-harness-kit init [path] [--force]
+codex-harness-kit check-state [path]
+codex-harness-kit validate-harness [path]
+```
+
+### `init`
+
+Generates the minimal harness files in the current directory or a target path.
+
+Files created by default:
+
+- `AGENTS.md`
+- `docs/harness-config.json`
+- `docs/harness-state.json`
+- `docs/project-memory.md`
+- `docs/decisions.md`
+- `docs/contracts/README.md`
+- `docs/contracts/example-contract.md`
+
+When the target repo already has its own `AGENTS.md`, `init` also writes:
+
+- `AGENTS.harness.md`
+
+Safety behavior:
+
+- Existing files are not overwritten by default.
+- Re-running `init` is safe and mostly results in `unchanged` or `skipped` outcomes.
+- If the target repo already has an `AGENTS.md`, this tool preserves the existing content and appends a marker-based activation bridge to that file.
+- In that same case, the detailed harness rules are written to `AGENTS.harness.md`.
+- Re-running `init` does not duplicate the bridge block.
+- Use `--force` only when you explicitly want harness-managed files overwritten.
+
+### `check-state`
+
+Reads the harness config and state, then prints a concise summary:
+
+- current goal
+- current status
+- current contract
+- blockers
+- most recent verification result
+- next step suggestion
+
+If files are missing or invalid, it prints a clear error plus a recovery hint.
+
+### `validate-harness`
+
+Checks that the key harness files exist, required JSON is valid, required fields are present, and the harness is actually activated in `AGENTS.md`.
+
+It does not stop at marker detection. The validator also checks that the codex-harness-kit bridge block and harness block still contain non-empty, recognizable activation/workflow content.
+
+That means `validate-harness` now fails when:
+
+- there is a plain `AGENTS.md` with no codex-harness-kit block
+- `AGENTS.harness.md` exists but `AGENTS.md` does not bridge or merge it
+- the bridge exists but the harness supplement file is missing or malformed
+- the bridge or harness markers still exist, but their actual instructions were hand-edited away and left as empty shells
+
+## Initialize an Empty Repo
+
+Fastest first-use path after installation:
+
+```bash
+codex-harness-kit init
+codex-harness-kit check-state
+codex-harness-kit validate-harness
+```
+
+Inside the target repository:
+
+```bash
+codex-harness-kit init
+```
+
+Or from elsewhere:
+
+```bash
+codex-harness-kit init /path/to/repo
+```
+
+## Initialize an Existing Repo
+
+Run the same `init` command in the existing repo.
+
+If the repo already has its own `AGENTS.md`, the tool:
+
+1. preserves the existing content
+2. appends a clearly marked codex-harness-kit activation bridge to `AGENTS.md`
+3. writes the detailed harness workflow to `AGENTS.harness.md`
+
+This keeps the repo safe and readable while still making the harness an active instruction source instead of an ignored sidecar.
+
+## What Counts as "Harness Activated"
+
+The harness is considered activated only when `AGENTS.md` explicitly includes codex-harness-kit instructions.
+
+There are two valid states:
+
+1. `AGENTS.md` contains the full codex-harness-kit harness block.
+2. `AGENTS.md` contains the codex-harness-kit bridge block and that bridge points to a valid `AGENTS.harness.md`.
+
+Having an unrelated `AGENTS.md` file is not enough. Having only `AGENTS.harness.md` is not enough either.
+
+## What to Tell Codex After Initialization
+
+These prompts are intentionally simple. The harness files carry the durable details.
+
+Minimal examples:
+
+- `恢复状态并继续`
+- `先更新 contract，再实现`
+- `先别改代码，告诉我当前阻塞`
+- `把这个决定记进项目记忆`
+
+Equivalent English examples:
+
+- `Restore state and continue.`
+- `Update the contract first, then implement.`
+- `Do not change code yet; tell me the current blockers.`
+- `Write this decision into project memory.`
+
+## Recommended Codex Workflow
+
+1. Start by restoring state from the harness files.
+2. Update the contract if scope or acceptance changed.
+3. Implement only the scoped task.
+4. Run the smallest meaningful validation command.
+5. Update state, memory, or decisions before ending the thread.
+
+## Customizing Validation Commands
+
+Edit `docs/harness-config.json` after initialization:
+
+```json
+{
+  "commands": {
+    "verifyQuick": "npm test",
+    "verifyFull": "npm run verify",
+    "docsGenerate": ""
+  }
+}
+```
+
+`check-state` and the `AGENTS` rules assume these commands describe the repo's minimal and fuller validation steps.
+
+## Path Configuration and Recovery
+
+The fixed entrypoint is `docs/harness-config.json`.
+
+The `AGENTS` instructions intentionally tell Codex to read that config first, then follow:
+
+- `paths.stateFile`
+- `paths.memoryFile`
+- `paths.decisionsFile`
+- `paths.contractsDir`
+
+So if you later move the state or memory files, update `docs/harness-config.json` and the harness instructions still hold. The active contract path in the state file should also be updated if contract files move.
+
+## If Initialization Did Not Activate the Harness
+
+Run:
+
+```bash
+codex-harness-kit validate-harness
+```
+
+If validation fails on activation:
+
+1. rerun `codex-harness-kit init`
+2. check that `AGENTS.md` contains the codex-harness-kit block or bridge markers
+3. if the repo uses a bridge, check that `AGENTS.harness.md` exists and still contains the harness-managed block
+
+## Using It in Other Projects
+
+Until this package is published, the simplest options are:
+
+1. clone this repo
+2. run `npm install && npm run build`
+3. use `node /path/to/codex-harness-kit/dist/src/cli.js init /path/to/target-repo`
+
+Or link it globally with `npm link`.
+
+## Assumptions in v1
+
+- The default layout uses `docs/` because it stays readable in ordinary repos.
+- JSON stays intentionally small and explicit instead of introducing a DSL.
+- Validation commands are configured by the repository owner; the toolkit does not guess them.
+
+## Development
+
+```bash
+npm run build
+npm run typecheck
+npm test
+npm run verify
+```
+
+`npm run verify` currently runs:
+
+1. TypeScript typecheck
+2. build
+3. Node built-in tests
+
+## Current Limitations
+
+- `check-state` summarizes the active contract path and title, but it does not parse acceptance criteria yet.
+- `validate-harness` only validates the minimal v1 file set.
+- The CLI does not edit state or contracts for you; it scaffolds and validates the workflow.

package/dist/src/cli.d.ts

@@ -0,0 +1,2 @@
+#!/usr/bin/env node
+export declare function runCli(argv?: string[]): Promise<number>;

package/dist/src/cli.js

@@ -0,0 +1,84 @@
+#!/usr/bin/env node
+import { realpathSync } from "node:fs";
+import { fileURLToPath } from "node:url";
+import { initializeHarness, renderInitResult } from "./commands/init.js";
+import { runCheckState } from "./commands/check-state.js";
+import { runValidateHarness } from "./commands/validate-harness.js";
+export async function runCli(argv = process.argv.slice(2)) {
+    const [command, ...rest] = argv;
+    if (!command || command === "--help" || command === "-h") {
+        process.stdout.write(`${renderHelp()}\n`);
+        return 0;
+    }
+    const parsed = parseArgs(rest);
+    const targetPath = parsed.positionals[0];
+    switch (command) {
+        case "init": {
+            const result = await initializeHarness({
+                targetPath,
+                force: parsed.flags.has("force")
+            });
+            process.stdout.write(`${renderInitResult(result)}\n`);
+            return 0;
+        }
+        case "check-state": {
+            const result = await runCheckState(targetPath ?? process.cwd());
+            const stream = result.ok ? process.stdout : process.stderr;
+            stream.write(`${result.output}\n`);
+            return result.ok ? 0 : 1;
+        }
+        case "validate-harness": {
+            const result = await runValidateHarness(targetPath ?? process.cwd());
+            const stream = result.ok ? process.stdout : process.stderr;
+            stream.write(`${result.output}\n`);
+            return result.ok ? 0 : 1;
+        }
+        default:
+            process.stderr.write(`Unknown command: ${command}\n\n${renderHelp()}\n`);
+            return 1;
+    }
+}
+function parseArgs(argv) {
+    const positionals = [];
+    const flags = new Set();
+    for (const arg of argv) {
+        if (arg.startsWith("--")) {
+            flags.add(arg.slice(2));
+        }
+        else {
+            positionals.push(arg);
+        }
+    }
+    return { positionals, flags };
+}
+function renderHelp() {
+    return `codex-harness-kit
+
+Usage:
+  codex-harness-kit init [path] [--force]
+  codex-harness-kit check-state [path]
+  codex-harness-kit validate-harness [path]
+
+Commands:
+  init              Generate the minimal harness files for a repository.
+  check-state       Read the harness files and print a concise status summary.
+  validate-harness  Validate required harness files and JSON structure.`;
+}
+const isDirectExecution = isExecutedDirectly();
+if (isDirectExecution) {
+    runCli().then((code) => {
+        process.exitCode = code;
+    });
+}
+function isExecutedDirectly() {
+    if (process.argv[1] === undefined) {
+        return false;
+    }
+    try {
+        return realpathSync(process.argv[1]) === realpathSync(fileURLToPath(import.meta.url));
+    }
+    catch {
+        return fileURLToPath(import.meta.url) === process.argv[1];
+    }
+}
+//# sourceMappingURL=cli.js.map

package/dist/src/cli.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"cli.js","sourceRoot":"","sources":["../../src/cli.ts"],"names":[],"mappings":";AAEA,OAAO,EAAE,YAAY,EAAE,MAAM,SAAS,CAAC;AACvC,OAAO,EAAE,aAAa,EAAE,MAAM,UAAU,CAAC;AAEzC,OAAO,EAAE,iBAAiB,EAAE,gBAAgB,EAAE,MAAM,oBAAoB,CAAC;AACzE,OAAO,EAAE,aAAa,EAAE,MAAM,2BAA2B,CAAC;AAC1D,OAAO,EAAE,kBAAkB,EAAE,MAAM,gCAAgC,CAAC;AAOpE,MAAM,CAAC,KAAK,UAAU,MAAM,CAAC,IAAI,GAAG,OAAO,CAAC,IAAI,CAAC,KAAK,CAAC,CAAC,CAAC;IACvD,MAAM,CAAC,OAAO,EAAE,GAAG,IAAI,CAAC,GAAG,IAAI,CAAC;IAEhC,IAAI,CAAC,OAAO,IAAI,OAAO,KAAK,QAAQ,IAAI,OAAO,KAAK,IAAI,EAAE,CAAC;QACzD,OAAO,CAAC,MAAM,CAAC,KAAK,CAAC,GAAG,UAAU,EAAE,IAAI,CAAC,CAAC;QAC1C,OAAO,CAAC,CAAC;IACX,CAAC;IAED,MAAM,MAAM,GAAG,SAAS,CAAC,IAAI,CAAC,CAAC;IAC/B,MAAM,UAAU,GAAG,MAAM,CAAC,WAAW,CAAC,CAAC,CAAC,CAAC;IAEzC,QAAQ,OAAO,EAAE,CAAC;QAChB,KAAK,MAAM,CAAC,CAAC,CAAC;YACZ,MAAM,MAAM,GAAG,MAAM,iBAAiB,CAAC;gBACrC,UAAU;gBACV,KAAK,EAAE,MAAM,CAAC,KAAK,CAAC,GAAG,CAAC,OAAO,CAAC;aACjC,CAAC,CAAC;YACH,OAAO,CAAC,MAAM,CAAC,KAAK,CAAC,GAAG,gBAAgB,CAAC,MAAM,CAAC,IAAI,CAAC,CAAC;YACtD,OAAO,CAAC,CAAC;QACX,CAAC;QACD,KAAK,aAAa,CAAC,CAAC,CAAC;YACnB,MAAM,MAAM,GAAG,MAAM,aAAa,CAAC,UAAU,IAAI,OAAO,CAAC,GAAG,EAAE,CAAC,CAAC;YAChE,MAAM,MAAM,GAAG,MAAM,CAAC,EAAE,CAAC,CAAC,CAAC,OAAO,CAAC,MAAM,CAAC,CAAC,CAAC,OAAO,CAAC,MAAM,CAAC;YAC3D,MAAM,CAAC,KAAK,CAAC,GAAG,MAAM,CAAC,MAAM,IAAI,CAAC,CAAC;YACnC,OAAO,MAAM,CAAC,EAAE,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC;QAC3B,CAAC;QACD,KAAK,kBAAkB,CAAC,CAAC,CAAC;YACxB,MAAM,MAAM,GAAG,MAAM,kBAAkB,CAAC,UAAU,IAAI,OAAO,CAAC,GAAG,EAAE,CAAC,CAAC;YACrE,MAAM,MAAM,GAAG,MAAM,CAAC,EAAE,CAAC,CAAC,CAAC,OAAO,CAAC,MAAM,CAAC,CAAC,CAAC,OAAO,CAAC,MAAM,CAAC;YAC3D,MAAM,CAAC,KAAK,CAAC,GAAG,MAAM,CAAC,MAAM,IAAI,CAAC,CAAC;YACnC,OAAO,MAAM,CAAC,EAAE,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC;QAC3B,CAAC;QACD;YACE,OAAO,CAAC,MAAM,CAAC,KAAK,CAAC,oBAAoB,OAAO,OAAO,UAAU,EAAE,IAAI,CAAC,CAAC;YACzE,OAAO,CAAC,CAAC;IACb,CAAC;AACH,CAAC;AAED,SAAS,SAAS,CAAC,IAAc;IAC/B,MAAM,WAAW,GAAa,EAAE,CAAC;IACjC,MAAM,KAAK,GAAG,IAAI,GAAG,EAAU,CAAC;IAEhC,KAAK,MAAM,GAAG,IAAI,IAAI,EAAE,CAAC;QACvB,IAAI,GAAG,CAAC,UAAU,CAAC,IAAI,CAAC,EAAE,CAAC;YACzB,KAAK,CAAC,GAAG,CAAC,GAAG,CAAC,KAAK,CAAC,CAAC,CAAC,CAAC,CAAC;QAC1B,CAAC;aAAM,CAAC;YACN,WAAW,CAAC,IAAI,CAAC,GAAG,CAAC,CAAC;QACxB,CAAC;IACH,CAAC;IAED,OAAO,EAAE,WAAW,EAAE,KAAK,EAAE,CAAC;AAChC,CAAC;AAED,SAAS,UAAU;IACjB,OAAO;;;;;;;;;;wEAU+D,CAAC;AACzE,CAAC;AAED,MAAM,iBAAiB,GAAG,kBAAkB,EAAE,CAAC;AAE/C,IAAI,iBAAiB,EAAE,CAAC;IACtB,MAAM,EAAE,CAAC,IAAI,CAAC,CAAC,IAAI,EAAE,EAAE;QACrB,OAAO,CAAC,QAAQ,GAAG,IAAI,CAAC;IAC1B,CAAC,CAAC,CAAC;AACL,CAAC;AAED,SAAS,kBAAkB;IACzB,IAAI,OAAO,CAAC,IAAI,CAAC,CAAC,CAAC,KAAK,SAAS,EAAE,CAAC;QAClC,OAAO,KAAK,CAAC;IACf,CAAC;IAED,IAAI,CAAC;QACH,OAAO,YAAY,CAAC,OAAO,CAAC,IAAI,CAAC,CAAC,CAAC,CAAC,KAAK,YAAY,CAAC,aAAa,CAAC,MAAM,CAAC,IAAI,CAAC,GAAG,CAAC,CAAC,CAAC;IACxF,CAAC;IAAC,MAAM,CAAC;QACP,OAAO,aAAa,CAAC,MAAM,CAAC,IAAI,CAAC,GAAG,CAAC,KAAK,OAAO,CAAC,IAAI,CAAC,CAAC,CAAC,CAAC;IAC5D,CAAC;AACH,CAAC"}

package/dist/src/commands/check-state.d.ts

@@ -0,0 +1,4 @@
+export declare function runCheckState(repoRoot: string): Promise<{
+    ok: boolean;
+    output: string;
+}>;

package/dist/src/commands/check-state.js

@@ -0,0 +1,15 @@
+import { buildStateSummary, renderValidationReport, validateHarness } from "../harness.js";
+export async function runCheckState(repoRoot) {
+    const report = await validateHarness(repoRoot);
+    if (!report.ok) {
+        return {
+            ok: false,
+            output: `${renderValidationReport(report)}\n\nFix the errors above, then rerun \`codex-harness-kit check-state\`.`
+        };
+    }
+    return {
+        ok: true,
+        output: await buildStateSummary(repoRoot)
+    };
+}
+//# sourceMappingURL=check-state.js.map

package/dist/src/commands/check-state.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"check-state.js","sourceRoot":"","sources":["../../../src/commands/check-state.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,iBAAiB,EAAE,sBAAsB,EAAE,eAAe,EAAE,MAAM,eAAe,CAAC;AAE3F,MAAM,CAAC,KAAK,UAAU,aAAa,CAAC,QAAgB;IAClD,MAAM,MAAM,GAAG,MAAM,eAAe,CAAC,QAAQ,CAAC,CAAC;IAC/C,IAAI,CAAC,MAAM,CAAC,EAAE,EAAE,CAAC;QACf,OAAO;YACL,EAAE,EAAE,KAAK;YACT,MAAM,EAAE,GAAG,sBAAsB,CAAC,MAAM,CAAC,yEAAyE;SACnH,CAAC;IACJ,CAAC;IAED,OAAO;QACL,EAAE,EAAE,IAAI;QACR,MAAM,EAAE,MAAM,iBAAiB,CAAC,QAAQ,CAAC;KAC1C,CAAC;AACJ,CAAC"}

package/dist/src/commands/init.d.ts

@@ -0,0 +1,7 @@
+import type { InitResult } from "../types.js";
+export interface InitOptions {
+    targetPath?: string;
+    force?: boolean;
+}
+export declare function initializeHarness(options?: InitOptions): Promise<InitResult>;
+export declare function renderInitResult(result: InitResult): string;