prizmkit 1.1.177 → 1.1.178

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.
@@ -1,5 +1,5 @@
1
1
  {
2
- "frameworkVersion": "1.1.177",
3
- "bundledAt": "2026-08-14T15:01:11.231Z",
4
- "bundledFrom": "99ed585"
2
+ "frameworkVersion": "1.1.178",
3
+ "bundledAt": "2026-08-15T02:56:19.265Z",
4
+ "bundledFrom": "6b87213"
5
5
  }
@@ -1,5 +1,5 @@
1
1
  {
2
- "version": "1.1.177",
2
+ "version": "1.1.178",
3
3
  "skills": {
4
4
  "prizmkit": {
5
5
  "description": "Framework introduction and navigation for the formal single-requirement lifecycle, project initialization, Prizm docs, and independent deployment.",
@@ -45,6 +45,12 @@ Resource impact has three values:
45
45
 
46
46
  A material budget covers aggregate attempts rather than resetting per retry. Establish enough controller/target capacity, timeout/attempt limits, owned temporary outputs, cleanup, and stop thresholds to prevent uncontrolled work. Do not free capacity by pruning unowned, global, persistent, or shared resources.
47
47
 
48
+ ### Material Resource Lifecycle
49
+
50
+ Build, package, verification, and rehearsed candidate actions can create or enlarge producer caches, generated output, temporary candidates, and release artifacts beyond the selected environment's runtime. A successful command exit and an empty runtime inventory do not prove the material postcondition.
51
+
52
+ > Before running any selected action that may create or enlarge material resources, inspect the action and its material project-native children to identify every generated output, cache, runtime, service, artifact, candidate, persistent dependency, shared resource, and indirect producer effect. For each result, determine from current evidence whether it is a required deliverable, a useful and bounded reusable result, a persistent or shared resource outside cleanup ownership, or an exact project-owned temporary, failed, superseded, duplicate, or obsolete result. Reuse valid outputs and treat all retries and repairs as one operation so repeated execution does not accumulate retained copies. After success, failure, cancellation, timeout, or interruption, re-observe actual state, remove every safely owned result that should not remain, preserve persistent, shared, and unproven resources, and verify the complete residual state across all resource classes. Never infer complete cleanup from one empty runtime inventory, never use broad cleanup to manufacture capacity, and never report success while an unintended or unbounded material residual remains.
53
+
48
54
  Do not run a material producer when current project-native evidence already covers the same source/release, toolchain, target assumptions, and required scope. Run the least expensive missing producer at most once for that binding. A changed binding starts a newly observed current→desired decision; it does not justify automatic repeated full rings.
49
55
 
50
56
  ## SSH Execution Boundary
@@ -62,6 +62,12 @@ For each unchecked or explicitly repair-scoped task, in plan order:
62
62
  6. Stop dependent tasks on failure; run `[P]` tasks in parallel only when safe.
63
63
  7. Execute focused implementation verification appropriate to the changed task; do not expand into a separate broad audit unrelated to implementation.
64
64
 
65
+ ### Focused Verification Material Residue
66
+
67
+ Focused verification may run build, package, or integration commands that create or enlarge material resources beyond the task-owned source files.
68
+
69
+ > Before running any selected action that may create or enlarge material resources, inspect the action and its material project-native children to identify every generated output, cache, runtime, service, artifact, candidate, persistent dependency, shared resource, and indirect producer effect. For each result, determine from current evidence whether it is a required deliverable, a useful and bounded reusable result, a persistent or shared resource outside cleanup ownership, or an exact project-owned temporary, failed, superseded, duplicate, or obsolete result. Reuse valid outputs and treat all retries and repairs as one operation so repeated execution does not accumulate retained copies. After success, failure, cancellation, timeout, or interruption, re-observe actual state, remove every safely owned result that should not remain, preserve persistent, shared, and unproven resources, and verify the complete residual state across all resource classes. Never infer complete cleanup from one empty runtime inventory, never use broad cleanup to manufacture capacity, and never report success while an unintended or unbounded material residual remains.
70
+
65
71
  ### Repair Scope
66
72
 
67
73
  When the caller requests repair, require an explicit `repair_scope` and concrete findings:
@@ -185,6 +185,12 @@ Use at most three execution-failure repair rounds. One round is reproduce → es
185
185
 
186
186
  Never retry until green or weaken scope/assertions to manufacture a pass.
187
187
 
188
+ ## Material Resource Lifecycle
189
+
190
+ Test execution, repair, and final regression can create or enlarge material resources beyond the source tree: generated build output, container images, compiler and package caches, temporary runtimes, isolated services, databases, coverage artifacts, and failed candidates. A green native command and an empty process inventory do not prove the material postcondition.
191
+
192
+ > Before running any selected action that may create or enlarge material resources, inspect the action and its material project-native children to identify every generated output, cache, runtime, service, artifact, candidate, persistent dependency, shared resource, and indirect producer effect. For each result, determine from current evidence whether it is a required deliverable, a useful and bounded reusable result, a persistent or shared resource outside cleanup ownership, or an exact project-owned temporary, failed, superseded, duplicate, or obsolete result. Reuse valid outputs and treat all retries and repairs as one operation so repeated execution does not accumulate retained copies. After success, failure, cancellation, timeout, or interruption, re-observe actual state, remove every safely owned result that should not remain, preserve persistent, shared, and unproven resources, and verify the complete residual state across all resource classes. Never infer complete cleanup from one empty runtime inventory, never use broad cleanup to manufacture capacity, and never report success while an unintended or unbounded material residual remains.
193
+
188
194
  ## Production Repair Boundary
189
195
 
190
196
  A repair may close inside this Skill only when evidence establishes that it is limited to private/internal implementation, a behavior-preserving algorithm correction, test infrastructure, a behavior-preserving testability seam, or local error handling with unchanged public obligations.
@@ -295,6 +301,7 @@ Before writing `TEST_PASS`:
295
301
  7. No accepted correction, unresolved finding, automated-verdict scope edge, missing required fidelity/composition proof, or required environment check remains.
296
302
  8. Every `manual-external-nonblocking` item is authoritatively classified, visibly unproven, and separate from release/deployment authorization.
297
303
  9. No high-risk production defect or correction remains, and no mutation occurred after final review and execution.
304
+ 10. The material-resource postcondition is verified across all resource classes: every safely owned temporary, failed, superseded, duplicate, or obsolete result is removed, retained deliverables and bounded reusable caches are justified, and no unintended or unbounded residual remains.
298
305
 
299
306
  ## Terminal Results
300
307
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "prizmkit",
3
- "version": "1.1.177",
3
+ "version": "1.1.178",
4
4
  "description": "Create a new PrizmKit-powered project with clean initialization — no framework dev files, just what you need.",
5
5
  "type": "module",
6
6
  "bin": {