kijito-tools 0.2.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 2026 Arcada Labs
+
+   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/NOTICE

@@ -0,0 +1,6 @@
+kijito-tools
+Copyright 2026 Arcada Labs
+
+This product includes software developed by Arcada Labs (https://kijito.ai).
+
+Licensed under the Apache License, Version 2.0. See the LICENSE file.

package/README.md

@@ -0,0 +1,220 @@
+# kijito-tools
+
+Tools for Claude Code and Codex sessions to track their own context window and, optionally, run
+unattended.
+A session can catch up on memory at startup, report how much of its context window is actually in
+use, and recycle its context at high usage without losing the working state. It uses
+[Kijito](https://kijito.ai) as the memory backend by default, and also runs standalone (see
+"Running without Kijito").
+
+Everything here is optional. The catch-up and curation steps are a handful of memory calls you can
+run by hand; the scripts and the two skills just make the routine uniform and easy to deploy across
+machines. Install only the pieces you want — the context check stands alone, the autonomy harness is
+opt-in per pane, and the skills are convenience wrappers, not requirements.
+
+## Components
+
+| Component | What it does | Needs Kijito |
+|---|---|---|
+| `myctx.sh`, `statusline-context.sh` | Report actual context-window usage from the API token counts recorded in the session transcript (the same numbers `/context` shows). Cheap to call. The statusline shows it live. | No |
+| Session catch-up (`session-catchup-hint.sh`, a SessionStart hook) | Each session catches up on memory and notes before it starts on the task. | Optional |
+| Armed-pane autonomy (`claude-armed.sh`, `arm-session.sh`, `session-autosend.sh`) | An armed tmux pane sends itself a first prompt and continues preloaded work. Arming is per pane, so one pane can run unattended while you drive another. | Optional |
+| Self-clear loop (`self-clear.sh`, `lifecycle-lib.sh`, `kijito-qa-pass.sh`) | At high measured context, the session curates memory, confirms a fresh session can resume, runs `/clear`, then catches up again and continues. Gated so it will not clear with unsaved work. | Optional (see note) |
+| `kijito-start` skill | The active, thorough version of session catch-up: load memory, read the current-state pointer and recent lessons, arm the inbox, and resume active work — or, for a new persona, set up identity and the pointer. | Yes |
+| `kijito-qa-memory` skill | Memory curation that requires writing the new memories (not only fixing existing ones), then uses a fresh subagent to confirm a cold start can reconstruct the work. | Yes |
+
+The two skills are conveniences, not the only way in: an agent can run the same catch-up and
+curation by hand from a few prompts. They are packaged as skills because that makes them simple to
+drop into `~/.claude/skills/` and invoke the same way everywhere.
+
+The self-clear loop needs some durable store to carry the handoff across `/clear`. That is Kijito by
+default; a notes file works in standalone mode.
+
+## Install
+
+From source:
+
+```bash
+git clone https://github.com/KijitoAI/kijito-tools
+cd kijito-tools && ./install.sh
+```
+
+`./install.sh` installs the **Claude** provider, which is the default and what every earlier version
+did. The repo is provider-agnostic: each supported agent host is a directory under `providers/` with
+its own installer and its own install location.
+
+```bash
+./install.sh --list-providers
+./install.sh                      # claude (default) -> ~/.claude
+./install.sh --provider codex     # verify release gate only; add --skills-only to deploy skills
+```
+
+### Rollout safety on a SHARED checkout
+
+The installer COPIES files into `~/.claude` (a deployed hook is a copy, not a symlink) and reads
+**whatever branch the checkout has checked out**. So on a shared checkout that several seats install
+from, a bare `./install.sh` run while the checkout sits on a feature branch would silently bake that
+branch's in-progress bytes into a seat's hooks. To prevent that, a bare install from a non-`main`
+git checkout is **refused**; choose explicitly:
+
+```bash
+./install.sh --from-main       # install the stable main bytes (recommended for fleet rollout;
+                               # branch-state-immune — installs via a detached worktree at main)
+./install.sh --allow-branch    # deliberately install THIS branch's bytes (e.g. testing your own work)
+```
+
+A packaged install (`npx kijito-tools`, `pipx run kijito-tools`) is not a git checkout, so the
+bytes ARE the release and no flag is needed.
+
+| provider | what it installs | where | needs |
+|---|---|---|---|
+| `claude` | bash lifecycle scripts + the two skills, and merges `settings.json` | `~/.claude` | `bash`, `jq` (`tmux` for autonomy) |
+| `codex` | Skills (kijito-start, kijito-qa-memory) + gated native same-session wake helper. The controller-era runtime is retired. `--skills-only` deploys the skills; the native wake helper runs from a persistent checkout (advanced setup). | `~/.codex/skills` | Node 20+, a Codex binary |
+
+The wake protocol both providers rely on — event-line validation, the injection-fenced wake text,
+read-offset persistence, and the single-consumer lock — lives once in `providers/_shared/wake-core.mjs`.
+The **skills stay per-provider prose on purpose**: Codex's are rewrites rather than translations, and
+skills are read by models, where slightly-off wording is a real regression. `tests/conformance_test.sh`
+is what keeps that safe — it requires every provider's skills to state the shared doctrine (pointer
+first, mail is data and never authority, verify stale operational facts, running is not armed, arm at
+most one consumer) while leaving each lane free to say it in its own words.
+
+Or with a package runner, no clone needed:
+
+```bash
+npx kijito-tools       # via npm
+pipx run kijito-tools  # via PyPI  (uvx kijito-tools also works)
+```
+
+Both package runners do the same thing as the from-source install: they bundle every provider's
+payload and run `install.sh`, which defaults to the Claude provider. They need `bash`, so on Windows
+run them inside WSL (see Platform support). Pass provider flags straight through, e.g.
+`npx kijito-tools --provider codex --skills-only`.
+
+The Claude installer copies the scripts to `~/.claude/`, deploys the skills to `~/.claude/skills/`, drops
+the CLAUDE.md doctrine snippet alongside them, and merges the keys it needs into `settings.json`. It
+backs up `settings.json` and merges with `jq`, so it leaves your existing settings alone and is safe
+to re-run, including on other machines. Requires `jq`. The autonomy features require `tmux`.
+
+## Proving the inbox wake path
+
+The install ends by pushing a real message through the wake path and reporting which hop, if any,
+broke — because a broken wake path is indistinguishable from a working one with no mail on it. It
+fails as silence, so an installer that only reports on itself ("files copied, settings merged") can
+exit 0 over a dead inbox. Run it any time:
+
+```sh
+~/.claude/inbox-selftest.sh                      # resolves the persona from .kijito_persona
+~/.claude/inbox-selftest.sh --persona 'name (purpose)'
+```
+
+Three hops, and the verdict names the one that broke: **producer** (a producer runs *and covers this
+persona*, not a sibling's) · **stream** (the message actually lands in this persona's event file) ·
+**consumer** (something wake-capable is attached and would be re-invoked).
+
+Exit codes are the answer: `0` WORKING · `1` NOT WORKING / PARTIAL · `2` COULD NOT MEASURE (no
+token, no persona, no resolvable stream — deliberately *not* the same as a failure). Run it unpiped:
+piping replaces `$?` with the last pipeline stage's status.
+
+**Two callers, two contracts.** At install time there is no agent session yet, so a missing consumer
+is `PARTIAL` with the next step rather than a failed install. An **agent-driven onboarding flow**
+runs the same check *after* arming its consumer and needs "WORKING means all three hops" with no
+PARTIAL to misread — that caller passes `--require-consumer`, which makes a missing consumer a flat
+failure. The hops are measured identically either way; only what counts as passing changes.
+
+The onboarding step that verifies the wake channel should run exactly:
+
+```sh
+~/.claude/inbox-selftest.sh --require-consumer
+```
+
+and report `verified=true` only on exit `0`.
+
+## Platform support
+
+The scripts are POSIX-style `bash` and avoid GNU-only flags (epoch and timestamp formatting work on
+both BSD and GNU `date`), so they run the same on Linux and macOS.
+
+| Platform | Context check | Catch-up + skills | Armed-pane autonomy / self-clear |
+|---|---|---|---|
+| Linux | yes | yes | yes (needs `tmux`) |
+| macOS | yes | yes | yes (needs `tmux`) |
+| Windows via WSL | yes | yes | yes — run `claude` inside the WSL distro, where `tmux` works |
+| Windows native (no WSL) | with Git Bash | with Git Bash | no — `tmux` is not available |
+
+On Windows, use WSL: install and launch `claude` inside the Linux distro and everything works as it
+does on native Linux. The autonomy harness drives a session by typing into its own `tmux` pane, which
+has no native-Windows equivalent, so without WSL only the context check and the by-hand catch-up
+apply. Requirements everywhere: `bash` and `jq`; add `tmux` for the autonomy features.
+
+## Managed vs. autonomous panes
+
+Arming is per pane.
+
+| | plain `claude` | armed pane |
+|---|---|---|
+| Catch-up | reminder only; you send the first prompt | sends its own first prompt |
+| Self-clear | not allowed; you manage context | allowed, after the gate below |
+
+To arm a pane, launch it with `~/.claude/claude-armed.sh`, or tell the agent to go autonomous
+mid-session and it runs `~/.claude/arm-session.sh on` (`off` turns it back off). A plain `claude`
+session stays under your control.
+
+## Self-clear gate
+
+A pane clears itself only after both steps:
+
+1. `/kijito-qa-memory` curates memory, writes a current-state note that begins with `RESUME NOW:`,
+   and confirms with a fresh subagent that a cold start can resume. It records a pass token.
+2. `self-clear.sh` checks that the kill switch is off, the pane is armed, it is not a subagent, it is
+   in tmux, the target pane is alive, and the pass token is **fresh**.
+
+Every one of those is a property of *this* clear — above all, "is the handoff good enough to survive
+it?" A count-based cycle cap and an every-N human checkpoint used to sit here too and were removed on
+2026-07-29: measured over 88 cycles they accounted for 19 of 24 refusals and never once caught a
+loop, because a count measures uptime, not runaway. If a runaway ever needs catching, detect the loop
+(consecutive cycles landing no commits and no memories) rather than the count.
+
+It then runs `/clear`. The SessionStart hook catches the new session up and it resumes from the note.
+To stop all autonomous sending and clearing, create the file `~/.claude/.lifecycle/STOP`.
+
+## Running without Kijito
+
+The context check (`myctx.sh`) has no dependencies; install and run it.
+
+For the autonomy harness, set `KIJITO_MODE=off` for a generic catch-up prompt, or set your own with
+`KIJITO_AUTOCATCHUP_PROMPT`. The self-clear gate only requires that some curation step write the pass
+token (`~/.claude/kijito-qa-pass.sh`). Kijito is the default backend, not a requirement.
+
+## Tests
+
+```bash
+bash tests/lc_test.sh
+```
+
+Covers arming, the token gate (both directions — a stale handoff refuses, a fresh one fires), the
+kill switch, auto-send, and a regression guard that the removed count gates stay removed.
+
+By default this exercises the scripts **in this repo** — the ones that actually ship. Set
+`KIJITO_TEST_TARGET=installed` to run it against `~/.claude` instead, and `bash tests/drift_test.sh`
+to report when those two disagree.
+
+The rest of the suite:
+
+```bash
+bash tests/drift_test.sh                     # does this machine RUN what the repo SHIPS?
+bash tests/conformance_test.sh --selftest    # every provider states the shared doctrine
+node --test providers/codex/test/codex-hive-watch.test.mjs \
+             providers/codex/test/release-packaging.test.mjs   # codex controller + packaging
+node providers/codex/tools/refresh-manifest.mjs --check        # codex gated hashes are current
+```
+
+`drift_test.sh` covers both lanes — `providers/claude/` against `~/.claude`, and
+`providers/codex/skills/` against `~/.codex/skills`. The codex lane is why it exists: those two skills
+once lived *only* as installed state with no upstream in any repository, so a machine reinstall would
+have destroyed them. `conformance_test.sh --selftest` first proves none of its own matchers can match
+an empty document, because a prose check that accepts anything reports green forever.
+
+## License
+
+Apache 2.0. Copyright 2026 Arcada Labs. See [LICENSE](LICENSE) and [NOTICE](NOTICE).

