feat: add GCP Artifact Registry publishing workflow

.claude/README.md

@@ -4,7 +4,7 @@ This directory contains Claude Code configuration and standards for this project
 
 ## Directory Structure
 
-```
+```text
 .claude/
 ├── README.md           # This file
 ├── claude.md           # Project-specific Claude guidelines
@@ -94,6 +94,7 @@ git subtree push --prefix .claude/standard \
 3. **Project Overrides**: Finally loads `.claude/claude.md` (project-specific)
 
 This layered approach ensures:
+
 - Consistent standards across all projects
 - Project flexibility where needed
 - Easy updates to universal guidelines

.claude/agents/code-reviewer.md

@@ -9,24 +9,28 @@ Review code changes for quality, maintainability, and adherence to project stand
 ## Capabilities
 
 ### Code Analysis
+
 - Identify code smells and anti-patterns
 - Check adherence to Python best practices
 - Evaluate code complexity and maintainability
 - Detect potential bugs and edge cases
 
 ### Standards Compliance
+
 - Verify PEP 8 and project style guide compliance
 - Check type annotation completeness
 - Validate docstring coverage and quality
 - Ensure consistent naming conventions
 
 ### Security Review
+
 - Identify potential security vulnerabilities
 - Check for hardcoded secrets or credentials
 - Validate input handling and sanitization
 - Review authentication and authorization logic
 
 ### Performance Review
+
 - Identify potential performance bottlenecks
 - Check for unnecessary database queries (N+1)
 - Review memory usage patterns
@@ -35,31 +39,35 @@ Review code changes for quality, maintainability, and adherence to project stand
 ## Review Checklist
 
 ### Code Quality
+
 - [ ] Code is readable and self-documenting
 - [ ] Functions are single-purpose (SRP)
 - [ ] No unnecessary complexity
 - [ ] Error handling is appropriate
 
 ### Testing
+
 - [ ] Tests cover new functionality
 - [ ] Edge cases are tested
 - [ ] Test names are descriptive
 - [ ] Mocks are used appropriately
 
 ### Documentation
+
 - [ ] Public APIs are documented
 - [ ] Complex logic has comments
 - [ ] README updated if needed
 - [ ] CHANGELOG entry added
 
 ### Security
+
 - [ ] No hardcoded secrets
 - [ ] Input validation present
 - [ ] SQL injection prevented
 - [ ] XSS prevention in place
 
 ## Invocation
 
-```
+```text
 /review or via Task tool with subagent_type='code-reviewer'
 ```

.claude/agents/merge-standards.md

@@ -94,7 +94,7 @@ This agent helps merge updated baseline standards from `.standards/` into the pr
 
 ## Merge Process
 
-```
+```text
 1. Read both baseline and target files
 2. Identify what changed in baseline (git diff .standards/)
 3. For each change:
@@ -106,7 +106,7 @@ This agent helps merge updated baseline standards from `.standards/` into the pr
 
 ## Example Usage
 
-```
+```text
 User: "Merge the updated baseline standards"
 
 Agent:

.claude/agents/security-auditor.md

@@ -9,24 +9,28 @@ Proactively identify and mitigate security vulnerabilities, ensure compliance wi
 ## Capabilities
 
 ### Vulnerability Detection
+
 - Static code analysis for security issues
 - Dependency vulnerability scanning
 - Secret detection and prevention
 - Configuration security review
 
 ### Threat Assessment
+
 - Identify attack vectors
 - Assess risk levels
 - Prioritize security fixes
 - Document security findings
 
 ### Compliance Validation
+
 - OWASP Top 10 compliance
 - Security policy adherence
 - Secure coding standards
 - Audit trail verification
 
 ### Security Testing
+
 - Injection attack testing
 - Authentication testing
 - Authorization testing
@@ -35,6 +39,7 @@ Proactively identify and mitigate security vulnerabilities, ensure compliance wi
 ## Security Checklist
 
 ### Code Security
+
 - [ ] No hardcoded credentials
 - [ ] Input validation on all user input
 - [ ] Output encoding for XSS prevention
@@ -43,18 +48,21 @@ Proactively identify and mitigate security vulnerabilities, ensure compliance wi
 - [ ] Proper error handling (no info leakage)
 
 ### Dependency Security
+
 - [ ] No known vulnerabilities in dependencies
 - [ ] Dependencies up to date
 - [ ] Minimal dependency footprint
 - [ ] Trusted sources only
 
 ### Configuration Security
+
 - [ ] Secrets in environment variables
 - [ ] Secure default configurations
 - [ ] TLS/SSL properly configured
 - [ ] CORS properly restricted
 
 ### Authentication & Authorization
+
 - [ ] Strong password policies
 - [ ] Secure session management
 - [ ] Role-based access control
@@ -91,6 +99,6 @@ gitleaks detect --source .
 
 ## Invocation
 
-```
+```text
 /security or via Task tool with subagent_type='security-auditor'
 ```

.claude/agents/test-engineer.md

