claude-spotter 1.4.28 → 1.5.0

package/CHANGELOG.md

@@ -1,5 +1,48 @@
 # Changelog
 
+## 1.5.0 — 2026-08-04
+
+- **評価結果を端末別Web dashboardで表示。** 各端末の`~/.spotter/evaluation.db`をrequestごとに読み、
+  `S/P/I/C/A/M`、提案率`P/S`、採用率`A/C`、project/tool内訳、非採用caseと詳細を
+  dependency-freeのserver-side HTMLで表示する。request、auditorへ渡したcontext、Throughline
+  observer snapshotは混同せず別欄に置く。
+- **端末選択hubを追加。** 静的な4端末mapから一覧を表示し、`/devices/<id>/`を各device serverへ
+  proxyする。healthは一覧request時に各端末1回だけ取得し、offlineやtimeoutは該当端末だけ502にする。
+  DB同期、background monitor、retry queue、reconcilerは追加しない。
+- **運用面を同梱。** `spotter dashboard device` / `hub`、Mac LaunchAgent、Linux systemd user、
+  Windows Task Scheduler、SSH reverse tunnel、main-server hub config、Caddy/Cloudflare Accessの
+  配備手順を追加した。評価データは端末内に留め、公開面だけをowner emailのAccessで保護する。
+- **検証。** dashboard focused test 16件、fixture SQLiteからdevice HTTP・hub proxyまでの経路、
+  full suite 584件（582 pass / 2 platform skip）を通過した。
+
+## 1.4.29 — 2026-08-04
+
+- **提案率とtool採用率の端末内評価を追加。** Claude / Codexの成功UserPromptSubmitを母数に、
+  safe projector後に実際に提示したtool itemと、同じturnでのcanonical tool利用を
+  `~/.spotter/evaluation.db`へ記録する。採用率の母数はoutcome確定itemだけとし、利用記録不全は
+  `outcome_missing`へ分離する。組込みtoolは評価対象外で、既存turn-end auditorのraw usedToolsは変更しない。
+- **提案時の別文脈を保存。** proposal確定時刻を記録し、既存Throughline `observer-read`を一度だけ呼ぶ。
+  Spotterがauditorへ渡したcontextとは別fieldに保存し、失敗時はcontextだけunavailableとしてretryしない。
+  返却されたhost / thread hashを提案元sessionと照合し、同じprojectの並行sessionを取り違えた場合も
+  snapshotを保存しない。
+- **欠測とtool identityを率から分離。** Claudeの利用記録失敗、Codex transcript不全、Stopが30分以上
+  欠落したopen proposalは`outcome_missing`として投影し、非採用へ混ぜない。Codex Skillは提案済みの
+  正規`SKILL.md`を実際にreadしたcallだけを採用として認識する。現行Codexのouter `exec`内で実行される
+  nested MCP callと、同じturn内の複数`exec`も個別の利用入力として保持する。
+- **初回同時openを直列化。** 2 projectが未作成の評価DBを同時に開いてもWAL設定前に
+  `database is locked`とならないよう、bounded busy timeoutをschema初期化より先に有効化する。
+  retry、lockfile、background回収は追加しない。
+- **評価CLIを追加。** `spotter evaluation report`で全project / project / tool / host別の
+  `S/P/I/C/A/M`、`P/S`、`A/C`を表示し、`cases` / `case`で非採用caseのrequest、2種類の文脈、
+  提案ID、利用ID、outcomeを確認できる。reportは保存済みSQLiteだけを読み、JSONはWindows
+  PowerShell 5.1でも壊れないASCII-safe形式で出力する。
+- **検証・公開。** 固定fixture、Claude / Codex hook、Throughline束縛、2 process同時writeを含む
+  568 tests（macOS / Linuxは566 pass / 2 skip、Windowsは556 pass / 12 platform skip）、
+  macOS / Linux / Windows × Node 22.13 / 22.xのCI run `30913375991`、75-file packを通過した。
+  別projectの実Codex turnではThroughline文脈付きproposalから
+  `S=1 P=1 I=1 C=1 A=1 M=0`を記録し、Claude実turnのpass観測と両hostのproposal fixtureも確認した。
+  Windowsではouter `exec`内の絶対pathを壊さずSkill採用へ変換する回帰も固定した。
+
 ## 1.4.28 — 2026-07-21
 
 - **Windows Codex SessionStartの誤timeoutを修正。** detached refreshを起動するSpotter所有hookの

