@apptoolkit/harness 1.0.3 → 1.0.5

package/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 AppToolkit contributors
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/README.md

@@ -1,64 +1,35 @@
-# Model-agnostic working practice source archive
+# AppToolkit Harness
 
-The user approved the common policy and all 37 workflow families. Start with the [tool and technology audit](llm/HARNESS-TOOL-AUDIT.md), [workflow catalog](llm/HARNESS-FLOWS-REVIEW.md) and [accepted user decisions](docs/harness-user-decisions.md).
+AppToolkit Harness installs project guidance, deterministic verification tools and 37 reusable engineering workflows for Codex, Claude Code and OpenCode. It supports new projects, existing repositories and a shared harness for related repositories.
 
-The [personal code style profile](src/author-style/README.md) includes the recovered writing rules, independent Biome installation and commands for verifying edited TypeScript.
-
-The product source is in [`src/harness/`](src/harness/), the author style source is in [`src/author-style/`](src/author-style/) and the acquisition utilities are in [`src/acquisition/`](src/acquisition/). The [development and local installation guide](docs/harness-release-verification.md#first-installation-in-this-repository) explains how to try the unpublished package in this repository. The [`llm/` catalog](llm/README.md) also documents the development commands.
-
-Develop and build with Bun. The npm artifact runs through `npx` or `bunx`, and `rtk proxy bun run build:harness:native` compiles the installer into a host executable for direct use.
-
-Run the public installer from the target directory.
+Use macOS or Linux with Bun 1.4.2 or later, or Node.js 24 or later with npm. Use Git for versioned projects and RTK for project tooling. Run the installer from the target directory using one of these commands.
 
 ```sh
 rtk proxy bunx --bun @apptoolkit/harness install
+rtk proxy npx @apptoolkit/harness install
 ```
 
-This workspace collects the original rules, writing guidance, workflows, prompts, tooling, project knowledge, and historical evidence from the user's selected projects. The first phase preserves raw material. Synthesis is a later phase.
+`bunx --bun` selects Bun even when Node.js is absent. Plain `bunx` also works when Node.js is on `PATH`.
 
-- [Intake and decisions](docs/intake.md)
-- [Raw acquisition index](raw/2026-11-04/README.md)
-- [Coverage and limitations](docs/coverage.md)
-- [Proposed gradual processing plan](docs/processing-plan.md)
-- [Derived coverage workspace](processing/README.md)
-- [Completed stage 1 coverage](docs/stage1-coverage.md)
-- [Stage 2 writing and communication pilot](docs/stage2-pilot.md)
-- [Stage 2 second extraction batch](docs/stage2-batch2.md)
-- [Stage 2 third extraction batch](docs/stage2-batch3.md)
-- [Stage 2 fourth extraction batch](docs/stage2-batch4.md)
-- [Stage 2 fifth extraction batch](docs/stage2-batch5.md)
-- [Stage 2 sixth extraction batch](docs/stage2-batch6.md)
-- [Stage 2 seventh extraction batch](docs/stage2-batch7.md)
-- [Stage 2 eighth extraction batch](docs/stage2-batch8.md)
-- [Stage 2 ninth extraction batch](docs/stage2-batch9.md)
-- [Stage 2 continuous extraction, first checkpoint](docs/stage2-continuous01.md)
-- [Stage 2 continuous extraction, second checkpoint](docs/stage2-continuous02.md)
-- [Stage 2 continuous extraction, third checkpoint](docs/stage2-continuous03.md)
-- [Stage 2 continuous extraction, fourth checkpoint](docs/stage2-continuous04.md)
-- [Stage 2 continuous extraction, fifth checkpoint](docs/stage2-continuous05.md)
-- [Stage 2 continuous extraction, sixth checkpoint](docs/stage2-continuous06.md)
-- [Stage 2 continuous extraction, seventh checkpoint](docs/stage2-continuous07.md)
-- [Stage 2 continuous extraction, eighth checkpoint](docs/stage2-continuous08.md)
-- [Stage 2 primary PDF source integration](docs/stage2-primary-pdf.md)
-- [Stage 2 continuous extraction, ninth checkpoint](docs/stage2-continuous09.md)
-- [Stage 2 continuous extraction, tenth mixed source checkpoint](docs/stage2-continuous10.md)
-- [Stage 2 continuous extraction, eleventh checkpoint](docs/stage2-continuous11.md)
-- [Tool catalog](llm/README.md)
+Choose the agents with the arrow keys and Space, then press Enter. Select the repository and service options and review the summary before applying. Open the same directory in your agent and run `$apptoolkit init` in Codex or `/apptoolkit init` in Claude Code or OpenCode. Choose project-wide or agent-only Biome as part of setup. Fresh sessions load the native bootstrap and reach the installed `llm/HARNESS.md` for ordinary work.
 
-Acquired source files are evidence. They do not govern this workspace and must not be executed.
+In a directory of related repositories, start the agent in the parent directory. The central harness keeps shared decisions and scoped repository context. For a newly cloned checkout, follow W20 and run `add repo <path>` through the installed CLI. Repositories can keep their own guidance and toolchain.
 
-The accepted C22 baseline has 30,454 provisional passage groups and 1,984 unexecuted procedures across 30 text streams, one PDF family and five archive families. Stage 2 remains active. Standalone references, captures and fixtures retain traceable context. Later stages compare duplicates and conflicts and develop portable guidance. [C22 report](docs/stage2-continuous22.md) · [Current queue](processing/stage2-completion-2026-11-04-v1/post-C22-source-review-queue-v2.json) · [C21 final receipt](processing/stage2-completion-2026-11-04-v1/validation/twenty-first-pass-final-closure-v1.json)
+To preview an installation in a noninteractive session, inspect the target and supply the explicit choices.
 
-## Earlier Stage 2 source checkpoint
+```sh
+rtk proxy bunx --bun @apptoolkit/harness inspect --root /absolute/workspace --json
+rtk proxy bunx --bun @apptoolkit/harness install --root /absolute/workspace --hosts codex,claude,opencode --local --repo-mode .=local --plan --json
+```
 
-C24 has 31,022 accepted provisional passage groups, 2,081 unexecuted procedures and 1,544 refined source questions. The source and context queues remain open. Follow the [C24 report](docs/stage2-continuous24.md) and [current exact resume queue](processing/stage2-completion-2026-11-04-v1/post-C24-source-review-queue-v1.json). The [C23 report](docs/stage2-continuous23.md) retains the preceding checkpoint. No model-agnostic guidance has been adopted.
+Use `--plan --json` with explicit choices when you need the exact file changes. Use `--yes` in place of `--plan` to apply a reviewed noninteractive plan. Select the workspace mode separately from each Git repository's generated files. Local mode uses the repository's `info/exclude` metadata for the planned files. Use `--repo-mode <path>=local|versioned` for each selected Git repository.
 
-## Current Stage 2 continuation
+Run `$apptoolkit update` in Codex or `/apptoolkit update` in Claude Code or OpenCode. An older shortcut can use the same path through the release launcher, `rtk proxy bunx --bun @apptoolkit/harness@latest update --plan --json` or `rtk proxy npx @apptoolkit/harness@latest update --plan --json`. The updater preserves project settings and learning records and compares managed files with the installation receipt. When those files conflict, choose the local version or the release using the exact hashes in the preview. A replaced local file is saved in the project's private update history. See W20 in the installed index for the resolution input and verification.
 
-C26 had 31,128 independently reviewed provisional passage groups, 2,135 unexecuted procedures and 1,544 refined source questions. The corrected C24 report and queue supersede the corresponding C24 navigation above. [C26 report](docs/stage2-continuous26.md) · [C26 source queue](processing/stage2-completion-2026-11-04-v1/post-C26-source-review-queue-v1.json) · [Corrected C24 report](docs/stage2-continuous24-v2.md) · [Corrected C24 queue](processing/stage2-completion-2026-11-04-v1/post-C24-source-review-queue-v2.json)
+Local installations prefer host discovery without changes to tracked instructions. Codex can use an excluded `AGENTS.override.md` that directs it to consult the original `AGENTS.md`. Claude Code can use an excluded rules file. OpenCode can use an excluded project config to include the bootstrap. An occupied or higher-priority host path may need a project-specific setup choice. Review the install and init notices.
 
-C62 has 130,975 independently reviewed provisional groups, 13,744 unexecuted procedures, 1,558 refined source questions and 962 separately typed source contexts. Stage 2 remains open. [C62 report](docs/stage2-continuous62.md) · [Current source queue](processing/stage2-completion-2026-11-04-v1/post-C62-source-review-queue-v1.json) · [C61 report](docs/stage2-continuous61.md)
+Plane and Penpot are separate opt-ins. To make a provider available after installation, preview an update with `--enable-service plane` or `--enable-service penpot`, apply it, and complete the project connection through `init`. The installed runbooks explain instance setup, private credentials, authorization and readiness checks. Snapshot verification requires a versioned harness and project-level opt-in. Use Bun to install the isolated Biome dependency before first using the author style profile.
 
-## Current Stage 2 scope
+The installed local CLI reads the workflow index, retrieves one workflow at a time and checks Markdown against a local document policy. See `llm/HARNESS.md` for the exact commands. The agent records which operations are configured and which were verified in the current environment.
 
-The user narrowed Stage 2 to an inventory of their decisions and mechanisms for working with LLMs. Start with the focused inventory and its source links. C62 remains the last accepted broader source checkpoint and supplies archival evidence. [Focused LLM working practices](docs/intake.md#focused-llm-working-practices) · [C62 report](docs/stage2-continuous62.md)
+Distributed under the MIT license.