aiwcli 0.12.6 → 0.12.8

package/dist/templates/cc-native/_cc-native/lib-ts/plan-discovery.ts

@@ -1,80 +1,80 @@
-/**
- * Plan file discovery: find, read, and hash the plan file.
- * Extracted from cc-native-plan-review.ts.
- */
-
-import * as fs from "node:fs";
-import * as path from "node:path";
-import * as os from "node:os";
-import * as crypto from "node:crypto";
-
-import { logInfo, logDebug } from "../../_shared/lib-ts/base/logger.js";
-import { findPlanPathInTranscript } from "../../_shared/lib-ts/context/plan-manager.js";
-
-import type { DiscoveredPlan } from "./types.js";
-
-const HOOK = "plan-discovery";
-
-/**
- * Find the most recently modified plan file in ~/.claude/plans/.
- */
-export function findPlanFile(): string | null {
-  const plansDir = path.join(os.homedir(), ".claude", "plans");
-  if (!fs.existsSync(plansDir)) return null;
-  const files = fs.readdirSync(plansDir)
-    .filter(f => f.endsWith(".md"))
-    .map(f => {
-      const p = path.join(plansDir, f);
-      return { path: p, mtime: fs.statSync(p).mtimeMs };
-    })
-    .sort((a, b) => b.mtime - a.mtime);
-  return files.length > 0 ? files[0]!.path : null;
-}
-
-/**
- * Compute a short SHA-256 hash of plan content.
- */
-export function computePlanHash(content: string): string {
-  return crypto.createHash("sha256").update(content, "utf-8").digest("hex").slice(0, 16);
-}
-
-/**
- * Discover the plan file, read its content, and compute its hash.
- * Prefers transcript-based discovery (session-accurate), falls back to mtime scan.
- */
-export function discoverPlan(transcriptPath?: string): DiscoveredPlan | null {
-  let planPath: string | null = null;
-
-  if (transcriptPath) {
-    planPath = findPlanPathInTranscript(transcriptPath);
-    if (planPath) {
-      logInfo(HOOK, `Found plan via transcript: ${planPath}`);
-    } else {
-      logDebug(HOOK, "No plan Write found in transcript, falling back to mtime scan");
-    }
-  }
-
-  if (!planPath) {
-    planPath = findPlanFile();
-  }
-
-  if (!planPath) return null;
-
-  let content: string;
-  try {
-    content = fs.readFileSync(planPath, "utf-8").trim();
-  } catch {
-    return null;
-  }
-
-  if (!content) return null;
-
-  logInfo(HOOK, `Found plan at: ${planPath}`);
-  logDebug(HOOK, `Plan length: ${content.length} chars`);
-
-  return {
-    path: planPath,
-    content,
-    hash: computePlanHash(content),
-  };
-}
+/**
+ * Plan file discovery: find, read, and hash the plan file.
+ * Extracted from cc-native-plan-review.ts.
+ */
+
+import * as fs from "node:fs";
+import * as path from "node:path";
+import * as os from "node:os";
+import * as crypto from "node:crypto";
+
+import { logInfo, logDebug } from "../../_shared/lib-ts/base/logger.js";
+import { findPlanPathInTranscript } from "../../_shared/lib-ts/context/plan-manager.js";
+
+import type { DiscoveredPlan } from "./types.js";
+
+const HOOK = "plan-discovery";
+
+/**
+ * Find the most recently modified plan file in ~/.claude/plans/.
+ */
+export function findPlanFile(): string | null {
+  const plansDir = path.join(os.homedir(), ".claude", "plans");
+  if (!fs.existsSync(plansDir)) return null;
+  const files = fs.readdirSync(plansDir)
+    .filter(f => f.endsWith(".md"))
+    .map(f => {
+      const p = path.join(plansDir, f);
+      return { path: p, mtime: fs.statSync(p).mtimeMs };
+    })
+    .sort((a, b) => b.mtime - a.mtime);
+  return files.length > 0 ? files[0]!.path : null;
+}
+
+/**
+ * Compute a short SHA-256 hash of plan content.
+ */
+export function computePlanHash(content: string): string {
+  return crypto.createHash("sha256").update(content, "utf-8").digest("hex").slice(0, 16);
+}
+
+/**
+ * Discover the plan file, read its content, and compute its hash.
+ * Prefers transcript-based discovery (session-accurate), falls back to mtime scan.
+ */
+export function discoverPlan(transcriptPath?: string): DiscoveredPlan | null {
+  let planPath: string | null = null;
+
+  if (transcriptPath) {
+    planPath = findPlanPathInTranscript(transcriptPath);
+    if (planPath) {
+      logInfo(HOOK, `Found plan via transcript: ${planPath}`);
+    } else {
+      logDebug(HOOK, "No plan Write found in transcript, falling back to mtime scan");
+    }
+  }
+
+  if (!planPath) {
+    planPath = findPlanFile();
+  }
+
+  if (!planPath) return null;
+
+  let content: string;
+  try {
+    content = fs.readFileSync(planPath, "utf-8").trim();
+  } catch {
+    return null;
+  }
+
+  if (!content) return null;
+
+  logInfo(HOOK, `Found plan at: ${planPath}`);
+  logDebug(HOOK, `Plan length: ${content.length} chars`);
+
+  return {
+    path: planPath,
+    content,
+    hash: computePlanHash(content),
+  };
+}

