prizmkit 1.1.170 → 1.1.171

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.170",
3
- "bundledAt": "2026-08-05T18:03:01.414Z",
4
- "bundledFrom": "e849c27"
2
+ "frameworkVersion": "1.1.171",
3
+ "bundledAt": "2026-08-06T15:22:17.562Z",
4
+ "bundledFrom": "c90abca"
5
5
  }
@@ -1,5 +1,5 @@
1
1
  {
2
- "version": "1.1.170",
2
+ "version": "1.1.171",
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.",
@@ -44,7 +44,8 @@ AI-driven, context-aware. Read the existing `### Infrastructure` → `#### Deplo
44
44
  3. **AI-assisted deployment**:
45
45
  - Whether AI should help execute deploy commands (via SaaS CLI like `vercel deploy`, `fly deploy`, `railway up`, `docker push`, or SSH remote commands)
46
46
  - If yes: collect necessary info — API token storage method (env var name, e.g., `VERCEL_TOKEN`), project name/ID on the platform, target environment (production / staging)
47
- - Explicitly inform: "AI will show each command and wait for your confirmation before executing"
47
+ - Capture any explicit interaction preference without imposing one: quick/no-confirm deployment, preview-first deployment, or follow the current request
48
+ - Explicitly inform: "AI-assisted deployment follows the user's stated intent. A quick or no-confirm request collects only indispensable missing facts and continues through verified completion; a preview-first request stops after the plan. Explicit no-backup intent suppresses new backups for that operation. The deployment capability asks only when one exact user action remains unavoidable."
48
49
  4. **Environment variable management**: production env var strategy (SaaS platform dashboard / `.env.production` committed to repo / secret manager like AWS Secrets Manager, Vault / CI/CD secrets)
49
50
 
50
51
  Use `AskUserQuestion` for each batch. Each question MUST include a "Skip — decide later" option.
@@ -89,6 +90,7 @@ After infrastructure inquiry, update the `### Infrastructure` section in the pro
89
90
  #### Deployment
90
91
  - **Target**: [platform/method]
91
92
  - **AI-assisted deploy**: [yes/no]
93
+ - **Deployment interaction**: [explicit standing preference, or "follow the current deployment request"]
92
94
  - **Domain**: [domain or "not configured"]
93
95
  - **SSL**: [management method]
94
96
  - **CI/CD**: [tool or "not configured"]
@@ -1,6 +1,6 @@
1
1
  ---
2
2
  name: "prizmkit-deploy"
3
- description: "Deploy the latest allowed release to local, remote, test, production, or custom targets through a one-click Profile-based convergence loop, and handle status, health, logs, restart, rollback, takeover, and resume. Use this skill whenever the user asks to deploy, redeploy, publish a release, inspect or recover a deployment, promote an artifact, configure post-deploy CI/CD, or replace repeated local deployment with watch/hot reload. Explicit deploy invocation authorizes ordinary project-owned deployment actions; only identity, target ambiguity, irreversible data, and shared or unknown-ownership boundaries pause for the user. (project)"
3
+ description: "Deploy the latest allowed release to local, remote, test, production, or custom targets through an intent-first one-click Profile convergence loop, and handle status, health, logs, restart, rollback, takeover, and resume. Use this skill whenever the user asks to deploy, redeploy, ship quickly or without confirmation, publish a release, inspect or recover a deployment, promote an artifact, configure post-deploy CI/CD, or replace repeated local deployment with watch/hot reload. Explicit deploy invocation authorizes ordinary project-owned deployment actions; collect only indispensable missing information and continue through verification to a terminal result. Respect explicit no-confirmation and no-backup intent for the selected operation; unresolved identity, target, unbounded effects, and shared or unknown ownership remain real information boundaries. (project)"
4
4
  ---
5
5
 
6
6
  # PrizmKit Deploy — C-Lite AutoDeploy Gateway
@@ -30,12 +30,16 @@ Do not use it for unrelated application implementation, general server administr
30
30
 
31
31
  Explicit deploy invocation authorizes the standard deployment envelope: project reads, build/package, project-declared dependency resolution, non-destructive native migration, candidate creation, start/restart, live handoff, minimum verification, bounded retry, exact old-release retirement, failed-candidate/temporary-resource cleanup, and the selected Profile record update.
32
32
 
33
- Do not ask for a second complete-plan confirmation for those standard actions. Before returning `WAITING_USER`, exhaust bounded read-only discovery, unambiguous target resolution, and already configured non-interactive authentication. Pause only when no safe automatic continuation remains and the next action requires:
33
+ User intent controls optional confirmation and backup policy for the selected operation. For quick deployment, no-confirmation intent, or equivalent wording, collect only information indispensable to identify the target, authenticate, bind the release, or resolve an otherwise unknowable effect. Continue bounded discovery, execution, repair, recovery, and verification until a terminal outcome. Keep progress updates concise and non-blocking, then notify the user of the final verified result.
34
+
35
+ An explicit no-confirmation instruction satisfies any confirmation or effect decision already identified within the user's established authority; do not ask again. An explicit no-backup instruction creates no new data backup, snapshot, or retained application rollback copy for this operation. Preserve current live only until the desired candidate is proven, then retire exact superseded runtime after handoff. Leave unrelated pre-existing backups untouched unless the user explicitly requests their deletion. These instructions do not invent missing facts, make unknown effects bounded, bypass target identity, or establish ownership the user has not demonstrated.
36
+
37
+ Do not ask for a second complete-plan confirmation for standard actions. Before returning `WAITING_USER`, exhaust bounded read-only discovery, unambiguous target resolution, configured non-interactive authentication, and every safe bounded forward action. Pause only when no safe automatic continuation remains and the next action requires:
34
38
 
35
39
  1. an identity or authentication action only the user can complete after established credentials have been tried;
36
40
  2. a target choice that remains absent, conflicting, or ambiguous after current evidence is inspected;
37
- 3. an irreversible or insufficiently bounded data effect;
38
- 4. a shared or unknown-ownership resource decision.
41
+ 3. an irreversible data effect not already accepted for this exact target and action, or a data effect that remains insufficiently bounded;
42
+ 4. a shared or unknown-ownership resource decision not already resolved within the user's established authority.
39
43
 
40
44
  A missing Profile record, ordinary first deployment, selected-target SSH connection, known bounded downtime, material work inside the standard envelope, or missing rollback mechanism does not create a confirmation. Disclose relevant effects while continuing. Privileged or global work outside the Profile's already established target boundary is an authorization/ownership decision and pauses before execution.
41
45
 
@@ -128,11 +132,11 @@ Terminal status is exactly one of:
128
132
  SUCCEEDED, WAITING_USER, FAILED
129
133
  ```
130
134
 
131
- `WAITING_USER` is resumable and names one exact non-sensitive action. Use `FAILED` only when no safe continuation exists or the user stops the operation.
135
+ `WAITING_USER` is resumable and contains exactly one non-sensitive `next_actions` entry matching `recovery.pending_action.action`. Never return multiple user actions. Use `FAILED` only when no safe continuation exists or the user stops the operation.
132
136
 
133
137
  ### 6. Offer Automation
134
138
 
135
- After deployment has already reached `SUCCEEDED`, detect existing project-native automation and classify the controller/target boundary from observed evidence rather than the Profile ID or environment label. If no automation exists, ask whether the user wants to avoid future full manual deployment runs:
139
+ After deployment has already reached `SUCCEEDED`, detect existing project-native automation and classify the controller/target boundary from observed evidence rather than the Profile ID or environment label. If no automation exists and the user did not request quick or no-confirmation deployment, ask whether the user wants to avoid future full manual deployment runs:
136
140
 
137
141
  - for a remote Profile backed by a GitHub repository, offer a GitHub Actions CI/CD setup with project-appropriate push, tag/release, or manual trigger policy;
138
142
  - for another remote repository, offer only an equivalent supported by current project/host evidence;
@@ -140,6 +144,8 @@ After deployment has already reached `SUCCEEDED`, detect existing project-native
140
144
 
141
145
  Automation setup is optional and separate from the completed deployment. A decline or setup failure does not change `SUCCEEDED`. Do not create a PrizmKit automation-state file; detect automation from project-native workflow/config evidence. Credentials remain in the repository host or target Secret system.
142
146
 
147
+ For quick or no-confirmation deployment, do not turn automation into another question. Include at most one non-blocking automation note in the terminal success result, or omit it when it does not help the requested outcome.
148
+
143
149
  ## Output
144
150
 
145
151
  Report:
@@ -49,7 +49,7 @@ Every selected automatic or human action contains only these base facts:
49
49
 
50
50
  Keep executable and arguments separate where possible. Use project-relative working directories and inject Secret material through user- or target-owned systems. Never interpolate an untrusted value into an opaque shell command.
51
51
 
52
- An action is automatic when current evidence proves its executable shape, target, effects, ownership, bounded resource behavior, and verification inside the standard deployment envelope. Before creating a Human Checkpoint, perform bounded read-only discovery, resolve any single evidence-backed target, and try established non-interactive authentication. Only when a person must still authenticate, choose among unresolved targets, decide an irreversible data effect, or resolve shared ownership, represent one exact human action and expected postcondition. When no safe action can be established, report the missing evidence or unsupported capability instead of fabricating a command.
52
+ An action is automatic when current evidence proves its executable shape, target, effects, ownership, bounded resource behavior, and verification inside the standard deployment envelope. Treat an explicit user decision for one fully identified action and effect, including no-confirmation or no-backup intent, as a resolved Gate decision within the user's established authority; do not convert it into another Human Checkpoint. Before creating a Human Checkpoint, perform bounded read-only discovery, resolve any single evidence-backed target, and try established non-interactive authentication. Only when a person must still authenticate, choose among unresolved targets, decide an irreversible or insufficiently bounded data effect not already accepted for the exact action, or resolve shared ownership, represent one exact human action and expected postcondition. Missing facts, unresolved identity, unbounded impact, and unproven ownership remain information boundaries because user intent cannot make them known. When no safe action can be established, report the missing evidence or unsupported capability instead of fabricating a command.
53
53
 
54
54
  Evidence derivation basis such as maintained recipe or current dynamic derivation is internal provenance, not a user-visible deployment status and not a risk classification.
55
55
 
@@ -343,7 +343,7 @@
343
343
  },
344
344
  "next_actions": {
345
345
  "type": "array",
346
- "maxItems": 20,
346
+ "maxItems": 1,
347
347
  "items": {
348
348
  "type": "string",
349
349
  "minLength": 1,
@@ -352,6 +352,26 @@
352
352
  }
353
353
  },
354
354
  "allOf": [
355
+ {
356
+ "if": {
357
+ "properties": {
358
+ "status": {
359
+ "const": "WAITING_USER"
360
+ }
361
+ },
362
+ "required": [
363
+ "status"
364
+ ]
365
+ },
366
+ "then": {
367
+ "properties": {
368
+ "next_actions": {
369
+ "minItems": 1,
370
+ "maxItems": 1
371
+ }
372
+ }
373
+ }
374
+ },
355
375
  {
356
376
  "if": {
357
377
  "properties": {
@@ -8,16 +8,26 @@ An explicit deploy invocation authorizes the selected Profile's standard deploym
8
8
 
9
9
  `deploy plan` is read-only. It reports the selected Profile, observed current state, latest allowed desired release, expected actions, downtime/data/rollback/resource/cleanup effects, verification, and optional automation opportunity without performing writes.
10
10
 
11
- The standard envelope covers project-owned, bounded actions needed to build/package, resolve project-declared dependencies, apply non-destructive native migrations, create a candidate, start/restart, hand off live traffic, verify, retain bounded rollback, retire exact old runtime resources, clean failed/temporary resources, and update the selected Profile record.
11
+ The standard envelope covers project-owned, bounded actions needed to build/package, resolve project-declared dependencies, apply non-destructive native migrations, create a candidate, start/restart, hand off live traffic, verify, retain bounded rollback when not explicitly declined, retire exact old runtime resources, clean failed/temporary resources, and update the selected Profile record.
12
12
 
13
13
  For a selected directly managed remote machine, connecting and running bounded project-scoped actions through the established SSH destination are part of that standard envelope. Do not ask for another confirmation merely because the next executable is `ssh`; use established non-interactive credentials first. A missing Profile record or ordinary first deployment also does not create a checkpoint when one non-conflicting target resolves from current evidence.
14
14
 
15
- Exhaust bounded automatic discovery, target resolution, and configured non-interactive authentication before pausing with one exact `WAITING_USER` action. Pause only for:
15
+ ### User Intent and Fast Completion
16
+
17
+ Treat explicit user constraints as operation policy. A quick or no-confirmation deployment collects only indispensable missing facts and keeps progressing through bounded deployment, repair, recovery, and verification until a terminal result. Effects summaries and progress updates remain concise and non-blocking; they do not become approval gates.
18
+
19
+ An explicit no-confirmation instruction satisfies already-identified confirmation and effect decisions within the user's established authority. Do not ask the same decision again. The instruction does not supply a missing target or authentication fact, establish unknown ownership, or make an unknown or unbounded effect safe.
20
+
21
+ An explicit no-backup instruction overrides default rollback retention for this operation. Create no new data backup, snapshot, or retained application rollback release. Keep proven current live through candidate proof and handoff, then retire exact superseded application runtime. Leave unrelated pre-existing backups and snapshots untouched unless the user explicitly requests their deletion. For a fully identified, bounded data action, no-backup intent records acceptance of the disclosed no-backup consequence and resolves that Data Gate decision without another question.
22
+
23
+ If a project-native tool or enforced target policy makes no-backup execution impossible, do not silently create a backup. Return exactly one `WAITING_USER` action naming the single conflict that must be resolved. Unknown or insufficiently bounded data effects remain unresolved because no-backup intent cannot supply missing effect evidence.
24
+
25
+ Exhaust bounded automatic discovery, target resolution, configured non-interactive authentication, and every safe bounded forward action before pausing with one exact `WAITING_USER` action. Pause only for:
16
26
 
17
27
  1. an identity or authentication action that only the user can complete after established methods have been attempted;
18
28
  2. a target choice still absent, ambiguous, or conflicting after current evidence is inspected;
19
- 3. an irreversible data effect or data impact that cannot be bounded safely;
20
- 4. a shared or unknown-ownership resource decision.
29
+ 3. an irreversible data effect not already accepted for the exact target and action, or data impact that cannot be bounded safely;
30
+ 4. a shared or unknown-ownership resource decision not already resolved within the user's established authority.
21
31
 
22
32
  Known bounded downtime, material work inside the standard envelope, and missing reliable rollback are disclosed while execution continues; they do not create another approval. Privileged/global work not already established by the selected target boundary is treated as an authorization or shared-ownership decision rather than silently executed.
23
33
 
@@ -70,7 +80,7 @@ Prefer an evidence-supported candidate/handoff transition:
70
80
  3. run candidate pre-handoff checks;
71
81
  4. switch the supported live/traffic selector;
72
82
  5. verify desired through the actual live path;
73
- 6. retain the Profile's bounded rollback set; when neither project-native nor Profile policy defines one, retain one verified previous release if the target supports it, otherwise disclose rollback absence and continue without another confirmation;
83
+ 6. unless the user explicitly requested no backup or rollback retention, retain the Profile's bounded rollback set; when neither project-native nor Profile policy defines one, retain one verified previous release if the target supports it, otherwise disclose rollback absence and continue without another confirmation;
74
84
  7. retire exact superseded, failed, temporary, and orphaned runtime resources;
75
85
  8. observe the converged inventory.
76
86
 
@@ -84,7 +94,7 @@ Persistent data, shared infrastructure, and unproven resources are never classif
84
94
 
85
95
  Use project-native locked dependency mechanisms and actual installed capability. Project-local or target-local declared resolution within the selected deployment is standard. Never silently install or replace a privileged/global dependency, guess a wildcard version, or transfer a controller dependency directory whose target compatibility is unproven.
86
96
 
87
- For a data-affecting action, establish migration identity, old/new compatibility, locks/downtime, irreversible transformations, backup/restore evidence when required, traffic sequencing, post-migration verification, and unknown-outcome inspection. Non-destructive native migration can remain in the standard envelope. Irreversible or insufficiently bounded impact pauses for one data decision.
97
+ For a data-affecting action, establish migration identity, old/new compatibility, locks/downtime, irreversible transformations, backup/restore evidence when required and not explicitly declined, traffic sequencing, post-migration verification, and unknown-outcome inspection. Non-destructive native migration can remain in the standard envelope. A user who explicitly accepts one fully identified, bounded irreversible action without backup has resolved that action's Data Gate; proceed without another confirmation and report the no-backup consequence in the terminal result. Insufficiently bounded impact still pauses for one data decision.
88
98
 
89
99
  Do not treat a routing, certificate, firewall, load-balancer, domain, shared network/storage/database, or shared runtime change as project-owned until current evidence proves ownership and consumers. Shared or unknown ownership pauses before mutation.
90
100
 
@@ -116,7 +126,7 @@ Bound logs by source, purpose, time and/or line count. Prefer omission when reli
116
126
 
117
127
  ## Post-Success Automation
118
128
 
119
- Offer automation only after deployment has already reached `SUCCEEDED` and only when project-native evidence shows no suitable automation exists. The offer is a separate optional project-file change, not a condition of deployment success.
129
+ Offer automation only after deployment has already reached `SUCCEEDED` and only when project-native evidence shows no suitable automation exists. The offer is a separate optional project-file change, not a condition of deployment success. For quick or no-confirmation deployment, do not ask another question; include at most one non-blocking automation note in the terminal result or omit it.
120
130
 
121
131
  ### Remote Profile
122
132
 
@@ -98,6 +98,8 @@ Load only the selected Profile record's current, latest result, minimal recovery
98
98
 
99
99
  Resume from the first unproven current→desired action. Do not reconstruct commands from history summaries. When observed identity/effects differ, discard the stale proposed action and derive the next action from current evidence. If another operation already targets the same Profile/desired release, attach to it rather than creating a candidate.
100
100
 
101
+ For quick or no-confirmation deployment, continue every safe bounded forward action without waiting for progress approval. Keep intermediate updates concise and non-blocking, and notify the user after terminal verification. A missing indispensable fact may still produce `WAITING_USER`, but it contains exactly one action rather than a list of alternatives.
102
+
101
103
  A human “done” response is a signal to revalidate the pending postcondition, not proof. Clear recovery only after `SUCCEEDED` or a non-resumable `FAILED` result is recorded.
102
104
 
103
105
  ## Terminal Decision
@@ -107,7 +109,7 @@ Return exactly one status:
107
109
  | Status | Condition |
108
110
  |---|---|
109
111
  | `SUCCEEDED` | Desired release is live when deployment applies, all required observations pass, required inventory converges, and no effect needed for correctness remains unknown. |
110
- | `WAITING_USER` | One identity, target, irreversible-data, shared/ownership, source-fix, or indeterminate-outcome action can resume the same desired operation. |
112
+ | `WAITING_USER` | Exactly one identity, target, unresolved data-effect, shared/ownership, source-fix, or indeterminate-outcome action can resume the same desired operation. |
111
113
  | `FAILED` | No safe continuation exists, the desired release is unsupported/unrecoverable within scope, or the user stopped the operation. |
112
114
 
113
115
  A release may be live while a Profile record update failed; state both facts. A healthy old release, completed rollback, or partially live candidate never converts an incomplete desired deployment to `SUCCEEDED`.
@@ -121,7 +123,7 @@ Return and, when valid, persist one concise result containing:
121
123
  - desired and actual live release;
122
124
  - each selected verification observation with required/status/evidence;
123
125
  - bounded residual resources and rollback availability;
124
- - one exact pending action for `WAITING_USER` or evidence-backed reason for `FAILED`;
126
+ - exactly one `next_actions` entry for `WAITING_USER`, identical to `recovery.pending_action.action`, or one evidence-backed reason for `FAILED`;
125
127
  - Profile record update outcome in the conversation summary.
126
128
 
127
129
  Do not persist unrelated conversation, confirmation transcripts, raw diagnostics, credentials, or full logs. Secret values and credential-bearing URLs/headers/environment assignments are omitted before display or storage.
@@ -510,7 +510,17 @@ def _check_result(value: Any, path: str, errors: ErrorCollector) -> None:
510
510
  if isinstance(verification, list) and not names:
511
511
  errors.add("EMPTY_VERIFICATION", f"{path}.verification")
512
512
 
513
- if value.get("status") != "SUCCEEDED":
513
+ status = value.get("status")
514
+ next_actions = value.get("next_actions")
515
+ if status == "WAITING_USER" and (
516
+ not isinstance(next_actions, list) or len(next_actions) != 1
517
+ ):
518
+ errors.add(
519
+ "WAITING_USER_EXACTLY_ONE_NEXT_ACTION",
520
+ f"{path}.next_actions",
521
+ )
522
+
523
+ if status != "SUCCEEDED":
514
524
  return
515
525
  for index, item in _iter_list(verification):
516
526
  if (
@@ -559,6 +569,22 @@ def _validate_record(data: Any, errors: ErrorCollector) -> None:
559
569
  "RECOVERY_DESIRED_RELEASE_MISMATCH",
560
570
  "$.recovery.desired_release",
561
571
  )
572
+ next_actions = latest.get("next_actions")
573
+ pending_action = recovery.get("pending_action")
574
+ pending_text = (
575
+ pending_action.get("action")
576
+ if isinstance(pending_action, Mapping)
577
+ else None
578
+ )
579
+ if (
580
+ isinstance(next_actions, list)
581
+ and len(next_actions) == 1
582
+ and next_actions[0] != pending_text
583
+ ):
584
+ errors.add(
585
+ "WAITING_USER_ACTION_MISMATCH",
586
+ "$.recovery.pending_action.action",
587
+ )
562
588
 
563
589
  current = data.get("current")
564
590
  if (
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "prizmkit",
3
- "version": "1.1.170",
3
+ "version": "1.1.171",
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": {