teddy-cli 0.1.17.dev1299__tar.gz → 0.1.17.dev1301__tar.gz

{teddy_cli-0.1.17.dev1299 → teddy_cli-0.1.17.dev1301}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.5
 Name: teddy-cli
-Version: 0.1.17.dev1299
+Version: 0.1.17.dev1301
 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.dev1299 → teddy_cli-0.1.17.dev1301}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "teddy-cli"
-version = "0.1.17.dev1299"
+version = "0.1.17.dev1301"
 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.dev1299 → teddy_cli-0.1.17.dev1301}/src/teddy_executor/resources/templates/vertical-slice.md

@@ -26,6 +26,9 @@ Then [expected outcome]
 
 ## Key Unknowns
 
+**Format:**
+- [ ] [Tag] Title: Description of the unknown. Design Sensitivity.
+
 **Taxonomy:**
 - `[Domain]` = Ambiguities in business rules, policy decisions, domain definitions, or scope boundaries. Resolve by asking the user directly.
 - `[Technical]` = External dependencies, third-party libraries, APIs, internal state machines, complex algorithms, concurrency, performance, or data storage. Resolve via works-like prototypes.
@@ -38,9 +41,6 @@ Then [expected outcome]
 
 **Design Sensitivity:** For every unknown, record a one-line Design Sensitivity stating how the design reacts to each resolution (e.g., "if this resolves as X → contracts hold; if Y → this port/DTO changes").
 
-**Format:**
-- [ ] [Tag] Title: Description of the unknown. Design Sensitivity.
-
 ## Impact
 Surface of affected components using the Parallel Change (Expand-Migrate-Contract) model.
 Execute deliverables strictly in this order to maintain a Continuous Green State (`make test` passes at every commit). Never mutate shared contracts in place when existing consumers exist.
@@ -77,7 +77,8 @@ Free-form notes recording decisions, deviations, or discoveries during implement
 ## Verification
 <!-- Manual User Acceptance Testing (UAT) steps for the user to execute at slice conclusion. -->
 <!-- Provide clear, step-by-step instructions. Use copy-pasteable commands for CLI/APIs, or exact interactive steps for UI/visual flows. -->
+<!-- Do NOT include running automated tests here; those are covered by the automated test suite. -->
 
 **Format:**
-- [ ] **CLI / API:** Run `command <args>` and verify output contains `expected output`.
-- [ ] **UI / Interactive:** Navigate to `[View/Screen]`, trigger `[Action]`, and confirm `[Observed State/Element]`.
+- [ ] **[Title]:** Run `command <args>` and verify output contains `expected output`.
+- [ ] **[Title]:** Navigate to `[View/Screen]`, trigger `[Action]`, and confirm `[Observed State/Element]`.