@wrenai/genbi 0.0.1 → 0.0.2

package/README.md

@@ -8,8 +8,13 @@ The app does not write SQL itself. A question goes to the Wren agent harness,
 which answers with a structured envelope — the blocks to render, and whether the
 answer was verified — and the UI renders that.
 
-This README is for working on the app from source: getting it running, and the
-daily build/test/typecheck loop. Three companion docs cover the rest:
+To just run it, `npx @wrenai/genbi` is the whole story — see
+[Getting started](#getting-started) below, or [INSTALL.md](./INSTALL.md) for
+what it needs and how to configure it.
+
+The rest of this README is for working on the app **from source**: getting it
+running, and the daily build/test/typecheck loop. Three companion docs cover
+the rest:
 
 - [RUNNING.md](./RUNNING.md) — a live, BFF-backed dev loop against your own
   Warble build, and checking that the pieces still fit together.
@@ -20,10 +25,10 @@ daily build/test/typecheck loop. Three companion docs cover the rest:
 
 ## Developer preview
 
-`@wrenai/genbi` is at `0.0.0` and has not been published to npm. Nothing here is
-under a compatibility commitment yet — commands, environment variables and
-interfaces move without notice. The Codex runtime is supported in code but has
-not been exercised end to end; Claude is the one that is. See
+`@wrenai/genbi` is published at `0.0.2`. Nothing here is under a compatibility
+commitment yet — commands, environment variables and interfaces move without
+notice. The Codex runtime is supported in code but has not been exercised end
+to end; Claude is the one that is. See
 [MAINTAINING.md](./MAINTAINING.md#versioning) for what the version number does
 and does not promise.
 
@@ -40,8 +45,24 @@ pinned `@warble/*` packages are already pulled in by `pnpm install` — see
 
 ## Getting started
 
-This app lives in a pnpm workspace, so install JavaScript dependencies from
-the repo root:
+### Just run it
+
+```bash
+WREN_HARNESS_WORKSPACE_ROOT=/absolute/path/to/an/empty/directory npx @wrenai/genbi
+```
+
+That fetches the published package, downloads the Warble binary for your
+platform on install, and serves the built UI and the BFF from one process on
+`http://127.0.0.1:4787`. You still need a provider CLI you are logged in to
+(`claude` or `codex`) and the `wren` CLI on `PATH`.
+[INSTALL.md](./INSTALL.md) covers the prerequisites, what happens on first
+start, and every other environment variable.
+
+### From source
+
+Everything below is the development loop, and is only worth setting up if you
+are changing the app. It lives in a pnpm workspace, so install JavaScript
+dependencies from the repo root:
 
 ```bash
 corepack enable

package/dist-server/server/runtime-binding.d.ts

@@ -41,10 +41,20 @@ export declare function collectBundleTierNames(bundle: {
 /** Reads the tier contract directly from a compiled Warble IR document. */
 export declare function collectIrTierNames(ir: unknown): string[];
 /**
- * Compiles the canonical profile source without rebinding its context and
- * extracts its tier contract from IR. This is intentionally independent of
- * auth choice and of any user project: the Setup form must discover the rows
- * before either exists.
+ * Reads the profile's tier contract, which the Setup form needs before an auth
+ * choice or a user project exists.
+ *
+ * A tier name is a static property of the profile — it comes from each
+ * `llm_calls[].tier` — so nothing here depends on what project is bound. The
+ * profile ships its own compiled IR next to it, so the contract is read from
+ * that and no Warble process runs at all.
+ *
+ * Compiling instead is the fallback, and only for a profile source that has no
+ * golden beside it (`WREN_HARNESS_PROFILE` pointed at someone's own profile
+ * tree). It is a fallback rather than the default because `warble compile`
+ * requires a resolvable context binding, and the shipped profiles are bound to
+ * a path that only resolves inside a checkout of this repository: in an
+ * installed package that compile fails, and the Setup form has no rows.
  */
 export declare function compileUnboundProfileTierNames(options: {
     readonly profileSource: string;

package/dist-server/server/runtime-binding.js

@@ -4,7 +4,7 @@
  * reads an API key only while constructing an in-memory in-process adapter spec.
  */
 import { createHash } from "node:crypto";
-import { mkdirSync, writeFileSync } from "node:fs";
+import { existsSync, mkdirSync, writeFileSync } from "node:fs";
 import { mkdtemp, readFile, rm } from "node:fs/promises";
 import { tmpdir } from "node:os";
 import path from "node:path";
@@ -233,12 +233,26 @@ export function collectIrTierNames(ir) {
     return [...seen];
 }
 /**
- * Compiles the canonical profile source without rebinding its context and
- * extracts its tier contract from IR. This is intentionally independent of
- * auth choice and of any user project: the Setup form must discover the rows
- * before either exists.
+ * Reads the profile's tier contract, which the Setup form needs before an auth
+ * choice or a user project exists.
+ *
+ * A tier name is a static property of the profile — it comes from each
+ * `llm_calls[].tier` — so nothing here depends on what project is bound. The
+ * profile ships its own compiled IR next to it, so the contract is read from
+ * that and no Warble process runs at all.
+ *
+ * Compiling instead is the fallback, and only for a profile source that has no
+ * golden beside it (`WREN_HARNESS_PROFILE` pointed at someone's own profile
+ * tree). It is a fallback rather than the default because `warble compile`
+ * requires a resolvable context binding, and the shipped profiles are bound to
+ * a path that only resolves inside a checkout of this repository: in an
+ * installed package that compile fails, and the Setup form has no rows.
  */
 export async function compileUnboundProfileTierNames(options) {
+    const goldenPath = path.join(path.resolve(options.profileSource), "ir.golden.json");
+    if (existsSync(goldenPath)) {
+        return collectIrTierNames(JSON.parse(await readFile(goldenPath, "utf8")));
+    }
     const workDir = await mkdtemp(path.join(tmpdir(), "wren-harness-runtime-tiers-"));
     try {
         const irPath = path.join(workDir, "ir.json");

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@wrenai/genbi",
-  "version": "0.0.1",
+  "version": "0.0.2",
   "description": "Wren GenBI — the web UI for WrenAI: ask questions of your data and get dashboards back",
   "license": "Apache-2.0",
   "keywords": [