gcp-pytemplate 0.1.0__tar.gz

gcp_pytemplate-0.1.0/.gitattributes

@@ -0,0 +1,2 @@
+# Auto detect text files and perform LF normalization
+* text=auto

gcp_pytemplate-0.1.0/.github/CODEOWNERS

@@ -0,0 +1 @@
+* @jasonlopez01

gcp_pytemplate-0.1.0/.github/dependabot.yml

@@ -0,0 +1,36 @@
+version: 2
+
+updates:
+  # Only the tool itself is listed here.
+  #
+  # Deliberately excluded:
+  #   src/gcp_pytemplate/templates/  Jinja2 sources; the pyproject.toml there is not valid TOML
+  #                                  until rendered, so nothing can resolve its dependencies.
+  #   examples/                      generated output. Its pyproject.toml files must keep matching
+  #                                  what `make generate-examples` produces, so a bump there would
+  #                                  desync them from the template.
+  - package-ecosystem: "uv"
+    directory: "/"
+    schedule:
+      interval: "weekly"
+    open-pull-requests-limit: 5
+    # chore is non-releasable under [tool.semantic_release], so a dependency bump never cuts a
+    # release on its own. Change to "fix" if you would rather they ship as patch releases.
+    commit-message:
+      prefix: "chore"
+    groups:
+      python-dependencies:
+        patterns:
+          - "*"
+
+  - package-ecosystem: "github-actions"
+    directory: "/"
+    schedule:
+      interval: "weekly"
+    open-pull-requests-limit: 5
+    commit-message:
+      prefix: "ci"
+    groups:
+      github-actions:
+        patterns:
+          - "*"

gcp_pytemplate-0.1.0/.github/workflows/release.yml

@@ -0,0 +1,47 @@
+name: Release
+
+on:
+  workflow_run:
+    workflows: [Tests]
+    types: [completed]
+    branches: [main]
+
+permissions:
+  contents: write  # PSR: push version commit + tag, create GitHub release
+  id-token: write  # PyPI: OIDC trusted publisher (no token needed)
+
+jobs:
+  release:
+    runs-on: ubuntu-latest
+    if: github.event.workflow_run.conclusion == 'success'
+    steps:
+      - uses: actions/checkout@v4
+        with:
+          fetch-depth: 0  # PSR needs full git history to parse commits
+
+      - uses: astral-sh/setup-uv@v5
+
+      - name: Semantic Release
+        id: release
+        uses: python-semantic-release/python-semantic-release@v9
+        with:
+          github_token: ${{ secrets.GITHUB_TOKEN }}
+
+      # Built here rather than through PSR's build_command: that runs inside the PSR container,
+      # which has no uv, so it failed with exit 127. By this point PSR has created the version
+      # tag, so hatch-vcs resolves the real version rather than a .dev local one.
+      - name: Build distributions
+        if: steps.release.outputs.released == 'true'
+        run: uv build
+
+      - name: Publish to PyPI
+        # Note: no credentials needed, the OIDC trusted publisher handles auth
+        if: steps.release.outputs.released == 'true'
+        uses: pypa/gh-action-pypi-publish@release/v1
+
+      - name: Attach distributions to the GitHub Release
+        if: steps.release.outputs.released == 'true'
+        uses: python-semantic-release/publish-action@v9
+        with:
+          github_token: ${{ secrets.GITHUB_TOKEN }}
+          tag: ${{ steps.release.outputs.tag }}

gcp_pytemplate-0.1.0/.github/workflows/tests.yml

@@ -0,0 +1,32 @@
+name: Tests
+
+on:
+  pull_request:
+  push:
+    branches: [main]
+
+jobs:
+  lint:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: astral-sh/setup-uv@v5
+      - run: uv sync --group dev
+      - run: uv run ruff check .
+      - run: uv run ruff format --check .
+
+  test:
+    runs-on: ubuntu-latest
+    strategy:
+      fail-fast: false
+      matrix:
+        python-version: ["3.10", "3.11", "3.12", "3.13", "3.14"]
+    steps:
+      - uses: actions/checkout@v4
+        with:
+          fetch-tags: true  # hatch-vcs needs tags to resolve the package version
+      - uses: astral-sh/setup-uv@v5
+        with:
+          python-version: ${{ matrix.python-version }}
+      - run: uv sync --group dev
+      - run: uv run pytest

