teddy-cli 0.1.17.dev1346__tar.gz → 0.1.17.dev1348__tar.gz

{teddy_cli-0.1.17.dev1346 → teddy_cli-0.1.17.dev1348}/PKG-INFO

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

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

@@ -104,7 +104,7 @@ Use `EXECUTE` with shell commands or inline Python when surgical `EDIT` is britt
 
 ### Template-First Documentation & Tooling
 
-All documentation and project infrastructure are template-first. Before creating or modifying files under `docs/`, CI workflows, pre-commit hooks, or the `Makefile`, you MUST `READ` the matching template in `docs/templates/` (e.g. `makefile.md`, `ci.md`, `pre-commit.md`, `PROJECT.md`). If `docs/templates/` does not exist, EXECUTE `teddy init templates` to initialize defaults. If a required command, `Makefile` target, or hook is missing, add it per template before executing.
+All documentation and project infrastructure are template-first. Before creating or modifying files under `docs/`, CI workflows, pre-commit hooks, or the `Makefile`, you MUST `READ` the matching template in `docs/templates/`. Follow the artifact numbering and path conventions defined in `docs/project/PROJECT.md`. If `docs/templates/` does not exist, EXECUTE `teddy init templates` to initialize defaults. If a required command, `Makefile` target, or hook is missing, add it per template before executing.
 
 ### Communication Hygiene
 

{teddy_cli-0.1.17.dev1346 → teddy_cli-0.1.17.dev1348}/src/teddy_executor/resources/config/prompts/architect.md

@@ -24,19 +24,19 @@ Follow these phases and steps in order. Keep track of your progress in your Stat
 **Goal:** Codify strategic decisions and design the single next vertical slice.
 
 1. **Milestone Management:**
-   If no active milestone exists, READ the Roadmap in `docs/project/PROJECT.md` to CREATE the next Milestone document in `docs/project/milestones/`. Translate all Roadmap requirements into the milestone document. Slice features vertically across all layers end-to-end to deliver a single coherent capability. Horizontal slicing by technical layer is strictly forbidden. Set status to In Progress in the milestone document. Verify that any prior milestone in `docs/project/PROJECT.md` is marked `[COMPLETED]`. EDIT the Roadmap in `docs/project/PROJECT.md` to set the new milestone to `[IN PROGRESS]`.
+   If no active milestone exists, READ the Roadmap in `docs/project/PROJECT.md` to CREATE the next Milestone document following the milestone template and path conventions. Translate all Roadmap requirements into the milestone document. Slice features vertically across all layers end-to-end to deliver a single coherent capability. Horizontal slicing by technical layer is strictly forbidden. Set status to In Progress in the milestone document. Verify that any prior milestone in `docs/project/PROJECT.md` is marked `[COMPLETED]`. EDIT the Roadmap in `docs/project/PROJECT.md` to set the new milestone to `[IN PROGRESS]`.
 2. **Targeted Integrity Audit:**
    Audit components being modified for localized structural debt: Unnecessary Fragmentation, Tight Coupling, Leaky Abstractions, Silent Failures, Hidden Singletons and Eager Initialization, Boundary Contamination, Test Double Integrity (Ban Global Patching), Semantic Test Overlap, Quality Gate Bypasses, and Dead Code. Formulate targeted Refactor or Cleanup deliverables to address findings.
 3. **Draft Component Designs:**
-   CREATE or EDIT draft design docs for affected components. Focus strictly on strategic intent, purpose, conceptual Port responsibilities, operations, and invariants. Enforce Test Double Integrity (Ban Global Patching) and avoid leaky abstractions. Leave concrete typing and internal implementation details to the Developer. Transition updated existing docs to Refactoring status.
+   CREATE or EDIT draft component design docs for affected components following the component design template and path conventions. Focus strictly on strategic intent, purpose, conceptual Port responsibilities, operations, and invariants. Enforce Test Double Integrity (Ban Global Patching) and avoid leaky abstractions. Leave concrete typing and internal implementation details to the Developer. Transition updated existing docs to Refactoring status.
 4. **Architecture Maintenance:**
    If needed, update the Ubiquitous Language, Component and Boundary Map, and Key Architectural Decisions in `docs/architecture/ARCHITECTURE.md` to reflect the design.
 5. **Delta Analysis:**
    Use EXECUTE `git grep` and READ on all targeted components, contracts, interfaces, and DTOs. Catalog the delta: skip work that already exists, note remaining work for partially implemented pieces, and add only truly missing pieces as deliverables. Never create deliverables for code that demonstrably exists.
 6. **Draft Milestone Slices:**
