@cubis/foundry 0.3.57 → 0.3.59

package/CHANGELOG.md

@@ -2,6 +2,24 @@
 
 All notable changes to this project are documented in this file.
 
+## [0.3.59] - 2026-03-05
+
+### Added
+
+- Added dedicated Postman workflow routing across supported platforms:
+  - new `/postman` workflow definition
+  - generated platform assets for Codex, Antigravity, and Copilot
+  - generated wrapper skill `workflow-postman` for Codex.
+
+### Changed
+
+- Tightened Postman guidance to be MCP-first:
+  - explicitly prefer `postman.*` / `postman_*` tools for execution
+  - disallow default fallback to raw JSON/curl/Newman unless explicitly requested.
+- Updated Postman setup/troubleshooting docs to be scope-aware (`project|global`) so project installs stop drifting to global-only guidance.
+- Updated Codex rules template to reinforce no default JSON/curl fallback when Postman MCP tools are available.
+- Updated smoke test expectations from 18 to 19 workflows/prompts/commands where applicable.
+
 ## [0.3.57] - 2026-03-05
 
 ### Changed

package/dist/cli/core.js

@@ -811,9 +811,35 @@ function buildEngineeringRulesTemplate() {
         "## 8) Response Contract (Decision Log Required)",
         "",
         "- For planning/review/execution summaries, use a `Decision Log` structure.",
-        "- Each decision entry should include: `Context`, `Decision`, `Rationale`, `Tradeoffs`, `Validation`.",
-        "- Include a `Files Used` section with full absolute paths (not shorthand names).",
+        "- Each decision entry must include: `Context`, `Decision`, `Rationale`, `Tradeoffs`, `Validation`.",
+        "- Include `Files Used` with labeled keys and full absolute paths (not shorthand names).",
+        "- Include `Skills Used` with skill IDs and full skill file paths when skills are loaded.",
+        "- Minimum required entries in `Files Used` for project work:",
+        "  - `active_rules_file`: active platform rules file path (for example `AGENTS.md`, `.agent/rules/GEMINI.md`, or `.github/copilot-instructions.md`)",
+        "  - `engineering_rules_file`: `/abs/path/ENGINEERING_RULES.md`",
+        "  - `tech_map_file`: `/abs/path/TECH.md`",
+        "- If no skill is loaded, write `Skills Used: none` explicitly.",
         "- Never hide key file paths behind aliases or abbreviated labels.",
+        "- A Decision Log without required `Files Used` and `Skills Used` is incomplete and must be corrected before final response.",
+        "",
+        "Required shape:",
+        "",
+        "Decision Log",
+        "1. Context: ...",
+        "Decision: ...",
+        "Rationale: ...",
+        "Tradeoffs: ...",
+        "Validation: ...",
+        "",
+        "Files Used",
+        "- active_rules_file: /abs/path/<platform-rule-file>",
+        "- engineering_rules_file: /abs/path/ENGINEERING_RULES.md",
+        "- tech_map_file: /abs/path/TECH.md",
+        "- implementation_file: /abs/path/other/file.ts (as needed)",
+        "",
+        "Skills Used",
+        "- skill-id: /abs/path/<platform-skills-root>/<skill-id>/SKILL.md",
+        "- or: none",
         "",
         "## 9) Keep TECH.md Fresh",
         "",
@@ -842,7 +868,10 @@ function buildEngineeringRulesManagedBlock({ platform, engineeringRulesFilePath,
         "3. Apply SOLID pragmatically to reduce change risk, not add ceremony.",
         "4. Use clear naming with focused responsibilities and explicit boundaries.",
         "5. Require validation evidence (lint/types/tests) before merge.",
-        "6. Use Decision Log response style and include full absolute file paths in `Files Used`.",
+        "6. Use Decision Log response style.",
+        "7. Every Decision Log must include both `Files Used` and `Skills Used` sections.",
+        "8. `Files Used` must include labeled keys (`active_rules_file`, `engineering_rules_file`, `tech_map_file`) with full absolute paths.",
+        "9. If no skill loaded, `Skills Used: none` is mandatory.",
         "",
         "<!-- cbx:engineering:auto:end -->",
     ].join("\n");