@safetech/inheriti-cli 0.0.26-dev.0 → 0.0.27-dev.0

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/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@safetech/inheriti-cli",
3
- "version": "0.0.26-dev.0",
3
+ "version": "0.0.27-dev.0",
4
4
  "description": "Inheriti CLI (TEST builds only).",
5
5
  "type": "module",
6
6
  "bin": {
@@ -2,7 +2,7 @@
2
2
  name: inheriti-cli
3
3
  description: Use the Inheriti® CLI to find, create, inspect, reveal, download, or use protected plans and to configure Business automations from a user's natural-language request.
4
4
  metadata:
5
- version: 0.0.26-dev.0
5
+ version: 0.0.27-dev.0
6
6
  ---
7
7
 
8
8
  # Inheriti® CLI
@@ -17,4 +17,4 @@ Use [identity and discovery](references/identity-and-discovery.md) for login, Or
17
17
 
18
18
  For automations, preserve any Organisation, plan, provider, destination, member, and connection already supplied. Establish the intended cloud account/profile and region or project before discovering resources; use [provider workflows](references/automation-providers.md) to identify a specific target. A resource appearing in a list does not establish intent.
19
19
 
20
- Do not place secret values, custody shares, proofs, private keys, or bearer tokens in prompts, CLI arguments, shell history, environment setup, provider settings, or agent-visible output. `secrets resolve` is a special trusted-pipe API, not a way for the agent to read a value. Avoid `--output inherit` unless the user explicitly accepts the child program's logs. A natural-language request does not replace a plan's approval or authorise an unrelated deployment.
20
+ Do not place secret values, custody shares, proofs, private keys, or bearer tokens in prompts, CLI arguments, shell history, environment setup, provider settings, or agent-visible output. `secrets resolve` is a special trusted-pipe API, not a way for the agent to read a value. Outside GitHub Actions, avoid `--output inherit` unless the user explicitly accepts the child program's logs; GitHub Actions rejects it. A natural-language request does not replace a plan's approval or authorise an unrelated deployment.
@@ -2,6 +2,6 @@
2
2
 
3
3
  `inheriti plans create [--title NAME] [--description TEXT] [--asset TYPE ...]` passes **editable, non-secret hints** to the local plan assistant. Preserve title and description supplied in the user's request; use exact catalog IDs from `inheriti help plans create` for asset hints (for example, `--asset API-KEY`, not `--asset "API key"`). Do not put a password, recovery phrase, private key, token, or protected file contents in these options or in plan metadata. If the request already contains a secret-like value, do not repeat it or ask for another value in chat; tell the person to enter it only in the secure window.
4
4
 
5
- Creation requires sign-in, a selected Inheriti Business Organisation, an interactive terminal, a desktop window, and a claimed Organisation Key for that member. On first use, the CLI may offer to download its local assistant runtime and model (about 1.1 GB). The person enters protected content in the secure window, edits the draft, confirms creation, and may need to release the Organisation Key in SafeKey Mobile. Let the CLI present its progress. After the result appears, the person selects Continue or closes the window to return to the terminal. Report the plan ID and status returned by the CLI; do not claim completion while it is pending.
5
+ Creation requires sign-in, a selected Inheriti Business Organisation, an interactive terminal, a desktop window, and a claimed Organisation Key for that member. On first use, the CLI may offer to download its local assistant runtime and model (about 1.1 GB). Tell the person to keep the secure desktop window open and enter protected content only there. The person edits the draft, confirms creation, and may need to release the Organisation Key in SafeKey Mobile. Changing the asset type refreshes its fields; review them before saving. Editor activity renews the 30-minute idle session. The window warns two minutes before suspension; select Continue session to keep working. If suspended, select Continue session to resume with the entered values still in the window. The editor timer does not interrupt a creation or SafeKey wait already in progress. After the result appears, the person selects Continue or closes the window to return to the terminal. Report the plan ID and status returned by the CLI; do not claim completion while it is pending.
6
6
 
7
7
  `inheriti plans list` finds safe plan metadata, `inheriti plans show PLAN_ID` shows assets, fields, participants and policy, and `inheriti plans logs PLAN_ID` shows activity. Use these for verification and context, not as sources of protected values. For a request such as “create a plan called Family Archive with description Documents for my brother,” run the create command with those two hints, then hand off to the secure window. If the user requests an unsupported asset or omits important non-secret structure, explain the available choices rather than inventing one.
@@ -2,8 +2,8 @@
2
2
 
3
3
  Inspect the program's actual input contract and execution location before choosing a mapping. For a trusted local process, `inheriti plans use PLAN_ID [MAPPINGS] -- EXECUTABLE [ARGUMENT ...]` authorises selected fields and starts that exact executable without a shell. Available mappings are `--stdin ASSET.FIELD`, repeatable `--env NAME=ASSET.FIELD`, `--fd N=ASSET.FIELD`, `--temp-file NAME=ASSET.FIELD`, and `--socket NAME=ASSET.FIELD`. Use `--ttl DURATION` when a bounded run is appropriate. Check `inheriti help plans use` for platform limits: sockets and dedicated descriptors are unavailable on Windows. Confirm the exact executable, arguments, fields, destination names, and data path with the user before running it.
4
4
 
5
- For an environment-only child process, `inheriti secrets exec PLAN_ID --env NAME=ASSET.FIELD -- EXECUTABLE [ARGUMENT ...]` uses the same reveal and approval flow. Both commands suppress child stdout/stderr by default because the program might echo a credential. `--output inherit` exposes those logs; use it only with the user's informed choice. Environment variables can be inspected by processes of the same local user. The receiving program can persist or transmit values independently of Inheriti; inspect its configuration, state, and logs before promising a delivery outcome.
5
+ For an environment-only child process, `inheriti secrets exec PLAN_ID --env NAME=ASSET.FIELD -- EXECUTABLE [ARGUMENT ...]` uses the same reveal and approval flow. Both commands suppress child stdout/stderr by default because the program might echo a credential. Outside GitHub Actions, `--output inherit` exposes those logs; use it only with the user's informed choice. GitHub Actions rejects inherited child output before loading the plan. Environment variables can be inspected by processes of the same local user. The receiving program can persist or transmit values independently of Inheriti; inspect its configuration, state, and logs before promising a delivery outcome.
6
6
 
7
7
  An application name is not a command choice. For “use plan X in Terraform,” first identify whether Terraform runs on this computer or in CI/cloud, which input it expects, and whether the user intends a plan, apply, or setup. For a local run that accepts a variable through its environment, a candidate is `inheriti plans use PLAN_ID --env TF_VAR_name=asset.field -- terraform plan`. Inspect the Terraform variable declaration or ask for its exact name before presenting a runnable mapping; never derive `TF_VAR_name` from the credential's description. Use the real declared variable, selector, and exact requested Terraform command. A workload instead needs the [automation flow](automations.md). Do not run `terraform apply` from a request that only says “use.”
8
8
 
9
- `inheriti secrets resolve PLAN_ID --field ASSET.FIELD --allow-plaintext-output` is for a trusted machine wrapper with non-terminal stdout. It emits a raw value, so an agent must not call it into its own tool transcript or redirect it to logs. Prefer `plans use` or `secrets exec` for process delivery.
9
+ `inheriti secrets resolve PLAN_ID --field ASSET.FIELD --allow-plaintext-output` is for a trusted machine wrapper with non-terminal stdout outside GitHub Actions. GitHub Actions rejects this command before authentication because raw stdout can expose the value in workflow logs. It emits a raw value, so an agent must not call it into its own tool transcript or redirect it to logs. Prefer `plans use` or `secrets exec` for process delivery. The child can still transmit or store values elsewhere.
@@ -3,7 +3,7 @@
3
3
  - **Login or Organisation missing:** use browser `login` and `organizations list/use`, then retry the same safe discovery. A browser session alone is not evidence that the CLI holds a valid session.
4
4
  - **Command unavailable:** inspect `inheriti help` and the build's feature flags. Do not substitute a guessed flag or switch deployment channels to make an example work.
5
5
  - **Ambiguous plan or field:** list safe metadata and ask the person to choose. In a pipe, supply explicit ID and selector; interactive selection may not be available.
6
- - **Plan creation unavailable or interrupted:** check terminal/window availability, sign-in, selected Organisation, local assistant installation, and the CLI's returned plan status. Do not move protected inputs into chat to work around the window.
6
+ - **Plan creation unavailable or interrupted:** check terminal/window availability, sign-in, selected Organisation, local assistant installation, and the CLI's returned plan status. Do not move protected inputs into chat to work around the window. After a recoverable create error, use Retry create plan in the window; entered fields remain there. If the save outcome is unclear, inspect live plan metadata before retrying to avoid a duplicate. A timeout alone proves neither invalid account details nor that no plan was created.
7
7
  - **“Claim the Organisation key” during creation:** this is a prerequisite failure before a mobile relay request starts. Complete the member's key claim in SafeKey Mobile, then retry; distinguish it from a relay that is already waiting for release.
8
8
  - **Reveal pending:** report the CLI's current gate and the device or person who must act. Wait for the outcome; do not reissue a second reveal merely because an approval is slow. Denial, reconciliation, and DMS stop have distinct outcomes. `plans abort` resets an open operator access only when requested.
9
9
  - **Clipboard/file issue:** inspect the reported delivery status. TTL cleanup is best effort; downloads do not overwrite and may require a protected `.inheriti` path. Never read the value back to “verify” it.
@@ -1 +1 @@
1
- {"schema":1,"cliVersion":"0.0.26-dev.0","deployment":"dev","sha256":"659ea4497fe55c1e1a4cea018096277a2e11f5b6b62bb5a5cba0e98490864ded"}
1
+ {"schema":1,"cliVersion":"0.0.27-dev.0","deployment":"dev","sha256":"46b1bd53141f3894ddfe8a3e16b2c42c44ce8bc07840f9bc9ab1b794415d4f90"}