portable-agent-layer 0.54.0 → 0.54.2

package/assets/templates/PAL/ALGORITHM.md

@@ -296,7 +296,7 @@ bun ~/.pal/tools/handoff-note.ts --done --title "what we completed"
 **Project work** — use ISCs, not threads:
 ```bash
 # Close completed ISCs:
-bun ~/.pal/tools/project.ts check-isc <project-name> <id>
+bun ~/.pal/tools/project.ts complete-isc <project-name> <id>
 
 # Open new ISCs for unfinished work:
 bun ~/.pal/tools/project.ts add-isc <project-name> "what remains"

package/assets/templates/PAL/STEERING_RULES.md

@@ -49,3 +49,8 @@ Correct: Memory says user dislikes verbose summaries → you keep the summary to
 **Don't trust, verify.** When adding a test or asserting a change works, prove it by making it fail first. A test that passes without ever being broken demonstrates nothing — it may be testing the wrong thing or nothing at all. Break it intentionally, confirm it fails for the right reason, then restore it.
 Bad: Add a test, see it green, move on. The test may pass vacuously.
 Correct: Add the test → run it green → break the code it covers → confirm it goes red → restore → now it's a real test.
+
+**Functions, not comments.** Encode intent in small, well-named, self-contained functions instead of explanatory comments. Comments cost tokens, drift from the code they describe, and can lie; a name is enforced by the call site. When tempted to write a comment explaining *why* a block does what it does, extract that block into a function whose name carries the why. The ONLY acceptable comment is a fact about an external system that code genuinely cannot encode — an SDK/protocol/service quirk (EventBridge, S3, a required HTTP header) — and even those should be rare and live at a single file location, not scattered.
+Bad: `// Mark scheduled BEFORE creating the schedule so a failed write can't orphan it` above an inline update + create + rollback block.
+Correct: `getOwnedPostState()` → `setPostState("scheduled")` → `registerSchedule()` → on failure `setPostState(previous)`. The ordering and rollback ARE the explanation.
+Exception: `// X-Restli-Protocol-Version: 2.0.0 — without it LinkedIn replies in Rest.li 1.0 shape` — an external contract the code can't express.

package/assets/templates/settings.claude.json

@@ -43,7 +43,10 @@
       "Need something reusable? Use the /create-skill command.",
       "PAL learns from your feedback and improves over time. Don't be shy to give feedback!",
       "For simple PDFs use the /create-pdf skill. Need a styled one? Use /consulting-report instead.",
-      "Use the /research skill to run comprehensive web research with multiple parallel agents."
+      "Use the /research skill to run comprehensive web research with multiple parallel agents.",
+      "Create presentations in HTML using the /presentation skill.",
+      "PAL can \"see\" what you are doing in the browser with the /playwright skill.",
+      "Want PAL to watch a youtube video? There's /analyze-youtube for that."
     ]
   },
   "hooks": {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "portable-agent-layer",
-  "version": "0.54.0",
+  "version": "0.54.2",
   "description": "PAL — Portable Agent Layer: persistent personal context for AI coding assistants",
   "type": "module",
   "bin": {

package/src/tools/agent/project.ts

@@ -378,9 +378,9 @@ function cmdAddIsc(args: string[]): void {
   ok({ added: true, id, title });
 }
 
-function cmdCheckIsc(args: string[]): void {
-  const name = args[0] ?? fail("Usage: check-isc <name> <id>");
-  const id = Number(args[1] ?? fail("Usage: check-isc <name> <id>"));
+function cmdCompleteIsc(args: string[]): void {
+  const name = args[0] ?? fail("Usage: complete-isc <name> <id>");
+  const id = Number(args[1] ?? fail("Usage: complete-isc <name> <id>"));
   if (!Number.isInteger(id) || id < 1) fail("ISC id must be a positive integer");
   const p = requireProject(name);
   const current = p.criteria ?? "";
@@ -396,6 +396,24 @@ function cmdCheckIsc(args: string[]): void {
   ok({ checked: true, id });
 }
 
+function cmdReopenIsc(args: string[]): void {
+  const name = args[0] ?? fail("Usage: reopen-isc <name> <id>");
+  const id = Number(args[1] ?? fail("Usage: reopen-isc <name> <id>"));
+  if (!Number.isInteger(id) || id < 1) fail("ISC id must be a positive integer");
+  const p = requireProject(name);
+  const current = p.criteria ?? "";
+  const existing = parseIscs(current).find((i) => i.id === id);
+  if (!existing) fail(`ISC-${id} not found in project "${name}"`);
+  if (!existing.checked) {
+    ok({ checked: false, id, alreadyOpen: true });
+    return;
+  }
+  p.criteria = patchIsc(current, id, false);
+  p.updated = now();
+  writeProject(p);
+  ok({ checked: false, id });
+}
+
 function cmdListIsc(args: string[]): void {
   const name = args[0] ?? fail("Usage: list-isc <name>");
   const p = requireProject(name);
@@ -482,7 +500,8 @@ Commands:
   update-section <name> <section> "content"     set an ISA body section
   criteria <name>                               print the Criteria section
   add-isc <name> "title"                        append a new open ISC to Criteria
-  check-isc <name> <id>                         mark ISC-N as done
+  complete-isc <name> <id>                      mark ISC-N as done
+  reopen-isc <name> <id>                        reopen ISC-N (mark not done)
   list-isc <name>                               list all ISCs with open/done status
   isa-init <name>                               mark project as ISA-initialized
   scaffold-task-isa <title>                     create a one-shot task ISA in memory/work/
@@ -566,8 +585,11 @@ function run(): void {
     case "add-isc":
       cmdAddIsc(rest);
       return;
-    case "check-isc":
-      cmdCheckIsc(rest);
+    case "complete-isc":
+      cmdCompleteIsc(rest);
+      return;
+    case "reopen-isc":
+      cmdReopenIsc(rest);
       return;
     case "list-isc":
       cmdListIsc(rest);