package/dist/templates/cc-native/_cc-native/lib-ts/plan-enhancement.ts

@@ -1,41 +1,41 @@
-/**
- * Plan quality guidance for context emission.
- *
- * Provides prompt text that guides the main agent to review plans before
- * presenting them to the user. Emitted via emitContext() — NOT appended to plan files.
- *
- * Used by both SubagentStop hook (Plan agents) and PostToolUse:Write hook (direct writes).
- */
-
-/**
- * Returns the plan quality review prompt to emit as context after a plan is written.
- * This guides the main agent to review the plan before calling ExitPlanMode.
- *
- * Design principles:
- * - No hardcoded skill names — agent discovers relevant skills from system-reminders
- * - Documentation focuses on WHY (preserve decisions) not WHERE (file paths)
- * - Concise — every token in emitted context costs attention budget
- * - Trusts the agent's judgment — guidance, not mandate
- */
-export function getPlanQualityReviewContext(): string {
-  return `## Plan Quality Review
-
-Before presenting this plan, review it from the perspective of an agent with zero conversation history.
-
-### Self-Check
-- File paths are absolute and verified (not "the auth file" or "as discussed")
-- Function and class names are exact references (not "the handler" or "it")
-- Each step is specific enough to execute without this conversation's context
-- Verification steps are binary-testable (pass/fail in one check)
-
-### Skills Integration
-Review the skills listed in your system-reminder messages. Where a step would benefit from a specific skill, reference it inline (e.g., "Use \`SkillName\` skill for [specific purpose]"). Only reference skills relevant to this plan's domain.
-
-### Documentation Reasoning
-Evaluate whether the plan captures decisions that would be lost when this session ends. The implementation agent should understand:
-- What was decided and why alternatives were rejected
-- What constraints exist that aren't obvious from the code
-- What would break if assumptions change
-
-If the plan has gaps, address them before presenting to the user.`;
-}
+/**
+ * Plan quality guidance for context emission.
+ *
+ * Provides prompt text that guides the main agent to review plans before
+ * presenting them to the user. Emitted via emitContext() — NOT appended to plan files.
+ *
+ * Used by both SubagentStop hook (Plan agents) and PostToolUse:Write hook (direct writes).
+ */
+
+/**
+ * Returns the plan quality review prompt to emit as context after a plan is written.
+ * This guides the main agent to review the plan before calling ExitPlanMode.
+ *
+ * Design principles:
+ * - No hardcoded skill names — agent discovers relevant skills from system-reminders
+ * - Documentation focuses on WHY (preserve decisions) not WHERE (file paths)
+ * - Concise — every token in emitted context costs attention budget
+ * - Trusts the agent's judgment — guidance, not mandate
+ */
+export function getPlanQualityReviewContext(): string {
+  return `## Plan Quality Review
+
+Before presenting this plan, review it from the perspective of an agent with zero conversation history.
+
+### Self-Check
+- File paths are absolute and verified (not "the auth file" or "as discussed")
+- Function and class names are exact references (not "the handler" or "it")
+- Each step is specific enough to execute without this conversation's context
+- Verification steps are binary-testable (pass/fail in one check)
+
+### Skills Integration
+Review the skills listed in your system-reminder messages. Where a step would benefit from a specific skill, reference it inline (e.g., "Use \`SkillName\` skill for [specific purpose]"). Only reference skills relevant to this plan's domain.
+
+### Documentation Reasoning
+Evaluate whether the plan captures decisions that would be lost when this session ends. The implementation agent should understand:
+- What was decided and why alternatives were rejected
+- What constraints exist that aren't obvious from the code
+- What would break if assumptions change
+
+If the plan has gaps, address them before presenting to the user.`;
+}