fips-agents-cli 0.7.0__tar.gz → 0.9.1__tar.gz

fips_agents_cli-0.9.1/.github/CODEOWNERS

@@ -0,0 +1,2 @@
+# Code Owners - all PRs require approval from @rdwj
+*       @rdwj

{fips_agents_cli-0.7.0 → fips_agents_cli-0.9.1}/.gitignore

@@ -25,6 +25,7 @@ MANIFEST
 
 # Virtual environments
 venv/
+.venv/
 env/
 ENV/
 env.bak/
@@ -88,3 +89,6 @@ tokens.txt
 
 # Project specific
 setup_structure.sh
+
+# Session handoff notes (local-only — content lives in MEMORY.md)
+NEXT_SESSION.md

{fips_agents_cli-0.7.0 → fips_agents_cli-0.9.1}/CLAUDE.md

@@ -6,7 +6,12 @@ This file provides guidance to Claude Code (claude.ai/code) when working with co
 
 **fips-agents-cli** is a Python-based CLI tool for scaffolding FIPS-compliant AI agent projects. It scaffolds MCP (Model Context Protocol) servers and AI agent projects from production-ready templates, customizes them for new projects, and prepares them for immediate development use.
 
-**Current Status:** `create mcp-server` and `create agent` commands implemented.
+**Current Status:** Scaffolding commands implemented: `create mcp-server`, `create agent`, `create gateway`, `create ui`, `create sandbox`, `create model-car`. Post-scaffolding commands: `generate` (tool, resource, prompt, middleware), `patch` (check, all + type-specific category subcommands — see below), `add` (code-executor), `vendor`. Note: `create workflow` exists in code but is not yet working.
+
+The `patch` command is type-aware via `template.type` in `.template-info`:
+- **MCP server** projects expose `patch generators | core | docs | build`.
+- **Agent / workflow** projects expose `patch chart | docs | build | claude`.
+Running an MCP-only subcommand inside an agent project (or vice versa) exits with a clear "available categories" error. `patch check` and `patch all` work for any supported type.
 
 ## Development Commands
 
@@ -91,18 +96,25 @@ This command will:
 
 ```bash
 # 1. Update version in both files manually or use the script:
-./scripts/release.sh <version> "<commit-message>"
+./scripts/release.sh <version> [<summary>]
 
-# Example:
+# Examples:
+./scripts/release.sh 0.1.2
 ./scripts/release.sh 0.1.2 "Add new generator features"
 
 # The script handles:
 # - Updating version.py and pyproject.toml
+# - Constructing the release commit message from the project convention
 # - Committing changes (including README.md changelog)
 # - Creating and pushing tag
 # - Triggering GitHub Actions
 ```
 
+**Release commit message convention**: `chore: Release fips-agents-cli vX.Y.Z`,
+optionally followed by ` — <summary>`. The script always constructs the message
+from the version argument; callers only supply the summary, never the full
+message. This keeps `git log --grep "Release fips-agents-cli"` reliable.
+
 **Note**: Always update the changelog in README.md before running the script.
 
 See `RELEASE_CHECKLIST.md` for detailed release procedures and troubleshooting.
@@ -141,7 +153,7 @@ Two cloning strategies exist:
 1. Clone monorepo, extract `templates/agent-loop/` subdirectory
 2. Update `pyproject.toml` name field via tomlkit
 3. String-replace `agent-template` → new name in Chart.yaml, values.yaml, AGENTS.md, Containerfile, Makefile
-4. Source directories are NOT renamed — `base_agent` is a framework component
+4. Source directories are NOT renamed — the agent-loop template ships with `src/agent.py` directly, not a project-named module
 5. Initialize fresh git repository with initial commit
 
 **Rich Console Output**: All user-facing output uses Rich library for:
@@ -272,7 +284,7 @@ def test_something(temp_dir):
 
 **Agent Template** (`fips-agents/agent-template` — monorepo, `templates/agent-loop/`):
 - `pyproject.toml` with project name (no entry point scripts)
