scaffold-ca-python 0.1.2__tar.gz → 0.1.3__tar.gz

{scaffold_ca_python-0.1.2 → scaffold_ca_python-0.1.3}/.github/agents/copilot-instructions.md

@@ -7,7 +7,7 @@ Auto-generated from all feature plans. Last updated: 2026-04-20
 - N/A — file I/O only via `FileWriter` / `TemplateRenderer` (008-fastapi-entrypoint-baseline)
 - Python 3.13 + FastAPI ≥ 0.135.2, uvicorn[standard] ≥ 0.20, dependency-injector ≥ 4.49.0, pydantic-settings ≥ 2.13.1, Jinja2 ≥ 3.1, pydantic ≥ 2.0, typer ≥ 0.16, rich ≥ 14.1 (009-app-factory-split)
 - N/A (code-generation tool; no database) (009-app-factory-split)
-- Python 3.13 + yper, Rich (CLI); tomllib + tomli_w (TOML read/write); pytest + pytest-cov (testing); ruff (lint/format); mypy strict (types) (011-fix-restapi-cleanup)
+- Python 3.13 + Typer, Rich (CLI); tomllib + tomli_w (TOML read/write); pytest + pytest-cov (testing); ruff (lint/format); mypy strict (types) (011-fix-restapi-cleanup)
 - Local filesystem — `pyproject.toml` (TOML), `main.py` (plain file delete) (011-fix-restapi-cleanup)
 - Python 3.13 + Jinja2 (template rendering), Pydantic v2 (generated schema model), FastAPI + Starlette (generated test client), pytest + pytest-cov (testing), ruff (lint/format), mypy strict (types), uv (package management) (012-fix-restapi-test-templates)
 - Local filesystem — Jinja2 `.jinja2` template files (012-fix-restapi-test-templates)
@@ -15,9 +15,9 @@ Auto-generated from all feature plans. Last updated: 2026-04-20
 - Local filesystem — Path operations only (014-tests-in-src)
 - Python 3.13 + Typer ≥ 0.16, Rich ≥ 14.1, Jinja2 ≥ 3.1, Pydantic v2, uv (015-factory-builder-refactor)
 - File system only (pyproject.toml + generated project files) (015-factory-builder-refactor)
-- Python 3.13+ + yper>=0.16.0, rich>=14.1.0; ruff (linter/formatter), mypy strict (type checker) (016-dedup-command-aliases)
+- Python 3.13+ + Typer>=0.16.0, rich>=14.1.0; ruff (linter/formatter), mypy strict (type checker) (016-dedup-command-aliases)
 - N/A — CLI tool, no database (016-dedup-command-aliases)
-- Python 3.13+ + yper ≥ 0.16, pydantic ≥ 2.0, rich ≥ 14.1, jinja2 ≥ 3.1 (017-pep8-naming-validation)
+- Python 3.13+ + Typer ≥ 0.16, pydantic ≥ 2.0, rich ≥ 14.1, jinja2 ≥ 3.1 (017-pep8-naming-validation)
 - N/A (file generation only) (017-pep8-naming-validation)
 - Python 3.13+ + Typer (CLI), Rich (output), Jinja2 (templates), Pydantic v2 (context models), `mcp>=1.0` (generated project dep), `starlette` (generated project dep), `uvicorn` (generated project dep), `dependency-injector` (generated project dep) (019-mcp-entry-point-restructure)
 - N/A — file system writes only (019-mcp-entry-point-restructure)
@@ -35,7 +35,9 @@ tests/
 
 ## Commands
 
-cd src [ONLY COMMANDS FOR ACTIVE TECHNOLOGIES][ONLY COMMANDS FOR ACTIVE TECHNOLOGIES] pytest [ONLY COMMANDS FOR ACTIVE TECHNOLOGIES][ONLY COMMANDS FOR ACTIVE TECHNOLOGIES] ruff check .
+uv run pytest
+uv run ruff check src tests
+uv run mypy src
 
 ## Code Style
 
