one-code-extension 0.1.1 → 0.1.3

package/README.md

@@ -29,11 +29,17 @@ 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+**.
 
+> Tip: the app opens in a **full-screen TUI** (alt-screen, restores your
+> terminal on exit) by default. On your own pi that's opt-in — set
+> `"tuiMode": "fullscreen"` in `~/.pi/agent/settings.json`, or launch with
+> `pi --tui-mode fullscreen`.
+
 ## Two-minute quickstart — free, no card
 
 You need one model-provider key. Two providers hand out **free frontier-adjacent

package/docs/decisions/distribution.md

@@ -2,9 +2,10 @@
 
 Part of [Decisions](../decisions.md).
 
-## Two artifacts from one codebase: the app and the package (2026-08-10, unreviewed)
+## Two artifacts from one codebase: the app and the package (2026-08-10)
 
-One Code ships two npm packages built from this single repo:
+One Code ships two npm packages built from this single repo — **both live on
+npm since 2026-08-10 at 0.1.2** (GitHub release `v0.1.2`):
 
 | npm name | What it is | pi relationship |
 |---|---|---|
@@ -21,7 +22,11 @@ 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`)
+via team access rather than a scope. The npm org (`one-ai`) and the planned
+GitHub org (`oneai-hq` — `one-ai` was taken on GitHub) deliberately differ:
+registry namespaces are independent, install commands only ever cite the npm
+scope, and `repository` fields point at URLs, so the mismatch costs nothing
+beyond a profile cross-link. 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).
@@ -74,9 +79,29 @@ 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). Two
+release-process facts learned shipping 0.1.2: the formula's `url` + `sha256`
+must be bumped by hand each release until a release workflow automates it,
+and Homebrew's `std_npm_args` passes npm's supply-chain guard
+`--min-release-age=1`, so **the brew install of a release only works ~24h
+after its npm publish** — day-one users get "No matching version found …
+with a date before <now−1d>"; either schedule the formula bump a day after
+the npm publish or accept the gap.
+
 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
+`quietStartup: true`, and — from 0.1.3 — `tuiMode: "fullscreen"`, the
+alt-screen One Code look per the fullscreen decision in `tui.md`), which
+doubles as skipping pi's stock first-time theme picker — the branded first
+run. Seeded only when no settings file exists, so a user's later changes
+stick. Three hardcoded `~/.pi` paths found during
 this work (quiet-startup detection, the skills listing, the Anthropic-OAuth
 check) now resolve through pi's `getAgentDir()`, which honours the isolation
 env var.
@@ -114,6 +139,10 @@ Per project directive, prefer ecosystem packages over new code.
 
 ## Publish readiness (Phase 7)
 
+*(Historical — the release shipped 2026-08-10 as described in the two-artifact
+entry above. The tarball/install checks below were the single-package-era
+method and remain the template for pre-publish verification.)*
+
 `npm pack` produces a 69 kB / 47-file tarball: `extensions/`, `agents/`, `types/`,
 README, LICENSE and `docs/decisions.md`. Every path in the `pi.extensions`
 manifest is checked to be present in the tarball.

package/docs/decisions.md

@@ -11,7 +11,7 @@ entry. (Companion docs: [`findings.md`](findings.md) for how pi behaves,
 
 Full context: [`decisions/distribution.md`](decisions/distribution.md).
 
-- **[Two artifacts from one codebase: the app and the package](decisions/distribution.md#two-artifacts-from-one-codebase-the-app-and-the-package-2026-08-10-unreviewed)** *(unreviewed)* — npm `one-code` (bundled app: pinned pi, `~/.one-code` isolation via `PI_CODING_AGENT_DIR`, package-registration load shape, stdout rebranding, own update check) + npm `one-code-extension` (peer-dep pi package with a runtime tested-range warning); Homebrew tap delivers the app.
+- **[Two artifacts from one codebase: the app and the package](decisions/distribution.md#two-artifacts-from-one-codebase-the-app-and-the-package-2026-08-10)** — npm `@one-ai/one-code` (bundled app: pinned pi, `~/.one-code` isolation via `PI_CODING_AGENT_DIR`, package-registration load shape, stdout rebranding, own update check) + npm `one-code-extension` (peer-dep pi package with a runtime tested-range warning); lockstep versions from 0.1.2; Homebrew tap `isurumaduranga/one-ai` delivers the app (brew's `--min-release-age=1` makes day-one brew installs fail by design).
 - **[Distribution: pi package, not a wrapper binary](decisions/distribution.md#distribution-pi-package-not-a-wrapper-binary)** — *(partially superseded by the two-artifact model)* ship as an installable pi package because pi's rebranding resolves from pi's own `package.json`; a dependent can't rebrand it, and a package keeps upstream upgrades a version bump away.
 - **[Community packages: adopted where they work](decisions/distribution.md#community-packages-adopted-where-they-work)** — prefer ecosystem packages, but trial first: only `pi-ask-user` survived; `pi-subagents` was rejected (children SIGKILLed ~29 ms after spawn here).
 - **[Publish readiness (Phase 7)](decisions/distribution.md#publish-readiness-phase-7)** — what's done and what remains before `npm publish` (metadata, tarball, install-path verification).

package/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "one-code-extension",
-	"version": "0.1.1",
+	"version": "0.1.3",
 	"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",