-- `src/base_agent/` framework (NOT renamed during customization)
+- `src/agent.py` user agent subclass (lives at this path directly — no project-named module wrapper)
 - `chart/` Helm chart for OpenShift deployment
 - `agent.yaml` configuration (customized via `/plan-agent`, not during scaffolding)
 - `.claude/commands/` with agent development slash commands
@@ -325,6 +337,10 @@ Common causes:
 2. Dependencies not installed: `pip install -e .[dev]`
 3. Git not configured globally: `git config --global user.email "test@example.com"`
 
+## Release Process Notes
+
+When creating a new release, always update the changelog in README.md *before* running the release script. The changelog lives in the README under the `## Changelog` heading. Each version should have its own section with the version number and date, listing new features, fixes, and breaking changes. Forgetting the changelog entry leads to patch releases (like v0.8.1) that exist solely to backfill documentation — avoid that by treating the changelog update as a required step in every release.
+
 ## Repository-Specific Notes
 
 - The main branch is `main` (not `master`)

{fips_agents_cli-0.7.0 → fips_agents_cli-0.9.1}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: fips-agents-cli
-Version: 0.7.0
+Version: 0.9.1
 Summary: CLI tool for creating and managing FIPS-compliant AI agent projects
 Project-URL: Homepage, https://github.com/fips-agents/fips-agents-cli
 Project-URL: Repository, https://github.com/fips-agents/fips-agents-cli
@@ -145,6 +145,7 @@ fips-agents add --help
 fips-agents create --help
 fips-agents generate --help
 fips-agents patch --help
+fips-agents vendor --help
 ```
 
 ---
@@ -216,6 +217,12 @@ Creates an AI agent project from the [agent-template](https://github.com/fips-ag
 
 **Options:** Same as `create mcp-server` (see shared options table above).
 
+**Additional option:**
+
+| Option | Description |
+|--------|-------------|
+| `--vendored` | Copy fipsagents source into the project instead of using PyPI dependency |
+
 **Examples:**
 
 ```bash
@@ -227,6 +234,9 @@ fips-agents create agent my-agent --github --org fips-agents
 
 # Non-interactive mode
 fips-agents create agent my-agent --yes --local
+
+# Create with vendored fipsagents source
+fips-agents create agent my-agent --vendored --local
 ```
 
 #### `create gateway`
@@ -547,7 +557,9 @@ When using `--params` with `generate tool` or `generate prompt`, provide a JSON
 
 ### Patch Commands
 
-The `patch` command group updates files in existing MCP server projects from the upstream template repository without overwriting your custom code. It shows interactive diffs for files that may contain customizations.
+The `patch` command group updates files in existing projects from the upstream template repository without overwriting your custom code. It shows interactive diffs for files that may contain customizations.
+
+Supported project types: **MCP server**, **agent**, **workflow**. The available category subcommands depend on the project type — `patch` reads `template.type` from `.template-info` and surfaces a clear error if you run a category that doesn't apply (e.g. `patch generators` inside an agent project).
 
 Run these commands from within your project directory.
 
@@ -557,47 +569,35 @@ Run these commands from within your project directory.
 fips-agents patch check
 ```
 
-Check for available template updates. Shows what files have changed in the template since your project was created, organized by category.
-
-#### `patch generators`
-
-```bash
-fips-agents patch generators [--dry-run]
-```
-
-Update code generator templates (Jinja2 templates in `.fips-agents-cli/generators/`).
-
-#### `patch core`
-
-```bash
-fips-agents patch core [--dry-run]
-```
-
-Update core infrastructure files (loaders, server bootstrap).
+Check for available template updates. Shows what files have changed in the template since your project was created, organized by category. Works for any supported project type.
 
-#### `patch docs`
+#### `patch all`
 
 ```bash
-fips-agents patch docs [--dry-run]
+fips-agents patch all [--dry-run] [--skip-confirmation]
 ```
 
-Update documentation files and examples.
+Update every category that applies to the current project type. Prompts for confirmation before starting unless `--skip-confirmation` is passed.
 
-#### `patch build`
+#### MCP server categories
 
