prizmkit 1.1.173 → 1.1.174

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.173",
3
- "bundledAt": "2026-08-07T01:16:27.513Z",
4
- "bundledFrom": "1f3263d"
2
+ "frameworkVersion": "1.1.174",
3
+ "bundledAt": "2026-08-08T02:37:10.579Z",
4
+ "bundledFrom": "b12b5d8"
5
5
  }
@@ -1,5 +1,5 @@
1
1
  {
2
- "version": "1.1.173",
2
+ "version": "1.1.174",
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.",
@@ -20,6 +20,8 @@ Use this Skill for:
20
20
 
21
21
  Do not use it for unrelated application implementation, general server administration, or resources outside the selected environment and its necessary deployment dependencies. If the user says only “ship it” without explicitly invoking this Skill, clarify commit versus deploy; explicit invocation means deploy.
22
22
 
23
+ Deployment verification is Release-and-target convergence, not a generic software-development lifecycle. A caller cannot add hidden planning, review, commit, or exhaustive unit/integration/contract/browser test prerequisites. Run only checks required by the selected project-native deployment/preflight controller or by target-appropriate deployment verification, unless the user separately requests broader development work. A selected immutable worktree Release does not require creating a Git commit.
24
+
23
25
  ## Invocation and Authority
24
26
 
25
27
  ```text
@@ -36,6 +38,8 @@ User intent controls optional confirmation and backup policy for the selected op
36
38
 
37
39
  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, choose whether uncommitted code is deployed, make unknown effects bounded, bypass target identity, or establish ownership the user has not demonstrated.
38
40
 
41
+ Explicit permission to use local SSH credentials authorizes target-scoped use of configured SSH aliases, agent identities, and key files through the installed `ssh` executable. Do not ask whether to use them again. Let SSH consume the credential; do not read, copy, print, upload, or request the private-key value. This permission does not identify a missing destination, accept an unverified or changed host key, or authorize unrelated hosts.
42
+
39
43
  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:
40
44
 
41
45
  1. a release-source choice because tracked or untracked worktree changes exist;
@@ -46,6 +50,8 @@ Do not ask for a second complete-plan confirmation for standard actions. Before
46
50
 
47
51
  A missing Profile record, ordinary first deployment, selected-target 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 selected environment's established target boundary is an authorization/ownership decision and pauses before execution.
48
52
 
53
+ When SSH still cannot connect after bounded target-scoped discovery and use of authorized local credentials, diagnose the observed failure class before pausing. Report why connection failed, which non-sensitive binding was attempted, and exactly which destination, username, port, proxy/VPN, trusted host-key fingerprint, public-key registration, network rule, SSH service, or remote permission fact must change for future automatic access. Return one connection-enablement action, then retry and perform the server work yourself. Never ask the user to log into the server and run deployment commands on this Skill's behalf.
54
+
49
55
  ## Managed Artifacts
50
56
 
51
57
  Prefer project-native deployment configuration. PrizmKit owns only:
@@ -81,6 +87,8 @@ Read `${SKILL_DIR}/references/fast-path-selection.md` after resolving the operat
81
87
 
82
88
  Products and tools are evidence examples, not protocol identifiers. Existing project-native coordination decides whether multiple units deploy together or independently.
83
89
 
90
+ A cloud server, virtual machine, or directly managed host remains a direct remote-runtime target when project evidence establishes shell access. On that path, use the installed `ssh` executable as the default connection transport. A provider dashboard does not reclassify the machine as repository-hosted deployment. Do not use browser automation or a web terminal as a substitute for SSH to transfer a Release, execute deployment commands, or inspect runtime state. Browser automation is eligible only for an exact authoritative control-plane operation when no project-native command, API, CLI, or SSH path can perform that operation; it never bypasses identity or authentication boundaries.
91
+
84
92
  ## AutoDeploy Workflow
85
93
 
86
94
  ### 1. Resolve Unit and Environment
@@ -166,6 +174,7 @@ Report:
166
174
 
167
175
  - terminal status and operation;
168
176
  - selected environment and target reference, plus the internal Profile record result when one exists;
177
+ - for failed SSH access, the observed failure class, attempted non-sensitive binding, exact missing connection fact or durable server/cloud configuration change, and one retry action;
169
178
  - desired and actual live release;
170
179
  - concise verification observations and residual resources;
171
180
  - rollback availability without treating it as required approval;
@@ -31,7 +31,7 @@ A maintained recipe is reusable only while its project, tool, target, artifact,
31
31
 
32
32
  Select concrete controller guidance through `${SKILL_DIR}/references/fast-path-selection.md` and its matching playbook before deriving a material action. The playbook supplies observed command knowledge; this contract still owns semantic action fields, evidence, effects, Gates, and verification.
33
33
 
34
- For a direct remote target, load `${SKILL_DIR}/references/playbook-remote-runtime.md`. A remote playbook cannot bypass target identity, host-key, authentication, ownership, or unknown-outcome boundaries.
34
+ For a direct remote target, load `${SKILL_DIR}/references/playbook-remote-runtime.md`. When that target exposes shell access, the installed `ssh` executable is the default implementation of semantic `connect`; a browser dashboard or web terminal is not an equivalent transport. Explicit permission to use local SSH credentials resolves the credential-use decision: allow SSH to use the selected target's configured alias, agent, and key files without another question, while never reading or exposing private-key material. Browser automation is considered only for an exact authoritative control-plane operation with no supported project-native command, API, CLI, or SSH path. An SSH authentication failure does not authorize a silent transport change. A remote playbook cannot bypass target identity, host-key, authentication, ownership, or unknown-outcome boundaries.
35
35
 
36
36
  ## Base Action Contract
37
37
 
@@ -56,7 +56,7 @@ Before creating a Human Checkpoint:
56
56
  3. try established non-interactive authentication;
57
57
  4. honor an explicit decision already made for the exact identified effect.
58
58
 
59
- Return one human action only when identity, target, irreversible or unbounded data effect, or shared ownership still requires a person. Missing facts 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.
59
+ Return one human action only when identity, target, irreversible or unbounded data effect, or shared ownership still requires a person. For failed SSH access, classify the observed resolver, network, host-key, authentication, service, or remote-authorization failure and request only the missing durable connection fact or configuration change; never delegate the deployment commands to the user. Missing facts 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.
60
60
 
61
61
  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.
62
62
 
@@ -28,6 +28,12 @@ Select the smallest authoritative controller in this order:
28
28
 
29
29
  The presence of several configuration files does not mean every controller should run. Resolve conflicts through current live state and one bounded read-only observation.
30
30
 
31
+ ## Connection Transport Precedence
32
+
33
+ Controller selection and connection transport are separate decisions. A project-native controller may remain authoritative when it internally owns transport. Otherwise, when a directly managed machine exposes or is configured for shell access, use the installed `ssh` executable and the verified SSH binding as the default transport for observation, transfer, execution, and verification. When the user authorizes local SSH credentials, resolve only the selected target's alias/configuration and let SSH try its configured agent and key files without another permission question; do not enumerate unrelated hosts or reveal key material.
34
+
35
+ A cloud provider dashboard does not make a server a repository-hosted deployment target. Browser automation—for example, a browser-driving test tool—is a last-resort control-plane adapter, not a remote-shell transport. Use it only when the exact authoritative operation has no supported project-native command, API, CLI, or SSH path. Never type deployment commands into a web terminal or upload a Release through a dashboard when an SSH binding exists or can be established. If SSH reaches a user-only authentication boundary, diagnose it and return one exact durable connection-enablement action instead of silently switching to a browser console or asking the user to execute the deployment remotely.
36
+
31
37
  ## Conditional Playbook Loading
32
38
 
33
39
  - project-native controller → `playbook-project-native.md`
@@ -4,9 +4,37 @@ Use this playbook when the selected environment is a directly managed remote mac
4
4
 
5
5
  ## Connection
6
6
 
7
- Use the installed `ssh` executable as the default implementation of semantic `connect` when the target exposes shell access. Derive the destination from an explicit target, project evidence, or an observed/user-supplied SSH config alias. Reuse its user, port, proxy, agent/key, and host-verification settings.
7
+ Use the installed `ssh` executable as the default implementation of semantic `connect` when the target exposes shell access. This includes a cloud server, virtual machine, or directly managed host even when its provider also offers a dashboard. Derive the destination from an explicit target, project evidence, or an observed/user-supplied SSH config alias. Reuse its user, port, proxy, agent/key, and host-verification settings.
8
8
 
9
- Attempt one bounded non-interactive probe before requesting authentication. Do not guess host, user, port, key path, bastion, or fingerprint, and do not bypass host-key verification. Use a project-native controller instead when the target exposes no shell or defines another authoritative path.
9
+ A provider dashboard or browser-accessible terminal does not outrank SSH. Do not use browser automation to type into a web shell, upload the application, execute deployment commands, or inspect ordinary runtime state when the verified SSH binding can perform the operation. Browser automation—for example, a Playwright-driven dashboard—is eligible only for an exact provider control-plane operation that has no supported project-native command, API, CLI, or SSH path.
10
+
11
+ ### Authorized Local Credential Path
12
+
13
+ When the user authorizes local SSH credential use, proceed without another key-use question:
14
+
15
+ 1. Resolve only the selected destination's effective configuration with the installed SSH client, such as `ssh -G <verified-destination>`; do not enumerate unrelated aliases.
16
+ 2. When relevant, inspect only public agent fingerprints through `ssh-add -l`. Let SSH use the configured agent and `IdentityFile` paths; never read, copy, print, or upload private-key contents.
17
+ 3. Attempt one bounded non-interactive probe through the resolved binding, equivalent to `ssh -o BatchMode=yes -o ConnectTimeout=<bounded-seconds> <verified-destination> true`. Preserve ordinary host-key checking and bounded diagnostics.
18
+ 4. Continue immediately through the same binding when the probe succeeds. Do not ask the user to confirm SSH again.
19
+
20
+ Do not guess host, user, port, key path, bastion, or fingerprint, and do not bypass host-key verification. Use a project-native controller instead when the target exposes no shell or defines another authoritative path.
21
+
22
+ ### Connection Failure Diagnosis
23
+
24
+ Diagnose a failed probe before returning `WAITING_USER`:
25
+
26
+ | Observed failure | Durable information or configuration needed |
27
+ |---|---|
28
+ | destination absent or name resolution failed | SSH alias or hostname/IP, login user, port, and any required proxy, bastion, VPN, or private-network route |
29
+ | timeout or no route | reachable address/network path and the cloud security-group or firewall inbound rule for the selected SSH port and trusted source |
30
+ | connection refused | correct SSH port plus an enabled/listening SSH service and non-rejecting host firewall |
31
+ | unknown or changed host key | trusted expected host-key fingerprint, or verified key-rotation evidence before updating local trust |
32
+ | no usable local identity or encrypted key unavailable | target-specific SSH `IdentityFile`/agent configuration or a locally unlocked agent identity; never request the private key or passphrase in chat |
33
+ | public-key authentication denied | correct login user and registration of the matching local public-key fingerprint in the account's authorized-key or cloud-managed SSH-key configuration, with public-key authentication enabled |
34
+ | connected user lacks project access | deploy username, project-owned remote directory, and the minimum durable file/runtime/supervisor permission or bounded privilege policy |
35
+ | target intentionally exposes no shell | the authoritative project-native API, CLI, or controller binding instead of browser-emulated shell access |
36
+
37
+ Return exactly one connection-enablement action containing only the applicable missing facts or configuration changes and the instruction to retry. Explain the observed failure safely, but do not ask the user to log into the server and run deployment commands; after access is enabled, this Skill reconnects and performs those operations itself. Do not switch to a browser console merely because SSH authentication or reachability failed.
10
38
 
11
39
  ## Build, Transfer, and Runtime
12
40
 
@@ -1,6 +1,6 @@
1
1
  # Repository-Hosted Deployment Playbook
2
2
 
3
- Use this playbook when an observed hosting control plane owns build, release, promotion, traffic, or runtime operations and the project contains matching native configuration or binding evidence.
3
+ Use this playbook when an observed hosting control plane owns build, release, promotion, traffic, or runtime operations and the project contains matching native configuration or binding evidence. A cloud server or virtual machine does not match merely because its provider has a web dashboard; when the project directly owns the machine and shell access is established, use the remote-runtime playbook and SSH.
4
4
 
5
5
  ## Discovery
6
6
 
@@ -10,7 +10,7 @@ An explicit deploy invocation authorizes the selected Profile's standard deploym
10
10
 
11
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
- 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.
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. Explicit permission to use local SSH credentials authorizes the installed SSH client to consume the selected target's configured alias, agent, and key files without another question, but never authorizes reading or exposing private-key values. 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
15
  ### User Intent and Fast Completion
16
16
 
@@ -51,7 +51,9 @@ Do not run a material producer when current project-native evidence already cove
51
51
 
52
52
  For each selected SSH action, preserve the verified destination, authentication identity, proxy path, host-key evidence, and project-owned working boundary used during discovery. Execute the smallest exact remote command needed for the current difference, with bounded connection/action time and output. Reuse one proven connection binding across observation, transfer, write, and verification instead of silently changing users or endpoints between steps.
53
53
 
54
- Do not pass Secret values in command arguments, print private-key material, start a broad remote inventory, or bypass host-key verification. Attempt one bounded non-interactive connection with the established SSH configuration before deciding authentication cannot complete; continue immediately when it succeeds. Only then return one exact `WAITING_USER` authentication action when user input is unavoidable. If the target key or destination differs from established evidence, treat it as an identity conflict rather than a transient retry. After a disconnect during a possible write, use the same verified SSH destination to inspect actual state before considering replay.
54
+ When local credential use is authorized, perform target-scoped discovery through the SSH client: resolve the selected destination's effective configuration, inspect available agent public-key fingerprints when relevant, and let SSH select its configured key files. Do not open private-key files to obtain their contents, enumerate unrelated host aliases or keys, or print local credential paths in the result.
55
+
56
+ Do not pass Secret values in command arguments, print private-key material, start a broad remote inventory, or bypass host-key verification. Attempt one bounded non-interactive connection with the established SSH configuration before deciding authentication cannot complete; continue immediately when it succeeds. If it fails, preserve bounded safe diagnostics and classify whether the cause is unresolved destination, name resolution, timeout/no route, connection refusal, host-key trust/conflict, unavailable local key/agent, public-key denial, SSH service policy, or connected-user authorization. Only then return one exact `WAITING_USER` connection-enablement action when user input is unavoidable. State the exact missing server fact or cloud/server configuration change needed for durable automatic access, then retry and perform the server work through SSH; never ask the user to log in and run deployment commands. If the target key or destination differs from established evidence, treat it as an identity conflict rather than a transient retry. After a disconnect during a possible write, use the same verified SSH destination to inspect actual state before considering replay.
55
57
 
56
58
  ## Current → Desired Loop
57
59
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "prizmkit",
3
- "version": "1.1.173",
3
+ "version": "1.1.174",
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": {