@henryqw/pi-pr 6.0.2 → 6.0.4

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@henryqw/pi-pr",
3
- "version": "6.0.2",
3
+ "version": "6.0.4",
4
4
  "description": "Run /pr to safely discover or link the current pull request, then create, update, address feedback, fix CI, or merge when ready.",
5
5
  "keywords": [
6
6
  "pi-package",
@@ -27,8 +27,8 @@
27
27
  "pack:check": "npm pack --dry-run"
28
28
  },
29
29
  "peerDependencies": {
30
- "@earendil-works/pi-coding-agent": "^0.86.0",
31
- "@earendil-works/pi-tui": "^0.86.0",
30
+ "@earendil-works/pi-coding-agent": ">=0.86.0 <0.88.0",
31
+ "@earendil-works/pi-tui": ">=0.86.0 <0.88.0",
32
32
  "typebox": "^1.3.15"
33
33
  },
34
34
  "dependencies": {
@@ -38,8 +38,8 @@
38
38
  "proper-lockfile": "^4.1.2"
39
39
  },
40
40
  "devDependencies": {
41
- "@earendil-works/pi-coding-agent": "0.86.0",
42
- "@earendil-works/pi-tui": "0.86.0",
41
+ "@earendil-works/pi-coding-agent": "0.87.0",
42
+ "@earendil-works/pi-tui": "0.87.0",
43
43
  "@types/proper-lockfile": "^4.1.4"
44
44
  },
45
45
  "repository": {
@@ -33,9 +33,12 @@ Use the package-owned comment-sweep workflow. It exposes these closed actions:
33
33
  fresh feedback, clears the old ledger, and returns a new guard plus bounded
34
34
  IDs and kinds. Status never includes feedback bodies.
35
35
  8. Use `show` with the new guard for every returned ID. This catches new items
36
- and edits that kept the same ID. Then call `record` with that guard and one
37
- complete replacement ledger. Omit `ownedPaths`; the initial ownership stays
38
- fixed. A stale guard or mismatched coverage fails.
36
+ and edits that kept the same ID. The published head is frozen: do not edit,
37
+ commit, move `HEAD`, or call `publish` again after this refresh. Classify any
38
+ new actionable feedback not fixed in the published head as `blocked`, finish
39
+ this sweep, then run `/pr` again for a follow-up sweep. Call `record` with the
40
+ refreshed guard and one complete replacement ledger. Omit `ownedPaths`; the
41
+ initial ownership stays fixed. A stale guard or mismatched coverage fails.
39
42
  9. Call `resolve` only with addressed, unresolved parent thread IDs. Do not
40
43
  resolve a thread classified as non-actionable or blocked. Do not post replies
41
44
  unless the user asks.