@camstack/develop 0.1.10 → 0.1.12

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": "@camstack/develop",
3
- "version": "0.1.10",
3
+ "version": "0.1.12",
4
4
  "description": "CamStack developer tooling — catalogue, scaffold, validate, and example lookup shared by the CLI and MCP server.",
5
5
  "keywords": [
6
6
  "camstack",
@@ -68,12 +68,12 @@ own secrets), D798 (an addon reads its own settings resolved).
68
68
  ## 4. Never through the environment or argv — files for children
69
69
 
70
70
  - **No secret reaches any process through its environment** — not an addon
71
- credential, not the session signing key, not the cluster secret, not "an
71
+ credential, not the session signing key, not a node token, not "an
72
72
  optional token for power users" (D797 removed `HF_TOKEN`,
73
73
  `CAMSTACK_SECRET_KEY` and the like). A credential is a declared field, read
74
74
  from your config.
75
75
  - The hub's own secrets live in the keychain under owner `system`; an agent's
76
- cluster secret lives in its own `agent.json` (0600). The keychain master key
76
+ identity is its mesh certificate and key in its own `agent.json` (0600). The keychain master key
77
77
  comes from `keychain.keyFile` in `config.yaml`, the desktop app's OS
78
78
  keychain, or the default key file — never an env var (D788).
79
79
  - **A child process that needs a credential gets an owner-only FILE**: a fresh