bigpowers 2.92.0 → 2.93.1

package/scripts/lib/cli-version.js

@@ -0,0 +1,29 @@
+// story: BUG-2026-11-03-cli-update-stale-version
+// cli-version.js — read the installed version from disk, never from a require cache.
+//
+// `bigpowers update` runs `npm install -g bigpowers@latest` inside a *running*
+// process. bin/bigpowers.js has already require()d package.json by then, so when
+// bin/setup.js (required after the reinstall) reads the same resolved path, Node
+// hands back the cached object: the banner printed v2.88.5 while v2.92.0 was what
+// had just been installed, and `bigpowers install` — a fresh process — correctly
+// reported 2.92.0.
+//
+// readFileSync always sees the new file, so every user-facing version string goes
+// through here.
+
+'use strict';
+
+const fs = require('fs');
+const path = require('path');
+
+/** Version of the package rooted at `root`, read fresh from disk. */
+function readPackageVersion(root) {
+  try {
+    const text = fs.readFileSync(path.join(root, 'package.json'), 'utf8');
+    return JSON.parse(text).version || 'unknown';
+  } catch {
+    return 'unknown';
+  }
+}
+
+module.exports = { readPackageVersion };

package/scripts/lib/golden-suite-gates.sh

@@ -53,6 +53,10 @@ GOLDEN_GATES=(
   "target-contracts:bash scripts/test-target-contracts.sh:false"
   # Registry-driven replacements for the 25 hand-written per-target scripts.
   "install-hub:bash scripts/test-install-hub.sh:false"
+  # `bigpowers update` runs `npm install -g @latest` inside a live process; a
+  # version captured by require() at startup then reports the release that was
+  # just replaced (BUG-2026-11-03-cli-update-stale-version).
+  "bigpowers-cli-version:bash scripts/test-bigpowers-cli-version.sh:false"
   "adapter-render:bash scripts/test-adapter-render.sh:false"
   "adapters:bash scripts/test-adapters.sh:false"
   # Previously orphaned: present in scripts/ but reachable from no gate.

package/scripts/test-bigpowers-cli-version.sh

@@ -0,0 +1,104 @@
+#!/usr/bin/env bash
+# story: BUG-2026-11-03-cli-update-stale-version
+# test-bigpowers-cli-version.sh — `update` must report the version it just installed.
+#
+# Reproduces the reported symptom without touching npm or the real HOME:
+#   bigpowers update  → banner v2.88.5   (wrong: a require() cache captured at startup,
+#                                          before `npm install -g bigpowers@latest`)
+#   bigpowers install → banner v2.92.0   (right: a fresh process reads package.json)
+#
+# Three assertions:
+#   1. readPackageVersion() sees the on-disk version even after package.json was
+#      already require()d and then rewritten (the exact mechanism).
+#   2. the installer's banner renders that fresh value — end to end, from a copy
+#      of bin/ whose version changes between process start and banner render.
+#   3. neither CLI entry point still interpolates a cached `pkg.version` into a
+#      user-facing line (static guard: the cache is invisible at runtime until
+#      the day a self-update happens).
+#
+# Usage: bash scripts/test-bigpowers-cli-version.sh
+set -euo pipefail
+source "$(dirname "${BASH_SOURCE[0]}")/lib/skill-common.sh"
+resolve_repo_root
+cd "$REPO_ROOT"
+
+source scripts/lib/test-assertions.sh
+TA_PASS=0
+TA_FAIL=0
+TA_TMPDIR="$(mktemp -d)"
+trap ta_cleanup EXIT
+
+echo "=== test-bigpowers-cli-version.sh ==="
+
+# ── 1. readPackageVersion ignores the require cache ─────────────────────────
+mkdir -p "$TA_TMPDIR/pkgver"
+if [ ! -f scripts/lib/cli-version.js ]; then
+  ta_fail "(1) scripts/lib/cli-version.js is missing — nothing reads the version from disk"
+  CACHE_OUT=""
+else
+CACHE_OUT="$(node -e '
+const fs = require("fs"), path = require("path");
+const dir = process.argv[1];
+fs.writeFileSync(path.join(dir, "package.json"), JSON.stringify({ version: "2.88.5" }));
+const cached = require(path.join(dir, "package.json"));          // what bin/bigpowers.js does at startup
+fs.writeFileSync(path.join(dir, "package.json"), JSON.stringify({ version: "2.92.0" }));  // npm install -g @latest
+const { readPackageVersion } = require(process.argv[2]);
+process.stdout.write(`${cached.version}|${readPackageVersion(dir)}`);
+' "$TA_TMPDIR/pkgver" "$REPO_ROOT/scripts/lib/cli-version.js")"
+fi
+if [ "$CACHE_OUT" = "2.88.5|2.92.0" ]; then
+  ta_pass "(1) readPackageVersion sees the on-disk version after package.json is rewritten"
+else
+  ta_fail "(1) version read followed the require cache: got '$CACHE_OUT' (want '2.88.5|2.92.0')"
+fi
+
+# ── 2. the banner an `update` run prints carries the new version ────────────
+# Drive the exact sequence bin/bigpowers.js uses: read package.json at startup,
+# let `npm install -g bigpowers@latest` replace it, then require bin/setup.js —
+# which renders the banner. stdin at EOF makes setup draw the banner and exit, so
+# nothing is installed and no prompt is answered.
+FAKE_PKG="$TA_TMPDIR/fakepkg"
+mkdir -p "$FAKE_PKG"
+cp -R "$REPO_ROOT/bin" "$FAKE_PKG/bin"
+cp -R "$REPO_ROOT/scripts" "$FAKE_PKG/scripts"
+ln -sfn "$REPO_ROOT/node_modules" "$FAKE_PKG/node_modules"
+printf '{"name":"bigpowers-fake","version":"2.88.5"}\n' > "$FAKE_PKG/package.json"
+cat > "$FAKE_PKG/driver.js" <<'DRIVER'
+// Mimics `bigpowers update`: snapshot at startup, reinstall over it, then render.
+const { execFileSync } = require('child_process');
+const fs = require('fs');
+const path = require('path');
+
+const root = __dirname;
+const pkg = require(path.join(root, 'package.json'));   // 2.88.5 — the version the process booted with
+fs.writeFileSync(path.join(root, 'package.json'), JSON.stringify({ name: 'bigpowers-fake', version: '2.92.0' }));
+process.stdout.write(`startup=${pkg.version}\n`);
+require(path.join(root, 'bin', 'setup.js'));            // prints the banner
+DRIVER
+BANNER_OUT="$(
+  cd "$FAKE_PKG"
+  HOME="$TA_TMPDIR/home" perl -e 'alarm 25; exec @ARGV' node driver.js < /dev/null 2>&1 || true
+)"
+if printf '%s' "$BANNER_OUT" | grep -q "startup=2.88.5" && printf '%s' "$BANNER_OUT" | grep -q "v2.92.0"; then
+  ta_pass "(2) the banner after a self-update reports the installed version (2.92.0), not the startup one (2.88.5)"
+elif printf '%s' "$BANNER_OUT" | grep -q "v2.88.5"; then
+  ta_fail "(2) the banner reported the startup version (v2.88.5) after 2.92.0 was installed"
+else
+  ta_fail "(2) no banner version found in the update flow"
+fi
+
+# ── 3. no user-facing line interpolates the startup snapshot ────────────────
+# `pkg.version` is the value captured when the process started. Anywhere it
+# reaches the user after a self-update, it is the version that was replaced.
+STALE=0
+for f in bin/setup.js bin/bigpowers.js; do
+  grep -nE 'pkg\.version' "$f" | grep -vE '^\s*[0-9]+:\s*//' >/dev/null 2>&1 && STALE=1
+done
+if [ "$STALE" -eq 0 ]; then
+  ta_pass "(3) neither bin/setup.js nor bin/bigpowers.js prints a cached pkg.version"
+else
+  ta_fail "(3) a CLI entry point still interpolates pkg.version (stale after self-update)"
+fi
+
+echo "$TA_PASS passed, $TA_FAIL failed"
+[[ "$TA_FAIL" -eq 0 ]]

