teddy-cli 0.1.17.dev1180__tar.gz → 0.1.17.dev1181__tar.gz

{teddy_cli-0.1.17.dev1180 → teddy_cli-0.1.17.dev1181}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.5
 Name: teddy-cli
-Version: 0.1.17.dev1180
+Version: 0.1.17.dev1181
 Summary: A local-first, file-based AI coding workflow that applies the UNIX philosophy to AI collaboration.
 Author: Raphael Atteritano
 License: AGPL-3.0-only

{teddy_cli-0.1.17.dev1180 → teddy_cli-0.1.17.dev1181}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "teddy-cli"
-version = "0.1.17.dev1180"
+version = "0.1.17.dev1181"
 description = "A local-first, file-based AI coding workflow that applies the UNIX philosophy to AI collaboration."
 authors = [{ name = "Raphael Atteritano" }]
 license = { text = "AGPL-3.0-only" }

{teddy_cli-0.1.17.dev1180/src/teddy_executor/resources/config/prompts → teddy_cli-0.1.17.dev1181/src/teddy_executor/resources}/MRP.xml

@@ -51,7 +51,7 @@ WIP & REMINDERS:
       1. Pre-conditions: Clean up temporary files (spikes/, .tmp/). If unsure of changes, `EXECUTE git add . && git diff HEAD`.
       2. Commit Message: Use Conventional Commits '<type>(<scope>): <description>' wrapped in single quotes. Use imperative mood. Append ! for breaking changes.
       3. Execution: You MUST test, stage, commit locally, pull safely with rebase, and push by running `make commit '<type>(<scope>): <description>'`. If a `Makefile` does not exist in the project root, you MUST first create one following the template at `docs/templates/makefile.md`. To bypass pre-commit checks (e.g., for known false positives), use `make commit '<type>(<scope>): <description>' no-verify`.
-      4. Post-conditions: All tests MUST pass (post-commit hook enforces this; never bypass). Pre-commit may be bypassed with --no-verify if needed to bypass non-trivial quality gate failures (like file length); if so, log technical debt in PROJECT.md.
+      4. Post-conditions: All tests MUST pass (post-commit hook enforces this; never bypass). Pre-commit may be bypassed with --no-verify if needed to bypass non-trivial quality gate failures (like file length). If pre-commit is bypassed, you MUST make a follow-up cleanup commit that resolves the bypassed issues before resuming feature work, and log the debt in PROJECT.md if it cannot be resolved immediately.
     </rule>
 
     <rule n="7" name="Standardized Plan Types">
@@ -85,6 +85,10 @@ WIP & REMINDERS:
     <rule n="12" name="Template-First Documentation">
       <description>Before creating or modifying a documentation file under docs/, you MUST first READ the corresponding template from docs/templates/. Templates define the required structure and format for each artifact type. Template files are named by artifact type (e.g., specification-document.md, task-brief.md, case-file.md, PROJECT.md, ARCHITECTURE.md). If no template exists for your artifact, READ the most similar one as a reference.</description>
     </rule>
+
+    <rule n="13" name="Communication Hygiene">
+      <description>Applies to all user-facing Messages and turn titles: (1) Do not repeat the same title across consecutive turns — each turn's title MUST reflect its distinct responsibility, and if you detect a vicious loop with no new progress you MUST transition to BLOCKED 🔴 rather than repeating yourself. (2) Do not restate content already delivered in a prior Message, and do not send a new Message until the work previously agreed in the last Message is complete — the only exception is entering BLOCKED 🔴. (3) Record important findings and constraints as `[!]` entries in the State Dashboard so they persist across turns. (4) End every Message with a concise TL;DR line summarizing the key point or the decision requested.</description>
+    </rule>
   </general_rules>
 
   <response_format>

{teddy_cli-0.1.17.dev1180 → teddy_cli-0.1.17.dev1181}/src/teddy_executor/resources/templates/ARCHITECTURE.md

