@quolu/aishell 0.4.12 → 0.5.0

package/README.ja.md

@@ -21,7 +21,7 @@ state/schema migration、診断、復旧、更新、releaseを単独で所有し
 [dotagents](https://github.com/kitepon/dotagents)は公開contractを使って製品横断wireと
 互換性を統合しますが、AIShellの内部運用を制御しません。
 
-AIShellは許可root、file identity、filesystem照合state、直接起動したprocess、完全log、artifactを所有する。reasoning、thread、compaction、sub-agent、汎用terminalはAI hostの責務として残す。
+AIShellはfile identity、filesystem照合state、直接起動したprocess、完全log、artifactを所有する。reasoning、thread、compaction、sub-agent、汎用terminalはAI hostの責務として残す。
 
 ## 30秒で試す
 
@@ -33,7 +33,7 @@ aishell-open
 codex mcp add aishell --env AISHELL_CAPABILITY_SET=expanded-v1 -- aishell-mcp
 ```
 
-管理アプリでAIに許可するfolderを追加し、新しいCodex taskで次のように頼む。
+フォルダの事前登録は不要。新しいCodex taskで対象フォルダを指定して実行する。
 
 ```text
 初回workspace contextはworkspace_snapshotで取得して。focused testはrun_checkで実行し、
@@ -49,8 +49,8 @@ summaryから省略された証拠だけartifact_readで読んで。
 | `search_context` | 直接起動した`rg` workerによるbudget付き検索context |
 | `run_check` | 直接process実行、主要diagnostic、完全stdout/stderr artifact |
 | `artifact_read` | 保持artifactのrange、tail、pattern周辺read |
-| `runtime_status` | 未設定・停止中も含む許可root、停止、worktree、次操作の状態取得 |
-| `runtime_open_manager` | root追加またはAI操作再開のため管理アプリを開く |
+| `runtime_status` | 停止状態、相対パスの基準、次操作の状態取得 |
+| `runtime_open_manager` | AI操作の停止・再開のため管理アプリを開く |
 
 MCP serverへ`AISHELL_CAPABILITY_SET=expanded-v1`を設定すると、candidate surfaceへ明示opt-inできる。
 高密度development 9本と復旧control 2本を公開し、`run_observe`、`workspace_wait`、
@@ -79,7 +79,7 @@ statelessな連携では、モデルがworkspaceを何度もscanし、command出
 | Context | budget・cursor付きstructured result | stdoutを手動または暗黙に切り詰める |
 | Execution | executable URL、引数、cwd、lifecycleを分離 | shellが1本のcommand文字列を評価 |
 | Evidence | 完全stdout/stderrを期限付きhandleで保持 | response truncation時に証拠が失われやすい |
-| Scope | 人が管理する許可rootと明示的stop状態 | 周囲のshellとhost policyに依存 |
+| Scope | macOSのアクセス権と明示的stop状態 | 周囲のshellとhost policyに依存 |
 
 AIShellはsandboxではなく、任意code実行を安全化しない。process railの目的はtyped executionと観測可能なlifecycleを維持することであり、改名binaryや許可workerが起動する子processを阻止することではない。
 
@@ -89,7 +89,7 @@ AIShellはsandboxではなく、任意code実行を安全化しない。process
 flowchart LR
     Host[AI host<br/>reasoning · threads · compaction] --> MCP[AIShellMCP<br/>MCP 2025-11-25]
     MCP --> Core[AIShellCore]
-    Core --> State[Allowed roots · file identity<br/>FSEvents + reconciliation]
+    Core --> State[File identity<br/>FSEvents + reconciliation]
     Core --> Process[Direct process lifecycle<br/>stdout · stderr · timeout]
     Core --> Evidence[Retained evidence<br/>artifacts · freshness]
     Process --> Workers[git · rg · compiler · tests]
@@ -127,7 +127,7 @@ open build/AIShell.app
 
 MCP実行ファイルは`build/AIShell.app/Contents/Helpers/aishell-mcp`へ同梱される。
 
-管理アプリの「許可rootを追加」でAIに操作させるfolderを選ぶ。許可済みGit repositoryの`.git/worktrees`へ正式登録され、双方の管理情報が一致するworktreeは自動的に実効rootへ加わる。
+フォルダ登録は不要。絶対パスは指定した場所を、相対パスと省略時はMCP起動ディレクトリを基準にする。Git worktreeも直接指定でき、旧設定の許可フォルダ一覧は無視される。
 
 ## 別のAI hostへ接続
 
@@ -181,7 +181,7 @@ npm install -g @quolu/aishell@latest
 aishell-open
 ```
 
-未設定・停止中の復旧入口は`runtime_status`と`runtime_open_manager`である。
+停止中の復旧入口は`runtime_status`と`runtime_open_manager`である。
 工場consumerは専用`AISHELL_TOOL_PROFILE=factory` MCP surfaceから
 `factory_diagnostics`を呼ぶ。schemaとprivacy境界は
 [製品側diagnostics contract](https://github.com/kitepon/aishell/blob/main/docs/factory-diagnostics.md)が正である。

package/README.md

@@ -22,7 +22,7 @@ diagnostics, recovery, updates, and releases.
 for cross-product wiring and compatibility; it does not control AIShell's
 internal operation.
 
-AIShell owns the OS-facing state below the model: allowed roots, file identity, filesystem reconciliation, directly launched processes, complete logs, and retained artifacts. The AI host remains responsible for reasoning, threads, compaction, sub-agents, and general-purpose terminal work.
+AIShell owns the OS-facing state below the model: file identity, filesystem reconciliation, directly launched processes, complete logs, and retained artifacts. The AI host remains responsible for reasoning, threads, compaction, sub-agents, and general-purpose terminal work.
 
 ## Try it in 30 seconds
 
@@ -34,7 +34,7 @@ aishell-open
 codex mcp add aishell --env AISHELL_CAPABILITY_SET=expanded-v1 -- aishell-mcp
 ```
 
-In the manager app, add the folders the AI may access. Start a new Codex task and try:
+フォルダの事前登録は不要です。新しいCodex taskで対象フォルダを指定して実行します。
 
 ```text
 Use workspace_snapshot for the initial workspace context. Run the focused tests with
@@ -50,8 +50,8 @@ The default profile exposes five high-density development tools plus two always-
 | `search_context` | Budgeted lexical context from a directly launched `rg` worker, scoped to a directory or one regular file; the expanded capability also provides cursor-bound semantic definition/reference/symbol queries without lexical fallback |
 | `run_check` | Direct process execution, primary diagnostics, and complete stdout/stderr artifacts |
 | `artifact_read` | Range, tail, and pattern-centered reads from retained artifacts; the expanded capability also searches and compares finalized managed-run artifacts |
-| `runtime_status` | Allowed-root, pause, worktree, and next-action state, including while paused or unconfigured |
-| `runtime_open_manager` | Open the manager app to add roots or resume AI operations |
+| `runtime_status` | Pause, relative-path base, and next-action state |
+| `runtime_open_manager` | Open the manager app to pause or resume AI operations |
 
 Set `AISHELL_CAPABILITY_SET=expanded-v1` on the MCP server process to opt in to the candidate surface. It exposes nine high-density development tools plus the two recovery controls. The added tools are `run_observe`, `workspace_wait`, `change_impact`, and `apply_change_set`; existing tools gain closed managed-run, artifact query, semantic search, project-profile, and Git branch/worktree modes. Cross-run artifact operations require an explicit project path and reject live, expired, legacy-unbound, or different-project evidence instead of silently falling back to partial logs.
 
@@ -77,7 +77,7 @@ Typical stateless integrations repeatedly ask the model to rediscover workspace
 | Context | Bounded, cursor-based structured results | Unbounded or manually truncated stdout |
 | Execution | Executable URL, arguments, working directory, and lifecycle remain separate | A shell evaluates one command string |
 | Evidence | Complete stdout/stderr retained behind expiring handles | Evidence often disappears when the response is truncated |
-| Scope | Human-managed allowed roots and explicit stop state | Depends on the surrounding shell and host policy |
+| Scope | macOS access permissions and explicit stop state | Depends on the surrounding shell and host policy |
 
 AIShell is not a sandbox and does not make arbitrary code execution safe. Its process rails exist to preserve typed execution and observable lifecycle—not to stop renamed binaries or child processes launched by an allowed worker.
 
@@ -87,7 +87,7 @@ AIShell is not a sandbox and does not make arbitrary code execution safe. Its pr
 flowchart LR
     Host[AI host<br/>reasoning · threads · compaction] --> MCP[AIShellMCP<br/>MCP 2025-11-25]
     MCP --> Core[AIShellCore]
-    Core --> State[Allowed roots · file identity<br/>FSEvents + reconciliation]
+    Core --> State[File identity<br/>FSEvents + reconciliation]
     Core --> Process[Direct process lifecycle<br/>stdout · stderr · timeout]
     Core --> Evidence[Retained evidence<br/>artifacts · freshness]
     Process --> Workers[git · rg · compiler · tests]
@@ -126,7 +126,7 @@ open build/AIShell.app
 
 The MCP executable is bundled at `build/AIShell.app/Contents/Helpers/aishell-mcp`.
 
-After opening the app, use **Add Allowed Root** to select the folders AIShell may access. A Git worktree registered under an allowed repository is recognized automatically when both sides of the worktree metadata agree.
+フォルダ登録は不要です。絶対パスは指定した場所を、相対パスと省略時はMCP起動ディレクトリを基準にします。Git worktreeも直接指定できます。旧設定の許可フォルダ一覧は無視されます。
 
 ## Connect another AI host
 
@@ -184,7 +184,7 @@ aishell-open
 ```
 
 `runtime_status` and `runtime_open_manager` are the recovery entrypoints for an
-unconfigured or paused runtime. Factory consumers call `factory_diagnostics`
+paused runtime. Factory consumers call `factory_diagnostics`
 through the dedicated `AISHELL_TOOL_PROFILE=factory` MCP surface; its schema and
 privacy boundary are owned by [the product contract](https://github.com/kitepon/aishell/blob/main/docs/factory-diagnostics.md).
 

package/dist/AIShell.app/Contents/Info.plist

@@ -17,9 +17,9 @@
     <key>CFBundlePackageType</key>
     <string>APPL</string>
     <key>CFBundleShortVersionString</key>
-    <string>0.4.12</string>
+    <string>0.5.0</string>
     <key>CFBundleVersion</key>
-    <string>19</string>
+    <string>20</string>
     <key>LSApplicationCategoryType</key>
     <string>public.app-category.utilities</string>
     <key>LSMinimumSystemVersion</key>

package/dist/AIShell.app/Contents/_CodeSignature/CodeResources

@@ -10,19 +10,19 @@
 		<dict>
 			<key>cdhash</key>
 			<data>
-			uzkv8b/DrKQPJzoVL8NtTyIqqek=
+			YtRYGFYE+Yh3gPk+NxMYVUyUi6M=
 			</data>
 			<key>requirement</key>
-			<string>cdhash H"bb392ff1bfc3aca40f273a152fc36d4f222aa9e9"</string>
+			<string>cdhash H"62d458185604f9887780f93e371318554c948ba3"</string>
 		</dict>
 		<key>Helpers/aishell-run-supervisor</key>
 		<dict>
 			<key>cdhash</key>
 			<data>
-			0V5WoY6tV3Zqijm+8J8Zv0B6/Pw=
+			TcWgD4ePO0zxS53P4eI9iGT41LE=
 			</data>
 			<key>requirement</key>
-			<string>cdhash H"d15e56a18ead57766a8a39bef09f19bf407afcfc"</string>
+			<string>cdhash H"4dc5a00f878f3b4cf14b9dcfe1e23d8864f8d4b1"</string>
 		</dict>
 	</dict>
 	<key>rules</key>

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@quolu/aishell",
-  "version": "0.4.12",
+  "version": "0.5.0",
   "description": "A native macOS state runtime with high-density MCP tools for AI development",
   "license": "Apache-2.0",
   "author": {