-```bash
-fips-agents patch build [--dry-run]
-```
+| Subcommand           | Patches                                                                  |
+|----------------------|--------------------------------------------------------------------------|
+| `patch generators`   | Jinja2 templates in `.fips-agents-cli/generators/`                       |
+| `patch core`         | Core infrastructure (loaders, server bootstrap)                          |
+| `patch docs`         | Documentation files and examples                                         |
+| `patch build`        | Build and deployment files (Makefile, Containerfile)                     |
 
-Update build and deployment files (Makefile, Containerfile).
+#### Agent / workflow categories
 
-#### `patch all`
+| Subcommand     | Patches                                                                       |
+|----------------|-------------------------------------------------------------------------------|
+| `patch chart`  | Helm chart templates (`chart/templates/**`, `chart/Chart.yaml`)                |
+| `patch docs`   | `CLAUDE.md`, `AGENTS.md`, `docs/**`                                            |
+| `patch build`  | `Makefile`, `Containerfile`, `deploy.sh`, `redeploy.sh`                        |
+| `patch claude` | Claude Code slash commands shipped with the template (`.claude/commands/**`)   |
 
-```bash
-fips-agents patch all [--dry-run] [--skip-confirmation]
-```
-
-Update all patchable file categories at once. Prompts for confirmation before starting unless `--skip-confirmation` is passed.
+User-customized files are never patched: for MCP this means `src/tools/`, `src/resources/`, `src/prompts/`, `src/middleware/`, `pyproject.toml`, etc. For agent/workflow it means `src/agent.py`, `agent.yaml`, `chart/values.yaml`, `src/fipsagents/**` (managed by `fips-agents vendor`), and `pyproject.toml`.
 
 All patch subcommands (except `check`) accept `--dry-run` to preview changes without modifying files.
 
@@ -635,6 +635,45 @@ cd my-research-agent
 fips-agents add code-executor
 ```
 
+---
+
+### Vendor Commands
+
+The `vendor` command copies the fipsagents source into your agent project, replacing the PyPI dependency. This gives you full control over the fipsagents code.
+
+#### `vendor`
+
+```bash
+fips-agents vendor [OPTIONS]
+```
+
+Copies fipsagents source into `src/fipsagents/` and rewrites `pyproject.toml` to use individual dependencies instead of the fipsagents package.
+
+**Options:**
+
+| Option | Description |
+|--------|-------------|
+| `--update` | Update an already-vendored project with the latest upstream source |
+| `--version TEXT` | Vendor a specific version tag (e.g., `fipsagents-v0.7.0`). Default: latest main |
+
+**Examples:**
+
+```bash
+# Vendor into current project
+fips-agents vendor
+
+# Vendor a specific version
+fips-agents vendor --version fipsagents-v0.7.0
+
+# Update vendored source from upstream
+fips-agents vendor --update
+```
+
+**When to use vendored vs. PyPI:**
+
+- **PyPI dependency** (default): Best for teams running multiple agents that share the same fipsagents version. Centralized updates.
+- **Vendored source**: Best for agents that need custom BaseAgent modifications, environments with no PyPI access, or when you want to read and debug the fipsagents source locally.
+
 ## Project Name Requirements
 
 Project names must follow these rules:
@@ -663,10 +702,9 @@ pytest
 
 ```bash
 cd my-research-agent