@@ -16,6 +16,15 @@ This section defines foundational engineering practices. Each entry MUST be a sp
 - **CI Pipeline:** Two parallel jobs — 1) Blocking OS matrix test suite with strict test coverage targets. 2) Non-blocking (continue-on-error: true) quality checks running fast formatters, linters, security/secret scanners, type checkers, and repository-wide structural checks (excluding sandboxes and third-party dependencies).
 - **Pre-commit Hooks:** Scope (staged files only), required hooks (formatters, linters, type checkers, security scanners).
 - **Post-commit Execution:** Full test suite run on commit, automatic revert on failure.
+- **Makefile Commands:** The `Makefile` is the canonical entry point for the VCP commit workflow and on-demand test runs. `make test` runs the full suite, `make commit '<msg>'` performs a VCP commit, and `make probe '<reason>'` runs the Remote Probing Protocol. See [docs/templates/makefile.md](docs/templates/makefile.md).
+
+### Pre-commit Quick-Start
+
+```shell
+pre-commit install                          # install the pre-commit stage hook
+pre-commit install --hook-type post-commit  # install the post-commit test gate
+pre-commit run --all-files                  # run all hooks manually against the repo
+```
 
 ## 2. Component & Boundary Map
 

{teddy_cli-0.1.17.dev1180 → teddy_cli-0.1.17.dev1181}/src/teddy_executor/resources/templates/PROJECT.md

@@ -20,6 +20,27 @@ Defines the high-level artifact lifecycle and conventions for project management
 - **Numbering:** Sequential MM-NN format, 00 prefix for ad-hoc work.
 - **Archiving Policy:** When and how completed artifacts are archived or deleted.
 - **Spec Organization:** Organize specification documents by lifecycle into two subfolders: `docs/project/specs/invariants/` (formats, contracts, and workflows of record — long-lived system invariants) and `docs/project/specs/features/` (to-be-implemented initiatives that feed the Spec → Milestone → Slice lifecycle — deleted per the Archiving Policy once implemented).
+- **Run Environment:** Specify the project's designated environment/dependency manager (e.g., `uv`, `poetry`, `pip`) and prefix ALL execution commands with its runner (e.g., `uv run pytest`). The chosen runner MUST be reflected in the `Makefile`.
+- **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>'` (VCP), and `make probe '<reason>'` (Remote Probing Protocol).
+
+## Templates
+
+Before creating or modifying any documentation artifact, agents MUST read the corresponding template from `docs/templates/`. The bundled templates are:
+
+| Template | Purpose |
+| -------- | ------- |
+| `specification-document.md` | Specification documents (features and invariants) |
+| `milestone.md` | Milestone documents |
+| `vertical-slice.md` | Vertical slice definitions |
+| `component-design.md` | Component design documents (ports and contracts) |
+| `task-brief.md` | Tactical task briefs |
+| `case-file.md` | Debugger case files |
+| `PROJECT.md` | This project dashboard |
+| `ARCHITECTURE.md` | System architecture document |
+| `makefile.md` | Makefile (VCP commit + Remote Probing Protocol commands) |
+| `ci.md` | CI workflow template (debug workflow for the Remote Probing Protocol) |
+
+These files live in `docs/templates/` and are created or refreshed by `teddy init templates`.
 
 ## Roadmap
 
@@ -42,12 +63,12 @@ A living list of upcoming Milestones and their high-level features.
 - **Core Goal:** Establish the foundational project infrastructure for testing, CI/CD, and pre-commit quality gates.
 - **Specs:** N/A — Milestone 0 is self-defining.
 - **Requirements:**
-    - **Testing Framework Setup:** Configure the project's designated test runner (e.g., `pytest`) with test discovery conventions.
+    - **Testing Framework Setup:** Configure the project's designated test runner (e.g., `pytest`) with test discovery conventions, exposed via a `make test` target (see the Makefile below).
     - **CI/CD Pipeline:** Set up two parallel jobs: 1) Blocking OS matrix test suite with coverage targets. 2) Non-blocking quality checks (formatters, linters, security scanners).
     - **Pre-commit Hooks:** Install the Pre-commit framework with hooks for formatters, linters, security scanners.