package/README.ja.md

@@ -13,6 +13,16 @@
 
 > **気づく役と実行する役を分離する。** Claude Code の横で並走し、主役の Claude が**ツールを呼び忘れたとき**だけ静かに指摘する監査役。
 
+[kitepon.dev](https://kitepon.dev/)を運営する[クオ（@QLyun35332）](https://x.com/QLyun35332)が
+開発・メンテナンスしています。
+
+## 所有境界
+
+本repositoryは監査挙動、project marker、installer、release、diagnosticsを所有します。
+製品横断のcatalogとhost統合は、kitepon.devの製品開発を支える内部基盤
+[dotagents](https://github.com/kitepon-rgb/dotagents)が担当します。
+MarkItDownは別区分の第三者CLIです。
+
 Claude には「使えるツールがあるのに、使うべきタイミングで使わない」という構造的な弱点があります。記録すべき決定を memory / caveat MCP に残さない、docs lookup MCP を呼ばずに古い知識で応答する、ブラウザ自動化 MCP で確認せず UI 状態を推測する — **「分からないと自覚できない」から、ツールを取りに行けない**。
 
 Spotter はツールカタログを完全に把握した別の監査エージェントで、ユーザー入力と主役 AI の応答を並走監査します。自動選択では Claude host は Codex CLI があればそれを、なければ session-scoped Haiku を選び、Codex host は Codex CLI を既定にします。明示 backend override は host より優先しますが、runtime failure で別 backend へ黙って切り替えません。応答前は検証済みtool IDだけを固定・非命令形の助言へ変換でき、応答後のfindingは構造eventに留めて後続turnへ注入しません。監査用AIの自由文が親セッションへ入ることはありません。**主役 AI が自覚して自己監査する**設計は本プロダクトの存在意義を破壊するため、hook 経由でその意思と独立に検出します。
@@ -207,6 +217,16 @@ spotter db rebuild       # Claude local + Claude global DB を両方消してか
 spotter status           # 稼働中の daemon 一覧
 spotter doctor           # 環境診断 (Node / claude CLI / Codex readiness / tool-db 整合性)
 spotter diagnostics logs # daemon log から pass=false / backend latency / anomaly signal を集計
+spotter evaluation report
+                         # 端末内DBからproject横断の提案率・tool採用率を集計
+spotter evaluation cases --outcome not-adopted
+                         # 提案されたが同じturnで使われなかったtool itemを一覧
+spotter evaluation case <observation-id>
+                         # request、2種類の文脈、提案、利用、outcomeを確認
+spotter dashboard device --id mac --name Mac
+                         # この端末の評価DBを127.0.0.1:53940で配信
+spotter dashboard hub --config dashboard-hub.json --host 172.18.0.1
+                         # 端末一覧と/devices/<id>/の端末別proxyを配信
 spotter codex risk-check --findings findings.json --host-agent claude
                          # Spotter finding を codex-sidecar に渡して read-only risk analysis
 spotter codex review|explore|opinion --findings findings.json --host-agent claude
@@ -223,6 +243,17 @@ spotter auditor model-matrix --fixtures test/fixtures/auditor-model-matrix.v2.js
 spotter uninstall        # hook 登録を解除 (~/.spotter は残す)
 ```
 
+### 端末別評価dashboard
+
+dashboardはlocal-firstで動く。各端末が自身の`~/.spotter/evaluation.db`を読み、hubは固定の
+端末・upstream対応だけを持つ。評価データをcloud DBへ複製しない。端末画面では
+`S/P/I/C/A/M`、提案率、採用率、project/tool内訳、非採用case、別々に取得した2種類の文脈を
+確認できる。health確認は端末一覧request時だけなので、端末がofflineでもbackground監視や
+retry queueを作らず、その端末だけを切り離せる。
+
+4端末のservice、reverse tunnel、Caddy/Cloudflare構成は
+[docs/11_dashboard-operations.md](docs/11_dashboard-operations.md)を参照。
+
 Codex risk dispatch を daemon から非同期に流す場合:
 
 ```bash

package/README.md

@@ -13,6 +13,16 @@
 
 > **Separate the spotter from the doer.** Spotter runs alongside Claude Code and quietly flags the moments when your primary Claude **forgets to use a tool it has access to**.
 
+Built and maintained by [Quo](https://x.com/QLyun35332) at [kitepon.dev](https://kitepon.dev/en).
+
+## Ownership boundary
+
+This repository owns auditor behavior, project markers, installers, release,
+and diagnostics. The cross-product catalog and host integration are handled by
+[dotagents](https://github.com/kitepon-rgb/dotagents), the internal development
+toolchain behind kitepon.dev's products.
+MarkItDown is managed separately as a third-party CLI.
+
 Claude has a structural blind spot: **it can't reach for a tool it doesn't realize it needs**. It may skip a project memory MCP when a decision should be recorded, answer from stale memory instead of a docs-lookup MCP, or reason about UI state without a browser-automation MCP. The model can't always tell when it doesn't know — so the tool stays unused.
 
 Spotter runs a separate auditor with the full tool catalog and checks both the user's prompt and the primary agent's reply. Automatic selection uses Codex CLI on a Claude host when available, otherwise the session-scoped Haiku path; on a Codex host it defaults to Codex CLI. An explicit backend override takes precedence, but a runtime failure never silently switches backend. Before the primary reply, validated tool IDs may become fixed, non-directive advice; after the reply, findings remain structured events and are not injected into a later turn. Auditor prose never enters the parent session. **The primary agent is never asked to self-audit** — that would defeat the premise. Detection happens through hooks, independent of the primary agent's intent.
@@ -216,6 +226,16 @@ spotter doctor           # environment check (Node / claude CLI / Codex readines
 spotter diagnostics logs # summarize daemon logs for pass=false / backend latency / anomaly signals
 spotter diagnostics runtime-errors
                          # print the local allow-listed runtime-error aggregate snapshot (no network)
+spotter evaluation report
+                         # show cross-project proposal/adoption counts and rates from the local DB
+spotter evaluation cases --outcome not-adopted
+                         # list proposed tools that were not used in the same turn
+spotter evaluation case <observation-id>
+                         # inspect request, Spotter context, Throughline snapshot, proposal, usage, and outcome
+spotter dashboard device --id mac --name Mac
+                         # serve this terminal's local evaluation DB on 127.0.0.1:53940
+spotter dashboard hub --config dashboard-hub.json --host 172.18.0.1
+                         # list terminals and proxy /devices/<id>/ to their local servers
 spotter codex risk-check --findings findings.json --host-agent claude
                          # run read-only codex-sidecar risk analysis for Spotter findings
 spotter codex review|explore|opinion --findings findings.json --host-agent claude
@@ -232,6 +252,18 @@ spotter auditor model-matrix --fixtures test/fixtures/auditor-model-matrix.v2.js
 spotter uninstall        # remove hooks from this project (leaves ~/.spotter intact)
 ```
 
+### Device-routed evaluation dashboard
+
+The dashboard is local-first. Every terminal reads its own `~/.spotter/evaluation.db`; the hub
+keeps only a static device-to-upstream map and does not copy evaluation data into a cloud database.
+The device view shows `S/P/I/C/A/M`, proposal and adoption rates, project/tool breakdowns,
+non-adopted cases, and the two separately captured context sources. The hub checks health only
+when the device list is requested, so an offline terminal is isolated without a background monitor
+or retry queue.
+
+The reference four-terminal service, reverse-tunnel, and Caddy/Cloudflare layout is documented in
+[docs/11_dashboard-operations.md](docs/11_dashboard-operations.md).
+
 Optional async Codex risk dispatch:
 
 ```bash

package/bin/spotter.mjs

@@ -11,6 +11,8 @@ import { runCodexCommand } from '../src/cli/codex-cmd.mjs';
 import { runCodexHookCommand } from '../src/cli/codex-hook-cmd.mjs';
 import { runAuditorCommand } from '../src/cli/auditor-cmd.mjs';
 import { runDiagnosticsCommand } from '../src/cli/diagnostics-cmd.mjs';
+import { runEvaluationCommand } from '../src/cli/evaluation-cmd.mjs';
+import { runDashboardCommand } from '../src/cli/dashboard-cmd.mjs';
 import { runFactoryDiagnostics } from '../src/cli/factory-diagnostics.mjs';
 import { runDaemonStart } from '../src/cli/daemon-cmd.mjs';
 import { runSessionStart } from '../src/hooks/session-start.mjs';
@@ -45,6 +47,13 @@ Usage:
   spotter diagnostics logs [--json]     summarize daemon logs for precision diagnostics
   spotter diagnostics runtime-errors [snapshot|ack|resolve|reopen|compact]
                                         consume the local allow-listed aggregate store
+  spotter evaluation report [filters] [--json]
+  spotter evaluation cases --outcome OUTCOME [filters] [--json]
+  spotter evaluation case OBSERVATION_ID [--json]
+                                        read saved proposal-adoption observations
+  spotter dashboard device --id ID [--name NAME] [--host HOST] [--port PORT] [--db PATH]
+  spotter dashboard hub --config FILE [--host HOST] [--port PORT]
+                                        serve the local device-routed evaluation dashboard
   spotter codex risk-check --findings FILE
                                         run read-only codex-sidecar risk analysis
   spotter codex review|explore|opinion --findings FILE
@@ -124,6 +133,12 @@ async function main() {
       }
       await runDiagnosticsCommand({ argv: rest });
       return;
+    case 'evaluation':
+      await runEvaluationCommand({ argv: rest });
+      return;
+    case 'dashboard':
+      await runDashboardCommand({ argv: rest });
+      return;
     case 'daemon': {
       const sub = rest[0];
       if (sub === 'start') { await runDaemonStart({ argv: rest.slice(1) }); return; }

package/docs/11_dashboard-operations.md

@@ -0,0 +1,118 @@
+# Spotter評価dashboard運用
+
+## 固定構成
+
+各端末のdevice serverは`127.0.0.1:53940`だけで待ち受ける。main-serverのhubは
+Docker Caddyから到達できる`172.18.0.1:53940`で待ち受ける。評価DBは各端末の
+`~/.spotter/evaluation.db`をその場で読み、端末外へ複製しない。
+
+| 端末 | device ID | main-server側upstream |
+|---|---|---|
+| main-server Ubuntu | `main-server` | `127.0.0.1:53940` |
+| Mac | `mac` | `127.0.0.1:53941` |
+| FOX WSL2 | `fox-wsl` | `127.0.0.1:53942` |
+| FOX Windows native | `fox-windows` | `127.0.0.1:53943` |
+
+hub設定の正本は`ops/dashboard/hub-config.json`である。hubは一覧request時に各upstreamの
+healthを1回だけ確認し、端末をonline/offline表示する。常時監視、再試行queue、DB同期は行わない。
+
+## Mac
+
+`ops/dashboard/launchd/`の2 plistを`~/Library/LaunchAgents/`へ配置する。既存labelを更新する時は
+`launchctl bootout gui/$(id -u) <plist>`の後、`launchctl bootstrap gui/$(id -u) <plist>`を実行する。
+deviceはMac実DB、tunnelはmain-serverの`53941`へ接続する。
+
+確認:
+
+```sh
+curl --fail http://127.0.0.1:53940/_spotter/health
+ssh main-server curl --fail http://127.0.0.1:53941/_spotter/health
+```
+
+## main-server Ubuntu
+
+`ops/dashboard/systemd/spotter-dashboard-device.service`と
+`spotter-dashboard-hub.service`を`~/.config/systemd/user/`へ配置する。
+`~/.config/spotter/dashboard-device.env`は次の2行、hub configはrepo正本をコピーする。
+
+```ini
+SPOTTER_DEVICE_ID=main-server
+SPOTTER_DEVICE_NAME=main-server
+```
+
+```sh
+systemctl --user daemon-reload
+systemctl --user enable --now spotter-dashboard-device.service spotter-dashboard-hub.service
+curl --fail http://127.0.0.1:53940/_spotter/health
+curl --fail http://172.18.0.1:53940/
+```
+
+systemd user managerの`PATH`から`spotter`が見えない場合だけ、ユーザー環境の実際のnpm binを
+unitの`Environment=PATH=...`として追加する。別の起動経路へfallbackしない。
+
+## FOX WSL2
+
+device unitとtunnel unitを`~/.config/systemd/user/`へ配置する。device env:
+
+```ini
+SPOTTER_DEVICE_ID=fox-wsl
+SPOTTER_DEVICE_NAME=FOX-WSL2
+```
+
+tunnel env:
+
+```ini
+SPOTTER_REMOTE_FORWARD=127.0.0.1:53942:127.0.0.1:53940
+SPOTTER_TUNNEL_TARGET=main-server
+```
+
+```sh
+systemctl --user daemon-reload
+systemctl --user enable --now spotter-dashboard-device.service spotter-dashboard-tunnel.service
+```
+
+## FOX Windows native
+
+管理者権限は不要。`ops/dashboard/windows/`を固定pathへ配置し、Windows側から解決できる
+main-serverのSSH host名またはIPを明示して次を1回実行する。
+
+```powershell
+.\install-dashboard-tasks.ps1 -MainServer '<main-server-host-or-ip>'
+```
+
+登録される2 taskはログオン時にdevice serverとreverse tunnelを起動する。確認:
+
+```powershell
+Invoke-RestMethod http://127.0.0.1:53940/_spotter/health
+Get-ScheduledTask -TaskName 'Spotter dashboard *' | Get-ScheduledTaskInfo
+```
+
+## 公開経路
+
+Caddyへ次を追加する。`spotter.kitepon.dev`はcase詳細に会話文脈を含むため、Cloudflare側では
+同hostname全体をAccess applicationの対象にし、owner emailだけをallowする。
+
+```caddyfile
+spotter.kitepon.dev {
+  import cf-origin-tls
+  import security-headers-base
+  reverse_proxy 172.18.0.1:53940
+}
+```
+
+既存Cloudflare Tunnelのcatch-all 404より前に、hostname `spotter.kitepon.dev`、service
+`https://caddy:443`、`noTLSVerify: true`、`matchSNItoHost: true`のingressを追加する。
+DNSは同tunnel UUIDの`cfargotunnel.com`へCNAMEする。
+
+## 受入と切り分け
+
+確認順序はdevice loopback、main-serverの各upstream、hub、Caddy、Cloudflare Tunnel、Accessとする。
+端末がofflineならhub一覧のその端末だけがofflineになる。選択時の502は該当upstreamのserviceまたは
+reverse tunnelを確認する。hubや別端末を再起動する必要はない。
+
+公開受入:
+
+1. 未認証`https://spotter.kitepon.dev/`がCloudflare Accessへredirectされる。
+2. 認証後の`/`が4端末を表示する。
+3. online端末のoverview、project/tool内訳、非採用case、case詳細を表示できる。
+4. 1端末を停止しても一覧と他端末が表示でき、停止端末だけoffline/502になる。

package/ops/dashboard/hub-config.json

@@ -0,0 +1 @@
+{"devices":[{"id":"main-server","name":"main-server","upstream":"http://127.0.0.1:53940"},{"id":"mac","name":"Mac","upstream":"http://127.0.0.1:53941"},{"id":"fox-wsl","name":"FOX WSL2","upstream":"http://127.0.0.1:53942"},{"id":"fox-windows","name":"FOX Windows native","upstream":"http://127.0.0.1:53943"}]}

package/ops/dashboard/launchd/dev.kitepon.spotter-dashboard-device.plist

@@ -0,0 +1,21 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
+<plist version="1.0">
+<dict>
+  <key>Label</key><string>dev.kitepon.spotter-dashboard-device</string>
+  <key>ProgramArguments</key>
+  <array>
+    <string>/opt/homebrew/bin/spotter</string>
+    <string>dashboard</string><string>device</string>
+    <string>--id</string><string>mac</string>
+    <string>--name</string><string>Mac</string>
+    <string>--host</string><string>127.0.0.1</string>
+    <string>--port</string><string>53940</string>
+  </array>
+  <key>RunAtLoad</key><true/>
+  <key>KeepAlive</key><true/>
+  <key>ThrottleInterval</key><integer>10</integer>
+  <key>StandardOutPath</key><string>/Users/kite/.spotter/dashboard-device.log</string>
+  <key>StandardErrorPath</key><string>/Users/kite/.spotter/dashboard-device.log</string>
+</dict>
+</plist>

package/ops/dashboard/launchd/dev.kitepon.spotter-dashboard-tunnel.plist

@@ -0,0 +1,23 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
+<plist version="1.0">
+<dict>
+  <key>Label</key><string>dev.kitepon.spotter-dashboard-tunnel</string>
+  <key>ProgramArguments</key>
+  <array>
+    <string>/usr/bin/ssh</string><string>-N</string>
+    <string>-o</string><string>BatchMode=yes</string>
+    <string>-o</string><string>ExitOnForwardFailure=yes</string>
+    <string>-o</string><string>ServerAliveInterval=30</string>
+    <string>-o</string><string>ServerAliveCountMax=3</string>
+    <string>-o</string><string>TCPKeepAlive=yes</string>
+    <string>-R</string><string>127.0.0.1:53941:127.0.0.1:53940</string>
+    <string>main-server</string>
+  </array>
+  <key>RunAtLoad</key><true/>
+  <key>KeepAlive</key><true/>
+  <key>ThrottleInterval</key><integer>10</integer>
+  <key>StandardOutPath</key><string>/Users/kite/.spotter/dashboard-tunnel.log</string>
+  <key>StandardErrorPath</key><string>/Users/kite/.spotter/dashboard-tunnel.log</string>
+</dict>
+</plist>

package/ops/dashboard/systemd/spotter-dashboard-device.service

@@ -0,0 +1,13 @@
+[Unit]
+Description=Spotter evaluation dashboard device server
+After=network.target
+
+[Service]
+Type=simple
+EnvironmentFile=%h/.config/spotter/dashboard-device.env
+ExecStart=/usr/bin/env spotter dashboard device --id ${SPOTTER_DEVICE_ID} --name ${SPOTTER_DEVICE_NAME} --host 127.0.0.1 --port 53940
+Restart=on-failure
+RestartSec=10
+
+[Install]
+WantedBy=default.target

package/ops/dashboard/systemd/spotter-dashboard-hub.service

@@ -0,0 +1,12 @@
+[Unit]
+Description=Spotter evaluation dashboard hub
+After=network.target
+
+[Service]
+Type=simple
+ExecStart=/usr/bin/env spotter dashboard hub --config %h/.config/spotter/dashboard-hub.json --host 172.18.0.1 --port 53940
+Restart=on-failure
+RestartSec=10
+
+[Install]
+WantedBy=default.target

package/ops/dashboard/systemd/spotter-dashboard-tunnel.service

@@ -0,0 +1,14 @@
+[Unit]
+Description=Spotter evaluation dashboard reverse tunnel
+After=network-online.target
+Wants=network-online.target
+
+[Service]
+Type=simple
+EnvironmentFile=%h/.config/spotter/dashboard-tunnel.env
+ExecStart=/usr/bin/ssh -N -o BatchMode=yes -o ExitOnForwardFailure=yes -o ServerAliveInterval=30 -o ServerAliveCountMax=3 -o TCPKeepAlive=yes -R ${SPOTTER_REMOTE_FORWARD} ${SPOTTER_TUNNEL_TARGET}
+Restart=on-failure
+RestartSec=10
+
+[Install]
+WantedBy=default.target

package/ops/dashboard/windows/install-dashboard-tasks.ps1

@@ -0,0 +1,16 @@
+param([Parameter(Mandatory = $true)][string]$MainServer)
+$ErrorActionPreference = 'Stop'
+$ops = Split-Path -Parent $MyInvocation.MyCommand.Path
+$powershell = "$env:WINDIR\System32\WindowsPowerShell\v1.0\powershell.exe"
+$principal = New-ScheduledTaskPrincipal -UserId $env:USERNAME -LogonType Interactive -RunLevel Limited
+$settings = New-ScheduledTaskSettingsSet -RestartCount 999 -RestartInterval (New-TimeSpan -Minutes 1) -ExecutionTimeLimit ([TimeSpan]::Zero)
+$trigger = New-ScheduledTaskTrigger -AtLogOn -User $env:USERNAME
+
+$deviceAction = New-ScheduledTaskAction -Execute $powershell -Argument "-NoProfile -ExecutionPolicy Bypass -File `"$ops\spotter-dashboard-device.ps1`""
+Register-ScheduledTask -TaskName 'Spotter dashboard device' -Action $deviceAction -Trigger $trigger -Principal $principal -Settings $settings -Force | Out-Null
+
+$tunnelAction = New-ScheduledTaskAction -Execute $powershell -Argument "-NoProfile -ExecutionPolicy Bypass -File `"$ops\spotter-dashboard-tunnel.ps1`" -MainServer `"$MainServer`""
+Register-ScheduledTask -TaskName 'Spotter dashboard tunnel' -Action $tunnelAction -Trigger $trigger -Principal $principal -Settings $settings -Force | Out-Null
+
+Start-ScheduledTask -TaskName 'Spotter dashboard device'
+Start-ScheduledTask -TaskName 'Spotter dashboard tunnel'

package/ops/dashboard/windows/spotter-dashboard-device.ps1

@@ -0,0 +1,4 @@
+$ErrorActionPreference = 'Stop'
+$spotter = Join-Path $env:APPDATA 'npm\spotter.cmd'
+& $spotter dashboard device --id fox-windows --name 'FOX Windows native' --host 127.0.0.1 --port 53940
+exit $LASTEXITCODE

package/ops/dashboard/windows/spotter-dashboard-tunnel.ps1

@@ -0,0 +1,7 @@
+param([Parameter(Mandatory = $true)][string]$MainServer)
+$ErrorActionPreference = 'Stop'
+& "$env:WINDIR\System32\OpenSSH\ssh.exe" -N `
+  -o BatchMode=yes -o ExitOnForwardFailure=yes `
+  -o ServerAliveInterval=30 -o ServerAliveCountMax=3 -o TCPKeepAlive=yes `
+  -R '127.0.0.1:53943:127.0.0.1:53940' $MainServer
+exit $LASTEXITCODE

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "claude-spotter",
-  "version": "1.4.28",
+  "version": "1.5.0",
   "description": "Audit agent running alongside Claude Code that catches missed tool calls — 気づく役と実行する役の分離",
   "type": "module",
   "bin": {
@@ -11,6 +11,8 @@
   },
   "scripts": {
     "test": "node --test",
+    "verify:release-commit": "node scripts/verify-release-commit.mjs",
+    "prepublishOnly": "npm run verify:release-commit && npm test",
     "postinstall": "node scripts/postinstall.mjs",
     "preuninstall": "node scripts/preuninstall.mjs"
   },
@@ -23,7 +25,10 @@
     "audit",
     "spotter"
   ],
-  "author": "kitepon",
+  "author": {
+    "name": "Quo / クオ at kitepon.dev",
+    "url": "https://kitepon.dev/"
+  },
   "license": "MIT",
   "repository": {
     "type": "git",
@@ -43,6 +48,8 @@
     "bin",
     "src",
     "scripts",
+    "ops/dashboard",
+    "docs/11_dashboard-operations.md",
     "README.md",
     "LICENSE",
     "CHANGELOG.md"

package/scripts/verify-release-commit.mjs

@@ -0,0 +1,50 @@
+#!/usr/bin/env node
+
+// publishする成果が、既定ブランチへ着地済みのcommitから作られていることを保証する。
+// 着地していないbranchからpublishすると、そのbranchが取り残された時点で公開物が
+// 後続releaseから消え、統合契約だけが存在しない面を指し続ける（0.3.0の孤児releaseが実例）。
+
+import assert from "node:assert/strict";
+import { spawnSync } from "node:child_process";
+import path from "node:path";
+import { fileURLToPath } from "node:url";
+
+const scriptPath = fileURLToPath(import.meta.url);
+const defaultProjectDirectory = path.dirname(path.dirname(scriptPath));
+
+export function verifyReleaseCommit({
+  projectDirectory = defaultProjectDirectory,
+  spawn = spawnSync,
+} = {}) {
+  const git = (...args) => {
+    const result = spawn("git", args, { cwd: projectDirectory, encoding: "utf8" });
+    return { ok: result.status === 0, stdout: (result.stdout ?? "").trim() };
+  };
+
+  const head = git("rev-parse", "HEAD");
+  assert.ok(head.ok, "git HEAD を解決できません");
+  const originHead = git("symbolic-ref", "--quiet", "refs/remotes/origin/HEAD");
+  const defaultRef = originHead.ok && originHead.stdout
+    ? originHead.stdout.replace("refs/remotes/", "")
+    : "origin/main";
+  const defaultResolved = git("rev-parse", "--verify", `${defaultRef}^{commit}`);
+  assert.ok(defaultResolved.ok, `既定ブランチ ${defaultRef} を解決できません。git fetch origin を先に実行してください。`);
+  const isAncestor = git("merge-base", "--is-ancestor", head.stdout, defaultRef);
+  assert.ok(
+    isAncestor.ok,
+    `publish対象 ${head.stdout.slice(0, 12)} が ${defaultRef} の祖先ではありません。`
+      + " 先に既定ブランチへ着地させてpushしてから publish してください。"
+  );
+  const dirty = git("status", "--porcelain", "--untracked-files=normal");
+  assert.ok(dirty.ok, "working treeの状態を確認できません");
+  assert.equal(
+    dirty.stdout,
+    "",
+    `working treeに未commitの変更があります。publish対象commitとpayloadが一致しません:\n${dirty.stdout}`
+  );
+  return `release commit ${head.stdout.slice(0, 12)} is landed on ${defaultRef}.`;
+}
+
+if (process.argv[1] && path.resolve(process.argv[1]) === scriptPath) {
+  console.log(verifyReleaseCommit());
+}

package/scripts/verify-release-commit.test.mjs

@@ -0,0 +1,48 @@
+import assert from "node:assert/strict";
+import { execFileSync } from "node:child_process";
+import { mkdtemp, mkdir, rm, writeFile } from "node:fs/promises";
+import { tmpdir } from "node:os";
+import path from "node:path";
+import test from "node:test";
+
+import { verifyReleaseCommit } from "./verify-release-commit.mjs";
+
+function git(cwd, ...args) {
+  return execFileSync("git", args, { cwd, encoding: "utf8", stdio: ["ignore", "pipe", "pipe"] });
+}
+
+async function createReleaseFixture(t) {
+  const root = await mkdtemp(path.join(tmpdir(), "spotter-release-gate-"));
+  const remote = path.join(root, "origin.git");
+  const work = path.join(root, "work");
+  t.after(async () => rm(root, { recursive: true, force: true }));
+  await mkdir(work);
+  git(root, "init", "--bare", remote);
+  git(work, "init", "--initial-branch=main");
+  git(work, "config", "user.name", "Spotter release gate test");
+  git(work, "config", "user.email", "spotter-release-gate@example.invalid");
+  await writeFile(path.join(work, ".gitignore"), "ignored.tmp\n", "utf8");
+  await writeFile(path.join(work, "tracked.txt"), "tracked\n", "utf8");
+  git(work, "add", ".gitignore", "tracked.txt");
+  git(work, "commit", "-m", "fixture");
+  git(work, "remote", "add", "origin", remote);
+  git(work, "push", "--set-upstream", "origin", "main");
+  return work;
+}
+
+test("release gate passes for a commit landed on main", async (t) => {
+  const work = await createReleaseFixture(t);
+  assert.match(verifyReleaseCommit({ projectDirectory: work }), /landed on origin\/main/);
+});
+
+test("release gate rejects an untracked publish payload", async (t) => {
+  const work = await createReleaseFixture(t);
+  await writeFile(path.join(work, "untracked.txt"), "must block publish\n", "utf8");
+  assert.throws(() => verifyReleaseCommit({ projectDirectory: work }), /working treeに未commitの変更があります/);
+});
+
+test("release gate permits ignored generated output", async (t) => {
+  const work = await createReleaseFixture(t);
+  await writeFile(path.join(work, "ignored.tmp"), "generated\n", "utf8");
+  assert.match(verifyReleaseCommit({ projectDirectory: work }), /landed on origin\/main/);
+});