@chatpanel/pii 0.7.2 → 0.7.4

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@chatpanel/pii",
-  "version": "0.7.2",
+  "version": "0.7.4",
   "description": "The canonical ChatPanel privacy engine \u2014 reversible PII redaction + pseudonymization with local entity detection. Pure, dependency-free ESM shared by the ChatPanel extension, gateway, and bridge.",
   "type": "module",
   "main": "index.js",

package/tool-harness.js

@@ -54,6 +54,22 @@ export function restoreToolArgs(value, vault) {
 // Codex chose its own web search over ChatPanel's `find` on one turn and answered from
 // nothing. The extra sentence says which tools restore and which do not, so the choice is
 // no longer a coin toss.
+/**
+ * The note for a turn with NO tools armed. The model still meets `[[LOCATION_1]]` in the
+ * conversation, and a coding agent told nothing about it stops to ask what the "unresolved
+ * placeholder" means — exactly what a redaction layer must never cause. So: treat it as a
+ * concrete value, write around it, echo it exactly; the real value is restored on the way
+ * back. Short, because there is nothing to call.
+ */
+export function placeholderNote() {
+  return 'PRIVACY PLACEHOLDERS: some values in this conversation are tokens like [[PERSON_1]], '
+    + '[[LOCATION_1]], [[ORG_1]] that stand in for the user\'s real private data. Treat each one as '
+    + 'a CONCRETE, specific value you already have — not missing or unknown information. Do not ask '
+    + 'what it stands for, do not say it is unresolved, and do not refuse on privacy grounds. Reason '
+    + 'and write with the placeholder exactly as written; the real value is restored in your answer '
+    + 'automatically.';
+}
+
 export function placeholderToolNote({ toolData = 'real', ownTools = false } = {}) {
   const intro =
     'PRIVACY PLACEHOLDERS: some values in this conversation are tokens like [[PERSON_1]], '
@@ -87,7 +103,8 @@ export function placeholderToolNote({ toolData = 'real', ownTools = false } = {}
       + 'yourself — your own web search, shell, file or code tools — receives the placeholder '
       + 'text literally and will find nothing. So for ANY lookup that involves a placeholder, '
       + 'call the listed tool (for example `find` with action `web_search` or `history_search`) '
-      + 'rather than your own; use your own tools only for things that involve no placeholder.'
+      + 'rather than your own. Prefer the listed tools for lookups in general — the user sees '
+      + 'those as steps — and keep your own tools for what the listed ones cannot do.'
     : '';
   return intro + remote + rules + own;
 }