@pourkit/cli 0.0.0-next-20260727021939 → 0.0.0-next-20260727065110

package/dist/cli.js

@@ -23078,11 +23078,11 @@ function createCliProgram(version) {
   return program;
 }
 async function resolveCliVersion() {
-  if (isPackageVersion("0.0.0-next-20260727021939")) {
-    return "0.0.0-next-20260727021939";
+  if (isPackageVersion("0.0.0-next-20260727065110")) {
+    return "0.0.0-next-20260727065110";
   }
-  if (isReleaseVersion("0.0.0-next-20260727021939")) {
-    return "0.0.0-next-20260727021939";
+  if (isReleaseVersion("0.0.0-next-20260727065110")) {
+    return "0.0.0-next-20260727065110";
   }
   try {
     const root = repoRoot();

package/dist/managed/skills/grill-with-docs/SKILL.md

@@ -126,6 +126,13 @@ There are two trigger paths:
 - The current grill session splits a larger effort into multiple PRD-sized Continuation Phases.
 - A follow-up grill session continues from a previous `Continuation Snapshot` in an earlier PRD. Findings from `improve-codebase-architecture` can be context for starting that follow-up grill, but the grill still locks the snapshot.
 
+For the follow-up trigger path, read the previous PRD's `Continuation Snapshot` and use it as the starting state. Carry forward prior `Carried Decisions` by default; do not rebuild continuation memory from only `Remaining Phases`, the current grill topic, or historical `Future Work` prose. Before handoff, explicitly resolve:
+
+- Which previously carried decisions, deferred ideas, rejected alternatives, future constraints, or ADR links remain unresolved and still need to stay in `Carried Decisions`?
+- Which previously carried items are intentionally removed because they were implemented, superseded by a newer locked decision, or made irrelevant by a locked architecture change?
+
+Any previously carried item that disappears must be named in `State Change From Previous Snapshot` under `Removed` with the reason. If removal was not explicitly resolved during the grill, keep the item carried forward.
+
 When a snapshot is needed, lock the exact state before handoff. It must include these fields, using normal Markdown:
 
 - **Origin**: the prior PRD, grill session, ADR, or decision that started the continuation chain.
@@ -135,7 +142,7 @@ When a snapshot is needed, lock the exact state before handoff. It must include
 - **State Change From Previous Snapshot**: explicit completed/current phase movement plus `Added`, `Removed`, and `Reordered`, even when each value is `None`.
 - **Carried Decisions**: grill-locked decisions, deferred decisions, rejected alternatives, future constraints, and ADR links that must carry into this phase or later phases, or `None` with a short explanation. Link an ADR when one exists for a carried decision.
 
-Use phase names directly; do not introduce phase IDs such as `P-01`. A Continuation Phase is PRD-sized and must not be called a slice, Implementation Slice, child Issue, or task. Reword a phase name only when the rewording is recorded in `State Change From Previous Snapshot`. Add a remaining phase only with explicit justification and user confirmation during the grill session.
+Use phase names directly; do not introduce phase IDs such as `P-01`. A Continuation Phase is PRD-sized and must not be called a slice, Implementation Slice, child Issue, or task. Reword a phase name only when the rewording is recorded in `State Change From Previous Snapshot`. Add a remaining phase only with explicit justification and user confirmation during the grill session. Do not drop unresolved deferred memory merely because it is not promoted to a named `Remaining Phase`; keep it in `Carried Decisions` until it is implemented, superseded, or explicitly removed with reason.
 
 Treat the `Continuation Snapshot` as memory for the continuation chain, not just a phase cursor. When the grill session discusses work that is intentionally deferred, rejected, or constrained because of code/doc findings, capture the durable decision in `Carried Decisions` if a future PRD would need that context to avoid rediscovering or contradicting it. Preserve the rationale briefly, including whether the decision came from user direction, a subagent finding, an ADR, a prior PRD, or current grill consensus.
 

package/dist/managed/skills/to-prd/SKILL.md

@@ -127,7 +127,7 @@ Every slice marked `AFK: yes` must have zero unresolved decisions. If a contract
 
 ## Continuation Snapshot
 
-Write `## Continuation Snapshot` only when `grill-with-docs` locked a snapshot for the PRD being authored. If no snapshot was locked, omit this section entirely; do not infer one from historical `Future Work`, deferred ideas, roadmap language, or your own decomposition.
+Write `## Continuation Snapshot` only when `grill-with-docs` locked a snapshot for the PRD being authored. If no snapshot was locked, omit this section entirely; do not infer one from historical `Future Work`, deferred ideas, roadmap language, or your own decomposition. When the locked snapshot continues from a prior PRD, use the prior PRD's `Continuation Snapshot` only as validation evidence for carry-forward integrity, not as permission to invent new continuation state.
 
 When a snapshot was locked, write the locked state exactly as handed off, allowing only formatting or clarity edits that do not change meaning. The section must include these fields:
 
@@ -140,6 +140,8 @@ When a snapshot was locked, write the locked state exactly as handed off, allowi
 
 Do not infer, add, remove, reorder, rename, or reinterpret Continuation Phases or carried decisions. If any required field is missing or unclear, ask or block before writing `PRD.md`; do not fill the gap yourself. Use phase names directly and do not introduce phase IDs such as `P-01`.
 
+For follow-up snapshots, compare the previous snapshot's `Carried Decisions` to the locked snapshot. If a previously carried deferred decision, rejected alternative, future constraint, or ADR link disappeared, `State Change From Previous Snapshot` must name it under `Removed` and explain that it was implemented, superseded by a newer locked decision, or made irrelevant by a locked architecture change. If the removal is not explicit, block and ask for the locked snapshot to be corrected; do not silently drop the item and do not re-add it yourself.
+
 `Completed Phases`, `Remaining Phases`, and `Carried Decisions` may be empty only when the locked snapshot explicitly writes `None` with a short explanation. `State Change From Previous Snapshot` must explicitly record completed/current phase movement plus `Added`, `Removed`, and `Reordered`, even when each value is `None`.
 
-Treat `Carried Decisions` as continuation memory, not only as decisions implemented by the current PRD. If `grill-with-docs` locked deferred decisions, rejected alternatives, future constraints, or code/doc findings that future phases must remember, preserve them in `Carried Decisions` exactly as handed off. Do not move them into a generic backlog, omit them because they are non-goals for the current phase, or expand them into detailed requirements for remaining phases.
+Treat `Carried Decisions` as continuation memory, not only as decisions implemented by the current PRD. If `grill-with-docs` locked deferred decisions, rejected alternatives, future constraints, or code/doc findings that future phases must remember, preserve them in `Carried Decisions` exactly as handed off. Do not move them into a generic backlog, omit them because they are non-goals for the current phase, omit them because they are not named as `Remaining Phases`, or expand them into detailed requirements for remaining phases.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@pourkit/cli",
-  "version": "0.0.0-next-20260727021939",
+  "version": "0.0.0-next-20260727065110",
   "private": false,
   "type": "module",
   "repository": {