aiki-cli 0.2.0 → 0.2.1

package/CHANGELOG.md

@@ -17,6 +17,10 @@
   intent preflight and the judge seat also writes the validation plan. The default budget is now 13 so
   a normal run still has room for one repair without skipping the validation plan.
 
+### Fixed
+- Codex provider smoke no longer crashes in non-git folders; Aiki now passes Codex's verified
+  `--skip-git-repo-check` flag while keeping `-s read-only`.
+
 ## 0.2.0 — 2026-07-06 — v2 product round
 
 ### Added

package/README.md

@@ -104,12 +104,21 @@ n = 10 cases, single run per arm — directional, not a p-value. Full method and
 aiki doctor          # lists each provider: version, ready/not, read-only mode
 ```
 
+`aiki doctor` is safe to run from any folder. For Codex, Aiki passes `--skip-git-repo-check` while
+keeping the read-only sandbox enabled, so non-git folders do not crash the provider smoke:
+
+```bash
+aiki doctor --fresh
+```
+
 ## Install
 
 ```bash
 npm install -g aiki-cli
 ```
 
+The package is `aiki-cli`; it installs the `aiki` command.
+
 From source:
 
 ```bash
@@ -123,9 +132,24 @@ npm link             # puts `aiki` on your PATH   (or run directly: node dist/cl
 ## Quickstart
 
 ```bash
+cd /path/to/your/project
 aiki                 # opens the interactive home screen
 ```
 
+## Use Aiki For
+
+- Code review: "review this branch", "check this patch", "find bugs in this diff".
+- Idea stress-testing: "pressure-test this product idea", "find risks in this plan", "what must be validated first?"
+- Decisions where disagreement helps: multiple models analyze independently, cross-examine, then a judge writes the brief.
+
+## Do Not Use Aiki For
+
+- Chatting, trivia, writing emails, summaries, or general Q&A.
+- Questions with one straightforward answer, like "what is Docker?" or "explain React hooks".
+- Asking it to edit files, run commands, or act like an autonomous coding agent.
+
+If you want chat, use your normal assistant. Aiki is for expensive council-style review and idea pressure-testing.
+
 Type a command, or just describe an idea and press Enter:
 
 | Command | What it does |

package/dist/providers/codex.js

@@ -1,7 +1,7 @@
 import { runAdapter } from './adapter-core.js';
 /**
  * Codex CLI (`codex`). Invocation (verified live, T3):
- *   codex exec [-s read-only] "<prompt>"   (cwd set via spawn's cwd option)
+ *   codex exec --skip-git-repo-check [-s read-only] "<prompt>"   (cwd set via spawn's cwd option)
  *
  * Output split (verified): stdout carries ONLY the model's final message; the full session
  * transcript (session id, echoed prompt, "tokens used") goes to stderr. So stdout *is* the
@@ -11,13 +11,13 @@ import { runAdapter } from './adapter-core.js';
  * Because codex mirrors the prompt + result into stderr, error classification must not scan
  * stderr on success — adapter-core.classify short-circuits on exit 0 for exactly this reason.
  *
- * T10 note: `codex exec` may need a git-repo/writable-cwd check for arbitrary review dirs;
- * verify when wiring code-review. NEVER pass --dangerously-bypass-approvals-and-sandbox (§19).
+ * `--skip-git-repo-check` is safe here: it only permits arbitrary cwd for run-anywhere
+ * support and does not bypass approvals or the read-only sandbox.
  */
 const codexSpec = {
     id: 'codex',
     buildArgs(req, flags) {
-        const args = ['exec'];
+        const args = ['exec', '--skip-git-repo-check'];
         if (req.readOnly !== false && flags.readOnlyFlag === 'sandbox')
             args.push('-s', 'read-only');
         if (flags.model)

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "aiki-cli",
-  "version": "0.2.0",
+  "version": "0.2.1",
   "description": "Local-first orchestration CLI binding your installed AI coding CLIs into schema-validated multi-model workflows.",
   "type": "module",
   "license": "MIT",