sync: upstream pstack c742dd6 (0.15.36)

.omp-plugin/marketplace.json

@@ -5,13 +5,13 @@
   },
   "metadata": {
     "description": "pstack, poteto's engineering methodology for Cursor, ported to oh-my-pi. Model and provider agnostic.",
-    "version": "0.15.34"
+    "version": "0.15.36"
   },
   "plugins": [
     {
       "name": "pstack",
-      "description": "60 skills, 23 playbooks, 24 principles, the poteto-mode pin, and two agents. Upstream cursor/plugins pstack at 519d36a.",
-      "version": "0.15.34",
+      "description": "60 skills, 23 playbooks, 24 principles, the poteto-mode pin, and two agents. Upstream cursor/plugins pstack at c742dd6.",
+      "version": "0.15.36",
       "category": "development",
       "license": "MIT",
       "source": "./plugins/pstack"

PORTING.md

@@ -221,13 +221,12 @@ The split is by kind, not by size.
   therefore cannot conflict with upstream at all.
 - A patch is for code: control flow, a data shape, a file upstream does not have.
   `worktree-audit-omp.patch` and `zzz-script-typecheck.patch` are the port's own changes; the
-  second typechecks `orch/` and `bootstrap.ts` as well as `watch-pr/`. `zzz-make-bot-ui-omp.patch`
-  is the one markdown patch, a notice that the skill's webhook mechanic does not exist on omp. Two
-  `zzz*` patches carry open upstream PRs. `zzz-watch-pr-fixes.patch` carries #769, and
-  `zzzz-orch-lock-takeover.patch` carries #733 with an age-limited marker. When upstream merges an
-  equivalent, delete the hunks it covers rather than resolving them, and do not wait for the patch
-  to fail first. A hunk that only adds lines can still find its context at an offset, which at
-  `e73df47` would have added #804's tests to `orch.test.ts` a second time.
+  second typechecks `bootstrap.ts` as well as `watch-pr/`. `zzz-make-bot-ui-omp.patch` is the one
+  markdown patch, a notice that the skill's webhook mechanic does not exist on omp. One `zzz*`
+  patch carries an open upstream PR. `zzz-watch-pr-fixes.patch` carries #769. When upstream merges
+  an equivalent, delete the hunks it covers rather than resolving them, and do not wait for the
+  patch to fail first. A hunk that only adds lines can still find its context at an offset and
+  apply a second time.
 
 Author a patch against **post-rules** text. `rules.sed` runs first, so a hunk quoting the raw
 upstream line fails whenever an earlier rule rewrote it. `worktree-audit-omp.patch` deletes a
@@ -323,10 +322,8 @@ The injected reminder is a pointer, not the playbook. It tells the agent to read
   prints the binary's builtin tool list, which on 18.12.6 carries `wait` and no `hub`; the binary's
   only other `hub` is the `/hub` slash command that opens Agent Hub. An earlier tree read a `hub`
   tool with list/send/inbox/wait ops off a stale pi-coding-agent 17.x package, and the gate now
-  fails any shipped sentence that names one. The orchestrator uses its own TSV store and
-  `orch inbox` for the queue instead, so sibling messaging stays unused there. Cross-session
-  messaging does not exist locally and gets no workaround here. It is tracked upstream and stays
-  open.
+  fails any shipped sentence that names one. Cross-session messaging does not exist locally and
+  gets no workaround here. It is tracked upstream and stays open.
 
 ## Still missing in omp
 

omp-port/UPSTREAM

@@ -1 +1 @@
-519d36aa98955bf680db01bcde5fdfba686dc901
+c742dd61706fbacc1b95f1a20b7b988cf096ce6c

omp-port/patches/zzz-script-typecheck.patch

@@ -22,5 +22,5 @@ new file mode 100644
 +    "target": "esnext",
 +    "types": ["bun-types"]
 +  },
-+  "include": ["bootstrap.ts", "orch/**/*.ts", "watch-pr/**/*.ts"]
++  "include": ["bootstrap.ts", "watch-pr/**/*.ts"]
 +}