omnilane 0.42.2 → 0.42.4

package/.claude-plugin/marketplace.json

@@ -6,14 +6,14 @@
   },
   "metadata": {
     "description": "One routing table, native-first or CLI delegation, supervised completion workflows.",
-    "version": "0.42.2"
+    "version": "0.42.4"
   },
   "plugins": [
     {
       "name": "omnilane",
       "source": "./",
       "description": "Route each subtask to the model that fits, then delegate through a compatible caller-owned native agent or vendor CLI.",
-      "version": "0.42.2",
+      "version": "0.42.4",
       "category": "development",
       "keywords": [
         "routing",

package/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "omnilane",
-  "version": "0.42.2",
+  "version": "0.42.4",
   "description": "One routing table, every harness: classify subtasks into lanes and delegate through compatible caller-owned native agents or vendor CLIs with exact-AA downward policy and supervised jobs.",
   "author": {
     "name": "Seraphim0916"

package/CHANGELOG.md

@@ -6,6 +6,43 @@ semantic version tags.
 
 ## [Unreleased]
 
+## [0.42.4] - 2026-09-07
+
+### Fixed
+
+- The 60-second start in all five READMEs ran `omnilane route` with no caller
+  identity, so a new user following it was refused with `missing-caller-context`
+  and the READMEs said nothing about the fix. The quickstart now asserts the
+  human operator once with `OMNILANE_AA_OPERATOR_ASSERTED_HUMAN=1`, and a note
+  explains why a dispatch must say who is asking, what a model caller passes
+  instead, and what happens when neither is present.
+- The `dispatch.sh` synopsis in the command reference gains
+  `[--caller-context FILE | --operator-asserted-human]`.
+
+0.42.3 documented this inside the dispatch skill but left the user-facing
+quickstart unchanged, which is the path a new install actually takes.
+
+## [0.42.3] - 2026-09-07
+
+### Documentation
+
+- The dispatch quick reference now shows `--caller-context FILE` in the command
+  signature and states that a model caller without it is refused with
+  `missing-caller-context` before a job exists.
+- The frozen exact-AA downward gate section gains a complete caller-context
+  example and says to build the file before the first dispatch rather than after
+  a refusal.
+- New guidance for a harness that names a model but no effort: read the exact
+  flags from the launching process by walking your own ancestor chain, matching
+  the chain rather than the first same-named process on the host. Declaring the
+  lowest-scoring row is documented as the fallback when that yields nothing, not
+  as the first move, because an unnecessarily low ceiling silently closes lanes.
+- `missing-caller-context` and `runtime-mapping-unverified` are now distinguished
+  with the fix for each, including the warning that the second is never resolved
+  by editing the frozen registry whose SHA-256 is pinned in `aa_policy.py`.
+
+No routing, scoring, gate, or runner behaviour changes in this release.
+
 ## [0.42.2] - 2026-09-07
 
 ### Fixed
@@ -849,7 +886,9 @@ work to the wrong model, and records the evidence behind the shipped defaults.
 - Initial shared routing table, cross-vendor dispatcher, runners, installer,
   and baseline lint fixes.
 
-[Unreleased]: https://github.com/Seraphim0916/omnilane/compare/v0.42.2...HEAD
+[Unreleased]: https://github.com/Seraphim0916/omnilane/compare/v0.42.4...HEAD
+[0.42.4]: https://github.com/Seraphim0916/omnilane/compare/v0.42.3...v0.42.4
+[0.42.3]: https://github.com/Seraphim0916/omnilane/compare/v0.42.2...v0.42.3
 [0.42.2]: https://github.com/Seraphim0916/omnilane/compare/v0.42.1...v0.42.2
 [0.42.1]: https://github.com/Seraphim0916/omnilane/compare/v0.42.0...v0.42.1
 [0.42.0]: https://github.com/Seraphim0916/omnilane/compare/v0.41.1...v0.42.0

package/README.ja.md

@@ -52,6 +52,7 @@ Cursor、Gemini CLI** など——を使っていますよね。どれも一つ
 
 ```bash
 npm i -g omnilane                                    # CLI をインストール
+export OMNILANE_AA_OPERATOR_ASSERTED_HUMAN=1         # 呼び出しているのは人間の操作者
 omnilane route hardest-coding "auth トークン更新テストの不安定さを修正"
 omnilane doctor                                      # 使える AI CLI / キーを確認
 omnilane ui start                                    # 任意:ブラウザでジョブをライブ表示
@@ -62,9 +63,17 @@ omnilane ui start                                    # 任意:ブラウザでジ
 ```bash
 git clone https://github.com/Seraphim0916/omnilane && cd omnilane
 ./install.sh          # CLI を検出、スキルを接続、あなたの言語で対話
+export OMNILANE_AA_OPERATOR_ASSERTED_HUMAN=1         # 呼び出しているのは人間の操作者
 omnilane route hardest-coding "auth トークン更新テストの不安定さを修正"
 ```
 
+> **あの export は何のため?** omnilane は呼び出し元自身の能力スコアで各ディスパッチを
+> ゲートするため、「誰が依頼しているか」を必ず示す必要があります。端末の前にいる人間は
+> `OMNILANE_AA_OPERATOR_ASSERTED_HUMAN=1` を一度設定するか、呼び出しごとに
+> `--operator-asserted-human` を付けます。omnilane を動かすモデルは**自分でこれを主張
+> できません**。代わりに正確なベンダー・モデル・effort を持つ `--caller-context FILE` を
+> 渡します。どちらも無い場合、ジョブ生成前に `missing-caller-context` で拒否されます。
+
 > はじめての方は、まず `omnilane doctor` を実行してください。omnilane が今どのモデル CLI と
 > API キーに接続できるかがわかり、実際に何が動くか把握できます。
 
@@ -292,6 +301,7 @@ omnilane ui stop                               # Live UI を停止
 omnilane doctor [--json]                       # ルーティングとローカル実行環境を読み取り専用で診断
 dispatch.sh [--background] [--dry-run] [--thread NAME] [--mode advise|work|sysops] [--workdir DIR]
             [--vendor V] [--model M] [--effort E] [--timeout SEC] [--job-timeout SEC]
+            [--caller-context FILE | --operator-asserted-human]   # who is asking
             LANE "TASK"                              # "-" で stdin から読む
 dispatch.sh [--json] --list [--json]
 dispatch.sh [--json] --explain LANE [--json]       # 候補ごとの決定理由をオフライン表示
@@ -533,6 +543,20 @@ work の別名ではありません。サービス管理など、work の境界
 
 ## 📜 リリース履歴
 
+## v0.42.4 の新機能
+
+- **クイックスタートが実際に動くようになりました。** `omnilane route` は「誰が依頼しているか」を必要としますが、60 秒クイックスタートにその記載が無く、新規インストールでは案内無しに `missing-caller-context` で拒否されていました。今は `OMNILANE_AA_OPERATOR_ASSERTED_HUMAN=1` で人間の操作者を一度宣言し、モデル呼び出し元が代わりに渡すものも説明します。
+- **コマンドリファレンス。** `dispatch.sh` の書式に `[--caller-context FILE | --operator-asserted-human]` を追加しました。
+
+## v0.42.3 の新機能
+
+- **ドキュメントのみの更新。** ルーティング、スコア、ゲート、ランナーの動作は変更していません。
+- **`--caller-context` をクイックリファレンスに明記。** ディスパッチのコマンド書式に追加し、モデル呼び出し元がこれを渡さない場合はジョブ生成前に `missing-caller-context` で拒否されることを明示しました。
+- **caller-context の完全な例。** 凍結 exact-AA 下方ゲートの節に、そのまま使える JSON 例を追加し、拒否されてからではなく最初のディスパッチ前に作成するよう記載しました。
+- **effort は推測せず調べる。** ハーネスがモデル名のみで effort を示さない場合、自分の祖先プロセス連鎖をたどって正確なフラグを読み取ります。同名プロセスの先頭ではなく連鎖を照合してください。最低スコア行の宣言は取得できなかった場合の代替であり最初の手段ではありません。不必要に低い上限はレーンを黙って閉じます。
+- **二つの拒否コード、二つの対処。** `missing-caller-context` はファイル未指定、`runtime-mapping-unverified` は対象にホストローカルの検証済みセレクタが無いことを意味し、実証拠に基づく `--transport-overlay` 項目で解決します。凍結レジストリの編集では決して解決しません。
+- **アップグレード。** npm 公開後に `npm i -g omnilane@0.42.3` を実行します。既存のリポジトリシンボリックリンク導入はチェックアウトを更新し `omnilane --version` を確認すれば、再インストールは不要です。
+
 ## v0.42.2 の新機能
 
 - **Grok の推論強度を CLI に渡します。** 明示的な `low`、`medium`、`high`、`xhigh` は `--reasoning-effort` で渡され、Grok 4.6 の既定ルートは `high` を選択します。

package/README.ko.md

@@ -51,6 +51,7 @@ Gemini CLI** 같은——를 쓰고 계시죠. 각각은 하나의 모델 계열
 
 ```bash
 npm i -g omnilane                                    # CLI 설치
+export OMNILANE_AA_OPERATOR_ASSERTED_HUMAN=1         # 호출자는 모델이 아닌 사람 운영자
 omnilane route hardest-coding "간헐적으로 실패하는 auth 토큰 갱신 테스트 수정"
 omnilane doctor                                      # 사용 가능한 AI CLI / 키 확인
 omnilane ui start                                    # 선택: 브라우저에서 잡을 실시간 확인
@@ -61,9 +62,17 @@ omnilane ui start                                    # 선택: 브라우저에
 ```bash
 git clone https://github.com/Seraphim0916/omnilane && cd omnilane
 ./install.sh          # CLI 감지, 스킬 연결, 당신의 언어로 대화
+export OMNILANE_AA_OPERATOR_ASSERTED_HUMAN=1         # 호출자는 모델이 아닌 사람 운영자
 omnilane route hardest-coding "간헐적으로 실패하는 auth 토큰 갱신 테스트 수정"
 ```
 
+> **그 export 는 왜 필요한가요?** omnilane 은 호출자 자신의 능력 점수로 모든 디스패치를
+> 게이트하므로, 디스패치는 «누가 요청하는지»를 반드시 밝혀야 합니다. 터미널 앞의 사람은
+> `OMNILANE_AA_OPERATOR_ASSERTED_HUMAN=1` 을 한 번 설정하거나 호출마다
+> `--operator-asserted-human` 을 붙입니다. omnilane 을 구동하는 모델은 **스스로 이를 주장할
+> 수 없으며**, 대신 정확한 벤더·모델·effort 를 담은 `--caller-context FILE` 을 전달합니다.
+> 둘 다 없으면 잡 생성 전에 `missing-caller-context` 로 거부됩니다.
+
 > 처음이신가요? 먼저 `omnilane doctor` 를 실행하세요. omnilane 이 지금 어떤 모델 CLI 와
 > API 키에 접근할 수 있는지 알려 주어, 실제로 무엇이 실행될지 파악할 수 있습니다.
 
@@ -284,6 +293,7 @@ omnilane ui stop                               # Live UI 중지
 omnilane doctor [--json]                       # 라우팅과 로컬 실행 환경을 읽기 전용으로 진단
 dispatch.sh [--background] [--dry-run] [--thread NAME] [--mode advise|work|sysops] [--workdir DIR]
             [--vendor V] [--model M] [--effort E] [--timeout SEC] [--job-timeout SEC]
+            [--caller-context FILE | --operator-asserted-human]   # who is asking
             LANE "TASK"                              # "-" 는 stdin 에서 읽기
 dispatch.sh [--json] --list [--json]
 dispatch.sh [--json] --explain LANE [--json]       # 후보별 라우팅 결정을 오프라인 설명
@@ -518,6 +528,20 @@ work 는 지정한 디렉터리 안의 변경만 허용하며 모델 연결은
 
 ## 📜 릴리스 기록
 
+## v0.42.4 새 기능
+
+- **퀵스타트가 실제로 동작합니다.** `omnilane route` 는 «누가 요청하는지»를 알아야 하지만 60초 시작에 그 내용이 없어, 새 설치에서는 안내 없이 `missing-caller-context` 로 거부되었습니다. 이제 `OMNILANE_AA_OPERATOR_ASSERTED_HUMAN=1` 로 사람 운영자를 한 번 선언하며, 모델 호출자가 대신 전달할 것도 설명합니다.
+- **명령 참조.** `dispatch.sh` 서식에 `[--caller-context FILE | --operator-asserted-human]` 을 추가했습니다.
+
+## v0.42.3 새 기능
+
+- **문서 전용 업데이트.** 라우팅, 점수, 게이트, 러너 동작은 변경되지 않았습니다.
+- **`--caller-context` 를 빠른 참조에 명시.** 디스패치 명령 서식에 추가했고, 모델 호출자가 이를 전달하지 않으면 작업 생성 전에 `missing-caller-context` 로 거부된다는 점을 명시했습니다.
+- **완전한 caller-context 예시.** 동결된 exact-AA 하향 게이트 절에 그대로 사용할 수 있는 JSON 예시를 추가하고, 거부된 뒤가 아니라 첫 디스패치 전에 파일을 만들도록 기술했습니다.
+- **effort 는 추측하지 말고 확인.** 하네스가 모델명만 제공하고 effort 를 주지 않으면, 자신의 조상 프로세스 체인을 따라 정확한 플래그를 읽습니다. 호스트의 동일 이름 첫 프로세스가 아니라 체인을 대조해야 합니다. 최저 점수 행 선언은 확인이 불가능할 때의 대안이지 첫 수단이 아닙니다. 불필요하게 낮은 상한은 레인을 조용히 닫습니다.
+- **두 거부 코드, 두 가지 해결.** `missing-caller-context` 는 파일 미전달이고, `runtime-mapping-unverified` 는 대상에 검증된 호스트 로컬 셀렉터가 없다는 뜻으로, 실제 증거에 기반한 `--transport-overlay` 항목으로 해결합니다. 동결 레지스트리 편집으로는 결코 해결되지 않습니다.
+- **업그레이드.** npm 게시 후 `npm i -g omnilane@0.42.3` 을 실행합니다. 기존 리포지토리 심볼릭 링크 설치는 체크아웃을 갱신하고 `omnilane --version` 을 확인하면 되며 재설치는 필요 없습니다.
+
 ## v0.42.2 새 기능
 
 - **Grok 추론 강도를 CLI에 전달합니다.** 명시적 `low`, `medium`, `high`, `xhigh` 선택을 `--reasoning-effort`로 전달하며 Grok 4.6 기본 경로는 `high`를 선택합니다.

package/README.md

@@ -52,6 +52,7 @@ subscription.
 
 ```bash
 npm i -g omnilane                                    # install the CLI
+export OMNILANE_AA_OPERATOR_ASSERTED_HUMAN=1         # you are the operator, not a model
 omnilane route hardest-coding "fix the flaky auth token refresh"
 omnilane doctor                                      # see which AI CLIs / keys you have
 omnilane ui start                                    # optional: watch jobs live in your browser
@@ -62,9 +63,18 @@ omnilane ui start                                    # optional: watch jobs live
 ```bash
 git clone https://github.com/Seraphim0916/omnilane && cd omnilane
 ./install.sh          # finds your CLIs, links the skill, speaks your language
+export OMNILANE_AA_OPERATOR_ASSERTED_HUMAN=1         # you are the operator, not a model
 omnilane route hardest-coding "fix the flaky auth token refresh"
 ```
 
+> **Why that export?** Omnilane gates every delegation against the caller's own
+> capability score, so a dispatch has to say who is asking. A human at a terminal
+> asserts that once with `OMNILANE_AA_OPERATOR_ASSERTED_HUMAN=1`, or per call with
+> `--operator-asserted-human`. A model driving omnilane cannot assert it for
+> itself — it passes `--caller-context FILE` carrying its exact vendor, model and
+> effort instead. With neither, the dispatch is refused with
+> `missing-caller-context` before any job is created.
+
 > New to this? Run `omnilane doctor` first — it tells you which model CLIs and
 > API keys omnilane can already reach, so you know what will actually run.
 
@@ -372,6 +382,7 @@ omnilane doctor [--json] [--strict] [--probe V] [--probe-timeout SEC]  # live pr
 omnilane benchmark [--json] [--run] [--vendor V] [--cost-per-call V=USD] # dry-run by default
 dispatch.sh [--background] [--dry-run] [--thread NAME] [--mode advise|work|sysops] [--workdir DIR]
             [--vendor V] [--model M] [--effort E] [--timeout SEC] [--job-timeout SEC]
+            [--caller-context FILE | --operator-asserted-human]   # who is asking
             LANE "TASK"                              # "-" reads task from stdin
 dispatch.sh [--json] --list [--json]
 dispatch.sh [--json] --explain LANE [--json]       # offline candidate-by-candidate decision trace
@@ -627,6 +638,20 @@ working notes, including per-benchmark caveats, live in
 
 ## 📜 Release history
 
+## What's new in v0.42.4
+
+- **The quickstart actually runs now.** `omnilane route` needs to know who is asking; the 60-second start omitted that, so a fresh install hit `missing-caller-context` with no guidance. It now asserts the human operator once with `OMNILANE_AA_OPERATOR_ASSERTED_HUMAN=1`, and explains what a model caller passes instead.
+- **Command reference.** The `dispatch.sh` synopsis shows `[--caller-context FILE | --operator-asserted-human]`.
+
+## What's new in v0.42.3
+
+- **Documentation only.** No routing, scoring, gate, or runner behaviour changes.
+- **`--caller-context` is in the quick reference.** The dispatch command signature now shows it, and states that a model caller without it is refused with `missing-caller-context` before a job exists.
+- **A worked caller-context example.** The frozen exact-AA downward gate section gains a complete JSON example, and says to build the file before the first dispatch rather than after a refusal.
+- **Find your own effort instead of guessing.** When a harness names a model but no effort, read the exact flags from the launching process by walking your own ancestor chain; match the chain rather than the first same-named process on the host. Declaring the lowest-scoring row is the fallback, not the first move, because an unnecessarily low ceiling silently closes lanes.
+- **Two refusal codes, two fixes.** `missing-caller-context` means no file was passed; `runtime-mapping-unverified` means the target lacks a proven host-local selector, which is fixed by a `--transport-overlay` entry backed by real evidence and never by editing the frozen registry.
+- **Upgrade.** After npm publication, run `npm i -g omnilane@0.42.3`. Existing repo-symlink installations can update their checkout and verify `omnilane --version` without rerunning installation.
+
 ## What's new in v0.42.2
 
 - **Grok effort reaches the CLI.** Explicit `low`, `medium`, `high`, and `xhigh` selections are passed with `--reasoning-effort`; Grok 4.6 default routes now select `high`.

package/README.zh-CN.md

@@ -47,6 +47,7 @@ Gemini CLI** 之类。每一个都只接一个模型家族,所以你交代的每
 
 ```bash
 npm i -g omnilane                                    # 装 CLI
+export OMNILANE_AA_OPERATOR_ASSERTED_HUMAN=1         # 你是操作者本人,不是模型
 omnilane route hardest-coding "修掉会间歇失败的 auth token 更新测试"
 omnilane doctor                                      # 看你手上有哪些 AI CLI / 金钥
 omnilane ui start                                    # 选配:在浏览器即时看派工
@@ -57,9 +58,17 @@ omnilane ui start                                    # 选配:在浏览器即时
 ```bash
 git clone https://github.com/Seraphim0916/omnilane && cd omnilane
 ./install.sh          # 侦测你的 CLI、接好技能、说你的语言
+export OMNILANE_AA_OPERATOR_ASSERTED_HUMAN=1         # 你是操作者本人,不是模型
 omnilane route hardest-coding "修掉会间歇失败的 auth token 更新测试"
 ```
 
+> **那个 export 是做什么的?** omnilane 会用调用者自己的能力分数来把关每一次派工,
+> 所以派工必须表明「是谁在问」。人类在终端前只要设一次
+> `OMNILANE_AA_OPERATOR_ASSERTED_HUMAN=1`,或每次带 `--operator-asserted-human`。
+> 模型驱动 omnilane 时**不能替自己主张**这个标志,它要改用 `--caller-context FILE`
+> 提供确切的厂商、模型与强度。两者都没有的话,派工会在创建作业前就被
+> `missing-caller-context` 拒绝。
+
 > 第一次用?先跑 `omnilane doctor`——它会告诉你 omnilane 现在能接到哪些模型 CLI 与
 > API 金钥,你就知道实际会跑什么。
 
@@ -267,6 +276,7 @@ omnilane ui stop                               # 停止 Live UI
 omnilane doctor [--json]                       # 只读检查路由与本地运行环境
 dispatch.sh [--background] [--dry-run] [--thread NAME] [--mode advise|work|sysops] [--workdir 目录]
             [--vendor V] [--model M] [--effort E] [--timeout SEC] [--job-timeout SEC]
+            [--caller-context FILE | --operator-asserted-human]   # who is asking
             通道 "任务"                              # "-" 表示从 stdin 读任务
 dispatch.sh [--json] --list [--json]
 dispatch.sh [--json] --explain 通道 [--json]       # 离线逐候选解释路由决策
@@ -493,6 +503,20 @@ scripts/dispatch.sh --dry-run hardest-coding "…"   # 完整解析后的计划,
 
 ## 📜 版本历程
 
+## v0.42.4 新功能
+
+- **快速上手现在真的跑得起来。** `omnilane route` 必须知道「是谁在问」,但 60 秒上手漏了这件事,新安装照抄会直接吃到 `missing-caller-context` 且没有任何指引。现在会先用 `OMNILANE_AA_OPERATOR_ASSERTED_HUMAN=1` 表明操作者身分,并说明模型主控该改用什么。
+- **命令参考。** `dispatch.sh` 的用法摘要补上 `[--caller-context FILE | --operator-asserted-human]`。
+
+## v0.42.3 新功能
+
+- **纯文档更新。** 路由、评分、闸门与执行器行为均未变更。
+- **`--caller-context` 进入快速参考。** 派工命令签名现已列出该参数，并说明模型主控未携带时会在创建作业前被 `missing-caller-context` 拒绝。
+- **完整的 caller-context 示例。** 冻结 exact-AA 下行闸章节补充了可直接复制的 JSON 示例，并要求在首次派工前建好，而非被拒后才补。
+- **自行查询强度，不要猜测。** 当运行环境只给出模型名称而无强度时，沿自身祖先进程链读取确切标志；应比对整条链，而非主机上第一个同名进程。声明最低分配置是查不到时的退路，而非首选，因为过低的上限会静默关闭车道。
+- **两个拒绝码，两种修法。** `missing-caller-context` 表示未提供文件；`runtime-mapping-unverified` 表示目标缺少已验证的本机选择器，须以真实证据支撑的 `--transport-overlay` 条目修正，绝不可通过修改冻结注册表解决。
+- **升级。** npm 发布后执行 `npm i -g omnilane@0.42.3`。既有的 repo 符号链接安装可更新检出并确认 `omnilane --version`，无需重跑安装。
+
 ## v0.42.2 新功能
 
 - **Grok 强度确实传入 CLI。** 显式的 `low`、`medium`、`high`、`xhigh` 通过 `--reasoning-effort` 传递；Grok 4.6 默认路由指定 `high`。

package/README.zh-TW.md

@@ -47,6 +47,7 @@ Gemini CLI** 之類。每一個都只接一個模型家族,所以你交代的每
 
 ```bash
 npm i -g omnilane                                    # 裝 CLI
+export OMNILANE_AA_OPERATOR_ASSERTED_HUMAN=1         # 你是操作者本人,不是模型
 omnilane route hardest-coding "修掉會間歇失敗的 auth token 更新測試"
 omnilane doctor                                      # 看你手上有哪些 AI CLI / 金鑰
 omnilane ui start                                    # 選配:在瀏覽器即時看派工
@@ -57,9 +58,17 @@ omnilane ui start                                    # 選配:在瀏覽器即時
 ```bash
 git clone https://github.com/Seraphim0916/omnilane && cd omnilane
 ./install.sh          # 偵測你的 CLI、接好技能、說你的語言
+export OMNILANE_AA_OPERATOR_ASSERTED_HUMAN=1         # 你是操作者本人,不是模型
 omnilane route hardest-coding "修掉會間歇失敗的 auth token 更新測試"
 ```
 
+> **那個 export 是做什麼的?** omnilane 會用呼叫者自己的能力分數來把關每一次派工,
+> 所以派工必須表明「是誰在問」。人類在終端機前只要設一次
+> `OMNILANE_AA_OPERATOR_ASSERTED_HUMAN=1`,或每次帶 `--operator-asserted-human`。
+> 模型驅動 omnilane 時**不能替自己主張**這個旗標,它要改用 `--caller-context FILE`
+> 提供確切的廠商、模型與強度。兩者都沒有的話,派工會在建立工作前就被
+> `missing-caller-context` 拒絕。
+
 > 第一次用?先跑 `omnilane doctor`——它會告訴你 omnilane 現在能接到哪些模型 CLI 與
 > API 金鑰,你就知道實際會跑什麼。
 
@@ -306,6 +315,7 @@ omnilane doctor [--json] [--strict] [--probe V] [--probe-timeout SEC]  # 實際
 omnilane benchmark [--json] [--run] [--vendor V] [--cost-per-call V=USD] # 預設只乾跑
 dispatch.sh [--background] [--dry-run] [--thread NAME] [--mode advise|work|sysops] [--workdir 目錄]
             [--vendor V] [--model M] [--effort E] [--timeout SEC] [--job-timeout SEC]
+            [--caller-context FILE | --operator-asserted-human]   # who is asking
             通道 "任務"                              # "-" 表示從 stdin 讀任務
 dispatch.sh [--json] --list [--json]
 dispatch.sh [--json] --explain 通道 [--json]       # 離線逐候選解釋路由決策
@@ -534,6 +544,20 @@ scripts/dispatch.sh --dry-run hardest-coding "…"   # 完整解析後的計畫,
 
 ## 📜 版本歷程
 
+## v0.42.4 新功能
+
+- **快速上手現在真的跑得起來。** `omnilane route` 必須知道「是誰在問」,但 60 秒上手漏了這件事,新安裝照抄會直接吃到 `missing-caller-context` 且沒有任何指引。現在會先用 `OMNILANE_AA_OPERATOR_ASSERTED_HUMAN=1` 表明操作者身分,並說明模型主控該改用什麼。
+- **指令參考。** `dispatch.sh` 的用法摘要補上 `[--caller-context FILE | --operator-asserted-human]`。
+
+## v0.42.3 新功能
+
+- **純文件更新。** 路由、評分、閘門與執行器行為皆未變更。
+- **`--caller-context` 進入快速參考。** 派工指令簽名現在明列這個參數，並說明模型主控未帶時會在建立工作前被 `missing-caller-context` 拒絕。
+- **完整的 caller-context 範例。** 凍結 exact-AA 下行閘章節補上可直接複製的 JSON 範例，並要求在第一次派工前就建好，而非被拒絕後才補。
+- **自己查強度，不要猜。** 當執行環境只給模型名稱而沒有強度時，走自己的祖先行程鏈讀出確切旗標；要比對整條鏈，不要抓主機上第一個同名行程。宣告最低分設定是查不到時的退路，不是第一步，因為過低的上限會靜默關掉車道。
+- **兩個拒絕碼，兩種修法。** `missing-caller-context` 是沒有提供檔案；`runtime-mapping-unverified` 是目標缺少已驗證的本機選擇器，須以有真實證據支撐的 `--transport-overlay` 條目修正，絕不可透過修改凍結登錄檔解決。
+- **升級。** npm 發布後執行 `npm i -g omnilane@0.42.3`。既有的 repo 符號連結安裝可更新檢出並確認 `omnilane --version`，不需重跑安裝。
+
 ## v0.42.2 新功能
 
 - **Grok 強度確實傳入 CLI。** 明示的 `low`、`medium`、`high`、`xhigh` 透過 `--reasoning-effort` 傳遞；Grok 4.6 預設路由指定 `high`。

package/VERSION

@@ -1 +1 @@
-0.42.2
+0.42.4

package/docs/release-notes-0.42.4.md

@@ -0,0 +1,47 @@
+# Omnilane 0.42.4
+
+This patch fixes the user-facing quickstart. It changes no routing, scoring, gate,
+runner, or CLI behaviour.
+
+## Why
+
+0.42.3 documented `--caller-context` inside the dispatch skill, which is what a
+model driving omnilane reads. It left the READMEs' 60-second start untouched —
+and that is the path a new install actually takes. A user who ran
+
+```bash
+npm i -g omnilane
+omnilane route hardest-coding "fix the flaky auth token refresh"
+```
+
+was refused with `missing-caller-context`, and no README section explained the
+flag that resolves it. The gate was working as designed; the documentation simply
+never told a first-time user how to satisfy it.
+
+## Changes
+
+- The 60-second start in all five READMEs asserts the human operator once with
+  `OMNILANE_AA_OPERATOR_ASSERTED_HUMAN=1` before the first `omnilane route`.
+- A note after the quickstart explains why a dispatch must say who is asking:
+  a human at a terminal asserts it with that variable or `--operator-asserted-human`
+  per call; a model driving omnilane cannot assert it for itself and passes
+  `--caller-context FILE` with its exact vendor, model, and effort instead; with
+  neither, the dispatch is refused before any job is created.
+- The `dispatch.sh` synopsis in the command reference now shows
+  `[--caller-context FILE | --operator-asserted-human]`.
+
+## Verification boundary
+
+`--operator-asserted-human` is cooperative operator metadata. It is not automatic
+model detection and not OS authentication, and this release does not change that.
+A model caller still must not assert it on its own behalf.
+
+The frozen AA registry and its approved SHA are unchanged. Coverage remains 78
+scored targets, one scored reference-only entry, and 10 unknown configurations.
+
+## Upgrade
+
+After npm publication, run `npm i -g omnilane@0.42.4`. An existing repo-symlink
+installation can update its checkout and verify `omnilane --version` without
+rerunning installation. GitHub release and npm publication remain separate
+verification surfaces from Linux CI.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "omnilane",
-  "version": "0.42.2",
+  "version": "0.42.4",
   "description": "One routing table, every harness — classify subtasks into lanes and delegate each lane through a compatible caller-owned native agent or vendor CLI.",
   "bin": {
     "omnilane": "bin/omnilane"
@@ -29,7 +29,7 @@
     "docs/model-capabilities-2026-09.md",
     "docs/native-executor.md",
     "docs/completion-wakeup.md",
-    "docs/release-notes-0.42.2.md",
+    "docs/release-notes-0.42.4.md",
     "hooks/",
     "skills/",
     ".claude-plugin/",

package/plugin.json

@@ -1,6 +1,6 @@
 {
   "$schema": "https://antigravity.google/schemas/v1/plugin.json",
   "name": "omnilane",
-  "version": "0.42.2",
+  "version": "0.42.4",
   "description": "One routing table, every harness: classify subtasks into lanes and delegate through compatible caller-owned native agents or vendor CLIs with exact-AA downward policy and supervised jobs."
 }

package/skills/omnilane/SKILL.md

@@ -17,7 +17,12 @@ You (the main loop) may be Claude, GPT, Grok, or Gemini. The procedure is identi
    reading public results, acceptance, operator replies, git commit/push and
    governance edits. Workers execute the assigned task and never delegate again.
    Read-only work uses advise; edits require `--mode work --workdir <repo>`.
-   `<repo>/scripts/dispatch.sh [--executor auto|native|cli] [--native-context FILE] [--vendor V] [--mode work] [--workdir DIR] <lane> "<task>"`
+   `<repo>/scripts/dispatch.sh --caller-context FILE [--executor auto|native|cli] [--native-context FILE] [--vendor V] [--mode work] [--workdir DIR] <lane> "<task>"`
+
+   A model caller MUST pass `--caller-context`; without it every dispatch is
+   refused with `missing-caller-context` before a job exists. Build that file
+   before the first dispatch — see **Frozen exact-AA downward gate** for the
+   schema, a worked example, and what to do when your own effort is unverifiable.
 
    Add `--background` for long tasks; poll with `scripts/jobs.sh status|result <id>`.
    Use `--thread NAME` when later claude, codex, grok or gemini dispatches
@@ -332,6 +337,47 @@ that exact frozen score and the inherited ceiling. Targets at or below it are al
 unknown identities and unresolved request-selector mappings fail closed. No family,
 displayed grade, highest-effort assumption, retry or fallback grants an uplift.
 
+Build the file before the first dispatch, not after a refusal. Every field is an
+exact identity: `caller` must reproduce one `scored_configs` row byte-for-byte,
+and `snapshot_id` must equal the registry's own `snapshot.id`.
+
+```json
+{
+  "schema_version": 1,
+  "snapshot_id": "<registry snapshot.id>",
+  "kind": "model",
+  "caller": {"vendor": "claude", "model": "claude-opus-5", "effort": "high",
+             "reasoning": "adaptive", "fallback": null},
+  "inherited_ceiling": 52
+}
+```
+
+Set `inherited_ceiling` to your own row's score when you are the root caller, or
+to the ceiling you were handed when you are a child.
+
+**When your harness names a model but no effort, look before you guess.** The
+launching process usually carries the exact flags. Walk your own ancestor chain
+(`ps -o ppid=,comm= -p <pid>` upward, then `ps -o args= -p <ancestor>`) and read
+its `--model` / `--effort`. Match the ancestor chain rather than the first
+matching process on the host — a second session of the same CLI is common and
+its flags are not yours. This is request-selector evidence, the same class the
+transport overlay carries, and it does not certify upstream identity.
+
+Only when that genuinely yields nothing: ask the operator, or declare the
+lowest-scoring row of your model and say so in your report. Understating only
+narrows what you may dispatch to, so it fails in the safe direction — but it is
+the fallback, not the first move, and an unnecessarily low ceiling silently
+closes lanes and pushes the question back onto the operator. Never raise the
+declared effort to unblock a refused target, and never assert
+`--operator-asserted-human` on your own behalf.
+
+Two refusal codes mean different things and need different fixes.
+`missing-caller-context` means you passed no file — write one.
+`runtime-mapping-unverified` means the file is fine but the *target* has no proven
+host-local request selector; that is fixed by a `--transport-overlay` entry backed
+by real evidence, never by editing the frozen registry (its sha256 is pinned in
+`scripts/lib/aa_policy.py`, so any edit fails the whole gate closed).
+
 A `--transport-overlay /absolute/overlay.json` may prove a small set of host-local
 request selectors using exact identities and hashed local contract evidence. It does
 not change frozen AA scores or certify upstream provider identity. The explicit

package/docs/release-notes-0.42.2.md

@@ -1,31 +0,0 @@
-# Omnilane 0.42.2
-
-This patch repairs the Grok single-shot reasoning-effort transport. It does not raise caller scores or remove the exact-AA downward-delegation gate.
-
-## Changes
-
-- Explicit Grok effort is forwarded as `--reasoning-effort VALUE`. The supported selector spellings are `low`, `medium`, `high`, and `xhigh`; invalid values fail before provider startup.
-- Grok 4.6 entries in the default routing table explicitly select `high`.
-- A scored Grok target requires a verified `cli_reasoning_effort` mapping and the exact `--reasoning-effort` flag. The existing host-local transport overlay validates host, snapshot, exact identity, evidence hashes, vendor, flag, and effort.
-- Explicit effort on the live ACP path is rejected rather than discarded. This release does not add Grok work-mode network isolation on macOS.
-
-## Verification boundary
-
-The frozen AA registry and its approved SHA remain unchanged. Transport evidence belongs to the local host; the package does not ship a blanket assertion that every Grok model/effort combination is verified.
-
-`request-selector-contract` proves how Omnilane selects the model and effort. It does not independently authenticate the upstream model's internal identity: `upstream_identity_verified` remains false. A successful reply alone is not an identity attestation.
-
-For an existing local overlay, use `selector_type: cli_reasoning_effort`, `cli_flag: --reasoning-effort`, and matching model/effort identity only after checking the installed CLI and runner. Retain absolute evidence paths and SHA-256 hashes. Changed evidence requires re-verification; do not merely relabel an old mapping as verified. Select it with `--transport-overlay /absolute/overlay.json` or `OMNILANE_AA_TRANSPORT_OVERLAY`.
-
-## Upgrade
-
-After npm publication:
-
-```sh
-npm i -g omnilane@0.42.2
-omnilane --version
-```
-
-Repo-symlink installations use the updated checkout. Do not rerun `install.sh` just to update the version. Local routing overrides take precedence; review any Grok entries still using `-`.
-
-GitHub release, npm publication, local provider smoke, and Linux CI are separate verification surfaces. Release evidence must identify each result rather than equating one with the others.