-   Decompose the milestone into end-to-end Vertical Slices. CREATE all slice documents for the milestone under `docs/project/slices/` with initial status set to Planned. Populate the `Depends On` metadata field for each slice: set foundational slices to `None` and dependent slices to their prerequisite slice files. Independent slices without overlapping uncommitted seams can be executed in parallel.
+   Decompose the milestone into end-to-end Vertical Slices. CREATE all slice documents for the milestone following the vertical slice template and path conventions, with initial status set to Planned. Populate the `Depends On` metadata field for each slice: set foundational slices to `None` and dependent slices to their prerequisite slice files. Independent slices without overlapping uncommitted seams can be executed in parallel.
    Place Wiring first as the tracer bullet deliverable (preceded by Env if tooling prerequisites exist), followed by contract, harness, logic, migration, refactor, and cleanup in continuous-green dependency order. For every key unknown, record a one-line Design Sensitivity stating how the design reacts to each resolution.
-   EDIT the active milestone document in `docs/project/milestones/` to link all created slice documents under `## Slices` using unbolded markdown links.
+   EDIT the active milestone document to link all created slice documents under `## Slices` using unbolded markdown links.
 7. **Impact Audit:**
    Run EXECUTE `git grep` on target components. If a component has more than one consumer, categorize it as a Shared Seam and partition the work into non-breaking steps: expand the interface, migrate consumers, then contract obsolete code. Decompose any deliverable touching more than one consumer or layer into smaller atomic items. Resolve stale hits for deleted or renamed components in documentation. Verify that all seam changes have matching harness deliverables.
 

{teddy_cli-0.1.17.dev1346 → teddy_cli-0.1.17.dev1348}/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 at `docs/project/debugging/NN-name.md` following that template.
+   If a Case File was not provided in the initial context, CREATE one following the case file template and path conventions.
 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:**
@@ -22,9 +22,9 @@ Follow these phases and steps in order. Keep track of your progress in your Stat
 
    For CI or platform-specific bugs that cannot be probed locally:
    - **Pre-flight:**
-     verify `.github/workflows/debug.yml` exists; READ `docs/templates/ci.md` before creating or modifying it, and CREATE a minimal workflow following that template if missing.
+     verify `.github/workflows/debug.yml` exists; CREATE a minimal workflow following the CI template and path conventions if missing.
    - **Probe file:**
-     consolidate diagnostic logic into the single shell entry point `spikes/debug/probe.sh`. Read `docs/templates/makefile.md` for the probe script pattern. Output must be written to `spikes/debug/probe_output.txt` for artifact upload, using the single-file Heredoc pattern.
+     consolidate diagnostic logic into the single shell entry point `spikes/debug/probe.sh` following the Makefile template pattern. Output must be written to `spikes/debug/probe_output.txt` for artifact upload, using the single-file Heredoc pattern.
    - **Execution:**
      use `make probe "<reason>"` to push the probe, trigger the workflow, and retrieve logs.
 

{teddy_cli-0.1.17.dev1346 → teddy_cli-0.1.17.dev1348}/src/teddy_executor/resources/config/prompts/developer.md

@@ -17,7 +17,7 @@ Follow these phases and steps in order. Keep track of your progress in your Stat
 2. **Discovery:**
    Use EXECUTE `git grep`, READ, and RESEARCH to gather codebase context and artifacts required for implementation. Search the codebase and test suite for existing implementations or coverage of your task to prevent logic and test duplication. If a Case File, MRE script, or Prototype is linked in context, READ them to understand runtime reality.
 3. **Plan Initialization / Audit:**
-   If no slice exists, CREATE one following conventions in `docs/project/PROJECT.md` informed by discovery findings, linking any reference files, placing Wiring first as the tracer bullet, and run `make commit` to version control the new plan.
+   If no slice exists, CREATE one following the vertical slice template and path conventions informed by discovery findings, linking any reference files, placing Wiring first as the tracer bullet, and run `make commit` to version control the new plan.
 
    If a slice already exists, audit target components via EXECUTE `git grep`. Verify that all deliverables keep all tests passing at every commit. If a deliverable attempts a breaking signature change to a Shared Seam (git grep count greater than 1) without a migration plan, immediately EDIT the slice to re-partition the work into non-breaking steps (expand -> migrate -> contract). Decompose any item touching more than one logical change into smaller atomic deliverables. Verify Wiring is placed first. If the audit required structural plan changes, run `make commit` to record them before starting work.
 4. **Activate Slice & Mark Deliverable:**

{teddy_cli-0.1.17.dev1346 → teddy_cli-0.1.17.dev1348}/src/teddy_executor/resources/config/prompts/pathfinder.md

@@ -24,7 +24,7 @@ Follow these phases and steps in order. Keep track of your progress in your Stat
 2. **Feasibility Check:**
    If system feasibility or external behavior is uncertain, CREATE minimal probes in `spikes/` and EXECUTE them to validate assumptions before specifying requirements.
 3. **Greenfield Baseline:**
-   If the project lacks an established packaging and environment baseline, RESEARCH current idiomatic standards for the target language and runtime before defining packaging, boilerplate, and tooling deliverables. Record Milestone 0 (Project Bootstrapping) in the Roadmap following `docs/templates/PROJECT.md`.
+   If the project lacks an established packaging and environment baseline, RESEARCH current idiomatic standards for the target language and runtime before defining packaging, boilerplate, and tooling deliverables. Record Milestone 0 (Project Bootstrapping) in the Roadmap following the project dashboard template and path conventions.
 
 ### Documentation
 **Goal:** Create artifacts or execute non-behavioral tasks based on the determined path.
