arey-pi 0.6.0 → 0.6.2

package/README.md

@@ -74,7 +74,7 @@ tech-lead
 The intended daily experience is natural language first:
 
 ```txt
-Implement password reset following Arey Pi.
+Implement password reset.
 ```
 
 The parent agent should act as the tech lead,
@@ -140,15 +140,16 @@ Arey Pi includes a polished extension-backed setup and natural-language workflow
 /arey-bootstrap --full      # explicit alias for the default full bootstrap
 /arey-bootstrap --force     # full bootstrap and overwrite selected project-local files
 # Development workflows are natural-language first:
-# "Implementa password reset siguiendo Arey Pi"
-# "Corrige este bug con Arey Pi"
-# "Revisa el current diff contra Arey Pi"
+# "Implementa password reset"
+# "Corrige este bug"
+# "Revisa el current diff"
 ```
 
 The goal is that users work naturally without development commands.
-Requests such as `Implementa password reset siguiendo Arey Pi` automatically activate quiet harness context behind the scenes.
-Arey Pi lets the parent agent infer the work mode,
-act as orchestrator,
+When the package is installed,
+Arey Pi automatically injects quiet harness context behind the scenes on every agent turn.
+The parent agent infers the work mode,
+acts as orchestrator,
 use specialist subagents when available,
 inject the relevant delivery guidance,
 and apply simple event-based guardrails for protected paths.
@@ -201,7 +202,7 @@ documentation sync rule,
 core subagent role definitions,
 and professional setup extension commands exist.
 
-Arey Pi now includes natural-language harness activation,
+Arey Pi now includes always-on natural-language harness injection,
 focused prompts,
 TDD/spec-sync/review skills,
 and extension-core tests.

package/docs/adoption.md

@@ -88,7 +88,7 @@ agents should be able to discover:
 Ask naturally:
 
 ```txt
-Evalúa este repo contra Arey Pi
+Evalúa este repo
 ```
 
 You can also use the focused prompt template if desired:
@@ -206,7 +206,7 @@ run setup diagnostics and ask for a natural readiness assessment:
 
 ```txt
 /arey-doctor
-Evalúa este repo contra Arey Pi
+Evalúa este repo
 ```
 
 A good first adoption result is not perfection.

package/docs/commands.md

@@ -2,7 +2,8 @@
 
 Arey Pi ships a Pi extension that registers native setup slash commands.
 Development workflows are intentionally natural-language first:
-the extension recognises explicit Arey Pi opt-in and injects quiet harness guidance automatically.
+when the package is installed,
+the extension injects quiet harness guidance automatically on every agent turn.
 
 ## Command overview
 
@@ -152,17 +153,17 @@ Use this command after installing Arey Pi and `pi-subagents` in a repository whe
 ## Natural-language development workflows
 
 Arey Pi is designed to work without development slash commands.
-When the user explicitly opts into Arey Pi in normal language,
-for example:
+When the package is installed,
+the extension injects quiet harness context automatically before every agent turn.
+Users can simply ask naturally:
 
 ```txt
-Implementa password reset siguiendo Arey Pi
-Corrige este bug con Arey Pi
-Revisa el current diff contra Arey Pi
-Evalúa este repo contra Arey Pi
+Implementa password reset
+Corrige este bug
+Revisa el current diff
+Evalúa este repo
 ```
 
-The extension injects quiet harness context automatically before the agent turn.
 The harness is not meant to add ceremony for the user.
 It asks the agent to infer whether the request is a feature,
 bugfix,
@@ -187,7 +188,7 @@ The injected harness guidance emphasises:
 While Arey Pi is active,
 Arey Pi applies simple tool-call guardrails:
 
-- writes or edits to protected paths such as `.env`, `.git/`, and `node_modules/` are blocked.
+- writes or edits to env files such as `.env` and `.env.local` are blocked; `.git/` and `node_modules/` remain readable and writable when the task genuinely requires them.
 
 
 ## Prompt templates and skills

package/docs/pi-subagents.md

@@ -79,7 +79,7 @@ They should not create their own subagent workflows unless explicitly launched w
 Good parent request:
 
 ```txt