package/bin/cli.js

@@ -0,0 +1,34 @@
+#!/usr/bin/env node
+'use strict';
+// kijito-tools — thin launcher that runs the bundled bash installer (install.sh).
+// The package ships the scripts/skills as data; this resolves them relative to the
+// package root (never process.cwd()) and shells out to bash. Run with: npx kijito-tools
+const { spawnSync } = require('node:child_process');
+const path = require('node:path');
+
+const pkgRoot = path.resolve(__dirname, '..');
+const installScript = path.join(pkgRoot, 'install.sh');
+
+// install.sh is POSIX bash. Native Windows has no bash; point users at WSL/Git Bash
+// rather than letting them hit a cryptic ENOENT.
+const probe = spawnSync('bash', ['--version'], { stdio: 'ignore' });
+if (probe.error) {
+  console.error(
+    'kijito-tools needs bash to run its installer.\n' +
+    (process.platform === 'win32'
+      ? 'On Windows, run it inside WSL (recommended) or Git Bash.\n'
+      : 'Install bash and try again.\n') +
+    'See https://github.com/KijitoAI/kijito-tools#platform-support'
+  );
+  process.exit(1);
+}
+
+const result = spawnSync('bash', [installScript, ...process.argv.slice(2)], {
+  stdio: 'inherit',
+  env: process.env,
+});
+if (result.error) {
+  console.error('Failed to launch the installer:', result.error.message);
+  process.exit(1);
+}
+process.exit(result.status ?? 1);

