@prjct.app/pi-signals 0.1.1 → 0.1.2

package/CHANGELOG.md

@@ -1,3 +1,7 @@
+## 0.1.2 (2026-10-09)
+
+- No system-prompt rule. signal_report no longer asks every session to watch Pi and extensions; its description says what it records and when to inspect targets first.
+
 ## 0.1.1 (2026-10-07)
 
 - Bind the standalone npm CLI to the Pi host's public SDK peers, which Pi intentionally omits from extension installs. Record the host location on session start and use the same bootstrap for scheduled runs.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@prjct.app/pi-signals",
-  "version": "0.1.1",
+  "version": "0.1.2",
   "description": "Local failure signals, daily agent-owned triage and verified repair candidates for Pi.",
   "type": "module",
   "license": "MIT",

package/src/index.ts

@@ -20,8 +20,8 @@ export function installSignals(pi: ExtensionAPI, dependencies: SignalsDependenci
   };
   pi.registerTool({
     name: 'signal_report', label: 'Record failure signal',
-    description: 'Record a local issue in the global .prjct database for an installed extension or Pi: latency regression, crash, or concrete response-quality regression. Supply a stable defect signature, exact session evidence, reproduction steps, expected and actual behavior. No GitHub or model request occurs during capture.',
-    promptGuidelines: ['When you detect a latency regression, crash, or concrete response-quality regression in Pi or an installed extension, record minimal evidence with signal_report, then continue the original task. Use signal_inspect for targets. Detection is a signal, not proof of causality; the active agent and later triage decide.'],
+    // No promptGuidelines: a system-prompt rule asked every session to watch Pi, whatever the task.
+    description: 'Record a local issue in the global .prjct database for an installed extension or Pi: latency regression, crash, or concrete response-quality regression. Supply a stable defect signature, exact session evidence, reproduction steps, expected and actual behavior. Find targets with signal_inspect first; a detection is a signal, not proof of causality. No GitHub or model request occurs during capture; afterwards, continue the original task.',
     parameters: ReportSchema,
     async execute(_id, input, _signal, _update, ctx) {
       const target = catalog(ctx).find(target => target.id === input.target);