-Implement password reset following Arey Pi.
+Implement password reset.
 Use specialist subagents where useful.
 ```
 

package/docs/templates.md

@@ -133,7 +133,7 @@ The readiness report template captures Arey Pi assessment output.
 
 Use it when you want a persistent audit snapshot under `docs/`.
 For routine checks,
-ask naturally: `Evalúa este repo contra Arey Pi`.
+ask naturally: `Evalúa este repo`.
 
 ## Template Maintenance
 

package/docs/workflows.md

@@ -3,15 +3,15 @@
 See `docs/workflow-diagram.md` for a visual overview of the framework workflow.
 
 Arey Pi development workflows are natural-language first.
-When the user asks to work following Arey Pi,
-the extension injects quiet harness guidance automatically before the agent turn.
+When the package is installed,
+the extension injects quiet harness guidance automatically before every agent turn.
 
 ## Feature Workflow
 
 Example request:
 
 ```txt
-Implementa password reset siguiendo Arey Pi
+Implementa password reset
 ```
 
 Expected flow:
@@ -43,7 +43,7 @@ The workflow should:
 Example request:
 
 ```txt
-Corrige el bug de verificación de email con Arey Pi
+Corrige el bug de verificación de email
 ```
 
 Use this when behaviour is wrong.
@@ -63,7 +63,7 @@ and it should live outside production source directories by default.
 Example request:
 
 ```txt
-Sincroniza specs y docs con Arey Pi para el current diff
+Sincroniza specs y docs para el current diff
 ```
 
 Use this before completing non-trivial work or when drift is suspected.
@@ -103,7 +103,7 @@ or justified unaffected statuses.
 Example request:
 
 ```txt
-Revisa el current diff contra Arey Pi
+Revisa el current diff
 ```
 
 Use this for adversarial engineering review.
@@ -130,7 +130,7 @@ Findings should be classified by severity.
 Example request:
 
 ```txt
-Evalúa este repo contra Arey Pi
+Evalúa este repo
 ```
 
 Use this to assess project readiness.
@@ -185,7 +185,7 @@ Users do not need to memorise commands.
 This should work:
 
 ```txt