@@ -44,7 +46,7 @@ Python 3.13: Follow standard conventions
 ## Recent Changes
 - 020-pypi-publish-readme: Added Python 3.13+ + hatchling (build backend), uv-dynamic-versioning (git-tag versioning, PEP 440), uv (build + publish)
 - 019-mcp-entry-point-restructure: Added Python 3.13+ + Typer (CLI), Rich (output), Jinja2 (templates), Pydantic v2 (context models), `mcp>=1.0` (generated project dep), `starlette` (generated project dep), `uvicorn` (generated project dep), `dependency-injector` (generated project dep)
-- 017-pep8-naming-validation: Added Python 3.13+ + yper ≥ 0.16, pydantic ≥ 2.0, rich ≥ 14.1, jinja2 ≥ 3.1
+- 017-pep8-naming-validation: Added Python 3.13+ + Typer ≥ 0.16, pydantic ≥ 2.0, rich ≥ 14.1, jinja2 ≥ 3.1
 
 
 <!-- MANUAL ADDITIONS START -->

{scaffold_ca_python-0.1.2 → scaffold_ca_python-0.1.3}/.pre-commit-config.yaml

@@ -1,5 +1,10 @@
 # See https://pre-commit.com for more information
 # See https://pre-commit.com/hooks.html for more hooks
+
+# SDD documentation and Spec-Kit tooling are authored artifacts, not source code:
+# keep the fixer/formatter hooks out of them so runs stay scoped to code changes.
+exclude: '^(\.specify/|specs/|\.github/agents/)'
+
 repos:
 -   repo: https://github.com/pre-commit/pre-commit-hooks
     rev: v5.0.0

scaffold_ca_python-0.1.3/.release-please-manifest.json

@@ -0,0 +1,3 @@
+{
+  ".": "0.1.3"
+}

{scaffold_ca_python-0.1.2 → scaffold_ca_python-0.1.3}/.specify/memory/constitution.md

@@ -258,4 +258,4 @@ dependencies listed in Principle III, installed via `uv` at generation time.
 - Compliance reviews MUST occur at the start of each new feature branch and before
   merging to `main`.
 
-**Version**: 1.0.0 | **Ratified**: 2026-03-25 | **Last Amended**: 2026-03-25
+**Version**: 2.0.3 | **Ratified**: 2026-03-25 | **Last Amended**: 2026-04-10

{scaffold_ca_python-0.1.2 → scaffold_ca_python-0.1.3}/CHANGELOG.md

@@ -1,5 +1,12 @@
 # Changelog
 
