@zeldrisho/pi-gate 0.4.1 → 0.5.0

package/CHANGELOG.md

@@ -7,6 +7,12 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [0.5.0] - 2026-09-24
+
+### Changed
+
+- Use `gate.json` as the default configuration filename, retaining `pi-gate.json` as a legacy fallback only when `gate.json` is absent; existing files are never automatically renamed or overwritten.
+
 ## [0.4.1] - 2026-09-17
 
 ### Security
@@ -56,7 +62,8 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 - support `prompt`, `block`, and `allow` actions, with longest-pattern-wins resolution
 - block rather than auto-approve in non-UI modes
 
-[Unreleased]: https://github.com/zeldrisho/pi-packages/compare/pi-gate-v0.4.1...HEAD
+[Unreleased]: https://github.com/zeldrisho/pi-packages/compare/pi-gate-v0.5.0...HEAD
+[0.5.0]: https://github.com/zeldrisho/pi-packages/compare/pi-gate-v0.4.1...pi-gate-v0.5.0
 [0.4.1]: https://github.com/zeldrisho/pi-packages/compare/pi-gate-v0.4.0...pi-gate-v0.4.1
 [0.4.0]: https://github.com/zeldrisho/pi-packages/compare/pi-gate-v0.3.0...pi-gate-v0.4.0
 [0.3.0]: https://github.com/zeldrisho/pi-packages/compare/pi-gate-v0.2.0...pi-gate-v0.3.0

package/README.md

@@ -12,7 +12,9 @@ pi install -l npm:@zeldrisho/pi-gate
 
 ## Configure
 
-On first load, the extension creates `~/.pi/agent/pi-gate.json` with starter rules and a 30-second prompt timeout. Existing files are never overwritten. If no configuration can be created yet, pi-gate warns at session start and allows commands until the file is created. If an existing configuration cannot be read or parsed, pi-gate warns and prompts for every command until it is fixed. The published package includes [`config.schema.json`](config.schema.json); use this schema URL for editor completion:
+The extension reads `~/.pi/agent/gate.json`, falling back to legacy `~/.pi/agent/pi-gate.json` only when `gate.json` is absent. Set `PI_CODING_AGENT_DIR` to use a different configuration directory. If both files exist, only `gate.json` is used—even if it is invalid. To migrate, rename `pi-gate.json` to `gate.json` and run `/reload`; existing files are never automatically renamed, merged, or overwritten.
+
+On first load, if neither file exists, the extension creates `gate.json` with starter rules and a 30-second prompt timeout. If no configuration can be created yet, pi-gate warns at session start and allows commands until the file is created. If an existing configuration cannot be read or parsed, pi-gate warns and prompts for every command until it is fixed. The published package includes [`config.schema.json`](config.schema.json); use this schema URL for editor completion:
 
 ```json
 {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@zeldrisho/pi-gate",
-  "version": "0.4.1",
+  "version": "0.5.0",
   "description": "Pi extension that blocks or confirms bash commands based on a user-provided JSON configuration",
   "keywords": [
     "command-blocking",
@@ -32,10 +32,10 @@
     "access": "public"
   },
   "devDependencies": {
-    "@earendil-works/pi-coding-agent": "^0.84.2",
+    "@earendil-works/pi-coding-agent": "^0.85.1",
     "typescript": "^7.0.2",
-    "vite": "npm:@voidzero-dev/vite-plus-core@0.3.2",
-    "vite-plus": "0.3.2"
+    "vite": "npm:@voidzero-dev/vite-plus-core@0.3.3",
+    "vite-plus": "0.3.3"
   },
   "peerDependencies": {
     "@earendil-works/pi-coding-agent": "*"

package/src/config.ts

@@ -16,7 +16,9 @@ export interface ConfigLoadResult {
   status: ConfigLoadStatus;
 }
 
-const CONFIG_FILE_NAME = "pi-gate.json";
+const CONFIG_FILE_NAME = "gate.json";
+
+const LEGACY_CONFIG_FILE_NAME = "pi-gate.json";
 
 export const CONFIG_SCHEMA_URL =
   "https://raw.githubusercontent.com/zeldrisho/pi-packages/main/packages/pi-gate/config.schema.json";
@@ -54,10 +56,18 @@ function agentDir(): string {
 /**
  * Returns the full path to the pi-gate configuration file.
  *
- * @returns The absolute path to pi-gate.json
+ * Prefers gate.json, falling back to pi-gate.json only when gate.json is absent.
+ *
+ * @returns The selected configuration path, or gate.json for first-run creation
  */
 export function configPath(): string {
-  return join(agentDir(), CONFIG_FILE_NAME);
+  const path = join(agentDir(), CONFIG_FILE_NAME);
+
+  if (existsSync(path)) return path;
+
+  const legacyPath = join(agentDir(), LEGACY_CONFIG_FILE_NAME);
+
+  return existsSync(legacyPath) ? legacyPath : path;
 }
 
 /**

package/src/index.ts

@@ -5,7 +5,7 @@
  * user-provided JSON configuration. Without a configuration file, the
  * extension creates one with starter rules and a default prompt timeout.
  *
- * Configuration file: `~/.pi/agent/pi-gate.json`
+ * Configuration file: `~/.pi/agent/gate.json` (legacy fallback: `pi-gate.json`)
  *
  * The configuration has an `operations` section, which maps a substring
  * pattern to one of three actions, and an optional `promptTimeoutMs` setting:
@@ -18,7 +18,7 @@
  * narrow `allow` rule can override a broader `prompt` or `block` rule.
  *
  * On first run, a configuration with the default prompt timeout and starter
- * operation rules is written to `~/.pi/agent/pi-gate.json`.
+ * operation rules is written to `~/.pi/agent/gate.json` when neither file exists.
  *
  * Non-UI modes (print, JSON) never auto-approve. A `prompt` or `block` rule
  * in non-UI mode always blocks and requests termination of the agent turn.