-Implement password reset following Arey Pi.
+Implement password reset.
 ```
 
 The parent agent should act as tech lead,

package/extensions/arey-pi/core.ts

@@ -56,12 +56,6 @@ export function parseBootstrapFlags(args: string): BootstrapPlan {
   };
 }
 
-export function shouldActivateAreyPiHarness(prompt: string): boolean {
-  const normalized = prompt.toLowerCase();
-  if (normalized.includes("arey pi harness is active")) return false;
-  return /\barey(?:\s+pi)?\b/.test(normalized);
-}
-
 const evidenceSummary = `Final evidence format:\n- Behaviour/spec impact:\n- Tests/TDD, including test location:\n- Validation commands and results:\n- Quality tooling:\n- Spec sync:\n- Documentation sync:\n- Architecture/ADR/glossary impact:\n- Database/DBML impact:\n- Residual risks:`;
 
 export function areyPiHarnessContext(prompt: string): string {
@@ -129,7 +123,7 @@ export function buildDoctorReport(input: DoctorReportInput): string {
     "",
     "## Recommended next step",
     input.installedAgentsCount === input.requiredAgentsCount
-      ? "- Project-local Arey Pi subagents are installed. Use natural language such as `Implementa password reset siguiendo Arey Pi`."
+      ? "- Project-local Arey Pi subagents are installed. Work naturally; Arey Pi harness guidance is injected automatically."
       : "- Run `/arey-bootstrap` to install project-local Arey Pi subagents.",
   ].join("\n");
 }

package/extensions/arey-pi/workflow-runtime.ts

@@ -1,62 +1,13 @@
 import {
   isToolCallEventType,
   type ExtensionAPI,
-  type ExtensionContext,
   type ToolCallEvent,
   type ToolCallEventResult,
 } from "@earendil-works/pi-coding-agent";
-import { areyPiHarnessContext, shouldActivateAreyPiHarness } from "./core.ts";
+import { areyPiHarnessContext } from "./core.ts";
 
-const areyPiSessionEntryType = "arey-pi-session";
-
-type HarnessSessionData = { active: boolean };
-type HarnessStore = { active: boolean };
-type SessionEntry = ReturnType<ExtensionContext["sessionManager"]["getEntries"]>[number];
-type CustomSessionEntry = Extract<SessionEntry, { type: "custom" }>;
-type HarnessCustomEntry = CustomSessionEntry & { customType: typeof areyPiSessionEntryType };
-
-function isObject(value: unknown): value is Record<string, unknown> {
-  return typeof value === "object" && value !== null;
-}
-
-function isHarnessSessionData(value: unknown): value is HarnessSessionData {
-  return isObject(value) && typeof value.active === "boolean";
-}
-
-function isHarnessCustomEntry(value: unknown): value is HarnessCustomEntry {
-  return isObject(value) && value.type === "custom" && value.customType === areyPiSessionEntryType;
-}
-
-function latestHarnessSessionState(ctx: ExtensionContext): boolean {
-  const entry = ctx.sessionManager.getEntries().filter(isHarnessCustomEntry).at(-1);
-  return entry && isHarnessSessionData(entry.data) ? entry.data.active : false;
-}
-
-function persistHarnessState(pi: ExtensionAPI, active: boolean): void {
-  pi.appendEntry(areyPiSessionEntryType, { active } satisfies HarnessSessionData);
-}
-
-function updateHarnessUi(active: boolean, ctx: ExtensionContext): void {
-  ctx.ui.setStatus("arey-pi", active ? ctx.ui.theme.fg("accent", "Arey Pi") : undefined);
-  ctx.ui.setWidget(
-    "arey-pi-harness",
-    active
-      ? [
-          "Arey Pi active: natural-language harness guidance is injected.",
-          "The agent infers feature/bugfix/sync/review/assessment intent.",
-        ]
-      : undefined,
-  );
-}
-
-function activateHarness(pi: ExtensionAPI, store: HarnessStore, ctx: ExtensionContext): void {
-  store.active = true;
-  persistHarnessState(pi, true);
-  updateHarnessUi(true, ctx);
-}
-
-function isSensitivePath(path: string): boolean {
-  return [".env", ".git/", "node_modules/"].some((protectedPath) => path.includes(protectedPath));
+function isProtectedEnvPath(path: string): boolean {
+  return path.split("/").some((segment) => segment === ".env" || segment.startsWith(".env."));
 }
 
 function editedPath(event: ToolCallEvent): string | undefined {
@@ -67,46 +18,26 @@ function editedPath(event: ToolCallEvent): string | undefined {
   return undefined;
 }
 
-function handleMutationGuardrails(
-  store: HarnessStore,
-  event: ToolCallEvent,
-  ctx: ExtensionContext,
-): ToolCallEventResult | undefined {
+function handleMutationGuardrails(event: ToolCallEvent): ToolCallEventResult | undefined {
   const path = editedPath(event);
   if (!path) return undefined;
 
-  if (isSensitivePath(path)) {
-    ctx.ui.notify(`Blocked write to protected path: ${path}`, "warning");
-    return { block: true, reason: `Arey Pi guardrail: path is protected: ${path}` };
+  if (isProtectedEnvPath(path)) {
+    return { block: true, reason: `Arey Pi guardrail: env file writes are protected: ${path}` };
   }
 
-  if (!store.active) return undefined;
-
   return undefined;
 }
 
 export function registerWorkflowRuntime(pi: ExtensionAPI): void {
-  const store: HarnessStore = { active: false };
-
-  pi.on("session_start", (_event, ctx) => {
-    store.active = latestHarnessSessionState(ctx);
-    updateHarnessUi(store.active, ctx);
-  });
-
-  pi.on("before_agent_start", (event, ctx) => {
-    const requestedAreyPi = shouldActivateAreyPiHarness(event.prompt);
-    if (!store.active && !requestedAreyPi) return undefined;
-    if (requestedAreyPi) activateHarness(pi, store, ctx);
-
-    return {
-      message: {
-        customType: "arey-pi-harness-context",
-        content: areyPiHarnessContext(event.prompt),
-        display: false,
-        details: { source: requestedAreyPi ? "natural-language" : "active-session" },
-      },
-    };
-  });
-
-  pi.on("tool_call", (event, ctx) => handleMutationGuardrails(store, event, ctx));
+  pi.on("before_agent_start", (event) => ({
+    message: {
+      customType: "arey-pi-harness-context",
+      content: areyPiHarnessContext(event.prompt),
+      display: false,
+      details: { source: "always-on" },
+    },
+  }));
+
+  pi.on("tool_call", (event) => handleMutationGuardrails(event));
 }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "arey-pi",
-  "version": "0.6.0",
+  "version": "0.6.2",
   "description": "A Pi package for canonical Gherkin specs, non-negotiable TDD, spec synchronisation, AI harness readiness, and senior-quality software delivery.",
   "license": "MIT",
   "author": "Alejandro Rey Leyva",