@cubis/foundry 0.3.28 → 0.3.29

package/Ai Agent Workflow/powers/postman/POWER.md

@@ -12,7 +12,7 @@ Before proceeding, validate that the user has completed the following steps befo
 
 ## Step 1
 
-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.
+Generate and maintain `cbx_config.json` as the only Postman configuration source (workspace: `./cbx_config.json`, global: `~/.cbx/cbx_config.json`). Use named profiles in `postman.profiles` and choose `postman.activeProfileName`. Use env-first authentication by default: keep `apiKey` as `null`, set `apiKeyEnvVar` to `POSTMAN_API_KEY` (or another profile alias), and read the key from environment variables. Only store `apiKey` inline when the user explicitly requests file-based key storage. Keep workspace selection in the active profile `workspaceId` (`null` when unknown).
 
 ## Step 2
 
@@ -68,7 +68,7 @@ Create a hook that runs anytime the source code or configuration file has been c
 
 Automate API testing and collection management with Postman. Create workspaces, collections, environments, and run tests programmatically.
 
-**Authentication**: Env-first via `cbx_config.json` + `POSTMAN_API_KEY` (legacy fallback: `postman_setting.json`); inline `apiKey` is optional.
+**Authentication**: Env-first via `cbx_config.json` + profile env alias (default `POSTMAN_API_KEY`); inline `apiKey` is optional.
 
 ## Available MCP Servers
 

package/Ai Agent Workflow/powers/postman/SKILL.md

@@ -10,7 +10,7 @@ Before proceeding, validate that the user has completed the following steps befo
 
 ## Step 1
 
-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.
+Generate and maintain `cbx_config.json` as the only Postman configuration source (workspace: `./cbx_config.json`, global: `~/.cbx/cbx_config.json`). Use named profiles in `postman.profiles` and choose `postman.activeProfileName`. Use env-first authentication by default: keep `apiKey` as `null`, set `apiKeyEnvVar` to `POSTMAN_API_KEY` (or another profile alias), and read the key from environment variables. Only store `apiKey` inline when the user explicitly requests file-based key storage. Keep workspace selection in the active profile `workspaceId` (`null` when unknown).
 
 ## Step 2
 
@@ -66,7 +66,7 @@ Create a hook that runs anytime the source code or configuration file has been c
 
 Automate API testing and collection management with Postman. Create workspaces, collections, environments, and run tests programmatically.
 
-**Authentication**: Env-first via `cbx_config.json` + `POSTMAN_API_KEY` (legacy fallback: `postman_setting.json`); inline `apiKey` is optional.
+**Authentication**: Env-first via `cbx_config.json` + profile env alias (default `POSTMAN_API_KEY`); inline `apiKey` is optional.
 
 ## Available MCP Servers
 

package/Ai Agent Workflow/skills/postman/POWER.md

@@ -12,7 +12,7 @@ Before proceeding, validate that the user has completed the following steps befo
 
 ## Step 1
 
-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.
+Generate and maintain `cbx_config.json` as the only Postman configuration source (workspace: `./cbx_config.json`, global: `~/.cbx/cbx_config.json`). Use named profiles in `postman.profiles` and choose `postman.activeProfileName`. Use env-first authentication by default: keep `apiKey` as `null`, set `apiKeyEnvVar` to `POSTMAN_API_KEY` (or another profile alias), and read the key from environment variables. Only store `apiKey` inline when the user explicitly requests file-based key storage. Keep workspace selection in the active profile `workspaceId` (`null` when unknown).
 
 ## Step 2
 
@@ -68,7 +68,7 @@ Create a hook that runs anytime the source code or configuration file has been c
 
 Automate API testing and collection management with Postman. Create workspaces, collections, environments, and run tests programmatically.
 
-**Authentication**: Env-first via `cbx_config.json` + `POSTMAN_API_KEY` (legacy fallback: `postman_setting.json`); inline `apiKey` is optional.
+**Authentication**: Env-first via `cbx_config.json` + profile env alias (default `POSTMAN_API_KEY`); inline `apiKey` is optional.
 
 ## Available MCP Servers
 

package/Ai Agent Workflow/skills/postman/SKILL.md

@@ -10,7 +10,7 @@ Before proceeding, validate that the user has completed the following steps befo
 
 ## Step 1
 
-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.
+Generate and maintain `cbx_config.json` as the only Postman configuration source (workspace: `./cbx_config.json`, global: `~/.cbx/cbx_config.json`). Use named profiles in `postman.profiles` and choose `postman.activeProfileName`. Use env-first authentication by default: keep `apiKey` as `null`, set `apiKeyEnvVar` to `POSTMAN_API_KEY` (or another profile alias), and read the key from environment variables. Only store `apiKey` inline when the user explicitly requests file-based key storage. Keep workspace selection in the active profile `workspaceId` (`null` when unknown).
 
 ## Step 2
 
@@ -66,7 +66,7 @@ Create a hook that runs anytime the source code or configuration file has been c
 
 Automate API testing and collection management with Postman. Create workspaces, collections, environments, and run tests programmatically.
 
-**Authentication**: Env-first via `cbx_config.json` + `POSTMAN_API_KEY` (legacy fallback: `postman_setting.json`); inline `apiKey` is optional.
+**Authentication**: Env-first via `cbx_config.json` + profile env alias (default `POSTMAN_API_KEY`); inline `apiKey` is optional.
 
 ## Available MCP Servers
 

package/CHANGELOG.md

@@ -2,6 +2,31 @@
 
 All notable changes to this project are documented in this file.
 
+## [0.3.29] - 2026-02-27
+
+### Changed
+
+- Switched credential/config source to `cbx_config.json` only for Postman and Stitch runtime selection.
+- Added profile-based credential model for Postman/Stitch (`profiles[]` + `activeProfileName`) with compatibility mirrors.
+- Updated `cbx workflows config --show` to include computed `status` with stored source vs effective source and active profile/env alias context.
+- Changed default skill install resolution to indexed top-level skills (`skills_index.json` + resolved skill dirs), instead of curated manifest subset.
+- Added automatic nested duplicate skill cleanup during install (for example duplicate skill packs nested under `postman/*`).
+- Rewrote README into a full operational guide (quickstarts, scopes, credential flows, MCP placement, troubleshooting, migration).
+
+### Added
+
+- Added `cbx workflows config keys` profile-management commands:
+  - `list`
+  - `add`
+  - `use`
+  - `remove`
+- Added `cbx skills config keys` compatibility alias.
+
+### Fixed
+
+- Removed legacy Postman fallback file references from runtime/docs and enforce migration to `cbx_config.json`.
+- Updated validation/smoke scripts to align with global-skill default install model and profile-based config behavior.
+
 ## [0.3.28] - 2026-02-27
 
 ### Fixed
@@ -13,7 +38,7 @@ All notable changes to this project are documented in this file.
 ### Changed
 
 - Updated Postman skill/power guidance to use `cbx_config.json` as the default config source with `POSTMAN_API_KEY` env-first auth.
-- Added explicit instruction to avoid referencing `postman_setting.json` in normal responses when `cbx_config.json` exists.
+- Added explicit instruction to avoid referencing legacy Postman fallback configs in normal responses when `cbx_config.json` exists.
 
 ## [0.3.26] - 2026-02-26