@henryqw/pi-pr 3.1.2 → 3.1.3

package/README.md

@@ -21,10 +21,13 @@ keeps the complete JSON output. Read one item with
 `pr-feedback.mjs show --snapshot FILE --id ID`.
 
 `show` prints one JSON record with its exact stored body and fields. A thread
-record includes child IDs without child bodies. A nested comment includes only
-its parent thread's ID, state, and location. Missing, unknown, duplicate, or
-ambiguous IDs fail. `show` does not run Git, call GitHub, use the network, or
-write files.
+record includes child IDs without child bodies. Treat that record as a container.
+Inspect the `thread_comment` IDs directly. Do not call `show` on the parent only
+to find children. Show the parent only when it has no child, or when you need
+parent-level metadata. Issue independent `show` lookups in one tool-call round.
+A nested comment includes only its parent thread's ID, state, and location.
+Missing, unknown, duplicate, or ambiguous IDs fail. `show` does not run Git, call
+GitHub, use the network, or write files.
 
 ## Works with
 
@@ -106,7 +109,7 @@ The comment sweep resolves its bundled helper and references from the installed
 
 The footer and widget load at session start. A directory outside a Git worktree stays silent and does not start polling. The UI shows `PR · status unavailable` for other discovery failures and reports only a generic error.
 
-They refresh after local commits, PR creation, pushes, and each dispatched workflow settles. They also refresh after any successful delegated task settles. Active Git worktrees poll every 30 seconds. Polling updates presentation only and may be stale.
+They refresh after local commits, PR creation, pushes, and each dispatched workflow settles. During creation, intermediate refreshes wait until the workflow settles. They also refresh after any successful delegated task settles. Active Git worktrees poll every 30 seconds. Polling updates presentation only and may be stale.
 
 The create widget stays hidden until the local branch has a commit beyond its creation point. Any displayed widget clears as soon as `/pr` starts. A dispatched workflow keeps it hidden until the agent settles. A direct merge, no-action route, or failed command refreshes the widget when the handler finishes.
 

package/extensions/pr.ts

@@ -203,7 +203,7 @@ export default function pullRequestExtension(
 
 	const refresh = async (): Promise<void> => {
 		const ctx = context;
-		if (!ctx) return;
+		if (!ctx || [...activeInvocations.values()].includes("create-workflow")) return;
 		const generation = sessionGeneration;
 		if (active) {
 			queued = true;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@henryqw/pi-pr",
-  "version": "3.1.2",
+  "version": "3.1.3",
   "description": "Run /pr to safely discover or link the current pull request, then create, update, address feedback, fix CI, or merge when ready.",
   "keywords": [
     "pi-package",

package/skills/pi-pr-comment-sweep/SKILL.md

@@ -33,13 +33,17 @@ Run standalone; never invoke, defer to, or modify Shipyard.
 
 2. Initial fetch prints a compact index of every feedback ID. Later fetches into
    a copied snapshot print compact indexes of additions, edits, and state changes.
-   The snapshot remains complete. For each non-obvious item, inspect only that item:
+   The snapshot remains complete. A thread record with child IDs is a container:
+   inspect `thread_comment` IDs directly. Do not call `show` on the parent solely
+   to discover its children. Show the parent only if it has no child or parent-level
+   metadata is actually needed. For each non-obvious item, inspect only that item:
 
    ```bash
    node "<skill>/scripts/pr-feedback.mjs" show --snapshot "$SNAPSHOT" --id "$ID"
    ```
 
-   Always inspect every unresolved feedback item before triage. Never
+   Issue independent `show` lookups in one tool-call round. Always inspect every
+   unresolved feedback item before triage. Never
    read or print the whole raw snapshot when `show` provides the bounded lookup.
    Follow [Thread triage](<skill>/references/thread-triage.md>) and ledger every item as
    `actionable`, `non-actionable`, or `blocked`, with terse evidence, smallest