pi-keyboard 0.1.8 → 0.1.9

package/README.md

@@ -32,7 +32,10 @@ Supports discrete control for keyboard lighting channels:
 ## Shared Directory Session Registry
 
 Per-session glow records use pi-kit’s canonical directory identity, hashed into
-the registry directory name. Existing paths are resolved through `realpath`,
+the registry directory name. The registry location also comes from pi-kit, so
+`PI_DIRECTORY_SESSIONS_DIR`, `PI_CODING_AGENT_DIR`, and `PI_AGENT_DIR` point every
+writer in this process at one directory instead of splitting the registry. Existing
+paths are resolved through `realpath`,
 while missing paths use their absolute path; this keeps slash-versus-hyphen
 project names separate. Reads, cleanup, and clean shutdown verify the stored
 `cwd` belongs to the requested directory. Older registry directory names are

package/README.zh-CN.md

@@ -30,6 +30,8 @@
 ## 共享目录会话注册表
 
 每个会话的灯光记录使用 pi-kit 的规范目录身份，并将其哈希为注册表目录名。
+注册表位置同样来自 pi-kit：`PI_DIRECTORY_SESSIONS_DIR`、`PI_CODING_AGENT_DIR` 与
+`PI_AGENT_DIR` 会让本进程内的所有写入方指向同一个目录，而不会把注册表分成两处。
 已存在的路径通过 `realpath` 解析，不存在的路径使用绝对路径，因此仅以斜杠和连字符
 区分的项目不会碰撞。读取、清理和正常退出删除记录前都会核验记录中的 `cwd` 属于请求的
 目录；旧目录名不会迁移。

package/features/keyboard.feature

@@ -168,3 +168,9 @@ Feature: Pi Keyboard Lighting Indicator
   Scenario: Keyboard state notifications use Pi's native notification surface
     Given the keyboard extension reports an interactive command outcome
     Then it uses ctx.ui.notify without a custom notification renderer
+
+  Scenario: The glow registry follows the shared agent directory
+    Given PI_CODING_AGENT_DIR or PI_AGENT_DIR points outside the default home registry
+    When a session writes its glow record
+    Then it writes to that directory
+    And it resolves the same directory as every other registry writer

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "pi-keyboard",
-  "version": "0.1.8",
+  "version": "0.1.9",
   "description": "Dynamic VIA/QMK keyboard RGB lighting indicator reflecting Pi states (idle, thinking, unread, need-approval, error)",
   "author": "Frad LEE <fradser@gmail.com>",
   "license": "MIT",
@@ -38,6 +38,6 @@
     "@earendil-works/pi-tui": "*"
   },
   "dependencies": {
-    "@fradser/pi-kit": "0.5.1"
+    "@fradser/pi-kit": "0.6.0"
   }
-}
+}

package/src/global-sessions.ts

@@ -1,7 +1,6 @@
 import fs from "node:fs";
-import os from "node:os";
 import path from "node:path";
-import { getDirectorySessionKey, isSameDirectory } from "@fradser/pi-kit";
+import { directorySessionsDir, getDirectorySessionKey, isSameDirectory } from "@fradser/pi-kit";
 import type { KeyboardState } from "./types";
 
 export interface SessionGlowRecord {
@@ -14,11 +13,10 @@ export interface SessionGlowRecord {
 }
 
 export function getRegistryDir(): string {
-  // Test seam: allow pointing at an isolated registry so tests never touch the
-  // real ~/.pi/agent/directory-sessions directory.
-  const override = process.env.PI_DIRECTORY_SESSIONS_DIR;
-  if (override) return override;
-  return path.join(os.homedir(), ".pi", "agent", "directory-sessions");
+  // pi-kit owns the shared location: its PI_DIRECTORY_SESSIONS_DIR override is the
+  // test seam, and the agent-directory overrides must agree with every other
+  // registry writer, or a sandboxed session splits the registry in two.
+  return directorySessionsDir();
 }
 
 /** Shared directory-session key used by every registry writer and reader. */