@camstack/develop 0.1.42 → 0.1.44

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/CHANGELOG.md CHANGED
@@ -7,12 +7,25 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
7
7
 
8
8
  ## [Unreleased]
9
9
 
10
+ ## [0.1.44] - 2026-11-01
11
+
12
+ ### Changed
13
+
14
+ - camstack-secrets skill: the external keychain master key is the fixed mounted path /run/secrets/camstack-master-key, not a config.yaml key
15
+
16
+ ## [0.1.43] - 2026-11-01
17
+
18
+ ### Changed
19
+
20
+ - Skills and scaffolds updated for the single framework package and the required server minimum
21
+
10
22
  ## [0.1.42] - 2026-11-01
11
23
 
12
24
  ### Changed
13
25
 
14
26
  - The login hints now name the browser approval for a terminal with no TTY
15
27
  - A saved sign-in session file is written atomically and always ends up 0600, even over a loose existing file
28
+ - Skills and scaffolds updated for the single framework package and the required server minimum
16
29
 
17
30
  ## [0.1.41] - 2026-10-30
18
31
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@camstack/develop",
3
- "version": "0.1.42",
3
+ "version": "0.1.44",
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",
@@ -125,7 +125,7 @@ Manifest fields worth knowing: `protected: true` blocks uninstall ·
125
125
 
126
126
  **`icon` is a promise the hub must keep.** It is an asset PATH inside the
127
127
  package (`assets/icon.svg`, or `assets/<addonId>/icon.svg` when one package ships
128
- several addons — `@camstack/system` does this for every builtin), and the folder
128
+ several addons — `@camstack/server` does this for every builtin), and the folder
129
129
  must be in `files` or `npm pack` drops it. The Admin UI requests
130
130
  `/api/addon-assets/<addonId>/<icon>` only for an addon that declares one
131
131
  (`addon-admin-ui/src/lib/addon-icons.ts`); everything else draws a glyph with no
@@ -178,13 +178,13 @@ Spec in `server/backend/src/__tests__/cap-routers/` — the router builder does
178
178
  not re-validate OUTPUT, so the test pins the shape.
179
179
 
180
180
  **What must be published.** The hub reads `ALL_CAPABILITY_DEFINITIONS` from
181
- **`@camstack/system`**, which bundles the cap definitions — and nx-affected
182
- does NOT mark `@camstack/system` changed for an edit under `packages/types`.
181
+ **`@camstack/server/system`**, which bundles the cap definitions — and nx-affected
182
+ does NOT mark `@camstack/server` changed for an edit under `packages/types`.
183
183
  So a cap change always force-publishes it with the server:
184
184
 
185
185
  ```bash
186
186
  gh workflow run "Publish Packages" --ref main -f bump=patch -f scope=affected \
187
- -f include_dependents=false -f force_packages=@camstack/system,@camstack/server
187
+ -f include_dependents=false -f force_packages=@camstack/server/system,@camstack/server
188
188
  ```
189
189
 
190
190
  Then the server-side chain — publish → `applyServerUpdate` on the hub AND every
@@ -74,8 +74,8 @@ own secrets), D798 (an addon reads its own settings resolved).
74
74
  from your config.
75
75
  - The hub's own secrets live in the keychain under owner `system`; an agent's
76
76
  identity is its mesh certificate and key in its own `agent.json` (0600). The keychain master key
77
- comes from `keychain.keyFile` in `config.yaml`, the desktop app's OS
78
- keychain, or the default key file — never an env var (D788).
77
+ comes from the file `/run/secrets/camstack-master-key`, the desktop app's OS
78
+ keychain, or the default key file — never an env var or config (D788, D991).
79
79
  - **A child process that needs a credential gets an owner-only FILE**: a fresh
80
80
  `0700` temp dir, the value written with `mode: 0o600`, the PATH passed on
81
81
  argv (`--auth-key=file:<path>`, `--token-file <path>`), the dir removed when