teddy-cli 0.1.17.dev1341__tar.gz → 0.1.17.dev1342__tar.gz

{teddy_cli-0.1.17.dev1341 → teddy_cli-0.1.17.dev1342}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.5
 Name: teddy-cli
-Version: 0.1.17.dev1341
+Version: 0.1.17.dev1342
 Summary: The local-first, test-driven agentic engineering harness. Because you should own the means of development.
 Author: Raphael Atteritano
 License: AGPL-3.0-only

{teddy_cli-0.1.17.dev1341 → teddy_cli-0.1.17.dev1342}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "teddy-cli"
-version = "0.1.17.dev1341"
+version = "0.1.17.dev1342"
 description = "The local-first, test-driven agentic engineering harness. Because you should own the means of development."
 readme = "README.md"
 keywords = [

{teddy_cli-0.1.17.dev1341 → teddy_cli-0.1.17.dev1342}/src/teddy_executor/resources/config/prompts/debugger.md

@@ -12,7 +12,7 @@ Follow these phases and steps in order. Keep track of your progress in your Stat
 **Goal:** Gather context and build or verify an end-to-end Minimal Reproducible Example (MRE).
 
 1. **Case File Check:**
-   If a Case File was not provided in the initial context, READ `docs/templates/case-file.md` and CREATE one following that template.
+   If a Case File was not provided in the initial context, READ `docs/templates/case-file.md` and CREATE one at `docs/project/debugging/NN-name.md` following that template.
 2. **Context and History Gathering:**
    Use EXECUTE `git grep`, EXECUTE `git log`, READ, and RESEARCH to understand the codebase, recent changes, and identify the last known green CI run or commit. For historical CI failures, do not try to read the entire log: extract failed step logs by executing `make logs [ID]` (for all failed steps) or `make logs [ID] "[STEP_NAME]"` (for a specific step).
 3. **Diagnostic MRE and Platform Check:**

{teddy_cli-0.1.17.dev1341 → teddy_cli-0.1.17.dev1342}/src/teddy_executor/resources/templates/ARCHITECTURE.md

@@ -56,6 +56,27 @@ Test drivers, observers, shared fakes, and test setup fixtures.
 
 Each Contract column links to the Component Design Document or Interface definition.
 
+## Domain Model & Ubiquitous Language
+
+The shared vocabulary exchanged by every service, port, and adapter. Record the core entities, enumerations, value objects, domain exceptions, and port bundles that do not warrant a dedicated component design document.
+
+**Template format:** Group the types by concept. List each type with its module, kind, fields, and any invariant.
+
+### Enumerations
+- **`TypeName`** (`module.py`, Enum): `VALUE_A`, `VALUE_B`.
+
+### Aggregates
+- **`AggregateName`** (`module.py`, dataclass): `field_a`, `field_b`. Exposes `helper_method()`.
+
+### Port Bundles
+- **`PortBundleName`** (`module.py`, frozen dataclass): `dependency_a`, `dependency_b`.
+
+### Supporting Value Objects
+- **`ValueObjectName`** (`module.py`, frozen dataclass): `field_a`, `field_b`.
+
+### Domain Exceptions
+- **`ExceptionName`** (`BaseException`): carries `field`.
+
 ## Key Architectural Decisions
 
 A living "System Law" document capturing explicit, prescriptive design decisions.

{teddy_cli-0.1.17.dev1341 → teddy_cli-0.1.17.dev1342}/src/teddy_executor/resources/templates/PROJECT.md

@@ -20,8 +20,8 @@ Defines the high-level artifact lifecycle and conventions for project management
 - **Numbering:** Artifacts are numbered sequentially using a per-type filename convention so agents can infer the correct filename:
     - **Vertical Slices:** `MM-NN-name.md` (in `docs/project/slices/`) — `MM` is the target Milestone number and `NN` is the sequence number within that milestone.
     - **Milestones:** `MM-name.md` (in `docs/project/milestones/`).
-    - **Case Files (Debugger):** `NN-name.md` — numbered sequentially.
-    - **Milestone 0 (bootstrapping) & Ad-hoc work (not tied to a milestone):** `00-NN-name.md` — `00` is used as the Milestone prefix for Milestone 0 bootstrapping slices and for ad-hoc slices. Ad-hoc slices are NOT tracked in Milestone documents or the Roadmap.
+    - **Case Files (Debugger):** `NN-name.md` (in `docs/project/debugging/`) — numbered sequentially.
+    - **Milestone 0 (bootstrapping) & Ad-hoc work (not tied to a milestone):** `00-NN-name.md` (in `docs/project/slices/`) — `00` is used as the Milestone prefix for Milestone 0 bootstrapping slices and for ad-hoc slices. Ad-hoc slices are NOT tracked in Milestone documents or the Roadmap.
 - **Archiving Policy:** When and how completed artifacts are archived or deleted.
 - **Spec Organization:** Specification documents live in a single flat directory `docs/project/specs/` and are reserved strictly for **permanent system invariants** — formats, contracts, protocols (e.g. the MRP), core data models, and non-negotiable architectural rules. Feature goals, requirements, and acceptance criteria belong in Milestone documents (`docs/project/milestones/`), not in specs.
 - **Build & Run Commands:** Document the standard commands in the project `Makefile` (see [docs/templates/makefile.md](docs/templates/makefile.md)). At minimum: `make test` (full suite), `make commit '<msg>'`, `make push`, `make ci-watch` (CI monitoring), and `make probe '<reason>'` (Remote Probing Protocol).