-python -m venv venv
-source venv/bin/activate
-pip install -e .[dev]
-pytest
+make install         # Create venv, install dependencies
+make run-local       # Start HTTP server on port 8080
+make test            # Run tests
 # See AGENTS.md for the /plan-agent slash command workflow
 ```
 
@@ -778,7 +816,8 @@ fips-agents-cli/
 │       │   ├── create.py   # create mcp-server, agent, gateway, ui
 │       │   ├── generate.py # generate tool/resource/prompt/middleware
 │       │   ├── model_car.py # create model-car
-│       │   └── patch.py    # patch command
+│       │   ├── patch.py    # patch command
+│       │   └── vendor.py   # vendor fipsagents source
 │       └── tools/          # Utility modules
 │           ├── filesystem.py
 │           ├── git.py
@@ -897,6 +936,45 @@ MIT License - see LICENSE file for details
 
 ## Changelog
 
+### Version 0.9.1
+
+- Chore: Realign `tests/` formatting with black 26.3.1 to match CI (v0.9.0's release pipeline failed because local black 24.x produced different output than CI's 26.x; no functional change)
+
+### Version 0.9.0
+
+- Feature: `fips-agents patch` now supports agent and workflow projects in addition to MCP servers (#12)
+- Feature: New `patch chart` and `patch claude` subcommands for agent/workflow projects (#15)
+- Feature: `.template-info` now records `template.type` and (for monorepo templates) `template.subdir` so post-scaffolding commands can route by project type (#13)
+- Feature: New `find_fips_project_root()` walks up to `.template-info`, replacing the MCP-only fastmcp-dependency probe in patch commands (#14)
+- Improvement: `_clone_template_for_patch()` resolves the monorepo subdir during patching, so glob/compare runs against `templates/agent-loop/` instead of the monorepo root (#16)
+- Improvement: Running an MCP-only subcommand inside an agent project (or vice versa) now exits with a clear "available categories" error
+- Improvement: `patch all` enumerates the project's actual category set instead of assuming MCP layout
+- Backwards compat: Projects scaffolded before `template.type` existed default to `mcp-server`; no migration required
+- Tests: 20 new tests in `tests/test_patch.py` covering the type-aware patch flow end-to-end against a fake-scaffolded agent project
+
+### Version 0.8.2
+
+- Test: New `TestGenerateMiddlewareRealTemplate` integration test renders the real v3.x middleware Jinja2 template against each `--hook-type` and the no-flag case, with templates committed under `tests/fixtures/middleware_template/` so the suite runs offline (#3)
+- Chore: `scripts/release.sh` now constructs the release commit message from the version argument using the project convention (`chore: Release fips-agents-cli vX.Y.Z` with optional ` — <summary>`); convention documented in CLAUDE.md (#4)
+- Docs: Drop broken `See Also` links from `.fips-agents-cli/README.md` in scaffolded MCP projects (#5, fixed in `fips-agents/mcp-server-template`)
+- Docs: Updated CLAUDE.md release section to reflect the new release-script signature
+
+### Version 0.8.1
+
+- Docs: Updated CLAUDE.md current-status line and added release-process notes
+- Chore: Repository hardening — added CODEOWNERS and enabled main branch protection
+- Chore: Black formatting drift cleanup; removed remaining "framework" language from docs in favor of "toolkit"
+- Chore: `.venv/` and `NEXT_SESSION.md` gitignored
+
+### Version 0.8.0
+
+- Feature: New `--vendored` flag on `create agent` copies fipsagents source instead of PyPI dependency
+- Feature: New `fips-agents vendor` command for post-scaffold vendoring of existing projects
+- Feature: `fips-agents vendor --update` refreshes vendored source from upstream
+- Feature: `fips-agents vendor --version` pins to a specific fipsagents release tag
+- Fix: `customize_agent_project` now removes monorepo Makefile install line (matching workflow template behavior)
+- Fix: Added `redeploy.sh` to agent project customization file list
+
 ### Version 0.7.0
 
 - Feature: New `add` command group for composable agent capabilities

{fips_agents_cli-0.7.0 → fips_agents_cli-0.9.1}/README.md

@@ -112,6 +112,7 @@ fips-agents add --help
 fips-agents create --help
 fips-agents generate --help
 fips-agents patch --help
+fips-agents vendor --help
 ```
 
 ---