-    - **Post-commit Hook:** Implement a hook that runs the full test suite and reverts on failure.
+    - **Post-commit Hook:** Implement a hook that runs the full test suite via `make test` and reverts the commit on failure (via `git reset --soft HEAD~1`, keeping changes staged). This is the unskippable safety net — `--no-verify` MUST NOT bypass it.
     - **Debug Workflow:** Create `.github/workflows/debug.yml` following [docs/templates/ci.md](docs/templates/ci.md) to enable the Remote Probing Protocol.
-    - **Makefile:** Create a `Makefile` following [docs/templates/makefile.md](docs/templates/makefile.md) with `make commit` and `make probe` commands.
+    - **Makefile:** Create a `Makefile` following [docs/templates/makefile.md](docs/templates/makefile.md) with `make commit`, `make probe`, and `make test` commands. `make commit` implements the VCP workflow, `make probe` implements the Debugger's Remote Probing Protocol, and `make test` runs the full suite on demand.
 
 ## Technical Debt
 Tracks known technical debt for future cleanup.

{teddy_cli-0.1.17.dev1180 → teddy_cli-0.1.17.dev1181}/src/teddy_executor/resources/templates/makefile.md

@@ -14,7 +14,15 @@ make commit 'fix(tests): resolve flaky assertion' no-verify
 ```
 
 **What is `.PHONY`?**
-`.PHONY` is a Makefile directive that declares `commit` and `probe` as phony targets — they do not correspond to actual files. Without `.PHONY`, if a file named `commit` or `probe` existed in the directory (e.g., a script called `commit`), Make would see it as up-to-date and skip the target entirely. By declaring them phony, Make always runs the recipe when you call `make commit` or `make probe`.
+`.PHONY` is a Makefile directive that declares `commit`, `probe`, and `test` as phony targets — they do not correspond to actual files. Without `.PHONY`, if a file named `commit` or `probe` existed in the directory (e.g., a script called `commit`), Make would see it as up-to-date and skip the target entirely. By declaring them phony, Make always runs the recipe when you call `make commit`, `make probe`, or `make test`.
+
+### Test
+```shell
+make test
+```
+
+**What does `make test` run?**
+`make test` runs the project's full test suite via the designated runner (e.g. `uv run pytest`). The post-commit hook runs the same suite automatically on every commit; this target exposes it as an on-demand command for agents and developers. If a project's Makefile lacks a `test` target, agents MUST add one following this template.
 
 ### Probe
 ```shell
@@ -59,6 +67,17 @@ The Makefile uses Make's built-in `-` prefix for error suppression (`-pre-commit
 - **Windows (cmd.exe):** `-` prefix works because Make suppresses the exit code check, avoiding shell-specific `||` operators that cmd.exe does not support.
 - **Error transparency:** If pre-commit, pull, or push fail, the commit still succeeds locally. The post-commit test gate is the real safety net; remote failures appear as non-zero exit codes in the terminal output.
 
+## Test Workflow
+
+### Example
+
+```makefile
+test:
+	uv run pytest
+```
+
+**Usage:** `make test`
+
 ## VCP Commit Workflow
 
 ### Example

teddy_cli-0.1.17.dev1180/src/teddy_executor/resources/templates/MM-NN-vertical-slice.md → teddy_cli-0.1.17.dev1181/src/teddy_executor/resources/templates/vertical-slice.md

@@ -4,7 +4,7 @@
 - **Specs:** [links]
 - **Prototype:** [link]
 - **Component Docs:** [links]
-- **Scope Slug:** `feature-slug`
+- **Scope Slug:** `feature-slug`  <!-- 1-2 kebab-case words only. -->
 
 ## Business Goal