@cubis/foundry 0.3.26 → 0.3.28

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.
@@ -12,7 +12,7 @@ Before proceeding, validate that the user has completed the following steps befo
12
12
 
13
13
  ## Step 1
14
14
 
15
- Generate and maintain `postman_setting.json` as the primary Postman configuration. Use env-first authentication by default: keep `apiKey` as `null`, set `apiKeyEnvVar` to `POSTMAN_API_KEY`, and read the key from environment variables. Only store `apiKey` inline when the user explicitly requests file-based key storage. Keep `defaultWorkspaceId` nullable (`null` when unknown) so workflows can run without a preselected workspace.
15
+ Generate and maintain `cbx_config.json` as the primary Postman configuration (workspace: `./cbx_config.json`, global: `~/.cbx/cbx_config.json`). Use `postman_setting.json` only as a legacy fallback when `cbx_config.json` is unavailable. When both files exist, always use `cbx_config.json` and do not reference `postman_setting.json` in normal responses. Use env-first authentication by default: keep `apiKey` as `null`, set `apiKeyEnvVar` to `POSTMAN_API_KEY`, and read the key from environment variables. Only store `apiKey` inline when the user explicitly requests file-based key storage. Keep `defaultWorkspaceId` nullable (`null` when unknown) so workflows can run without a preselected workspace.
16
16
 
17
17
  ## Step 2
18
18
 
@@ -68,7 +68,7 @@ Create a hook that runs anytime the source code or configuration file has been c
68
68
 
69
69
  Automate API testing and collection management with Postman. Create workspaces, collections, environments, and run tests programmatically.
70
70
 
71
- **Authentication**: Env-first via `postman_setting.json` + `POSTMAN_API_KEY`; inline `apiKey` is optional.
71
+ **Authentication**: Env-first via `cbx_config.json` + `POSTMAN_API_KEY` (legacy fallback: `postman_setting.json`); inline `apiKey` is optional.
72
72
 
73
73
  ## Available MCP Servers
74
74
 
@@ -10,7 +10,7 @@ Before proceeding, validate that the user has completed the following steps befo
10
10
 
11
11
  ## Step 1
12
12
 
13
- Generate and maintain `postman_setting.json` as the primary Postman configuration. Use env-first authentication by default: keep `apiKey` as `null`, set `apiKeyEnvVar` to `POSTMAN_API_KEY`, and read the key from environment variables. Only store `apiKey` inline when the user explicitly requests file-based key storage. Keep `defaultWorkspaceId` nullable (`null` when unknown) so workflows can run without a preselected workspace.
13
+ Generate and maintain `cbx_config.json` as the primary Postman configuration (workspace: `./cbx_config.json`, global: `~/.cbx/cbx_config.json`). Use `postman_setting.json` only as a legacy fallback when `cbx_config.json` is unavailable. When both files exist, always use `cbx_config.json` and do not reference `postman_setting.json` in normal responses. Use env-first authentication by default: keep `apiKey` as `null`, set `apiKeyEnvVar` to `POSTMAN_API_KEY`, and read the key from environment variables. Only store `apiKey` inline when the user explicitly requests file-based key storage. Keep `defaultWorkspaceId` nullable (`null` when unknown) so workflows can run without a preselected workspace.
14
14
 
15
15
  ## Step 2
16
16
 
@@ -66,7 +66,7 @@ Create a hook that runs anytime the source code or configuration file has been c
66
66
 
67
67
  Automate API testing and collection management with Postman. Create workspaces, collections, environments, and run tests programmatically.
68
68
 
69
- **Authentication**: Env-first via `postman_setting.json` + `POSTMAN_API_KEY`; inline `apiKey` is optional.
69
+ **Authentication**: Env-first via `cbx_config.json` + `POSTMAN_API_KEY` (legacy fallback: `postman_setting.json`); inline `apiKey` is optional.
70
70
 
71
71
  ## Available MCP Servers
72
72
 
@@ -12,7 +12,7 @@ Before proceeding, validate that the user has completed the following steps befo
12
12
 
13
13
  ## Step 1
14
14
 
15
- Generate and maintain `postman_setting.json` as the primary Postman configuration. Use env-first authentication by default: keep `apiKey` as `null`, set `apiKeyEnvVar` to `POSTMAN_API_KEY`, and read the key from environment variables. Only store `apiKey` inline when the user explicitly requests file-based key storage. Keep `defaultWorkspaceId` nullable (`null` when unknown) so workflows can run without a preselected workspace.
15
+ Generate and maintain `cbx_config.json` as the primary Postman configuration (workspace: `./cbx_config.json`, global: `~/.cbx/cbx_config.json`). Use `postman_setting.json` only as a legacy fallback when `cbx_config.json` is unavailable. When both files exist, always use `cbx_config.json` and do not reference `postman_setting.json` in normal responses. Use env-first authentication by default: keep `apiKey` as `null`, set `apiKeyEnvVar` to `POSTMAN_API_KEY`, and read the key from environment variables. Only store `apiKey` inline when the user explicitly requests file-based key storage. Keep `defaultWorkspaceId` nullable (`null` when unknown) so workflows can run without a preselected workspace.
16
16
 