gcp_pytemplate-0.1.0/.gitignore

@@ -0,0 +1,223 @@
+# Byte-compiled / optimized / DLL files
+__pycache__/
+*.py[cod]
+*$py.class
+
+# C extensions
+*.so
+
+# Distribution / packaging
+.Python
+build/
+develop-eggs/
+dist/
+downloads/
+eggs/
+.eggs/
+lib/
+lib64/
+parts/
+sdist/
+var/
+wheels/
+share/python-wheels/
+*.egg-info/
+.installed.cfg
+*.egg
+MANIFEST
+
+# PyInstaller
+#  Usually these files are written by a python script from a template
+#  before PyInstaller builds the exe, so as to inject date/other infos into it.
+*.manifest
+*.spec
+
+# Installer logs
+pip-log.txt
+pip-delete-this-directory.txt
+
+# Unit test / coverage reports
+htmlcov/
+.tox/
+.nox/
+.coverage
+.coverage.*
+.cache
+nosetests.xml
+coverage.xml
+*.cover
+*.py,cover
+.hypothesis/
+.pytest_cache/
+cover/
+
+# Translations
+*.mo
+*.pot
+
+# Django stuff:
+*.log
+local_settings.py
+db.sqlite3
+db.sqlite3-journal
+
+# Flask stuff:
+instance/
+.webassets-cache
+
+# Scrapy stuff:
+.scrapy
+
+# Sphinx documentation
+docs/_build/
+
+# PyBuilder
+.pybuilder/
+target/
+
+# Jupyter Notebook
+.ipynb_checkpoints
+
+# IPython
+profile_default/
+ipython_config.py
+
+# pyenv
+#   For a library or package, you might want to ignore these files since the code is
+#   intended to run in multiple environments; otherwise, check them in:
+# .python-version
+
+# pipenv
+#   According to pypa/pipenv#598, it is recommended to include Pipfile.lock in version control.
+#   However, in case of collaboration, if having platform-specific dependencies or dependencies
+#   having no cross-platform support, pipenv may install dependencies that don't work, or not
+#   install all needed dependencies.
+#Pipfile.lock
+
+# poetry
+#   Similar to Pipfile.lock, it is generally recommended to include poetry.lock in version control.
+#   This is especially recommended for binary packages to ensure reproducibility, and is more
+#   commonly ignored for libraries.
+#   https://python-poetry.org/docs/basic-usage/#commit-your-poetrylock-file-to-version-control
+#poetry.lock
+
+# pdm
+#   Similar to Pipfile.lock, it is generally recommended to include pdm.lock in version control.
+#pdm.lock
+#   pdm stores project-wide configurations in .pdm.toml, but it is recommended to not include it
+#   in version control.
+#   https://pdm.fming.dev/#use-with-ide
+.pdm.toml
+
+# PEP 582; used by e.g. github.com/David-OConnor/pyflow and github.com/pdm-project/pdm
+__pypackages__/
+
+# Celery stuff
+celerybeat-schedule
+celerybeat.pid
+
+# SageMath parsed files
+*.sage.py
+
+# Environments
+.venv
+env/
+venv/
+ENV/
+env.bak/
+venv.bak/
+
+# Spyder project settings
+.spyderproject
+.spyproject
+
+# Rope project settings
+.ropeproject
+
+# mkdocs documentation
+/site
+
+# mypy
+.mypy_cache/
+.dmypy.json
+dmypy.json
+
+# Pyre type checker
+.pyre/
+
+# pytype static type analyzer
+.pytype/
+
+# Cython debug symbols
+cython_debug/
+
+# PyCharm
+#  JetBrains specific template is maintained in a separate JetBrains.gitignore that can
+#  be found at https://github.com/github/gitignore/blob/main/Global/JetBrains.gitignore
+#  and can be added to the global gitignore or merged into this file.  For a more nuclear
+#  option (not recommended) you can uncomment the following to ignore the entire idea folder.
+ .idea/
+
+
+# VSCode
+.vscode/*
+!.vscode/settings.json
+!.vscode/tasks.json
+!.vscode/launch.json
+!.vscode/extensions.json
+!.vscode/*.code-snippets
+
+# Local History for Visual Studio Code
+.history/
+
+# Built Visual Studio Code Extensions
+*.vsix
+
+# Mac files
+**/.DS_Store
+
+
+# Terraform
+
+# Local .terraform directories
+**/.terraform/*
+
+# .tfstate files
+*.tfstate
+*.tfstate.*
+
+# Crash log files
+crash.log
+
+# Exclude all .tfvars files, which are likely to contain sentitive data, such as
+# password, private keys, and other secrets. These should not be part of version
+# control as they are data points which are potentially sensitive and subject
+# to change depending on the environment.
+#
+*.tfvars
+
+# Ignore override files as they are usually used to override resources locally and so
+# are not checked in
+override.tf
+override.tf.json
+*_override.tf
+*_override.tf.json
+
+# Include override files you do wish to add to version control using negated pattern
+#
+# !example_override.tf
+
+# Include tfplan files to ignore the plan output of command: terraform plan -out=tfplan
+# example: *tfplan*
+
+# Ignore CLI configuration files
+.terraformrc
+terraform.rc
+
+
+# Added:
+secrets/
+TODO
+
+# Per-machine Claude Code settings (contains local absolute paths)
+.claude/settings.local.json

gcp_pytemplate-0.1.0/.mcp.json

@@ -0,0 +1,7 @@
+{
+    "mcpServers": {
+        "gcp-pytemplate": {
+            "command": "gcp-pytemplate-mcp"
+        }
+    }
+}

gcp_pytemplate-0.1.0/.pre-commit-config.yaml

@@ -0,0 +1,17 @@
+repos:
+  - repo: https://github.com/pre-commit/pre-commit-hooks
+    rev: v5.0.0
+    hooks:
+      - id: trailing-whitespace
+      - id: end-of-file-fixer
+      # Files under templates/ contain Jinja2 syntax and are not valid TOML/YAML until rendered.
+      - id: check-yaml
+        exclude: ^src/gcp_pytemplate/templates/
+      - id: check-toml
+        exclude: ^src/gcp_pytemplate/templates/
+
+  - repo: https://github.com/commitizen-tools/commitizen
+    rev: v4.1.0
+    hooks:
+      - id: commitizen
+        stages: [commit-msg]

gcp_pytemplate-0.1.0/.python-version

@@ -0,0 +1 @@
+3.13

gcp_pytemplate-0.1.0/AGENTS.md

@@ -0,0 +1,115 @@
+# gcp-pytemplate — Agent Guide
+
+A CLI tool that scaffolds production-ready GCP Python projects. It renders a Jinja2 template tree into a new project directory.
+
+## Commands
+
+Use `make` for all core operations.
+
+| Command | Description |
+|---|---|
+| `make setup` | Install dependencies and git hooks |
+| `make install` | Install CLI and MCP server globally as editable (source changes apply immediately) |
+| `make lint` | Lint and autoformat (ruff) |
+| `make test` | Run tests |
+| `make test-all` | Run tests against all supported Python versions (3.10–3.14) |
+| `make generate-examples` | Regenerate `examples/` from the YAML files in `examples/*.yaml` |
+
+Do not invoke `uv`, `ruff`, or `pytest` directly — use the make targets above.
+
+### MCP server
+
+```bash
+gcp-pytemplate-mcp   # starts the stdio MCP server (requires the [mcp] extra)
+```
+
+See the **MCP Server** section in `README.md` for installation and client config.
+
+### Running the CLI
+
+```bash
+uv run gcp-pytemplate new                              # interactive prompts
+uv run gcp-pytemplate new --from-file examples/api_project.yaml
+uv run gcp-pytemplate update <project-path> --components logging_config
+```
+
+## Project Layout
+
+- `src/gcp_pytemplate/main.py` — Typer CLI (`new` and `update` commands), input validation, Jinja2 context assembly
+- `src/gcp_pytemplate/render.py` — walks the template tree, renders file contents and paths with Jinja2
+- `src/gcp_pytemplate/templates/app/{{ project_slug }}/` — the project template (Jinja2; not valid Python until rendered)
+- `examples/` — pre-generated example projects (`example-api-service`, `example-cli-job`) plus the YAML inputs used to generate them
+- `src/gcp_pytemplate/mcp_server.py` — MCP server (`create_project`, `update_project`, `list_components` tools)
+- `tests/` — `test_render.py` (template output), `test_update.py` (update command), `test_mcp_server.py` (MCP tools)
+
+## Coding Standards
+
+**Use Pydantic for data modeling.** Prefer `pydantic.BaseModel` over native `@dataclass` for any structured data (config objects, request/response shapes, context models). Use `model_validator` and `field_validator` for validation logic rather than `__post_init__`. Pydantic models are the single source of truth for schema, validation, and serialization.
+
+**Use modern Python type hints.** Target Python 3.10+ syntax throughout:
+- Built-in generics: `list[str]`, `dict[str, int]`, `tuple[str, ...]` — not `List`, `Dict`, `Tuple` from `typing`
+- Union shorthand: `str | None` — not `Optional[str]` or `Union[str, None]`
+- `typing.Any`, `typing.Literal`, `typing.TypeVar`, `typing.Protocol` are still fine where needed
+- Annotate all function signatures (parameters and return types); omit only where the type is genuinely unknowable
+
+**Write pytest-style tests.** Use plain functions (`def test_*`) and `assert` statements — no `unittest.TestCase`. Fixtures go in `conftest.py`. Parametrize with `@pytest.mark.parametrize` rather than looping inside a test. Use `tmp_path` for filesystem fixtures. Avoid mocking internals; test at the public API surface.
+
+## Key Rules
+
+**CLI and MCP server must stay in sync.** When adding or changing inputs to the `new` command in `main.py` (parameters, defaults, validation, resolution logic), apply the equivalent change to `create_project` in `mcp_server.py`. Both share `_build_context()` for validation, but default resolution (e.g. git/gcloud config lookups) and the elicitation summary in `_format_summary` must be updated manually to match.
+
+**Templates and examples must stay in sync.** When editing any file under `templates/`, apply the equivalent change to the corresponding file in `examples/example-api-service/` and/or `examples/example-cli-job/`. Alternatively, run `make generate-examples` to fully regenerate both examples (only appropriate when the change should affect all generated content, not for manual example-specific edits).
+
+**Templates are excluded from ruff.** Files under `src/gcp_pytemplate/templates/` contain Jinja2 syntax and are not valid Python — ruff is configured to skip them. Don't run linting on template files.
+
+**A `.jinja` suffix on a template file is stripped when rendered.** `pyproject.toml.jinja` renders to `pyproject.toml`. Use this for any template whose real filename would make external tooling try to parse it: under its real name, GitHub's dependency graph picked up the template `pyproject.toml` as a pip manifest and failed on the Jinja2 syntax. The suffix is stripped before the exclusion rules in `render.py` are evaluated, so those rules are written against the final path.
+
+**Keep documentation in sync.** When making changes that affect functionality or interfaces (CLI flags, MCP tools, Python version support, make targets, project layout), update `README.md` and `AGENTS.md` to match. The Prerequisites, Usage, and Development sections of `README.md` and the Commands table in `AGENTS.md` are the primary places to check.
+
+**Commit style: conventional commits.** Pre-commit hooks enforce the format. Prefixes and their effect on versioning and the changelog:
+
+| Prefix | Version bump | In changelog |
+|---|---|---|
+| `feat:` | minor | yes |
+| `fix:`, `perf:` | patch | yes |
+| `docs:` | none | yes |
+| `chore:`, `ci:`, `style:`, `test:`, `refactor:` | none | no |
+
+## SQL Conventions
+
+**Use fully qualified resource paths.** Always reference tables with their full path — no bare table names:
+- BigQuery: `project.dataset.table`
+- Other databases: `database.schema.table`
+
+**Use lowercase keywords.** Write all SQL keywords in lowercase: `select`, `from`, `where`, `join`, `group by`, `order by`, etc.
+
+**Use single spaces around aliases.** No alignment padding — exactly one space on each side of `as`:
+```sql
+-- correct
+select
+    order_id as id,
+    customer_name as name
+from project.dataset.orders
+
+-- wrong
+select
+    order_id     as id,
+    customer_name as name
+from project.dataset.orders
+```
+
+**Use trailing commas.** Place commas at the end of each item in a select list, not the beginning.
+
+**Indent with 4 spaces.** Indent column lists and `on` clauses 4 spaces relative to their clause keyword.
+
+
+## Writing Style
+
+**Avoid AI tells.** Comments, docs, commit messages, and PR descriptions should read like they were written by a developer, not generated. Specific patterns to avoid:
+
+- No em-dashes (`—`). Use a comma, semicolon, colon, or rewrite the sentence.
+- No filler openers: "Certainly", "Sure", "Of course", "Absolutely", "Great", "Happy to help".
+- No over-explanation of obvious things. If the code is clear, don't restate it in a comment.
+- No "This commit..." or "This PR..." prefix in commit/PR titles. Start with the verb: "Add", "Fix", "Remove", "Update".
+- No closing affirmations: "Let me know if you have questions", "Hope this helps", "Feel free to reach out".
+- Prefer plain words over formal ones: "use" not "utilize", "show" not "demonstrate", "check" not "verify" when the meaning is the same.

gcp_pytemplate-0.1.0/CHANGELOG.md

@@ -0,0 +1,185 @@
+# CHANGELOG
+
+
+## v0.1.0 (2026-08-06)
+
+### Bug Fixes
+
+- Guard destructive scaffolding and repair generated project defects
+  ([`20be16b`](https://github.com/jasonlopez01/gcp-pytemplate/commit/20be16b8212ae0e155e9acfbf5787b9c2133102e))
+
+The MCP create_project tool silently overwrote an existing project's files. It now refuses a
+  non-empty target unless overwrite=true, validates input before prompting, and warns in the
+  confirmation summary when it will replace a directory. The CLI gained a matching --overwrite flag.
+
+A project name consisting only of punctuation slugified to "", which resolved the project root back
+  to the output directory itself; confirming the overwrite prompt then deleted that directory.
+  Project names are now rejected unless they produce an importable module name.
+
+Jinja2 strips the final newline by default, so every rendered file was written without one and
+  generated projects failed their own ruff format check. Render with keep_trailing_newline and fix
+  the template lint errors this exposed, plus the trailing blank lines it surfaced in the Makefile
+  and deploy configs.
+
+gcp_env raised a ValidationError at import when a runtime set a service name but no revision, and an
+  unreachable metadata server took the whole app down. It also stamped "not-set" over real
+  GCP_PROJECT and GCP_REGION values on local runs; the export is now gated on IS_DEPLOYED and never
+  overwrites.
+
+Also corrects the documented Python version: the tool needs 3.10+, but generated projects pin 3.13+.
+
+Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
+
+- Handle non-text files in the template tree
+  ([`d22c21c`](https://github.com/jasonlopez01/gcp-pytemplate/commit/d22c21ca1bf33b5a842a0ea572357b86c368371f))
+
+A .DS_Store inside the template root aborted the whole render with an uncaught UnicodeDecodeError.
+  Because it sorts first, no files were written at all, and the traceback did not name the offending
+  file. Only jinja2.TemplateError was caught, so the decode error escaped.
+
+Skip OS metadata by name, since it should never reach a generated project, and fall back to copying
+  any file that is not valid UTF-8 rather than trying to render it. Binary assets in the template
+  now pass through untouched.
+
+Pin the read and write encoding to UTF-8 and write with newline="" so output does not depend on the
+  host locale, and so rendered shell scripts and Procfiles keep LF endings on Windows hosts instead
+  of gaining CRLF.
+
+render_service takes an optional template_root so tests can render a fixture tree instead of the
+  packaged one; the five new tests each fail against the specific defect they cover.
+
+Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
+
+- Keep per-machine Claude Code settings out of the sdist
+  ([`a975aa1`](https://github.com/jasonlopez01/gcp-pytemplate/commit/a975aa1b00cf449e7486afaa94af119b14822cad))
+
+.claude/settings.local.json was reaching the published sdist, carrying local absolute paths. It is
+  untracked only because of a user-level global gitignore, which hatchling does not read.
+
+Ignore it in the repo and exclude /.claude from the sdist target so the result does not depend on
+  how an individual clone is configured.
+
+Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
+
+- Pin example authors so regeneration is user-independent
+  ([`850d24c`](https://github.com/jasonlopez01/gcp-pytemplate/commit/850d24c4dc592d87276be1be1636b6b882ca3756))
+
+The example YAML inputs omitted author_name and author_email, so 'new' fell back to the git config
+  of whoever ran make generate-examples and wrote that identity into each example's pyproject.toml
+  and .gcp-pytemplate.yaml.
+
+Set both fields explicitly to a documentation address (RFC 2606) so the examples regenerate
+  byte-identically for any contributor.
+
+Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
+
+- Rename the template pyproject so tooling stops parsing it
+  ([`4854701`](https://github.com/jasonlopez01/gcp-pytemplate/commit/4854701cd3100663f7c317fa00c5a465d8f854dd))
+
+GitHub's dependency graph scans the repo for manifests by filename, found
+  src/gcp_pytemplate/templates/app/{{ project_slug }}/pyproject.toml, and failed on the Jinja2
+  syntax. That produced a failing "Graph Update: pip in ..." job on every scan. Dependabot config
+  cannot exclude a path from the graph, so the file has to stop looking like a manifest.
+
+render.py now strips a trailing .jinja from the rendered path, and the template is named
+  pyproject.toml.jinja. Stripping happens before the exclusion rules are evaluated so those rules
+  stay written against final paths.
+
+Rendered output is unchanged: both examples regenerate byte-identically, and a project scaffolded
+  from the built wheel still produces a parseable pyproject.toml with no .jinja files left behind.
+
+Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
+
+- Serve the health check at the configured route
+  ([`28193f8`](https://github.com/jasonlopez01/gcp-pytemplate/commit/28193f8b867b430debc974f72fea373f51292039))
+
+HEALTH_CHECK_ROUTE was defined in app_config and set in the app config env files, but main_api
+  hardcoded "/healthcheck", so changing the setting had no effect. Bind the route to
+  APP_CONFIG.HEALTH_CHECK_ROUTE and read it from the same config in the generated test.
+
+invoke_cloud_run.sh --health also assumed the default path. It now resolves the route from the app
+  config named by the deploy config, falling back to /healthcheck, so the shorthand keeps working on
+  a customized route.
+
+Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
+
+- Validate update paths and fail cleanly without a terminal
+  ([`3b8f40d`](https://github.com/jasonlopez01/gcp-pytemplate/commit/3b8f40d5871d56e92ec6092fb90421273e76e0eb))
+
+The MCP update_project tool rejected absolute and parent-relative --files paths, but the CLI update
+  command did not, and an absolute path there crashed with an unhandled ValueError from relative_to
+  when printing results. Move the check into a shared _validate_rel_paths helper so both entry
+  points enforce it.
+
+The questionary prompts also raised an opaque OSError with a full traceback when stdin was not a
+  terminal, which made scripted use of new and update unusable. Fall back to the documented defaults
+  for the interfaces and deploy target prompts, decline the overwrite prompt (pointing at
+  --overwrite), and require --components or --files for update. Aborting because the target exists
+  now exits 1 instead of 0.
+
+Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
+
+### Documentation
+
+- Add security and codeowners
+  ([`b3741d1`](https://github.com/jasonlopez01/gcp-pytemplate/commit/b3741d128d6240c17b9a4a0a8403571d96b55a01))
+
+- Correct the deploy script referenced by execute_cloud_run_job
+  ([`81eccc1`](https://github.com/jasonlopez01/gcp-pytemplate/commit/81eccc1baaac666e0f3aafd6ae493d4fdc15c42e))
+
+The requirements comment pointed at deploy_job_from_image.sh, which is not part of the template; the
+  script that deploys the job is deploy_cloud_run_job.sh.
+
+Also record why args travel in an env var, and that --update-env-vars on 'jobs execute' is a
+  per-execution override rather than an edit to the deployed job definition.
+
+Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
+
+- Update agent guides
+  ([`0730b28`](https://github.com/jasonlopez01/gcp-pytemplate/commit/0730b28848969191f562e67504520cbb3b6e28c5))
+
+- Update docs
+  ([`d583193`](https://github.com/jasonlopez01/gcp-pytemplate/commit/d583193bca7784dc9451fb163633ef0393a5d1f6))
+
+- Update examples
+  ([`b583a45`](https://github.com/jasonlopez01/gcp-pytemplate/commit/b583a45454b798eb0bb9ed6fd542b650614993bc))
+
+- Update notes
+  ([`0c0404f`](https://github.com/jasonlopez01/gcp-pytemplate/commit/0c0404f84b1865d034aeef262e3ff8b96e51721e))
+
+- Update readmes
+  ([`7d3ab3d`](https://github.com/jasonlopez01/gcp-pytemplate/commit/7d3ab3ddcbc8b2c29ef8bcca8c578f30d9c361d5))
+
+### Features
+
+- Collect an author name only, never an email
+  ([`9bd8e7c`](https://github.com/jasonlopez01/gcp-pytemplate/commit/9bd8e7c7ffa53ef39079da12a9bc6fbfab86f94d))
+
+Author was the one input resolved silently: gcp_project, gcp_region and gcp_service_account are all
+  prompted with a visible default, while name and email were read from git config and written into
+  the generated project without ever being shown. Prompt for the name with git config as the default
+  so the identity that lands in pyproject.toml is always something the user saw, and drop email
+  collection entirely. Users who want an email published can add the key to their pyproject.toml by
+  hand.
+
+The generated authors block is now conditional. An empty entry is a hard build failure ("Author #1
+  of field project.authors must specify either name or email"), which create_project could already
+  produce on a machine with no git identity because it fell back to empty strings while the CLI fell
+  back to placeholder text. Both now agree, and the field is omitted rather than emitted blank.
+
+Removes the --author-email flag and the author_email tool argument.
+
+Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
+
+- Log unhandled request errors and report env in the health check
+  ([`8e2c6c3`](https://github.com/jasonlopez01/gcp-pytemplate/commit/8e2c6c38320f8fb8a25dfe7f10faeab03bbd49fb))
+
+The request logging middleware wrapped call_next without a handler, so an unhandled error in a route
+  produced no request log line at all, only the server's own traceback. Wrap it, emit the failure
+  with its duration, and re-raise.
+
+The health check hardcoded the project slug as the service name, which drifts from whatever APP_NAME
+  the loaded config sets. Source both the service name and the environment from APP_CONFIG so the
+  response follows APP_CONFIG_FILE.
+
+Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

gcp_pytemplate-0.1.0/CLAUDE.md

@@ -0,0 +1 @@
+@AGENTS.md