package/CLAUDE.md

@@ -1,400 +0,0 @@
-# story: e38s08
-# story: e51s05
-# story: e45s22
-# story: e45s23
-# story: e55s03
-
-# bigpowers — Claude Code
-
-Read CONVENTIONS.md before any GitHub or git operation.
-
-[`constitution.md`](constitution.md) is a consolidated entry point synthesizing
-this project's doctrine (this file, CONVENTIONS.md, docs/PRINCIPLES.md,
-docs/references/*.md) into bigspec's B0-B10 + Capstone blocks, with citations
-back to the fuller text. It's a starting point for a reader, not a
-replacement — this file remains fully authoritative for its own content today.
-
-<!-- BEGIN bigpowers:context-routing -->
-## Context Routing
-
-Load subdirectory context **by file glob** — do not read the full doc tree up front.
-
-| Glob / trigger | Load first | Fallback |
-|----------------|------------|----------|
-| `skills/**` | Active skill's `SKILL.md` + sibling `REFERENCE.md` if linked | `SKILL-INDEX.md` |
-| `specs/epics/**` | Capsule `epic.yaml` + active story `-tasks.yaml` | `specs/release-plan.yaml` |
-| `specs/product/**` | `SCOPE_LATEST.yaml`, `VISION_LATEST.yaml` | `specs/README.md` |
-| `specs/tech-architecture/**` | `tech-stack.md` + epic `eNN-TEST_PLAN_LATEST.md` if present | `CONVENTIONS.md` |
-| `scripts/**` | `CONVENTIONS.md` § Generated artifact targets | This file § Commands |
-| `website/**` | `website/README.md` if present | Never edit `website/src/content/docs/` (generated) |
-| `docs/**` | Matching doc under `docs/` | `docs/references/` |
-| Default / session start | This file → `CONVENTIONS.md` → `specs/state.yaml` | `survey-context` |
-
-Sub-AGENTS.md files (when present in consumer projects) override this table for their directory only.
-<!-- END bigpowers:context-routing -->
-
-<!-- BEGIN bigpowers:learned-preferences -->
-## Learned User Preferences
-
-_Durable preferences discovered across sessions. Update via `session-state` — do not infer from chat alone._
-
-- Prefer `rtk`-prefixed shell commands for git, test, and build output (token savings).
-- Run Preflight before forward work; never dismiss red gates as pre-existing.
-- Edit `skills/*/SKILL.md` sources only — never `.cursor/rules/` or `.gemini/` artifacts.
-
-## Workspace Facts
-
-_Stable repo facts — prefer these over re-discovery._
-
-- Stack: Markdown / Bash documentation project; skills sync via `bash scripts/sync-skills.sh`.
-- Planning SoT: `specs/state.yaml`, `specs/release-plan.yaml`, `specs/execution-status.yaml`.
-- Story traceability: `# story: eNNsNN` tags in implementing files; `bash scripts/trace-stories.sh --strict` in CI.
-- Rule matrix: `bash scripts/compile-rule-matrix.sh` → `specs/rule-matrix.json` (P0–P3 tiers from CONVENTIONS.md).
-<!-- END bigpowers:learned-preferences -->
-
-## Project
-
-bigpowers — agent skills for spec-driven, test-first software development by solo developers (skill count and catalog are auto-generated in `SKILL-INDEX.md`; never hardcode the count in docs).
-Stack: Markdown / Bash (documentation-based; skills integrate with Claude Code, Cursor, Gemini CLI)
-
-## Commands
-
-| Action  | Command |
-|---------|---------|
-| Install | `npm install -g bigpowers && bigpowers setup` |
-| Run     | `bash scripts/sync-skills.sh` |
-| Test    | N/A (documentation project) |
-| Build   | `bash scripts/install.sh` (from source) |
-| Lint    | `bash scripts/sync-skills.sh` (validates SKILL.md syntax) |
-| Validate specs YAML | `bash scripts/validate-specs-yaml.sh` |
-| Typecheck | N/A (Markdown / Bash project) |
-| CI platform | GitHub Actions — one pipeline `.github/workflows/test-build-release.yml` (sync, verification-gates, skill-verify, story-verify → release, and → pages-build → pages-deploy when docs paths change); plus `publish-wiki.yml` |
-| Compliance | `npm run compliance` |
-| Verification Gates | `bash scripts/run-verification-gates.sh` |
-| Traceability | `bash scripts/trace-stories.sh --strict` | grep for story tags (traceability check) |
-| Preflight | `npm run compliance && bash scripts/run-verification-gates.sh && bash scripts/sync-skills.sh && bash scripts/trace-stories.sh --strict` | Full local green stack before forward work. Chain ends on `--strict` traceability — no trailing always-exit-0 step. |
-| Catalog drift (advisory) | `bash scripts/check-catalog-drift.sh` | e54s02 Confirm gate during catalog freeze — always exits 0; run manually when changing skills, not part of Preflight. |
-| CI | `gh pr checks` | Remote CI green when a PR is open |
-
-### Pre-Merge Checklist
-
-Before opening a PR or landing a branch, run:
-
-```bash
-npm run compliance && bash scripts/run-verification-gates.sh
-```
-
-If any gate fails, fix before merging. Run `--baseline` after any intentional increase in skill count or structure.
-
-**BCP Plus:** For stories sized with the 13-dimension BCP Plus methodology, confirm the `bcp_plus_breakdown` is present in the epic YAML and carried into `state.yaml` as `epic_cycle.bcp_plus`. See `docs/references/bcp-plus.md` for the NFR Gate pattern.
-
-## Architecture
-
-Collection of verb-noun skills under `skills/`, each with a SKILL.md source file and supporting documentation. Runtime specs live in `specs/state.yaml`, `specs/release-plan.yaml`, and `specs/execution-status.yaml`; intent in `specs/product/`; epic shards in `specs/epics/`. The sync-skills.sh script auto-generates artifacts for Cursor (.cursor/rules) and Gemini CLI (.gemini/extensions/bigpowers/) from SKILL.md sources. All planning output goes to specs/ at the project root.
-
-## Conventions
-
-- Skill directories under `skills/` use verb-noun naming (two words, kebab-case)
-- Every skill has a single SKILL.md file as its source of truth
-- All planning/spec output goes to specs/ at project root
-- Artifacts in .cursor/rules and .gemini/ are auto-generated; edit SKILL.md, not artifacts
-- Run sync-skills.sh after any SKILL.md changes to regenerate artifacts
-- Website content in website/src/content/docs/ is auto-generated by prebuild; edit repo sources, not site files
-
-## Never
-
-- Never edit .cursor/rules or .gemini/extensions/ directly — these are generated files
-- Never edit website/src/content/docs/ directly — these are generated files; website/ is the fourth generated artifact target (alongside .cursor/, .gemini/, .pi/)
-- Never create a skill without a SKILL.md file and proper verb-noun naming
-- Never push changes without running sync-skills.sh first
-
-## Token Management
-
-**Mechanical backstop (e45s03):** `scripts/hooks/token-mgmt-pre-tool-use.sh` blocks oversized tool calls when prose rules are ignored. Wire as a `PreToolUse` hook for `Read`, `Grep`, and `Bash` (alongside `hooks/pre-tool-use.sh` for git safety). Thresholds: Read >100KB, Grep >200 matches without `head_limit`, Bash commands likely to exceed 500 output lines without `rtk`/`sqz compress`. Install snippet:
-
-```json
-{
-  "hooks": {
-    "PreToolUse": [
-      { "matcher": "Read|Grep|Bash", "hooks": [{ "type": "command", "command": "bash scripts/hooks/token-mgmt-pre-tool-use.sh" }] }
-    ]
-  }
-}
-```
-
-Context engineering (write/select/compress/isolate — see `docs/references/context-engineering.md`):
-
-- **Write (token-efficient content):** Short functions (4-20 lines), unique symbol names, headless tests. Don't restate code in comments.
-- **Select (include only what's relevant):** Use `bts_map` for ranked file lists, `survey-context` for phase bootstrap. Don't read files you don't need.
-- **Compress (reduce without losing structure):** Use `bts_compress` or pipe through `sqz compress`. Use `rtk` for build/test/git output (60-99% savings). Prefer `terse-mode` when context is heavy.
-- **Isolate (partition work):** Use `kickoff-branch` for isolated worktrees, `dispatch-agents` for parallel tasks with disjoint scopes, `session-state` for cold-start handoff.
-
-**Effort classification:** Skills carry an `effort:` frontmatter field (`light` | `standard` | `heavy`). Prefer `light` skills for bootstrap/status checks; reserve `heavy` for epic builds and multi-phase planning.
-
-- **Auto-Terse**: When a session exceeds 20 turns or the context window feels "heavy" (latency increasing), you MUST switch to `terse-mode` to save tokens.
-- **Context Compaction**: Every 10 turns, summarize the current session state and implementation decisions into a short, high-density note.
-- **Minimal Output**: Prefer text-only output for simple status; use `web_fetch` or `run_shell_command` only for evidence.
-- **Stream Stability**: When writing large files or long documents, output continuously in chunks of ~200 lines. Do not pause. If you need time to process, emit a placeholder comment rather than going silent.
-
-## Session Start
-
-Before any task, run this sequence — not optional:
-
-1. Read `CLAUDE.md` (this file)
-2. Read `CONVENTIONS.md`
-3. Read `specs/state.yaml` if it exists — current session and active epic
-4. Read `specs/release-plan.yaml` if it exists — active release context
-
-## Agent Rules
-
-- **Workflow Mandate:** You MUST use the bigpowers skills (e.g., `plan-work`, `develop-tdd`, `craft-skill`) to perform tasks. DO NOT write code directly in response to a user prompt like "build this feature".
-- **Always Green / fix-or-log:** Preflight and CI must be green before forward work. Any reproducible gate failure during unrelated work requires **quick-fix** or **fix-bug** — see CONVENTIONS § Discovered Defects. Never dismiss failures as pre-existing or out of scope.
-- Read specs/ and CONVENTIONS.md before writing code.
-- Write the minimum code that solves the stated problem. Nothing extra.
-- Run tests after every change. Show evidence before declaring done.
-- One clarifying question beats a wrong assumption baked into 200 lines.
-- All written output (plans, specs, investigations) goes in specs/.
-
-## bts toolchain
-
-`bts` is installed. Prefer its verbs over ad-hoc shell commands.
-
-| Task | Command | Avoid |
-|------|---------|-------|
-| Search code | `bts find --print <pattern>` | grep / find / cat |
-| Interactive search | `bts find <pattern>` | manual grep pipes |
-| Compress for context | `bts compress <file>` or `cmd \| bts compress` | summarising by hand |
-| Repo map | `bts map` | listing files by hand |
-| Library docs | `bts docs <lib>` | guessing from training data |
-| Package source | `bts src <pkg>` | git clone |
-| Toolchain health | `bts doctor` | which / command -v |
-
-**Rules**
-- Search with `bts find` before opening files to locate a symbol or pattern.
-- Pipe anything > 200 lines through `bts compress` before adding to context.
-- Run `bts map` when asked for a repo overview.
-- Use `bts docs <lib>` before answering questions about library APIs. Doc fetches use `scripts/lib/doc-fetch-cache.sh` (ETag-revalidated, 300s TTL).
-- If a tool is missing, say so and run `bts doctor` — do not silently substitute.
-
-<!-- BEGIN rtk-pretooluse-hook (e45s16 — mechanical PreToolUse backstop; remove block to disable) -->
-
-**RTK hook (installed):** `scripts/hooks/rtk-rewrite.sh` is symlinked into `~/.claude/hooks/` by `bash scripts/install.sh` and registered as a Bash `PreToolUse` hook. It delegates to `rtk hook claude` — prose rules below are a fallback only when the hook is absent.
-
-<!-- END rtk-pretooluse-hook -->
-
-<!-- BEGIN sqz-claude-guidance (auto-installed by sqz init; remove this block to disable) -->
-
-## sqz — Context Compression (READ FIRST)
-
-sqz is installed in this project. It compresses tool output so large
-files, long logs, and verbose command output cost far fewer tokens.
-There are **two ways** sqz is wired in, and you should prefer each
-one in the situations below.
-
-### Preferred tools (MCP)
-
-The `sqz-mcp` server is registered in this project's MCP config. It
-exposes three read-only tools that compress their output through the
-sqz pipeline:
-
-- **`sqz_read_file`** — read a file from disk and return a compressed
-  view. **PREFER this over the built-in `Read` tool** for any file
-  larger than ~2KB or any file you might read more than once in the
-  same session. Repeat reads return a 13-token `§ref:HASH§` reference
-  instead of the full content.
-
-- **`sqz_grep`** — search files for a literal string or regex.
-  **PREFER this over the built-in `Grep`** for anything that might
-  match more than a handful of lines. Caps at 200 matches by default;
-  raise with `max_matches` if needed.
-
-- **`sqz_list_dir`** — list a directory. Skips `.git`, `node_modules`,
-  `target`, `dist`, `build`, `vendor`, `__pycache__` so the output
-  stays focused. **PREFER this over `ls -la` via Bash** when you want
-  to see a project layout.
-
-The built-in `Read`, `Grep`, `Glob` tools remain available. Use them for:
-- Tiny config files (<1KB) where compression can't help.
-- Byte-exact reads you'll hash or diff (lockfiles, signatures).
-- Globbing (sqz has no glob tool; `Glob` is still the right choice).
-
-### Bash commands (hooked automatically)
-
-When you run a shell command through the `Bash` tool, a PreToolUse hook
-rewrites it to pipe output through `sqz compress`. This is transparent:
-you don't need to remember to add anything, but it's useful to know
-that these commands get compressed automatically:
-
-```bash
-git status           # → git status 2>&1 | sqz compress --cmd git
-cargo test           # → cargo test 2>&1 | sqz compress --cmd cargo
-docker ps            # → docker ps 2>&1 | sqz compress --cmd docker
-kubectl get pods     # → kubectl get pods 2>&1 | sqz compress --cmd kubectl
-```
-
-The rewrite is skipped for interactive commands (`vim`, `ssh`,
-`python`), compound commands (`a && b`, `a > file.txt`), and anything
-already going through sqz.
-
-### Escape hatch — when you see a `§ref:HASH§` token
-
-If tool output contains a `§ref:a1b2c3d4§` token and you need the full
-content it points at, resolve it. Three equivalent ways:
-
-- Shell: `/Users/danielvm/.local/bin/sqz expand a1b2c3d4` (or paste the whole token
-  `/Users/danielvm/.local/bin/sqz expand §ref:a1b2c3d4§`).
-- MCP tool: call `expand` with `{ "prefix": "a1b2c3d4" }`.
-- To get uncompressed output for one command: prefix it with
-  `SQZ_NO_DEDUP=1` (e.g. `SQZ_NO_DEDUP=1 git log | sqz compress`).
-
-If the compressed output is actively making the task harder (looping
-on refs, small retries replacing one big read), call the `passthrough`
-MCP tool to get raw text.
-
-### When NOT to use sqz tools
-
-- Writing or editing files — use the built-in `Write`/`Edit` tools.
-  sqz has no write tools (by design; see issue #5 follow-up).
-- Running commands interactively or in watch mode.
-- Reading very small files (<1KB) where compression can't help.
-
-<!-- END sqz-claude-guidance -->
-
-<!-- rtk-instructions v2 -->
-# RTK (Rust Token Killer) - Token-Optimized Commands
-
-## Golden Rule
-
-**Always prefix commands with `rtk`**. If RTK has a dedicated filter, it uses it. If not, it passes through unchanged. This means RTK is always safe to use.
-
-**Important**: Even in command chains with `&&`, use `rtk`:
-```bash
-# ❌ Wrong
-git add . && git commit -m "msg" && git push
-
-# ✅ Correct
-rtk git add . && rtk git commit -m "msg" && rtk git push
-```
-
-## RTK Commands by Workflow
-
-### Build & Compile (80-90% savings)
-```bash
-rtk cargo build         # Cargo build output
-rtk cargo check         # Cargo check output
-rtk cargo clippy        # Clippy warnings grouped by file (80%)
-rtk tsc                 # TypeScript errors grouped by file/code (83%)
-rtk lint                # ESLint/Biome violations grouped (84%)
-rtk prettier --check    # Files needing format only (70%)
-rtk next build          # Next.js build with route metrics (87%)
-```
-
-### Test (60-99% savings)
-```bash
-rtk cargo test          # Cargo test failures only (90%)
-rtk go test             # Go test failures only (90%)
-rtk jest                # Jest failures only (99.5%)
-rtk vitest              # Vitest failures only (99.5%)
-rtk playwright test     # Playwright failures only (94%)
-rtk pytest              # Python test failures only (90%)
-rtk rake test           # Ruby test failures only (90%)
-rtk rspec               # RSpec test failures only (60%)
-rtk test <cmd>          # Generic test wrapper - failures only
-```
-
-### Git (59-80% savings)
-```bash
-rtk git status          # Compact status
-rtk git log             # Compact log (works with all git flags)
-rtk git diff            # Compact diff (80%)
-rtk git show            # Compact show (80%)
-rtk git add             # Ultra-compact confirmations (59%)
-rtk git commit          # Ultra-compact confirmations (59%)
-rtk git push            # Ultra-compact confirmations
-rtk git pull            # Ultra-compact confirmations
-rtk git branch          # Compact branch list
-rtk git fetch           # Compact fetch
-rtk git stash           # Compact stash
-rtk git worktree        # Compact worktree
-```
-
-Note: Git passthrough works for ALL subcommands, even those not explicitly listed.
-
-### GitHub (26-87% savings)
-```bash
-rtk gh pr view <num>    # Compact PR view (87%)
-rtk gh pr checks        # Compact PR checks (79%)
-rtk gh run list         # Compact workflow runs (82%)
-rtk gh issue list       # Compact issue list (80%)
-rtk gh api              # Compact API responses (26%)
-```
-
-### JavaScript/TypeScript Tooling (70-90% savings)
-```bash
-rtk pnpm list           # Compact dependency tree (70%)
-rtk pnpm outdated       # Compact outdated packages (80%)
-rtk pnpm install        # Compact install output (90%)
-rtk npm run <script>    # Compact npm script output
-rtk npx <cmd>           # Compact npx command output
-rtk prisma              # Prisma without ASCII art (88%)
-```
-
-### Files & Search (60-75% savings)
-```bash
-rtk ls <path>           # Tree format, compact (65%)
-rtk read <file>         # Code reading with filtering (60%)
-rtk grep <pattern>      # Search grouped by file (75%). Format flags (-c, -l, -L, -o, -Z) run raw.
-rtk find <pattern>      # Find grouped by directory (70%)
-```
-
-### Analysis & Debug (70-90% savings)
-```bash
-rtk err <cmd>           # Filter errors only from any command
-rtk log <file>          # Deduplicated logs with counts
-rtk json <file>         # JSON structure without values
-rtk deps                # Dependency overview
-rtk env                 # Environment variables compact
-rtk summary <cmd>       # Smart summary of command output
-rtk diff                # Ultra-compact diffs
-```
-
-### Infrastructure (85% savings)
-```bash
-rtk docker ps           # Compact container list
-rtk docker images       # Compact image list
-rtk docker logs <c>     # Deduplicated logs
-rtk kubectl get         # Compact resource list
-rtk kubectl logs        # Deduplicated pod logs
-```
-
-### Network (65-70% savings)
-```bash
-rtk curl <url>          # Compact HTTP responses (70%)
-rtk wget <url>          # Compact download output (65%)
-```
-
-### Meta Commands
-```bash
-rtk gain                # View token savings statistics
-rtk gain --history      # View command history with savings
-rtk discover            # Analyze Claude Code sessions for missed RTK usage
-rtk proxy <cmd>         # Run command without filtering (for debugging)
-rtk init                # Add RTK instructions to CLAUDE.md
-rtk init --global       # Add RTK to ~/.claude/CLAUDE.md
-```
-
-## Token Savings Overview
-
-| Category | Commands | Typical Savings |
-|----------|----------|-----------------|
-| Tests | vitest, playwright, cargo test | 90-99% |
-| Build | next, tsc, lint, prettier | 70-87% |
-| Git | status, log, diff, add, commit | 59-80% |
-| GitHub | gh pr, gh run, gh issue | 26-87% |
-| Package Managers | pnpm, npm, npx | 70-90% |
-| Files | ls, read, grep, find | 60-75% |
-| Infrastructure | docker, kubectl | 85% |
-| Network | curl, wget | 65-70% |
-
-Overall average: **60-90% token reduction** on common development operations.
-<!-- /rtk-instructions -->

package/GEMINI.md

@@ -1,75 +0,0 @@
-# bigpowers — Gemini CLI
-
-> **Auto-generated** by `sync-skills.sh` from `CLAUDE.md`. Edit CLAUDE.md, not this file.
-
-Read CONVENTIONS.md before any GitHub or git operation.
-
-## Project
-
-bigpowers — 58 agent skills for spec-driven, test-first software development by solo developers.
-Stack: Markdown / Bash (documentation-based; skills integrate with Claude Code, Cursor, Gemini CLI)
-
-## Commands
-
-| Action  | Command |
-|---------|---------|
-| Install | `npm install -g bigpowers && bigpowers setup` |
-| Run     | `bash scripts/sync-skills.sh` |
-| Test    | N/A (documentation project) |
-| Build   | `bash scripts/install.sh` (from source) |
-| Lint    | `bash scripts/sync-skills.sh` (validates SKILL.md syntax) |
-
-## Architecture
-
-Collection of 58 verb-noun skills, each with a SKILL.md source file and supporting documentation. Includes Verify phase and profiles/. The sync-skills.sh script auto-generates artifacts for Cursor (.cursor/rules) and Gemini CLI (.gemini/extensions/bigpowers/) from SKILL.md sources. All planning and spec output goes to specs/ at the project root.
-
-## Conventions
-
-- Skill directories use verb-noun naming (two words, kebab-case)
-- Every skill has a single SKILL.md file as its source of truth
-- All planning/spec output goes to specs/ at project root
-- Artifacts in .cursor/rules and .gemini/ are auto-generated; edit SKILL.md, not artifacts
-- Run sync-skills.sh after any SKILL.md changes to regenerate artifacts
-
-## Never
-
-- Never edit .cursor/rules or .gemini/extensions/ directly — these are generated files
-- Never create a skill without a SKILL.md file and proper verb-noun naming
-- Never push changes without running sync-skills.sh first
-
-## Token Management
-
-- **Auto-Terse**: When a session exceeds 20 turns or the context window feels "heavy" (latency increasing), you MUST switch to `terse-mode` to save tokens.
-- **Context Compaction**: Every 10 turns, summarize the current session state and implementation decisions into a short, high-density note.
-- **Minimal Output**: Prefer text-only output for simple status; use `web_fetch` or `run_shell_command` only for evidence.
-
-## Agent Rules
-
-- **Workflow Mandate:** You MUST use the bigpowers skills (e.g., `plan-work`, `develop-tdd`, `craft-skill`) to perform tasks. DO NOT write code directly in response to a user prompt like "build this feature".
-- Read specs/ and CONVENTIONS.md before writing code.
-- Write the minimum code that solves the stated problem. Nothing extra.
-- Never refactor, rename, or reorganize code outside the task scope.
-- Run tests after every change. Show evidence before declaring done.
-- One clarifying question beats a wrong assumption baked into 200 lines.
-- All written output (plans, specs, investigations) goes in specs/.
-
-## bts toolchain
-
-`bts` is installed. Prefer its verbs over ad-hoc shell commands.
-
-| Task | Command | Avoid |
-|------|---------|-------|
-| Search code | `bts find --print <pattern>` | grep / find / cat |
-| Interactive search | `bts find <pattern>` | manual grep pipes |
-| Compress for context | `bts compress <file>` or `cmd \| bts compress` | summarising by hand |
-| Repo map | `bts map` | listing files by hand |
-| Library docs | `bts docs <lib>` | guessing from training data |
-| Package source | `bts src <pkg>` | git clone |
-| Toolchain health | `bts doctor` | which / command -v |
-
-**Rules**
-- Search with `bts find` before opening files to locate a symbol or pattern.
-- Pipe anything > 200 lines through `bts compress` before adding to context.
-- Run `bts map` when asked for a repo overview.
-- Use `bts docs <lib>` before answering questions about library APIs.
-- If a tool is missing, say so and run `bts doctor` — do not silently substitute.