@apptoolkit/harness 1.0.4 → 1.0.5

package/README.md

@@ -11,9 +11,9 @@ rtk proxy npx @apptoolkit/harness install
 
 `bunx --bun` selects Bun even when Node.js is absent. Plain `bunx` also works when Node.js is on `PATH`.
 
-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. The installed `llm/HARNESS.md` is the shared entry point.
+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.
 
-In a directory of related repositories, start the agent in the parent directory. The central harness keeps shared decisions and scoped repository context. Use `$apptoolkit add repo <path>` or `/apptoolkit add repo <path>` after cloning another repository. Repositories can keep their own guidance and toolchain.
+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.
 
 To preview an installation in a noninteractive session, inspect the target and supply the explicit choices.
 
@@ -24,7 +24,9 @@ rtk proxy bunx --bun @apptoolkit/harness install --root /absolute/workspace --ho
 
 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.
 
-Use `rtk proxy bunx --bun @apptoolkit/harness@latest update --plan --json` or `rtk proxy npx @apptoolkit/harness@latest update --plan --json` to preview a release update. The updater checks managed files against the installation receipt. Resolve reported conflicts before applying the update. Keep project decisions in the installed local profile, and review the affected paths and version before applying.
+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.
+
+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.
 
 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.