@camstack/develop 0.1.16 → 0.1.18

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.16",
3
+ "version": "0.1.18",
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",
@@ -86,7 +86,7 @@ own secrets), D798 (an addon reads its own settings resolved).
86
86
  child from a file or a pipe the child reads, never from a string you log.
87
87
  - Client-side developer tooling is different: the `camstack` CLI's
88
88
  `$CAMSTACK_TOKEN` / `--token-file` and `scripts/hub/hub.mjs`'s credential chain
89
- (`--token-file`, the 0600 admin token file, the `camstack login` session) are a developer's own credentials on their own machine,
89
+ (`--token-file`, then the `camstack login` session) are a developer's own credentials on their own machine,
90
90
  not server-side secrets.
91
91
 
92
92
  ## 5. Logs, fixtures, the repository
@@ -26,7 +26,7 @@ The server reads three environment variables. Nothing else, no flags.
26
26
 
27
27
  TLS verification is never turned off: a certificate error is fixed by naming the
28
28
  CA, not by disabling the check. Triage and frame need a normal token;
29
- **apply needs an admin token** and shows the hub's own refusal if the token
29
+ **apply needs admin permissions** and shows the hub's own refusal if the token
30
30
  lacks it. Tokens are never printed.
31
31
 
32
32
  ```json