clankerbend 0.1.0 → 0.1.1

package/cli.mjs

@@ -2,7 +2,7 @@
 import { readFileSync } from "node:fs";
 import { dirname, join } from "node:path";
 import { fileURLToPath } from "node:url";
-import { launchOneWhackCodex } from "./server.mjs";
+import { launchClankerBendCodex } from "./server.mjs";
 
 const ROOT = dirname(fileURLToPath(import.meta.url));
 const PACKAGE_JSON = JSON.parse(readFileSync(join(ROOT, "package.json"), "utf8"));
@@ -17,7 +17,7 @@ try {
 async function main(argv) {
   const [command, ...args] = argv;
 
-  if (!command || command === "help" || command === "--help" || command === "-h") {
+  if (command === "help" || command === "--help" || command === "-h") {
     printHelp();
     return;
   }
@@ -27,9 +27,15 @@ async function main(argv) {
     return;
   }
 
+  if (!command || command.startsWith("-")) {
+    const options = parseCodexArgs(argv);
+    await launchClankerBendCodex(options);
+    return;
+  }
+
   if (command === "codex") {
     const options = parseCodexArgs(args);
-    await launchOneWhackCodex(options);
+    await launchClankerBendCodex(options);
     return;
   }
 
@@ -59,29 +65,31 @@ function parseCodexArgs(args) {
 }
 
 function printHelp() {
-  console.log(`OneWhack
+  console.log(`ClankerBend
 
 Usage:
+  clankerbend [--mock] [--state-dir path]
   clankerbend codex [--mock] [--state-dir path]
   clankerbend help
   clankerbend --version
 
 Environment:
-  ONEWILL_ONEWHACK_STATE_DIR       Override OneWhack runtime state directory.
-  ONEWILL_ONEWHACK_TOKEN           Use a specific bearer token for host endpoints.
-  ONEWILL_ONEWHACK_DISABLE_AUTH=1  Disable bearer auth for local development only.
+  ONEWILL_CLANKERBEND_STATE_DIR       Override ClankerBend runtime state directory.
+  ONEWILL_CLANKERBEND_TOKEN           Use a specific bearer token for host endpoints.
+  ONEWILL_CLANKERBEND_DISABLE_AUTH=1  Disable bearer auth for local development only.
 `);
 }
 
 function printCodexHelp() {
-  console.log(`OneWhack Codex launcher
+  console.log(`ClankerBend Codex launcher
 
 Usage:
+  clankerbend [--mock] [--state-dir path]
   clankerbend codex [--mock] [--state-dir path]
 
 Options:
   --mock            Start against a mock transcript instead of Codex Desktop.
-  --state-dir path  Override OneWhack runtime state directory.
+  --state-dir path  Override ClankerBend runtime state directory.
 `);
 }
 

package/docs/app-lifecycle.md

@@ -1,12 +1,12 @@
-# OneWhack App Lifecycle
+# ClankerBend App Lifecycle
 
-OneWhack separates app installation from profile activation.
+ClankerBend separates app installation from profile activation.
 
 ## Install
 
-Installing records a manifest in the runtime registry. The public `onewhack`
+Installing records a manifest in the runtime registry. The public `clankerbend`
 CLI intentionally does not expose app-management commands; app installation is
-a product configuration concern for the running OneWhack experience.
+a product configuration concern for the running ClankerBend experience.
 
 The registry stores app id, version, manifest path, distribution metadata,
 bundle kind, source path, and install time. The current host loads bundled
@@ -14,10 +14,10 @@ manifests and additional manifest paths from this registry; copying directories
 or tarballs into a managed app store is reserved for installer tooling. The
 runtime root defaults to:
 
-- macOS: `~/Library/Application Support/OneWill/OneWhack`
-- Linux: `~/.local/state/onewill/onewhack`
+- macOS: `~/Library/Application Support/OneWill/ClankerBend`
+- Linux: `~/.local/state/onewill/clankerbend`
 
-Set `ONEWILL_ONEWHACK_STATE_DIR` to override the root location.
+Set `ONEWILL_CLANKERBEND_STATE_DIR` to override the root location.
 
 `distribution.integrity` is required. Local development installs can use
 `integrity: "dev-local"`. Downloaded packages should be installed with a real
@@ -30,7 +30,7 @@ Profiles decide which installed apps are active.
 Enablement is profile-scoped. A host can launch with the default profile or a
 custom user profile while using the same app registry. The default registry
 config path is `registry.json` under the runtime state directory, and launchers
-may override it with `ONEWILL_ONEWHACK_REGISTRY_CONFIG`.
+may override it with `ONEWILL_CLANKERBEND_REGISTRY_CONFIG`.
 
 ## Start
 
@@ -52,7 +52,7 @@ revalidate a replacement manifest and update the installed app record while
 preserving profile enablement.
 
 A future updater can replace the app bundle, validate the new manifest, compare
-`oneWhackVersion`, and update the registry atomically.
+`clankerbendVersion`, and update the registry atomically.
 
 ## Remove
 

package/docs/app-manifest.md

@@ -1,6 +1,6 @@
-# OneWhack App Manifest
+# ClankerBend App Manifest
 
-OneWhack apps are installed and launched from a `onewhack.manifest.json` file.
+ClankerBend apps are installed and launched from a `clankerbend.manifest.json` file.
 The manifest is the stable contract between the app bundle and the host. The
 host loads local manifests through this schema. The schema also reserves npm
 packages, tarballs, and binary-style bundles for installer tooling.
@@ -9,7 +9,7 @@ packages, tarballs, and binary-style bundles for installer tooling.
 
 ```json
 {
-  "oneWhackVersion": "0.1",
+  "clankerbendVersion": "0.1",
   "appId": "onewill.example.app",
   "version": "0.1.0",
   "name": "Example App",
@@ -69,7 +69,7 @@ Every app package must declare the same capabilities and permissions regardless
 of distribution shape.
 
 The current host accepts manifest paths. Future installers may accept an app
-directory containing `onewhack.manifest.json`, a `.tgz`/`.tar.gz` bundle, or an
+directory containing `clankerbend.manifest.json`, a `.tgz`/`.tar.gz` bundle, or an
 `npm:<package>` spec. Packaged sources should be verified with an external
 `sha256-...` integrity value before extraction. The manifest still carries
 `distribution.integrity` so registries and update tools can reason about the

package/docs/author-guide.md

@@ -1,4 +1,4 @@
-# OneWhack App Author Guide
+# ClankerBend App Author Guide
 
 The public reference apps are `apps/vim-nav` and `apps/sticky-notes`. VimNav
 demonstrates transcript navigation and annotations. Sticky Notes demonstrates
@@ -57,7 +57,7 @@ export function createExampleApp(options = {}) {
 }
 ```
 
-The host wraps app state and actions in OneWhack HTTP envelopes. The app should
+The host wraps app state and actions in ClankerBend HTTP envelopes. The app should
 throw `context.httpError(...)` for expected validation failures.
 
 ## Transcript Annotations
@@ -87,7 +87,7 @@ own final placement, sorting, and collision avoidance:
 ```
 
 Apps should not mutate Codex Desktop DOM directly for placement. Renderer
-bridges register through `window.__oneWhackRuntime` and call host-owned
+bridges register through `window.__clankerbendRuntime` and call host-owned
 annotation APIs.
 
 ## Text Ranges And Composer Context
@@ -100,14 +100,14 @@ contribute `selectionActions` from app state. Apps request overlays through
 
 Apps should not query Codex Desktop DOM, position floating menus, render
 composer chips, or write into the composer directly. Those details belong in
-the OneWhack host adapter and renderer runtime.
+the ClankerBend host adapter and renderer runtime.
 
 ## Actions
 
 Actions are routed through:
 
 ```text
-POST /onewhack/apps/:appId/actions
+POST /clankerbend/apps/:appId/actions
 ```
 
 An action must include non-empty `appId`, `actionId`, and `type`. Action IDs are

package/docs/launcher-profiles.md

@@ -1,4 +1,4 @@
-# OneWhack Launcher Profiles
+# ClankerBend Launcher Profiles
 
 A launcher profile is the host configuration for one Codex Desktop session. It
 selects app manifests, chooses the default side-panel app, and decides which
@@ -7,11 +7,14 @@ renderer bridge provides transcript primitives.
 ## Commands
 
 ```sh
-npx clankerbend codex
-npx clankerbend codex --mock
+npx clankerbend
+npx clankerbend --mock
 ```
 
-In this repository, `npm start` runs `clankerbend codex` through the local package.
+`npx clankerbend codex` is equivalent to `npx clankerbend` while Codex is the
+only supported surface.
+
+In this repository, `npm start` runs `clankerbend` through the local package.
 `npm run start:mock` runs the same profile without Codex Desktop.
 
 ## Profile Construction
@@ -28,20 +31,20 @@ Provider selection comes from renderer bridge metadata. The first primary bridge
 normally provides transcript snapshot, order, navigation, and highlight.
 
 The built-in Navigate profile always includes VimNav and Sticky Notes.
-Additional apps are product configuration owned by the running OneWhack
+Additional apps are product configuration owned by the running ClankerBend
 experience and stored in the runtime registry.
 
-The launcher also reads `ONEWILL_ONEWHACK_REGISTRY_CONFIG`, defaulting to
+The launcher also reads `ONEWILL_CLANKERBEND_REGISTRY_CONFIG`, defaulting to
 `registry.json` under the runtime state directory, and merges enabled app
-manifests from the selected registry profile. Set `ONEWILL_ONEWHACK_PROFILE` to
+manifests from the selected registry profile. Set `ONEWILL_CLANKERBEND_PROFILE` to
 override the selected registry profile when building a custom launcher.
 
 Runtime state defaults to:
 
-- macOS: `~/Library/Application Support/OneWill/OneWhack`
-- Linux: `~/.local/state/onewill/onewhack`
+- macOS: `~/Library/Application Support/OneWill/ClankerBend`
+- Linux: `~/.local/state/onewill/clankerbend`
 
-Set `ONEWILL_ONEWHACK_STATE_DIR` to override the root state directory.
+Set `ONEWILL_CLANKERBEND_STATE_DIR` to override the root state directory.
 
 ## Ports And Cleanup