pi-robot-hand 0.3.0 → 0.3.2

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "pi-robot-hand",
-  "version": "0.3.0",
+  "version": "0.3.2",
   "description": "The lazy kit for pi: no IDE, no copy-paste, safety net still on. The agent hands you commands (prompt, clipboard, or a Herdr pane that reports back), answers your ! commands, and takes secrets through a masked dialog it never sees",
   "type": "module",
   "license": "MIT",

package/skills/secret-drop/SKILL.md

@@ -10,7 +10,8 @@ Secrets reach files and commands through the `secret_drop` tool, so the value ne
 ## Writing a secret
 
 1. Pick the destination the consuming program expects. For a `regex` placement in a file that is not yet protected, read its structure first.
-2. Call `secret_drop` with a `label` naming exactly what to enter (service, account, environment), `instructions` the user can follow without asking (the exact page or menu path, every field to fill in such as name, scope, permissions, and expiration, and what to copy), the page as `url` when there is one, both in the user's language, and one format:
+2. When the value is newly created on a web page and a browser session on the user's signed-in profile is already open to you, ask the user with your question tool whether you should prepare that page; starting a browser only to qualify does not count. When they agree, open it, fill in every field (name, scope, permissions, expiration), and stop at the button that creates the value. From then on make no browser tool call in that session, whatever `secret_drop` returns, until the user has closed that tab: browser tools return page content, and the value is on that page once the button is pressed. Learn that the tab is closed from the user, through your question tool, rather than from a browser call. A page that shows an existing secret already holds the value in its DOM, so give its `url` and steps instead of opening it. When the user declines or no such session is open, write the full steps.
+3. Call `secret_drop` with a `label` naming exactly what to enter (service, account, environment), `instructions` the user can follow without asking (the exact page or menu path, every field to fill in such as name, scope, permissions, and expiration, and what to copy; for a prepared page, the tab, the button to press, what to copy, and closing the tab afterwards), the page as `url` when there is one, both in the user's language, and one format:
    - `key` + `destination` (format `env`): sets `KEY=value`, replacing existing `KEY` / `export KEY` lines or appending one. Other lines and trailing comments stay. For a file read by `docker --env-file`, pass `quote: "none"`, since Docker keeps quotes as part of the value.
    - `format: "regex"` + `destination` + `regex`: replaces capture group 1, or the whole match, in an existing file. Make the group cover only the value, e.g. `password: "([^"]*)"`.
    - `format: "file"` + `destination`: the whole file is the secret, for key files and single-value files. An existing destination is refused unless `overwrite: true` is passed; pass it only to rotate a single-value file, never for a multi-value file such as `.env`.
@@ -18,10 +19,10 @@ Secrets reach files and commands through the `secret_drop` tool, so the value ne
      - `ansible-vault encrypt_string --vault-password-file .vault-pass --stdin-name db_password < {secret} >> group_vars/prod/vault.yml`
      - `gh secret set DEPLOY_TOKEN < {secret}`
      - `kubectl create secret generic app-tls --from-file=tls.key={secret}`
-3. Call it once per secret and wait for the result:
+4. Call it once per secret and wait for the result:
    - **Applied**: the report states the change and `length check passed (N chars)`. That report is the verification; the value is in place.
    - **Question**: the user pressed Tab and asked instead; nothing was staged. Answer it, then call `secret_drop` again.
-   - **Cancelled or aborted**: nothing was applied. Ask the user how to proceed.
+   - **Cancelled or aborted**: nothing was applied. Ask the user how to proceed; have the user revoke a token created on a prepared page that was not applied.
    - **Apply failed**: the staged value was discarded. Fix the parameters from the error (a regex that does not match, a failing command) and call again.
 
 When the user offers to paste a secret into chat, call `secret_drop` instead.

package/src/secret-drop/index.ts

@@ -197,6 +197,7 @@ export default function secretDrop(pi: ExtensionAPI) {
 			"Use secret_drop whenever a password, token, key, or other credential must land in a file or be fed to a command; never ask the user to paste secrets into chat.",
 			"Files that hold secrets are consumed by programs, never read or printed by the agent.",
 			"Give secret_drop instructions the user can follow without asking: the exact page or menu, every field to fill in, and what to copy; write them and the label in the user's language.",
+			"When the secret is newly created on a web page and a browser session on the user's signed-in profile is already open to you, ask with your question tool whether to prepare that page up to its final create button, so the user only presses it and copies the value; then make no browser call in that session until the user tells you, when you ask, that the tab is closed, whatever secret_drop returns. Give the URL and steps instead of opening a page that shows an existing secret, and full steps when the user declines.",
 			"When secret_drop returns a question from the user, answer it, then call secret_drop again.",
 		],
 		parameters: Params,