@chatpanel/gateway 0.1.0 → 0.1.1

package/README.md

@@ -34,7 +34,7 @@ Two backends (config `backend`):
   the gateway stores no keys.
 
 The redaction engine is the **same code** the ChatPanel extension runs — the
-[`chatpanel-pii`](https://github.com/chatpanel/chatpanel-pii) package is the
+[`@chatpanel/pii`](https://github.com/chatpanel/chatpanel-pii) package is the
 single source of truth, so a privacy feature added once is shared everywhere.
 
 ## Quick start (bridge backend)
@@ -43,7 +43,7 @@ You need the [ChatPanel bridge](https://github.com/chatpanel/chatpanel-bridge)
 running and logged into codex/claude (the same bridge the extension uses).
 
 ```bash
-npm install -g chatpanel-gateway
+npm install -g @chatpanel/gateway
 chatpanel-gateway
 # → ChatPanel Privacy Gateway v0.1.0 on http://127.0.0.1:4320
 #     backend  : bridge (agent: codex, via http://127.0.0.1:4319)
@@ -129,7 +129,7 @@ restores cleanly.
 The [extension](https://github.com/chatpanel/chatpanel-extension) redacts inside
 the browser; the [bridge](https://github.com/chatpanel/chatpanel-bridge) lets the
 browser drive local CLI agents. This gateway reuses the bridge to put the **same
-redaction engine** ([`chatpanel-pii`](https://github.com/chatpanel/chatpanel-pii))
+redaction engine** ([`@chatpanel/pii`](https://github.com/chatpanel/chatpanel-pii))
 in front of *any* agent — so non-browser tools get the privacy too, and the
 agent's own multi-turn loop is blinded, not just the first prompt.
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@chatpanel/gateway",
-  "version": "0.1.0",
+  "version": "0.1.1",
   "description": "Local privacy gateway — redacts PII out of OpenAI/Anthropic API traffic before it reaches a model, then restores it in the reply. Point opencode, codex, aider, Claude Code, etc. at it.",
   "type": "module",
   "bin": {
@@ -28,7 +28,7 @@
     "node": ">=18"
   },
   "dependencies": {
-    "@chatpanel/pii": "^0.1.0"
+    "@chatpanel/pii": "^0.1.1"
   },
   "homepage": "https://chatpanel.net",
   "repository": {

package/src/redact.js

@@ -8,7 +8,7 @@
 // mapping is self-consistent within the request. (Same reasoning as the
 // extension's pii-pipeline.)
 
-import { createVault, redactText, detectEntities, effectiveTier, gatedDictionary } from 'chatpanel-pii';
+import { createVault, redactText, detectEntities, effectiveTier, gatedDictionary } from '@chatpanel/pii';
 
 // tier: 'basic' | 'full'. For 'full' we run the local detector over the combined
 // text to harvest names/orgs, then redact every segment against that entity set.

package/src/server.js

@@ -21,7 +21,7 @@ import { createServer } from 'node:http';
 import { loadConfig } from './config.js';
 import { redactSegments } from './redact.js';
 import { pipeRestoredStream, makeTokenRestorer } from './stream.js';
-import { restoreText } from 'chatpanel-pii';
+import { restoreText } from '@chatpanel/pii';
 import { streamBridgeChat, readBridgeToken } from './bridge.js';
 import { shaperFor } from './shape.js';
 import { startNer } from './ner.js';
@@ -31,7 +31,7 @@ import * as openai from './openai.js';
 import * as responses from './responses.js';
 import * as anthropic from './anthropic.js';
 
-export const VERSION = '0.1.0';
+export const VERSION = '0.1.1';
 
 const KNOWN_AGENTS = new Set(['codex', 'claude', 'opencode', 'pi', 'kiro', 'antigravity']);
 

package/src/stream.js

@@ -12,7 +12,7 @@
 // agent unchanged — its defined "permanent substitution" behavior. Only reversible
 // [[TYPE_n]] tokens are restored here.
 
-import { restoreText } from 'chatpanel-pii';
+import { restoreText } from '@chatpanel/pii';
 
 // Returns a TransformStream-free chunk transformer: feed it decoded string chunks,
 // it returns the prefix that's safe to forward now and buffers a possibly-partial