clawdi 0.14.80 → 0.14.82
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/dist/index.js +298 -298
- package/package.json +1 -1
- package/skills/clawdi/SKILL.md +6 -1
- package/skills/hosted-versions/1/clawdi/SKILL.md +6 -1
package/package.json
CHANGED
package/skills/clawdi/SKILL.md
CHANGED
|
@@ -137,7 +137,12 @@ when the user authorized updating them; do not delete them first. Existing Vault
|
|
|
137
137
|
remain unchanged until successful submission and are never shown or prefilled. Overlapping pending requests
|
|
138
138
|
are rejected; a change to any requested field conflicts with the entire batch.
|
|
139
139
|
Show the returned `url` unchanged to the user; do not ask them to paste secrets into chat.
|
|
140
|
-
Opening the link does not consume it.
|
|
140
|
+
Opening the link does not consume it. The user can add fields or import a pasted/uploaded
|
|
141
|
+
.env on the page, preview replacements, and apply them to the same form. Original requested
|
|
142
|
+
names remain mandatory; only the user chooses extras after link creation (32 fields total).
|
|
143
|
+
Saving the entire form consumes the link once. Selected fields must still match creation
|
|
144
|
+
state, and extras cannot overlap another pending request. Status includes saved extras and
|
|
145
|
+
their exact references; never assume only the originally requested names were saved.
|
|
141
146
|
|
|
142
147
|
Check `vault_request_status` with its `request_id` after the user finishes. `pending` is not
|
|
143
148
|
a secret value; `supplied` means the exact references are ready. On `expired` or `conflict`,
|
|
@@ -122,7 +122,12 @@ when the user authorized updating them; do not delete them first. Existing Vault
|
|
|
122
122
|
remain unchanged until successful submission and are never shown or prefilled. Overlapping pending requests
|
|
123
123
|
are rejected; a change to any requested field conflicts with the entire batch.
|
|
124
124
|
Show the returned `url` unchanged to the user; do not ask them to paste secrets into chat.
|
|
125
|
-
Opening the link does not consume it.
|
|
125
|
+
Opening the link does not consume it. The user can add fields or import a pasted/uploaded
|
|
126
|
+
.env on the page, preview replacements, and apply them to the same form. Original requested
|
|
127
|
+
names remain mandatory; only the user chooses extras after link creation (32 fields total).
|
|
128
|
+
Saving the entire form consumes the link once. Selected fields must still match creation
|
|
129
|
+
state, and extras cannot overlap another pending request. Status includes saved extras and
|
|
130
|
+
their exact references; never assume only the originally requested names were saved.
|
|
126
131
|
|
|
127
132
|
Check `vault_request_status` with its `request_id` after the user finishes. `pending` is not
|
|
128
133
|
a secret value; `supplied` means the exact references are ready. On `expired` or `conflict`,
|