@ours.network/install 0.11.0

package/LICENSE

@@ -0,0 +1,98 @@
+# Functional Source License, Version 1.1, Apache 2.0 Future License
+
+## Abbreviation
+
+FSL-1.1-Apache-2.0
+
+## Notice
+
+Copyright 2026 Adapt Framework Solutions Ltd
+
+## Terms and Conditions
+
+### Licensor ("We")
+
+The party offering the Software under these Terms and Conditions.
+
+### The Software
+
+The "Software" is each version of the software that we make available under
+these Terms and Conditions, as indicated by our inclusion of these Terms and
+Conditions with the Software.
+
+### License Grant
+
+Subject to your compliance with this License Grant and the Patents,
+Redistribution and Trademark clauses below, we hereby grant you the right to use,
+copy, modify, create derivative works, publicly perform, publicly display and
+redistribute the Software for any Permitted Purpose identified below.
+
+### Permitted Purpose
+
+A Permitted Purpose is any purpose other than a Competing Use. A Competing Use
+means making the Software available to others in a commercial product or service
+that:
+
+1. substitutes for the Software;
+
+2. substitutes for any other product or service we offer using the Software that
+   exists as of the date we make the Software available; or
+
+3. offers the same or substantially similar functionality as the Software.
+
+Permitted Purposes specifically include using the Software:
+
+1. for your internal use and access;
+
+2. for non-commercial education;
+
+3. for non-commercial research; and
+
+4. in connection with professional services that you provide to a licensee using
+   the Software in accordance with these Terms and Conditions.
+
+### Patents
+
+To the extent your use for a Permitted Purpose would necessarily infringe our
+patents, the license grant above includes a license under our patents. If you
+make a claim against any party that the Software infringes or contributes to the
+infringement of any patent, then your patent license to the Software ends
+immediately.
+
+### Redistribution
+
+The Terms and Conditions apply to all copies, modifications and derivatives of
+the Software.
+
+If you redistribute any copies, modifications or derivatives of the Software, you
+must include a copy of or a link to these Terms and Conditions and not remove any
+copyright notices provided in or with the Software.
+
+### Disclaimer
+
+THE SOFTWARE IS PROVIDED "AS IS" AND WITHOUT WARRANTIES OF ANY KIND, INCLUDING
+WITHOUT LIMITATION WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR
+PURPOSE, NON-INFRINGEMENT, OR THAT THE SOFTWARE IS FREE OF DEFECTS. IN NO EVENT
+WILL WE HAVE ANY LIABILITY TO YOU ARISING OUT OF OR RELATED TO THE SOFTWARE,
+INCLUDING INDIRECT, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES, EVEN IF WE HAVE
+BEEN INFORMED OF THEIR POSSIBILITY IN ADVANCE.
+
+### Grant of Future License
+
+We hereby irrevocably grant you an additional license to use the Software under
+the Apache License, Version 2.0 that is effective on the second anniversary of
+the date we make the Software available. On or after that date, you may use the
+Software under the Apache License, Version 2.0, in which case the following will
+apply:
+
+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,136 @@
+# @ours.network/install — `ours-install`
+
+The **unified ours.network stack installer**. ONE guided ~3-minute flow that installs the WHOLE
+stack for someone who already has Claude Code and/or Codex, then hands back a single copy-paste
+prompt to finish setup conversationally.
+
+## Install
+
+**Recommended — a persistent, versioned, integrity-checked command on your PATH:**
+
+```sh
+npm i -g @ours.network/install && ours-install
+```
+
+Re-run (or update / add a skipped piece) any time with just `ours-install`.
+
+**One-off, no global install:**
+
+```sh
+npx @ours.network/install
+```
+
+**Fallback for machines without npm** (least secure — pipes a script straight into your shell):
+
+```sh
+curl -fsSL https://raw.githubusercontent.com/adapt-toolkit/ours-mcp/main/packages/installer/install.sh | bash
+```
+
+The `curl … | bash` bootstrap simply gets Node.js/npm sorted, then does the `npm i -g
+@ours.network/install` and runs `ours-install` for you. `ours-install` is the single front door;
+`ours-codex-install` is kept as a **thin alias** that hands off to it (use
+`ours-codex-install --codex-only` for the legacy Codex-only path).
+
+The installer is a small **self-contained** Node package (Node built-ins only — no runtime
+dependency on the things it installs): an ASCII banner, tasteful colour (degrades under `NO_COLOR`
+/ no-tty), and plain-language **what + why** for every step.
+
+## The flow (what the user sees)
+
+1. **Pre-flight** — a short checklist, not a wall of logs: platform (Linux / macOS / WSL; native
+   Windows prints a WSL pointer and exits), Node.js, and **harness detection with alias-safety**.
+   Before ever calling `claude` / `codex`, it confirms each resolves to a **real executable** that
+   answers `--version` promptly. A shell alias / hanging wrapper is **never called** (that would
+   hang the run) — it's reported plainly with a fix, and a manual-install path is always offered.
+   If neither harness exists it says so and exits.
+2. **Config-first** (first install only) — the only two settings the user ever types, up front:
+   the **broker** (end-to-end encrypted; the broker never sees message content — almost everyone
+   just presses Enter) and the **port** (probes `3050`; only asks if it's busy; never hands out
+   `3051`, reserved for the Telegram connector). Applied once, then the stack is built with it.
+3. **Four consent gates**, each paced with a clean `✓ … No problems.` line + an explicit
+   **Continue?** — never a start-twice-then-ask, never a silent failure:
+   - **1/4 ours core (the daemon)** — write config → install/start ONCE → boot service. On a
+     re-run it reuses the running config (no re-ask) and only updates when you say yes.
+   - **2/4 harness plugins** — the installer **drives the plugin CLIs itself**
+     (`claude plugin marketplace add …` + `claude plugin install ours@ours.network`;
+     `codex plugin marketplace add …` + `codex plugin add ours@ours-codex-marketplace`). Choosing
+     Codex also installs the `ours-codex` live launcher in the same step. Any failure / alias
+     prints the exact manual commands and continues — it **never dead-ends**.
+   - **3/4 ours-fleet** — makes your harnesses persistent, always-online agent teams that survive
+     a reboot; runs `ours-fleet init`. Default **Yes**.
+   - **4/4 Telegram connector** — install-only (no bot tokens here), then optionally as a
+     boot service.
+4. **Summary + hand-off** — a recap (skipped/failed rows call out the fix), then a **literal
+   copy-paste prompt** (root identity + fleet + Telegram) with the steps for any skipped/failed
+   component dropped out. Copied to the clipboard where supported.
+
+The root identity is **deferred to the hand-off** — zero identity typing during install. Because
+`curl … | bash` gives the script its input over the pipe, every prompt is read from the
+controlling terminal (`/dev/tty`), so the flow still works piped.
+
+## Non-interactive / CI / safe dry-run
+
+```sh
+OURS_ASSUME_YES=1 bash install.sh          # accept every default, no prompts
+OURS_INSTALL_DRY_RUN=1 bash install.sh     # walk the WHOLE flow, install/change NOTHING
+```
+
+`OURS_INSTALL_DRY_RUN=1` routes every side-effecting action through a print-only seam — it shows
+exactly the commands it *would* run (npm installs, `ours-mcp start`, plugin adds, `ours-fleet
+init`, service installs) without executing them. That is the safe way to preview the flow on a
+machine you don't want to touch, and how the integration tests drive it.
+
+| var | meaning |
+|---|---|
+| `OURS_ASSUME_YES` | accept every default, never prompt (implies no tty needed) |
+| `OURS_INSTALL_DRY_RUN` | walk the flow without installing or changing anything |
+| `OURS_NPM` | npm binary to use (default `npm`) |
+| `OURS_CONFIG` | daemon config file location (default `~/.ours/config.json`) |
+
+## Uninstall
+
+The companion `uninstall.sh` reverses what the installers created — same thin-bootstrap +
+Node treatment (banner, colour, a clear explanation of what will be removed). Run it from a
+checkout:
+
+```sh
+bash packages/installer/uninstall.sh
+```
+
+or over the same raw-URL pattern as `install.sh` (pointing at `uninstall.sh`):
+
+```sh
+curl -fsSL https://raw.githubusercontent.com/adapt-toolkit/ours-mcp/main/packages/installer/uninstall.sh | bash
+```
+
+It uses the **same toggle UI** to pick what to remove — per-harness plugins, the ours data
+directory (`~/.ours`), and the `ours-mcp` daemon. It removes **only** what the installers
+created, and guards the two destructive items — the data directory and the daemon — behind
+an explicit typed `yes`.
+
+Headless (no terminal), drive it with environment variables:
+
+```sh
+OURS_UNINSTALL="hermes codex" \
+OURS_UNINSTALL_DATA=yes \
+OURS_UNINSTALL_DAEMON=yes \
+  bash uninstall.sh
+```
+
+| var | meaning |
+|---|---|
+| `OURS_UNINSTALL` | harnesses to remove (space/comma list of `claude-code codex hermes`, or `all`) |
+| `OURS_UNINSTALL_DATA` | `yes` — remove the ours data directory (`~/.ours`) |
+| `OURS_UNINSTALL_DAEMON` | `yes` — remove the `ours-mcp` daemon |
+
+## Notes
+
+- This package is **not published to npm** (`private: true`); it ships as the hosted
+  `install.sh` bootstrap plus the `install.mjs` Node installer (and its `lib/`), and exposes the
+  `ours-install` bin. The pieces it installs — the daemon (`@ours.network/mcp`), the harness
+  plugins via each marketplace, `@ours.network/fleet`, and `@ours.network/tg-connector` — are the
+  published components.
+- **Idempotent + safe to re-run.** A re-run adds a skipped piece, re-points the plugins, or (only
+  when you say yes) updates a component; an already-current daemon is left untouched, its running
+  port reused everywhere. Deep configuration (identities, bot tokens, fleet roles) is intentionally
+  **not** done here — it's the copy-paste hand-off's job.