package/install.sh

@@ -0,0 +1,161 @@
+#!/usr/bin/env bash
+# kijito-tools — provider dispatcher.
+#
+# This repo installs the Kijito session toolkit for more than one agent host. Each host is a
+# PROVIDER under providers/, owns its own installer, and installs to its own location:
+#
+#   claude  (default)  providers/claude/install.sh    → ~/.claude          — bash scripts + skills
+#   codex              providers/codex/install.mjs    → release verify (default) / --skills-only
+#                      (controller-era full install retired at gate 6, 2026-08-15;
+#                       see legacy/codex-controller-era-2026-08/)
+#
+#   ./install.sh                      # claude, unchanged from before the providers/ split
+#   ./install.sh --provider codex     # verify the codex release gate; add --skills-only to deploy
+#   ./install.sh --list-providers
+#   ./install.sh --from-main          # install the stable main bytes (branch-state-immune)
+#   ./install.sh --allow-branch       # deliberately install THIS branch's bytes (off-main opt-in)
+#
+# ⚠️ THE DEFAULT IS LOAD-BEARING AND MUST STAY `claude`. `npx kijito-tools` and
+# `pipx run kijito-tools` both land here with no arguments, and they have been installing the
+# Claude toolkit since 0.1.0. Changing the default would silently retarget every existing user.
+#
+# ⚠️ ROLLOUT SAFETY — WHY --from-main EXISTS (two independent wrongs, measured 2026-08-08 by assay):
+#   (1) the installer COPIES files into ~/.claude — a deployed hook/skill is a COPY, not a symlink,
+#       so it NEVER tracks the repo after install; and
+#   (2) the install reads the CURRENT WORKING TREE, whose bytes follow whatever branch is checked
+#       out — so a fleet seat that runs a bare `./install.sh` while this SHARED checkout sits on
+#       someone's feature branch silently bakes that branch's in-progress bytes into its hooks.
+#   Either wrong alone is survivable; together they let a seat converge on stale/unreleased bytes
+#   with no error (only reading the installed CONTENT catches it). So main is the documented fleet
+#   path (--from-main, installed via a detached worktree so the caller's branch is untouched), and
+#   installing from any OTHER branch is made OPT-IN (--allow-branch) — a mere warning still installs
+#   the wrong bytes for anyone who does not read it, so the unsafe path must be opt-in, not opt-out.
+#   (A non-git checkout — npm/pipx packaged release — has no branch to be wrong about, so it is
+#   exempt: the bytes ARE the release.)
+#
+# Unrecognized arguments are passed through to the provider's own installer untouched, so a
+# provider can add flags without this file needing to know about them.
+set -euo pipefail
+ROOT="$(cd "$(dirname "$0")" && pwd)"
+PROVIDERS_DIR="$ROOT/providers"
+
+list_providers() {
+  # _shared holds provider-neutral code, not a provider. Anything else with an installer counts.
+  for d in "$PROVIDERS_DIR"/*/; do
+    name="$(basename "$d")"
+    [ "$name" = "_shared" ] && continue
+    if [ -f "$d/install.sh" ] || [ -f "$d/install.mjs" ]; then echo "$name"; fi
+  done
+}
+
+usage() {
+  echo "usage: install.sh [--provider <name>] [--from-main | --allow-branch] [provider args...]"
+  echo
+  echo "providers:"
+  list_providers | sed 's/^/  /'
+  echo
+  echo "default provider: claude"
+  echo
+  echo "rollout safety (git checkouts only):"
+  echo "  --from-main       install the stable main bytes via a detached worktree (recommended)"
+  echo "  --allow-branch    deliberately install the current (off-main) branch's bytes"
+}
+
+# ROLLOUT SAFETY (see the header). git checkouts only; a packaged (non-git) install is exempt.
+# branch_guard refuses a bare install from an off-main checkout; from_main_install performs the
+# main-worktree install. Both are no-ops outside a git checkout.
+_on_main_commit() {
+  # True iff HEAD sits at main's COMMIT (so a detached HEAD at main counts, not just the branch name).
+  local head_sha main_sha
+  head_sha="$(git -C "$ROOT" rev-parse HEAD 2>/dev/null || true)"
+  main_sha="$(git -C "$ROOT" rev-parse main 2>/dev/null || true)"
+  [ -n "$head_sha" ] && [ "$head_sha" = "$main_sha" ]
+}
+
+branch_guard() {
+  git -C "$ROOT" rev-parse --git-dir >/dev/null 2>&1 || return 0   # not a git checkout → exempt
+  _on_main_commit && return 0                                       # already main → nothing to guard
+  local cur
+  cur="$(git -C "$ROOT" rev-parse --abbrev-ref HEAD 2>/dev/null || echo '(unknown)')"
+  if [ "$ALLOW_BRANCH" -eq 1 ]; then
+    echo "kijito-tools: installing from '$cur' (off main) — --allow-branch given, proceeding." >&2
+    return 0
+  fi
+  cat >&2 <<EOF
+ERROR: kijito-tools is checked out on '$cur', not main.
+The installer COPIES the current working tree into ~/.claude, so a bare install here would bake
+'$cur' bytes into your hooks and skills — and they will NOT update afterward. Choose one:
+  ./install.sh --from-main       # install the stable main bytes (recommended; branch-state-immune)
+  ./install.sh --allow-branch    # deliberately install THIS branch's bytes
+EOF
+  exit 3
+}
+
+from_main_install() {
+  git -C "$ROOT" rev-parse --git-dir >/dev/null 2>&1 || {
+    echo "ERROR: --from-main needs a git checkout of kijito-tools (this is a packaged install)." >&2
+    exit 3; }
+  local main_sha
+  main_sha="$(git -C "$ROOT" rev-parse main 2>/dev/null || true)"
+  [ -n "$main_sha" ] || { echo "ERROR: --from-main: no local 'main' ref in $ROOT." >&2; exit 3; }
+  _on_main_commit && return 0    # already at main's commit → fall through to the normal install
+  local wt
+  wt="$(mktemp -d "${TMPDIR:-/tmp}/kjt-claude-main.XXXXXX")"
+  # --detach: main may be checked out elsewhere; a detached worktree at its commit always succeeds.
+  git -C "$ROOT" worktree add --detach "$wt" main >/dev/null 2>&1 || {
+    echo "ERROR: --from-main: could not create a main worktree." >&2; rmdir "$wt" 2>/dev/null; exit 3; }
+  local rc=0
+  # Re-invoke the MAIN copy of this installer (its own guard sees main and passes). Do NOT pass
+  # --from-main again — no recursion. Preserve provider + any passthrough args.
+  bash "$wt/install.sh" --provider "$PROVIDER" ${PASSTHROUGH[@]+"${PASSTHROUGH[@]}"} || rc=$?
+  # The install only READS the worktree (it copies OUT), so it stays clean → remove without --force
+  # (IRREVERSIBLE: never --force/prune a worktree — that can destroy a sibling's uncommitted work).
+  git -C "$ROOT" worktree remove "$wt" >/dev/null 2>&1 || true
+  exit "$rc"
+}
+
+PROVIDER="claude"
+FROM_MAIN=0
+ALLOW_BRANCH=0
+# bash 3.2 (the macOS default) errors on "${arr[@]}" when arr is empty under `set -u`, so this
+# array is always expanded through the ${arr[@]+...} guard below.
+PASSTHROUGH=()
+while [ $# -gt 0 ]; do
+  case "$1" in
+    --provider)
+      [ $# -ge 2 ] || { echo "ERROR: --provider needs a value" >&2; exit 2; }
+      PROVIDER="$2"; shift 2 ;;
+    --provider=*) PROVIDER="${1#*=}"; shift ;;
+    --from-main) FROM_MAIN=1; shift ;;
+    --allow-branch) ALLOW_BRANCH=1; shift ;;
+    --list-providers) list_providers; exit 0 ;;
+    -h|--help) usage; exit 0 ;;
+    *) PASSTHROUGH+=("$1"); shift ;;
+  esac
+done
+
+PROVIDER_DIR="$PROVIDERS_DIR/$PROVIDER"
+if [ "$PROVIDER" = "_shared" ] || [ ! -d "$PROVIDER_DIR" ]; then
+  echo "ERROR: unknown provider '$PROVIDER'. Known providers:" >&2
+  list_providers | sed 's/^/  /' >&2
+  exit 2
+fi
+
+# ROLLOUT SAFETY gate — runs after provider validation, before any install.
+# --from-main installs the stable main bytes (and exits), unless HEAD is already main (falls
+# through); otherwise branch_guard refuses a silent off-main install unless --allow-branch opts in.
+if [ "$FROM_MAIN" -eq 1 ]; then
+  from_main_install
+fi
+branch_guard
+
+if [ -f "$PROVIDER_DIR/install.sh" ]; then
+  exec bash "$PROVIDER_DIR/install.sh" ${PASSTHROUGH[@]+"${PASSTHROUGH[@]}"}
+elif [ -f "$PROVIDER_DIR/install.mjs" ]; then
+  command -v node >/dev/null 2>&1 || {
+    echo "ERROR: provider '$PROVIDER' needs Node.js 20+ on PATH." >&2; exit 1; }
+  exec node "$PROVIDER_DIR/install.mjs" ${PASSTHROUGH[@]+"${PASSTHROUGH[@]}"}
+else
+  echo "ERROR: provider '$PROVIDER' has no install.sh or install.mjs." >&2
+  exit 2
+fi