one-code-extension 0.1.0 → 0.1.2

package/README.md

@@ -18,18 +18,19 @@ One project, two npm packages — pick the one that fits you:
 
 | You | Install | Package |
 |---|---|---|
-| **Most people** (new to pi included) | `npm install -g one-code` | [`one-code`](https://www.npmjs.com/package/one-code) — the app: its own `one-code` command, a pinned pi bundled inside, state isolated in `~/.one-code`, coexists with any existing `pi` |
+| **Most people** (new to pi included) | `npm install -g @one-ai/one-code` | [`@one-ai/one-code`](https://www.npmjs.com/package/@one-ai/one-code) — the app: its own `one-code` command, a pinned pi bundled inside, state isolated in `~/.one-code`, coexists with any existing `pi` |
 | Already running pi, want it on your own install | `pi install npm:one-code-extension` | [`one-code-extension`](https://www.npmjs.com/package/one-code-extension) — just the extensions; rides your pi (tested against pi 0.83–0.84, warns outside that range) |
 
 ```bash
-npm install -g one-code
+npm install -g @one-ai/one-code
 cd your-project && one-code
 ```
 
 Or via Homebrew (also installs Node for you):
 
 ```bash
-brew install isuruwijesiri/one-code/one-code
+brew install isurumaduranga/one-ai/one-code
+# or tap once, then it's just: brew tap isurumaduranga/one-ai && brew install one-code
 ```
 
 > The npm route needs **Node 22.19+**.

package/docs/decisions/distribution.md

@@ -8,14 +8,20 @@ One Code ships two npm packages built from this single repo:
 
 | npm name | What it is | pi relationship |
 |---|---|---|
-| **`one-code`** (`app/`) | the bundled app — a `one-code` bin | **exact-pins** pi (`0.84.1`) as a dependency |
+| **`@one-ai/one-code`** (`app/`) | the bundled app — a `one-code` bin | **exact-pins** pi (`0.84.1`) as a dependency |
 | **`one-code-extension`** (repo root) | the pi package | **peerDependency** range; runs on the user's own pi |
 
 The split exists because the two installs need opposite dependency stances
 (reproducible pin vs. ride-the-user's-pi), and nothing else: the app is a thin
 launcher over the same extension set. `one-code-extension` was chosen over
 `one-code-pi`, which reads as "one-code *with* pi bundled" — the opposite of
-what it is. A Homebrew tap (`brew install IsuruMaduranga/one-code/one-code`)
+what it is. The app is scoped under the **`one-ai`** npm org because npm's
+typosquat guard rejects unscoped `one-code` (an existing `onecode` package
+blocks every punctuation variant — discovered only at publish time; a 404 on
+`npm view` does not mean a name is claimable). The *command* the app installs
+is still `one-code`; the extension package stays unscoped so
+`pi install npm:one-code-extension` reads clean, and is attached to the org
+via team access rather than a scope. A Homebrew tap (`brew install IsuruMaduranga/one-code/one-code`)
 delivers the same app and solves the Node ≥22.19 requirement via
 `depends_on "node"`; a single compiled binary is not viable (pi-tui ships
 per-platform native modules).
@@ -62,12 +68,22 @@ injects one inline JS extension (`app/update-check.mjs`) via
 `extensionFactories`: a non-blocking, fail-silent fetch of
 `registry.npmjs.org/one-code/latest` on session start, notifying with an
 install-aware hint (`brew upgrade one-code` when the bin resolves under a
-Homebrew prefix, else `npm i -g one-code`). pi's semver helpers are not
+Homebrew prefix, else `npm i -g @one-ai/one-code`). pi's semver helpers are not
 exported from the package root, so the dotted-numeric compare lives in the
 app. `one-code --version` reports the app version with the pinned pi in
 parentheses. Both paths live-verified (drift warning and update notice each
 fired against a real TUI).
 
+**Versioning is lockstep.** Both packages share one version per release, even
+when only one changed, and the app pins the extension at exactly its own
+version — so one git tag (`vX.Y.Z`) names the whole release, GitHub Releases
+map one-to-one, and a pin/version mismatch is an instantly visible release
+mistake. Adopted at 0.1.2 (the app skipped 0.1.1 to converge); the cost is an
+occasional republish of an unchanged package. The Homebrew tap is
+`IsuruMaduranga/homebrew-one-ai` — named for the brand umbrella so future
+tools join the same tap — giving `brew install isurumaduranga/one-ai/one-code`
+(two-segment installs are not brew grammar; verified empirically).
+
 Registering the package also seeds first-run settings (`theme: "one-code"`,
 `quietStartup: true`), which doubles as skipping pi's stock first-time theme
 picker — the branded first run. Three hardcoded `~/.pi` paths found during

package/package.json

@@ -1,7 +1,7 @@
 {
 	"name": "one-code-extension",
-	"version": "0.1.0",
-	"description": "One Code as a pi package \u2014 the Claude Code experience on your own pi install: ported system prompt, Claude-Code-format permissions, .claude/ compatibility, ToolSearch-style deferred tools, and system-reminder steering. For the bundled app, install `one-code` instead.",
+	"version": "0.1.2",
+	"description": "One Code as a pi package \u2014 the Claude Code experience on your own pi install: ported system prompt, Claude-Code-format permissions, .claude/ compatibility, ToolSearch-style deferred tools, and system-reminder steering. For the bundled app, install `@one-ai/one-code` instead.",
 	"keywords": [
 		"pi",
 		"pi-package",