17
17
  ## Step 2
18
18
 
@@ -68,7 +68,7 @@ Create a hook that runs anytime the source code or configuration file has been c
68
68
 
69
69
  Automate API testing and collection management with Postman. Create workspaces, collections, environments, and run tests programmatically.
70
70
 
71
- **Authentication**: Env-first via `postman_setting.json` + `POSTMAN_API_KEY`; inline `apiKey` is optional.
71
+ **Authentication**: Env-first via `cbx_config.json` + `POSTMAN_API_KEY` (legacy fallback: `postman_setting.json`); inline `apiKey` is optional.
72
72
 
73
73
  ## Available MCP Servers
74
74
 
@@ -10,7 +10,7 @@ Before proceeding, validate that the user has completed the following steps befo
10
10
 
11
11
  ## Step 1
12
12
 
13
- Generate and maintain `postman_setting.json` as the primary Postman configuration. Use env-first authentication by default: keep `apiKey` as `null`, set `apiKeyEnvVar` to `POSTMAN_API_KEY`, and read the key from environment variables. Only store `apiKey` inline when the user explicitly requests file-based key storage. Keep `defaultWorkspaceId` nullable (`null` when unknown) so workflows can run without a preselected workspace.
13
+ Generate and maintain `cbx_config.json` as the primary Postman configuration (workspace: `./cbx_config.json`, global: `~/.cbx/cbx_config.json`). Use `postman_setting.json` only as a legacy fallback when `cbx_config.json` is unavailable. When both files exist, always use `cbx_config.json` and do not reference `postman_setting.json` in normal responses. Use env-first authentication by default: keep `apiKey` as `null`, set `apiKeyEnvVar` to `POSTMAN_API_KEY`, and read the key from environment variables. Only store `apiKey` inline when the user explicitly requests file-based key storage. Keep `defaultWorkspaceId` nullable (`null` when unknown) so workflows can run without a preselected workspace.
14
14
 
15
15
  ## Step 2
16
16
 
@@ -66,7 +66,7 @@ Create a hook that runs anytime the source code or configuration file has been c
66
66
 
67
67
  Automate API testing and collection management with Postman. Create workspaces, collections, environments, and run tests programmatically.
68
68
 
69
- **Authentication**: Env-first via `postman_setting.json` + `POSTMAN_API_KEY`; inline `apiKey` is optional.
69
+ **Authentication**: Env-first via `cbx_config.json` + `POSTMAN_API_KEY` (legacy fallback: `postman_setting.json`); inline `apiKey` is optional.
70
70
 
71
71
  ## Available MCP Servers
72
72
 
@@ -101,6 +101,7 @@
101
101
  "frontend-design",
102
102
  "game-development",
103
103
  "geo-fundamentals",
104
+ "golang-pro",
104
105
  "i18n-localization",
105
106
  "intelligent-routing",
106
107
  "lint-and-validate",
@@ -240,6 +241,7 @@
240
241
  "frontend-design",
241
242
  "game-development",
242
243
  "geo-fundamentals",
244
+ "golang-pro",
243
245
  "i18n-localization",
244
246
  "intelligent-routing",
245
247
  "lint-and-validate",
@@ -379,6 +381,7 @@
379
381
  "frontend-design",
380
382
  "game-development",
381
383
  "geo-fundamentals",
384
+ "golang-pro",
382
385
  "i18n-localization",
383
386
  "intelligent-routing",
384
387
  "lint-and-validate",
package/CHANGELOG.md CHANGED
@@ -2,6 +2,19 @@
2
2
 
3
3
  All notable changes to this project are documented in this file.
4
4
 
5
+ ## [0.3.28] - 2026-02-27
6
+
7
+ ### Fixed
8
+
9
+ - Added missing `golang-pro` skill to `agent-environment-setup` manifest for Codex, Antigravity, and Copilot installs.
10
+
11
+ ## [0.3.27] - 2026-02-26
12
+
13
+ ### Changed
14
+
15
+ - Updated Postman skill/power guidance to use `cbx_config.json` as the default config source with `POSTMAN_API_KEY` env-first auth.
16
+ - Added explicit instruction to avoid referencing `postman_setting.json` in normal responses when `cbx_config.json` exists.
17
+
5
18
  ## [0.3.26] - 2026-02-26
6
19
 
7
20
  ### Fixed
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@cubis/foundry",
3
- "version": "0.3.26",
3
+ "version": "0.3.28",
4
4
  "description": "Cubis Foundry CLI for workflow-first AI agent environments",
5
5
  "type": "module",
6
6
  "bin": {