@@ -9,24 +9,28 @@ Design and implement test strategies, generate test cases, and ensure code quali
 ## Capabilities
 
 ### Test Strategy
+
 - Design test plans and strategies
 - Identify critical paths for testing
 - Balance unit, integration, and e2e tests
 - Define coverage targets and metrics
 
 ### Test Generation
+
 - Generate unit tests for new code
 - Create integration test scenarios
 - Design edge case and boundary tests
 - Implement property-based tests
 
 ### Test Review
+
 - Review existing test quality
 - Identify gaps in test coverage
 - Suggest test improvements
 - Validate test isolation
 
 ### Test Automation
+
 - Configure CI/CD test pipelines
 - Set up parallel test execution
 - Implement test reporting
@@ -35,12 +39,14 @@ Design and implement test strategies, generate test cases, and ensure code quali
 ## Testing Standards
 
 ### Coverage Requirements
+
 - **Minimum Coverage**: 80%
 - **Branch Coverage**: Enabled
 - **Critical Paths**: 100% coverage
 
 ### Test Organization
-```
+
+```text
 tests/
 ├── unit/           # Fast, isolated tests
 ├── integration/    # Service integration tests
@@ -50,6 +56,7 @@ tests/
 ```
 
 ### Test Quality Criteria
+
 - Tests are deterministic (no flaky tests)
 - Tests are isolated (no shared state)
 - Tests are fast (< 1s for unit tests)
@@ -74,6 +81,6 @@ uv run mutmut run
 
 ## Invocation
 
-```
+```text
 /test or via Task tool with subagent_type='test-engineer'
 ```

.claude/commands/merge-standards.md

@@ -5,6 +5,7 @@ After running `cruft update`, merge any changes from `.standards/` into project
 ## Task
 
 1. Check for changes in baseline files:
+
    ```bash
    git diff .standards/
    ```

.claude/commands/plan.md

@@ -32,14 +32,16 @@ Using the `project-planning` skill, generate these four documents with expert re
 For EACH document, follow this generate-review-refine cycle:
 
 ### 1. Generate Document
+
 - Read the corresponding template from `.claude/skills/project-planning/templates/`
 - Generate project-specific content based on the user's description
 - Write to the appropriate location in `docs/planning/`
 
 ### 2. Expert Review (Consensus)
+
 After writing each document, request expert review:
 
-```
+```text
 mcp__zen__consensus with gemini-3-pro-preview:
 
 Review this [Document Type] for Python Libs.
@@ -60,12 +62,15 @@ DOCUMENT:
 ```
 
 ### 3. Refine if Needed
+
 - If NEEDS REVISION: Incorporate feedback and re-submit for review
 - If READY: Proceed to next document
 - Each document must be READY before generating the next
 
 ### 4. Final Validation
+
 After all documents pass review:
+
 - Run validation script
 - Ensure cross-references are valid
 - Summarize outcomes
@@ -99,6 +104,7 @@ This project was created from the cookiecutter-python-template with:
 ## Fallback (No MCP Server)
 
 If `mcp__zen__consensus` is not available:
+
 - Skip the expert review step
 - Generate all documents sequentially
 - Run validation script for basic checks

.claude/commands/pr.md

@@ -42,9 +42,9 @@ Analyze the current branch and prepare a PR description following the project te
 <!-- Optional: known issues, follow-up work -->
 ```
 
-4. **Output the PR description** ready to copy-paste into GitHub.
+1. **Output the PR description** ready to copy-paste into GitHub.
 
-5. **Suggest a PR title** following conventional commits:
+2. **Suggest a PR title** following conventional commits:
    - `feat:` for new features
    - `fix:` for bug fixes
    - `docs:` for documentation
@@ -57,7 +57,8 @@ Analyze the current branch and prepare a PR description following the project te
 **Title**: `feat: add user authentication with OAuth2`
 
 **Description**:
-```
+
+```markdown
 ## Summary
 
 Add OAuth2 authentication flow supporting Google and GitHub providers.

.claude/commands/quality.md

@@ -4,11 +4,12 @@ Run code quality checks including formatting, linting, and type checking.
 
 ## Usage
 
-```
+```text
 /quality [scope]
 ```
 
 **Arguments:**
+
 - `scope` (optional): `all`, `format`, `lint`, `types` (default: `all`)
 
 ## Workflow
@@ -21,22 +22,26 @@ Run code quality checks including formatting, linting, and type checking.
 ## Commands Executed
 
 ### Format
+
 ```bash
 uv run black --check .
 uv run ruff format --check .
 ```
 
 ### Lint
+
 ```bash
 uv run ruff check .
 ```
 
 ### Types
+
 ```bash
 uv run basedpyright src/
 ```
 
 ### All (Pre-commit)
+
 ```bash
 uv run pre-commit run --all-files
 ```
@@ -50,6 +55,7 @@ uv run pre-commit run --all-files
 ## Fix Issues
 
 To automatically fix formatting and some lint issues:
+
 ```bash
 uv run black .
 uv run ruff check --fix .