@@ -183,6 +184,12 @@ Creates an AI agent project from the [agent-template](https://github.com/fips-ag
 
 **Options:** Same as `create mcp-server` (see shared options table above).
 
+**Additional option:**
+
+| Option | Description |
+|--------|-------------|
+| `--vendored` | Copy fipsagents source into the project instead of using PyPI dependency |
+
 **Examples:**
 
 ```bash
@@ -194,6 +201,9 @@ fips-agents create agent my-agent --github --org fips-agents
 
 # Non-interactive mode
 fips-agents create agent my-agent --yes --local
+
+# Create with vendored fipsagents source
+fips-agents create agent my-agent --vendored --local
 ```
 
 #### `create gateway`
@@ -514,7 +524,9 @@ When using `--params` with `generate tool` or `generate prompt`, provide a JSON
 
 ### Patch Commands
 
-The `patch` command group updates files in existing MCP server projects from the upstream template repository without overwriting your custom code. It shows interactive diffs for files that may contain customizations.
+The `patch` command group updates files in existing projects from the upstream template repository without overwriting your custom code. It shows interactive diffs for files that may contain customizations.
+
+Supported project types: **MCP server**, **agent**, **workflow**. The available category subcommands depend on the project type — `patch` reads `template.type` from `.template-info` and surfaces a clear error if you run a category that doesn't apply (e.g. `patch generators` inside an agent project).
 
 Run these commands from within your project directory.
 
@@ -524,47 +536,35 @@ Run these commands from within your project directory.
 fips-agents patch check
 ```
 
-Check for available template updates. Shows what files have changed in the template since your project was created, organized by category.
-
-#### `patch generators`
-
-```bash
-fips-agents patch generators [--dry-run]
-```
-
-Update code generator templates (Jinja2 templates in `.fips-agents-cli/generators/`).
-
-#### `patch core`
-
-```bash
-fips-agents patch core [--dry-run]
-```
-
-Update core infrastructure files (loaders, server bootstrap).
+Check for available template updates. Shows what files have changed in the template since your project was created, organized by category. Works for any supported project type.
 
-#### `patch docs`
+#### `patch all`
 
 ```bash
-fips-agents patch docs [--dry-run]
+fips-agents patch all [--dry-run] [--skip-confirmation]
 ```
 
-Update documentation files and examples.
+Update every category that applies to the current project type. Prompts for confirmation before starting unless `--skip-confirmation` is passed.
 
-#### `patch build`
+#### MCP server categories
 
-```bash
-fips-agents patch build [--dry-run]
-```
+| Subcommand           | Patches                                                                  |
+|----------------------|--------------------------------------------------------------------------|
+| `patch generators`   | Jinja2 templates in `.fips-agents-cli/generators/`                       |
+| `patch core`         | Core infrastructure (loaders, server bootstrap)                          |
+| `patch docs`         | Documentation files and examples                                         |
+| `patch build`        | Build and deployment files (Makefile, Containerfile)                     |
 
-Update build and deployment files (Makefile, Containerfile).
+#### Agent / workflow categories
 
-#### `patch all`
+| Subcommand     | Patches                                                                       |
+|----------------|-------------------------------------------------------------------------------|
+| `patch chart`  | Helm chart templates (`chart/templates/**`, `chart/Chart.yaml`)                |
+| `patch docs`   | `CLAUDE.md`, `AGENTS.md`, `docs/**`                                            |
+| `patch build`  | `Makefile`, `Containerfile`, `deploy.sh`, `redeploy.sh`                        |
+| `patch claude` | Claude Code slash commands shipped with the template (`.claude/commands/**`)   |
 
-```bash
-fips-agents patch all [--dry-run] [--skip-confirmation]
-```
-
-Update all patchable file categories at once. Prompts for confirmation before starting unless `--skip-confirmation` is passed.
+User-customized files are never patched: for MCP this means `src/tools/`, `src/resources/`, `src/prompts/`, `src/middleware/`, `pyproject.toml`, etc. For agent/workflow it means `src/agent.py`, `agent.yaml`, `chart/values.yaml`, `src/fipsagents/**` (managed by `fips-agents vendor`), and `pyproject.toml`.
 
 All patch subcommands (except `check`) accept `--dry-run` to preview changes without modifying files.
 
@@ -602,6 +602,45 @@ cd my-research-agent
 fips-agents add code-executor
 ```
 
+---
+
+### Vendor Commands
+
+The `vendor` command copies the fipsagents source into your agent project, replacing the PyPI dependency. This gives you full control over the fipsagents code.
+
+#### `vendor`
+
+```bash
+fips-agents vendor [OPTIONS]
+```
+
+Copies fipsagents source into `src/fipsagents/` and rewrites `pyproject.toml` to use individual dependencies instead of the fipsagents package.
+
+**Options:**
+
+| Option | Description |
+|--------|-------------|
+| `--update` | Update an already-vendored project with the latest upstream source |
+| `--version TEXT` | Vendor a specific version tag (e.g., `fipsagents-v0.7.0`). Default: latest main |
+
+**Examples:**
+
+```bash
+# Vendor into current project
+fips-agents vendor
+
+# Vendor a specific version
+fips-agents vendor --version fipsagents-v0.7.0
+
+# Update vendored source from upstream
+fips-agents vendor --update
+```
+
+**When to use vendored vs. PyPI:**
+
+- **PyPI dependency** (default): Best for teams running multiple agents that share the same fipsagents version. Centralized updates.
+- **Vendored source**: Best for agents that need custom BaseAgent modifications, environments with no PyPI access, or when you want to read and debug the fipsagents source locally.
+
 ## Project Name Requirements
 
 Project names must follow these rules:
@@ -630,10 +669,9 @@ pytest
 
 ```bash
 cd my-research-agent
-python -m venv venv
-source venv/bin/activate
-pip install -e .[dev]
-pytest
+make install         # Create venv, install dependencies
+make run-local       # Start HTTP server on port 8080
+make test            # Run tests
 # See AGENTS.md for the /plan-agent slash command workflow
 ```
 
@@ -745,7 +783,8 @@ fips-agents-cli/
 │       │   ├── create.py   # create mcp-server, agent, gateway, ui
 │       │   ├── generate.py # generate tool/resource/prompt/middleware
 │       │   ├── model_car.py # create model-car
-│       │   └── patch.py    # patch command
+│       │   ├── patch.py    # patch command
+│       │   └── vendor.py   # vendor fipsagents source
 │       └── tools/          # Utility modules
 │           ├── filesystem.py
 │           ├── git.py
@@ -864,6 +903,45 @@ MIT License - see LICENSE file for details
 
 ## Changelog
 
+### Version 0.9.1
+
+- Chore: Realign `tests/` formatting with black 26.3.1 to match CI (v0.9.0's release pipeline failed because local black 24.x produced different output than CI's 26.x; no functional change)
+
+### Version 0.9.0
+
+- Feature: `fips-agents patch` now supports agent and workflow projects in addition to MCP servers (#12)
+- Feature: New `patch chart` and `patch claude` subcommands for agent/workflow projects (#15)
+- Feature: `.template-info` now records `template.type` and (for monorepo templates) `template.subdir` so post-scaffolding commands can route by project type (#13)
+- Feature: New `find_fips_project_root()` walks up to `.template-info`, replacing the MCP-only fastmcp-dependency probe in patch commands (#14)
+- Improvement: `_clone_template_for_patch()` resolves the monorepo subdir during patching, so glob/compare runs against `templates/agent-loop/` instead of the monorepo root (#16)
+- Improvement: Running an MCP-only subcommand inside an agent project (or vice versa) now exits with a clear "available categories" error
+- Improvement: `patch all` enumerates the project's actual category set instead of assuming MCP layout
+- Backwards compat: Projects scaffolded before `template.type` existed default to `mcp-server`; no migration required
+- Tests: 20 new tests in `tests/test_patch.py` covering the type-aware patch flow end-to-end against a fake-scaffolded agent project
+
+### Version 0.8.2
+
+- Test: New `TestGenerateMiddlewareRealTemplate` integration test renders the real v3.x middleware Jinja2 template against each `--hook-type` and the no-flag case, with templates committed under `tests/fixtures/middleware_template/` so the suite runs offline (#3)
+- Chore: `scripts/release.sh` now constructs the release commit message from the version argument using the project convention (`chore: Release fips-agents-cli vX.Y.Z` with optional ` — <summary>`); convention documented in CLAUDE.md (#4)
+- Docs: Drop broken `See Also` links from `.fips-agents-cli/README.md` in scaffolded MCP projects (#5, fixed in `fips-agents/mcp-server-template`)
+- Docs: Updated CLAUDE.md release section to reflect the new release-script signature
+
+### Version 0.8.1
+
+- Docs: Updated CLAUDE.md current-status line and added release-process notes
+- Chore: Repository hardening — added CODEOWNERS and enabled main branch protection
+- Chore: Black formatting drift cleanup; removed remaining "framework" language from docs in favor of "toolkit"
+- Chore: `.venv/` and `NEXT_SESSION.md` gitignored
+
+### Version 0.8.0
+
+- Feature: New `--vendored` flag on `create agent` copies fipsagents source instead of PyPI dependency
+- Feature: New `fips-agents vendor` command for post-scaffold vendoring of existing projects
+- Feature: `fips-agents vendor --update` refreshes vendored source from upstream
+- Feature: `fips-agents vendor --version` pins to a specific fipsagents release tag
+- Fix: `customize_agent_project` now removes monorepo Makefile install line (matching workflow template behavior)
+- Fix: Added `redeploy.sh` to agent project customization file list
+
 ### Version 0.7.0
 
 - Feature: New `add` command group for composable agent capabilities

{fips_agents_cli-0.7.0 → fips_agents_cli-0.9.1}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "hatchling.build"
 
 [project]
 name = "fips-agents-cli"
-version = "0.7.0"
+version = "0.9.1"
 description = "CLI tool for creating and managing FIPS-compliant AI agent projects"
 readme = "README.md"
 requires-python = ">=3.10"

{fips_agents_cli-0.7.0 → fips_agents_cli-0.9.1}/scripts/release.sh

@@ -2,9 +2,20 @@
 #
 # release.sh - Automated release script for fips-agents-cli
 #
-# Usage: ./scripts/release.sh <version> <commit-message>
+# Usage: ./scripts/release.sh <version> [<summary>]
 #
-# Example: ./scripts/release.sh 0.1.2 "Add new feature for X"
+# The release commit message is always constructed from the version using
+# the project convention:
+#
+#     chore: Release fips-agents-cli vX.Y.Z
+#
+# If a summary is provided, it is appended after an em-dash:
+#
+#     chore: Release fips-agents-cli vX.Y.Z — <summary>
+#
+# Examples:
+#   ./scripts/release.sh 0.1.2
+#   ./scripts/release.sh 0.1.2 "Add new generator features"
 #
 
 set -e  # Exit on error
@@ -29,14 +40,16 @@ print_info() {
 }
 
 # Check arguments
-if [ $# -ne 2 ]; then
-    print_error "Usage: $0 <version> <commit-message>"
-    echo "Example: $0 0.1.2 \"Add new feature for X\""
+if [ $# -lt 1 ] || [ $# -gt 2 ]; then
+    print_error "Usage: $0 <version> [<summary>]"
+    echo "Examples:"
+    echo "  $0 0.1.2"
+    echo "  $0 0.1.2 \"Add new generator features\""
     exit 1
 fi
 
 VERSION=$1
-COMMIT_MSG=$2
+SUMMARY=${2:-}
 
 # Validate version format (x.y.z)
 if ! [[ $VERSION =~ ^[0-9]+\.[0-9]+\.[0-9]+$ ]]; then
@@ -45,6 +58,14 @@ if ! [[ $VERSION =~ ^[0-9]+\.[0-9]+\.[0-9]+$ ]]; then
     exit 1
 fi
 
+# Construct the conventional release commit message.
+# Convention: "chore: Release fips-agents-cli vX.Y.Z" with optional " — <summary>".
+if [ -n "$SUMMARY" ]; then
+    COMMIT_MSG="chore: Release fips-agents-cli v${VERSION} — ${SUMMARY}"
+else
+    COMMIT_MSG="chore: Release fips-agents-cli v${VERSION}"
+fi
+
 print_info "Preparing release v$VERSION"
 echo
 

{fips_agents_cli-0.7.0 → fips_agents_cli-0.9.1}/src/fips_agents_cli/cli.py

@@ -7,6 +7,7 @@ from fips_agents_cli.commands.add import add
 from fips_agents_cli.commands.create import create
 from fips_agents_cli.commands.generate import generate
 from fips_agents_cli.commands.patch import patch
+from fips_agents_cli.commands.vendor import vendor
 from fips_agents_cli.version import __version__
 
 console = Console()
@@ -29,6 +30,7 @@ cli.add_command(add)
 cli.add_command(create)
 cli.add_command(generate)
 cli.add_command(patch)
+cli.add_command(vendor)
 
 
 def main():