+## [0.1.3](https://github.com/bancolombia/scaffold-clean-architecture-py/compare/v0.1.2...v0.1.3) (2026-09-17)
+
+
+### Documentation
+
+* clean up SDD specification audit artifacts ([1a0374e](https://github.com/bancolombia/scaffold-clean-architecture-py/commit/1a0374e5895864718b9c6ee7b0990023942441fa))
+
 ## [0.1.2](https://github.com/bancolombia/scaffold-clean-architecture-py/compare/v0.1.1...v0.1.2) (2026-09-16)
 
 

{scaffold_ca_python-0.1.2 → scaffold_ca_python-0.1.3}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.5
 Name: scaffold-ca-python
-Version: 0.1.2
+Version: 0.1.3
 Summary: Scaffolder to generate Clean Architecture apps
 Project-URL: Homepage, https://github.com/bancolombia/scaffold-clean-architecture-py
 Project-URL: Repository, https://github.com/bancolombia/scaffold-clean-architecture-py
@@ -217,8 +217,8 @@ scaffold update-project --dry-run
 |----------------|---------|------|
 | Python | >=3.13 | Runtime |
 | uv | latest | Dependency management, build, and publish |
-| Typer | >=0.16.0 | CLI framework |
-| Rich | >=14.1.0 | Terminal output formatting |
+| Typer | >=0.25.1 | CLI framework |
+| Rich | >=15.0.0 | Terminal output formatting |
 | Jinja2 | >=3.1 | Template engine for code generation |
 | Pydantic v2 | >=2.0 | Runtime validation of template context |
 | hatchling | latest | Build backend |
@@ -248,12 +248,12 @@ scaffold update-project --dry-run
 
 ## Contributing
 
-1. Fork the upstream repository on GitHub: https://github.com/santicalleg/scaffold-ca-python
+1. Fork the upstream repository on GitHub: https://github.com/bancolombia/scaffold-clean-architecture-py
 2. Clone your fork.
 
 ```bash
-git clone https://github.com/YOUR-USER/scaffold-ca-python.git
-cd scaffold-ca-python
+git clone https://github.com/YOUR-USER/scaffold-clean-architecture-py.git
+cd scaffold-clean-architecture-py
 ```
 
 3. Set up the development environment.

{scaffold_ca_python-0.1.2 → scaffold_ca_python-0.1.3}/README.md

@@ -186,8 +186,8 @@ scaffold update-project --dry-run
 |----------------|---------|------|
 | Python | >=3.13 | Runtime |
 | uv | latest | Dependency management, build, and publish |
-| Typer | >=0.16.0 | CLI framework |
-| Rich | >=14.1.0 | Terminal output formatting |
+| Typer | >=0.25.1 | CLI framework |
+| Rich | >=15.0.0 | Terminal output formatting |
 | Jinja2 | >=3.1 | Template engine for code generation |
 | Pydantic v2 | >=2.0 | Runtime validation of template context |
 | hatchling | latest | Build backend |
@@ -217,12 +217,12 @@ scaffold update-project --dry-run
 
 ## Contributing
 
-1. Fork the upstream repository on GitHub: https://github.com/santicalleg/scaffold-ca-python
+1. Fork the upstream repository on GitHub: https://github.com/bancolombia/scaffold-clean-architecture-py
 2. Clone your fork.
 
 ```bash
-git clone https://github.com/YOUR-USER/scaffold-ca-python.git
-cd scaffold-ca-python
+git clone https://github.com/YOUR-USER/scaffold-clean-architecture-py.git
+cd scaffold-clean-architecture-py
 ```
 
 3. Set up the development environment.

{scaffold_ca_python-0.1.2 → scaffold_ca_python-0.1.3}/specs/015-factory-builder-refactor/tasks.md

@@ -78,8 +78,8 @@ command tests pass with no modifications.
  [x] T027 [P] [US2] Implement `DrivenAdapterSecrets` in `src/scaffold_ca_python/factory/driven_adapters/da_secrets.py`
  [x] T028 [P] [US2] Write failing tests for `DrivenAdapterGeneric.build()` in `tests/factory/driven_adapters/test_da_generic.py`
  [x] T029 [P] [US2] Implement `DrivenAdapterGeneric` in `src/scaffold_ca_python/factory/driven_adapters/da_generic.py`
-- [ ] T030 [US2] Refactor `src/scaffold_ca_python/commands/generate_driven_adapter.py` to thin + `_REGISTRY`; remove FileWriter/TemplateRenderer/pyproject_writer imports
-- [ ] T031 [US2] Run `uv run pytest tests/commands/ --no-cov -q` and confirm zero regressions (no test file modified)
+- [x] T030 [US2] Refactor `src/scaffold_ca_python/commands/generate_driven_adapter.py` to thin + `_REGISTRY`; remove FileWriter/TemplateRenderer/pyproject_writer imports
+- [x] T031 [US2] Run `uv run pytest tests/commands/ --no-cov -q` and confirm zero regressions (no test file modified)
 
 ---
 
@@ -111,20 +111,20 @@ command in scope uses only `ModuleBuilder`. After this phase, no command file im
 
 **Independent test**: `uv run pytest tests/factory/test_registry.py tests/factory/test_dry_run_parity.py --no-cov -q`
 
-- [ ] T042 [US4] Write `tests/factory/test_registry.py` — assert `_REGISTRY` for `gep` contains exactly {restapi, agent, mcp, generic}; assert `_REGISTRY` for `gda` contains exactly {rest-consumer, secrets, generic}; assert all 6 simple commands have `_REGISTRY` with their respective types; assert unknown type lookup produces error listing valid keys
-- [ ] T043 [US4] Write `tests/factory/test_dry_run_parity.py` — for each type in both commands, compare dry-run preview path set against a captured pre-refactor baseline fixture
-- [ ] T044 [US4] Write SC-002 extensibility proof test in `tests/factory/test_extensibility.py` — define a stub factory inline, register it under a new key in a patched `_REGISTRY`, invoke the command with the stub type, assert factory was called; zero existing command files modified
+- [x] T042 [US4] Write `tests/factory/test_registry.py` — assert `_REGISTRY` for `gep` contains exactly {restapi, agent, mcp, generic}; assert `_REGISTRY` for `gda` contains exactly {rest-consumer, secrets, generic}; assert all 6 simple commands have `_REGISTRY` with their respective types; assert unknown type lookup produces error listing valid keys
+- [x] T043 [US4] Write `tests/factory/test_dry_run_parity.py` — for each type in both commands, compare dry-run preview path set against a captured pre-refactor baseline fixture
+- [x] T044 [US4] Write SC-002 extensibility proof test in `tests/factory/test_extensibility.py` — define a stub factory inline, register it under a new key in a patched `_REGISTRY`, invoke the command with the stub type, assert factory was called; zero existing command files modified
 
 ---
 
 ## Phase 7 — Polish & Quality Gates
 
-- [ ] T045 Run `uv run pytest` and confirm all tests pass with ≥ 95% coverage
-- [ ] T045b Assert template immutability: `git diff HEAD -- src/scaffold_ca_python/templates/` must be empty — no template file modified during implementation (FR-009)
-- [ ] T045c Assert model immutability: confirm no new files exist under `src/scaffold_ca_python/models/` beyond the pre-refactor baseline (FR-010)
-- [ ] T046 [P] Run `uv run ruff check src/ tests/` and fix any violations
-- [ ] T047 [P] Run `uv run ruff format src/ tests/` to normalise formatting
-- [ ] T048 [P] Run `uv run mypy src/` and confirm 0 new errors under strict mode
+- [x] T045 Run `uv run pytest` and confirm all tests pass with ≥ 95% coverage
+- [x] T045b Assert template immutability: `git diff HEAD -- src/scaffold_ca_python/templates/` must be empty — no template file modified during implementation (FR-009)
+- [x] T045c Assert model immutability: confirm no new files exist under `src/scaffold_ca_python/models/` beyond the pre-refactor baseline (FR-010)
+- [x] T046 [P] Run `uv run ruff check src/ tests/` and fix any violations
+- [x] T047 [P] Run `uv run ruff format src/ tests/` to normalise formatting
+- [x] T048 [P] Run `uv run mypy src/` and confirm 0 new errors under strict mode
 
 ---
 

{scaffold_ca_python-0.1.2 → scaffold_ca_python-0.1.3}/specs/019-mcp-entry-point-restructure/plan.md

@@ -1,7 +1,7 @@
 # Implementation Plan: MCP Entry Point Restructure
 
-**Branch**: `019-mcp-entry-point-restructure` | **Date**: 2026-04-16 | **Spec**: [spec.md](../018-mcp-entry-point-restructure/spec.md)  
-**Input**: Feature specification from `/specs/018-mcp-entry-point-restructure/spec.md`
+**Branch**: `019-mcp-entry-point-restructure` | **Date**: 2026-04-16 | **Spec**: [spec.md](spec.md)  
+**Input**: Feature specification from `/specs/019-mcp-entry-point-restructure/spec.md`
 
 ## Summary
 

{scaffold_ca_python-0.1.2 → scaffold_ca_python-0.1.3}/tests/factory/fixtures/dry_run_baseline.json

@@ -18,17 +18,24 @@
     "src/my_app/infrastructure/entry_points/agent/__init__.py",
     "src/my_app/infrastructure/entry_points/agent/agent.py",
     "src/my_app/infrastructure/entry_points/agent/card.py",
+    "src/my_app/main.py",
     "src/tests/infrastructure/entry_points/agent/test_agent.py"
   ],
   "gep:generic": [
     "src/my_app/infrastructure/entry_points/generic/__init__.py",
     "src/my_app/infrastructure/entry_points/generic/entry_point.py",
+    "src/my_app/main.py",
     "src/tests/infrastructure/entry_points/generic/test_entry_point.py"
   ],
   "gep:mcp": [
+    "src/my_app/application/app.py",
+    "src/my_app/application/config/config.py",
     "src/my_app/infrastructure/entry_points/mcp_server/__init__.py",
-    "src/my_app/infrastructure/entry_points/mcp_server/server.py",
-    "src/tests/infrastructure/entry_points/mcp_server/test_server.py"
+    "src/my_app/infrastructure/entry_points/mcp_server/tools.py",
+    "src/my_app/main.py",
+    "src/my_app/server.py",
+    "src/tests/infrastructure/entry_points/mcp_server/test_app.py",
+    "src/tests/infrastructure/entry_points/mcp_server/test_tools.py"
   ],
   "gep:restapi": [
     "src/my_app/application/app.py",

scaffold_ca_python-0.1.3/tests/factory/test_dry_run_parity.py

@@ -0,0 +1,96 @@
+"""Dry-run path parity against the captured baseline (T043 / SC-005).
+
+For each type of both entry-point (`gep`) and driven-adapter (`gda`) commands, the set
+of paths a dry-run would touch must match a golden baseline fixture. The baseline is
+regenerated from the real factory output and pins the file-generation contract; an
+accidental change to any factory's queued paths breaks these tests, prompting a
+deliberate baseline refresh.
+"""
+
+from __future__ import annotations
+
+import json
+from pathlib import Path
+
+import pytest
+from typer.testing import CliRunner
+
+from scaffold_ca_python.cli import app
+from scaffold_ca_python.commands import generate_driven_adapter, generate_entry_point
+from scaffold_ca_python.core.module_builder import ModuleBuilder
+from scaffold_ca_python.factory import ModuleFactory
+from scaffold_ca_python.models.context import ModuleContext, ProjectContext
+from scaffold_ca_python.models.layer import Layer
+
+runner = CliRunner()
+
+_BASELINE: dict[str, list[str]] = json.loads(
+    (Path(__file__).parent / "fixtures" / "dry_run_baseline.json").read_text(encoding="utf-8")
+)
+
+# Flags the gep command always attaches to the builder before invoking a factory.
+_GEP_PARAMS = {
+    "routes": [],
+    "enable_kafka": False,
+    "enable_mcp_client": False,
+    "with_resources": False,
+    "with_prompts": False,
+}
+
+
+@pytest.fixture()
+def project_root(tmp_path: Path, monkeypatch: pytest.MonkeyPatch) -> Path:
+    """Scaffold a real `my-app` project (package `my_app`) inside tmp_path."""
+    monkeypatch.chdir(tmp_path)
+    runner.invoke(app, ["ca", "--name", "my-app"], catch_exceptions=False)
+    project_dir = tmp_path / "my-app"
+    monkeypatch.chdir(project_dir)
+    return project_dir
+
+
+def _preview(
+    root: Path,
+    module_ctx: ModuleContext,
+    factory_cls: type[ModuleFactory],
+    params: dict[str, object] | None = None,
+) -> list[str]:
+    """Return the sorted relative paths a factory dry-run would touch."""
+    builder = ModuleBuilder(
+        project_root=root,
+        project_ctx=ProjectContext(name="my-app"),
+        module_ctx=module_ctx,
+        dry_run=True,
+    )
+    for key, value in (params or {}).items():
+        builder.add_param(key, value)
+    factory_cls().build(builder)
+    return sorted(p.relative_to(root).as_posix() for p in builder.persist())
+
+
+@pytest.mark.parametrize("type_", ["restapi", "agent", "mcp", "generic"])
+def test_gep_dry_run_parity(project_root: Path, type_: str) -> None:
+    module_ctx = ModuleContext(
+        name=type_.replace("-", "_"),
+        layer=Layer.ENTRY_POINTS,
+        project=ProjectContext(name="my-app"),
+        subtype=type_,
+    )
+    preview = _preview(project_root, module_ctx, generate_entry_point._REGISTRY[type_], _GEP_PARAMS)
+    assert preview == _BASELINE[f"gep:{type_}"]
+
+
+@pytest.mark.parametrize(
+    ("type_", "name"),
+    [("rest-consumer", None), ("secrets", None), ("generic", "my-adapter")],
+)
+def test_gda_dry_run_parity(project_root: Path, type_: str, name: str | None) -> None:
+    proj = ProjectContext(name="my-app")
+    if type_ == "rest-consumer":
+        module_ctx = ModuleContext(name="rest_consumer", layer=Layer.DRIVEN_ADAPTERS, project=proj)
+    elif type_ == "secrets":
+        module_ctx = ModuleContext(name="secrets", layer=Layer.DRIVEN_ADAPTERS, project=proj)
+    else:
+        assert name is not None
+        module_ctx = ModuleContext(name=name, layer=Layer.DRIVEN_ADAPTERS, project=proj)
+    preview = _preview(project_root, module_ctx, generate_driven_adapter._REGISTRY[type_])
+    assert preview == _BASELINE[f"gda:{type_}"]

scaffold_ca_python-0.1.3/tests/factory/test_extensibility.py

@@ -0,0 +1,46 @@
+"""Extensibility proof for factory registries (T044 / SC-002).
+
+A new module type must be addable by registering a ModuleFactory under a fresh key in
+a command's `_REGISTRY`, with no edits to the command file itself. Here a stub factory
+is registered under a new key and the command is shown to dispatch to it.
+"""
+
+from __future__ import annotations
+
+from pathlib import Path
+
+import pytest
+from typer.testing import CliRunner
+
+from scaffold_ca_python.cli import app
+from scaffold_ca_python.commands import generate_entry_point
+from scaffold_ca_python.core.module_builder import ModuleBuilder
+
+runner = CliRunner()
+
+
+@pytest.fixture()
+def project_root(tmp_path: Path, monkeypatch: pytest.MonkeyPatch) -> Path:
+    """Scaffold a real `my-app` project inside tmp_path."""
+    monkeypatch.chdir(tmp_path)
+    runner.invoke(app, ["ca", "--name", "my-app"], catch_exceptions=False)
+    project_dir = tmp_path / "my-app"
+    monkeypatch.chdir(project_dir)
+    return project_dir
+
+
+def test_new_type_routes_to_registered_factory(project_root: Path, monkeypatch: pytest.MonkeyPatch) -> None:
+    """Registering a new ModuleFactory key routes `gep` to it without editing the command."""
+    calls: list[str] = []
+
+    class _StubFactory:
+        def build(self, builder: ModuleBuilder) -> None:
+            calls.append("built")
+
+    # Add a brand-new type key; monkeypatch reverts the registry after the test.
+    monkeypatch.setitem(generate_entry_point._REGISTRY, "stub", _StubFactory)
+
+    result = runner.invoke(app, ["gep", "--type", "stub", "--dry-run"], catch_exceptions=False)
+
+    assert result.exit_code == 0
+    assert calls == ["built"], "Registered stub factory's build() was not invoked"

scaffold_ca_python-0.1.3/tests/factory/test_registry.py

@@ -0,0 +1,54 @@
+"""Tests for the command _REGISTRY dispatch tables (T042 / 015-factory-builder-refactor).
+
+Verifies each command exposes a factory registry keyed by its supported types, and
+that dispatching an unknown type fails with an error that lists the valid keys.
+"""
+
+from __future__ import annotations
+
+from typer.testing import CliRunner
+
+from scaffold_ca_python.cli import app
+from scaffold_ca_python.commands import (
+    delete_module,
+    generate_driven_adapter,
+    generate_entry_point,
+    generate_helper,
+    generate_model,
+    generate_use_case,
+)
+from tests.conftest import strip_ansi
+
+runner = CliRunner()
+
+
+def test_entry_point_registry_keys() -> None:
+    assert set(generate_entry_point._REGISTRY) == {"restapi", "agent", "mcp", "generic"}
+
+
+def test_driven_adapter_registry_keys() -> None:
+    assert set(generate_driven_adapter._REGISTRY) == {"rest-consumer", "secrets", "generic"}
+
+
+def test_simple_command_registries_expose_single_key() -> None:
+    assert set(generate_model._REGISTRY) == {"model"}
+    assert set(generate_use_case._REGISTRY) == {"use_case"}
+    assert set(generate_helper._REGISTRY) == {"helper"}
+    assert set(delete_module._REGISTRY) == {"delete"}
+
+
+def test_gep_unknown_type_lists_valid_keys() -> None:
+    result = runner.invoke(app, ["gep", "--type", "bogus"], catch_exceptions=False)
+    assert result.exit_code == 1
+    # Flatten soft-wrapped console output so key tokens stay intact.
+    out = strip_ansi(result.output).replace("\n", " ")
+    for key in generate_entry_point._REGISTRY:
+        assert key in out, f"Expected valid key '{key}' listed in error output"
+
+
+def test_gda_unknown_type_lists_valid_keys() -> None:
+    result = runner.invoke(app, ["gda", "--type", "bogus"], catch_exceptions=False)
+    assert result.exit_code == 1
+    out = strip_ansi(result.output).replace("\n", " ")
+    for key in generate_driven_adapter._REGISTRY:
+        assert key in out, f"Expected valid key '{key}' listed in error output"

scaffold_ca_python-0.1.2/.release-please-manifest.json

@@ -1,3 +0,0 @@
-{
-  ".": "0.1.2"
-}

scaffold_ca_python-0.1.2/specs/010-fix-restapi-cleanup/checklists/requirements.md

@@ -1,34 +0,0 @@
-# Specification Quality Checklist: Fix RestAPI Entry Point Cleanup
-
-**Purpose**: Validate specification completeness and quality before proceeding to planning
-**Created**: 2026-04-10
-**Feature**: [spec.md](../spec.md)
-
-## Content Quality
-
-- [X] No implementation details (languages, frameworks, APIs)
-- [X] Focused on user value and business needs
-- [X] Written for non-technical stakeholders
-- [X] All mandatory sections completed
-
-## Requirement Completeness
-
-- [X] No [NEEDS CLARIFICATION] markers remain
-- [X] Requirements are testable and unambiguous
-- [X] Success criteria are measurable
-- [X] Success criteria are technology-agnostic (no implementation details)
-- [X] All acceptance scenarios are defined
-- [X] Edge cases are identified
-- [X] Scope is clearly bounded
-- [X] Dependencies and assumptions identified
-
-## Feature Readiness
-
-- [X] All functional requirements have clear acceptance criteria
-- [X] User scenarios cover primary flows
-- [X] Feature meets measurable outcomes defined in Success Criteria
-- [X] No implementation details leak into specification
-
-## Notes
-
-- All items pass. Spec is ready for `/speckit.plan`.

scaffold_ca_python-0.1.2/specs/010-fix-restapi-cleanup/spec.md

@@ -1,76 +0,0 @@
-# Feature Specification: Fix RestAPI Entry Point Cleanup
-
-**Feature Branch**: `010-fix-restapi-cleanup`  
-**Created**: 2026-04-10  
-**Status**: Draft  
-**Input**: User description: "fix some issues when create a restapi entry point: 1. Delete main.py file because restapi entry point creates a server.py module to execute the app. 2. Update pyproject.toml [project.scripts] to point to server:start_server"
-
-## User Scenarios & Testing *(mandatory)*
-
-### User Story 1 - `main.py` Is Removed When a RestAPI Entry Point Is Scaffolded (Priority: P1)
-
-A developer runs `scaffold ca` which creates a default `main.py`. Later they run `gep --type restapi`, which sets up a FastAPI application and a `server.py` entry point. The old `main.py` is now irrelevant and misleading — the project should no longer contain it after the restapi setup completes.
-
-**Why this priority**: `main.py` left behind after `gep --type restapi` causes confusion: the project has two apparent entry points. Removing it is the single most visible correctness fix and is the prerequisite for the `pyproject.toml` scripts update to mean anything.
-
-**Independent Test**: Run `scaffold ca --name MyApp`, then `gep --type restapi`. Assert that `src/my_app/main.py` does **not** exist immediately after the command completes.
-
-**Acceptance Scenarios**:
-
-1. **Given** a fresh CA project with `main.py` created by `scaffold ca`, **When** `gep --type restapi` runs, **Then** `src/<package>/main.py` no longer exists on disk.
-2. **Given** a project where `main.py` was already manually deleted, **When** `gep --type restapi` runs, **Then** the command completes successfully without error (no-op delete).
-3. **Given** a project with a restapi entry point already present, **When** `gep --type restapi` is run a second time, **Then** the command exits with an error (duplicate guard) and `main.py` is not re-created.
-
----
-
-### User Story 2 - `pyproject.toml` `[project.scripts]` Points to `server:start_server` After RestAPI Scaffolding (Priority: P1)
-
-After `gep --type restapi` runs, the executable entry point registered in `pyproject.toml` must call `start_server()` from `server.py` (not `main()` from `main.py`, which no longer exists). A developer must be able to install the package and run the project CLI command immediately.
-
-**Why this priority**: Without this fix the installed CLI command points to a deleted module and crashes on every invocation. Equal priority to US1 — both are correctness bugs.
-
-**Independent Test**: Run `scaffold ca --name MyApp`, then `gep --type restapi`. Inspect `pyproject.toml` — the `[project.scripts]` entry must read `my_app = "my_app.server:start_server"`.
-
-**Acceptance Scenarios**:
-
-1. **Given** a fresh CA project with `[project.scripts]` pointing to `main:main`, **When** `gep --type restapi` runs, **Then** `[project.scripts]` in `pyproject.toml` reads `<package> = "<package>.server:start_server"`.
-2. **Given** `gep --type restapi --dry-run` is run, **Then** the output indicates the `pyproject.toml` scripts entry would be updated, but the file is not modified.
-3. **Given** a project using any other entry point type (agent, mcp, generic), **When** the corresponding `gep --type <other>` runs, **Then** `[project.scripts]` is **not** changed (only the restapi type triggers this update).
-
----
-
-### Edge Cases
-
-- What if `pyproject.toml` does not contain a `[project.scripts]` section at all? → The section and entry must be created.
-- What if the existing `[project.scripts]` entry already points to `server:start_server`? → No duplicate is written; the file remains unchanged.
-- What if `main.py` does not exist when `gep --type restapi` runs (already deleted manually)? → The delete step is silently skipped; command succeeds.
-
-## Requirements *(mandatory)*
-
-### Functional Requirements
-
-- **FR-001**: When `gep --type restapi` executes, the tool MUST delete `src/<package>/main.py` if it exists.
-- **FR-002**: When `gep --type restapi` executes, the tool MUST update `[project.scripts]` in `pyproject.toml` so the package CLI entry reads `<package> = "<package>.server:start_server"`, replacing any prior value.
-- **FR-003**: The `pyproject_toml.jinja2` template MUST NOT be changed to reference `server:start_server` — the update is applied at runtime by `gep --type restapi`, not at project creation time (project creation still generates `main:main`).
-- **FR-004**: When `gep --type restapi --dry-run` is invoked, the tool MUST report the scripts update in its preview output without modifying `pyproject.toml`.
-- **FR-005**: `gep` commands for non-restapi types (agent, mcp, generic) MUST NOT modify `[project.scripts]`.
-- **FR-006**: If `main.py` is absent when `gep --type restapi` runs, the command MUST complete successfully (silent no-op for the delete step).
-- **FR-007**: All other entry-point types continue to overwrite `main.py` as they do today; only the restapi type deletes it.
-
-## Success Criteria *(mandatory)*
-
-### Measurable Outcomes
-
-- **SC-001**: After `gep --type restapi` completes, `src/<package>/main.py` does not exist in 100% of test runs.
-- **SC-002**: After `gep --type restapi` completes, `pyproject.toml` contains exactly one `[project.scripts]` entry pointing to `<package>.server:start_server` — verified by test assertion.
-- **SC-003**: All existing tests continue to pass (no regressions); the overall test count increases by the number of new tests added for this feature.
-- **SC-004**: `gep --type agent`, `gep --type mcp`, and `gep --type generic` each still overwrite `main.py` and leave `[project.scripts]` pointing to `main:main`.
-- **SC-005**: `gep --type restapi --dry-run` does not modify any file on disk.
-
-## Assumptions
-
-- The `scaffold ca` command always creates `main.py` when scaffolding a new project; `gep --type restapi` is always run in a project that originally had `main.py`.
-- The `pyproject.toml` file always contains a `[project.scripts]` section after `scaffold ca` runs, because that section is included in the current `pyproject_toml.jinja2` template.
-- The `server.py` module (thin wrapper calling `start_server()`) is already emitted by `gep --type restapi` as of feature 009; this feature assumes that is complete.
-- The `start_server()` function is defined in `server.py` by the time `pyproject.toml` is updated; no further template changes to `server.py.jinja2` are needed.
-- Non-restapi entry-point types are out of scope for both the delete and the scripts-update steps.