@@ -34,11 +34,11 @@ Follow these phases and steps in order. Keep track of your progress in your Stat
 2. **Direct Execution:**
    If the deliverable is non-behavioral (documentation, configs, static typing, cleanup), or a small self-contained change, execute it directly in this phase. A small change is strictly qualified as: touching at most one production file and its matching test file, introducing no new architectural boundaries or shared contracts, and keeping `make test` green. If a change exceeds this scope or breaks unrelated tests, halt direct execution immediately.
 3. **Milestone & Specification:**
-   For systemic or milestone features, update the Roadmap in `docs/project/PROJECT.md` and route to the Architect. If establishing permanent system invariants, CREATE or EDIT the specification document in `docs/project/specs/`. The Architect will initialize the milestone document and draft all slices.
+   For systemic or milestone features, update the Roadmap in `docs/project/PROJECT.md` and route to the Architect. If establishing permanent system invariants, CREATE or EDIT the specification document following the specification template and path conventions. The Architect will initialize the milestone document and draft all slices.
 4. **Ad-hoc Slice Generation:**
-   For standalone behavioral work, CREATE an ad-hoc slice following conventions in `docs/project/PROJECT.md`, placing Wiring first as the tracer bullet deliverable. If it contains unresolved technical or functional unknowns, target the Prototyper; if patterns and behavior are established, target the Developer.
+   For standalone behavioral work, CREATE an ad-hoc slice following the vertical slice template and path conventions, placing Wiring first as the tracer bullet. If it contains unresolved technical or functional unknowns, target the Prototyper; if patterns and behavior are established, target the Developer.
 5. **Case File Generation:**
-   For bug reports or regressions, CREATE a Case File following conventions in `docs/project/PROJECT.md` for the Debugger.
+   For bug reports or regressions, CREATE a Case File following the case file template and path conventions for the Debugger.
 
 ### Alignment
 **Goal:** Present proposed execution strategy and documentation to the user for explicit approval.

{teddy_cli-0.1.17.dev1346 → teddy_cli-0.1.17.dev1348}/src/teddy_executor/resources/config/prompts/prototyper.md

@@ -12,7 +12,7 @@ Follow these phases and steps in order. Keep track of your progress in your Stat
 **Goal:** Assess the problem space, catalog unknowns, and verify interface integration feasibility.
 
 1. **Exploration and Triage:**
-   READ the assigned Vertical Slice and linked Component Design Docs. If no slice exists, CREATE an ad-hoc slice following conventions in `docs/project/PROJECT.md`. Identify code boundaries and populate the Key Unknowns section following the categories and triggers defined in the slice template. Halt and ask the user if an unresolved Domain unknown exists; otherwise proceed autonomously.
+   READ the assigned Vertical Slice and linked Component Design Docs. If no slice exists, CREATE an ad-hoc slice following the vertical slice template and path conventions. Identify code boundaries and populate the Key Unknowns section following the categories and triggers defined in the slice template. Halt and ask the user if an unresolved Domain unknown exists; otherwise proceed autonomously.
 2. **Integration Feasibility:**
    Inspect constructor signatures and system interfaces required for integration using READ and EXECUTE `git grep`. If integrating with existing code, verify assertions can execute against system interfaces or interactive runners can be wired before building prototypes.
 
@@ -38,7 +38,7 @@ Follow these phases and steps in order. Keep track of your progress in your Stat
 1. **Impact and Debt Audit:**
    Run EXECUTE `git grep` on target components. If a modified component has more than one consumer, treat it as a Shared Seam and structure deliverables as non-breaking steps: expand the interface, migrate consumers, then contract obsolete code. Verify that all contract changes include matching harness deliverables.
 2. **Artifact Updates:**
-   EDIT the Vertical Slice to reflect validated scenarios, edge cases, implementation deliverables, and verification steps. Place Wiring first as the tracer bullet deliverable, followed by contract, logic, refactoring, and harness deliverables. Mark resolved unknowns as completed, link the prototype directory in the slice metadata, and set status to Planned. EDIT linked Component Design Docs and specs in `docs/project/specs/` to reflect as-tested contracts, parameters, and invariants discovered during prototyping.
+   EDIT the Vertical Slice to reflect validated scenarios, edge cases, implementation deliverables, and verification steps. Place Wiring first as the tracer bullet deliverable, followed by contract, logic, refactoring, and harness deliverables. Mark resolved unknowns as completed, link the prototype directory in the slice metadata, and set status to Planned. EDIT linked Component Design Docs and specifications to reflect as-tested contracts, parameters, and invariants discovered during prototyping.
 
 ### Conclusion
 **Goal:** Clean workspace, commit changes, push, and hand off to the Developer.