teddy-cli 0.1.17.dev1343__tar.gz → 0.1.17.dev1345__tar.gz

{teddy_cli-0.1.17.dev1343 → teddy_cli-0.1.17.dev1345}/PKG-INFO

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

@@ -1,6 +1,6 @@
 [project]
 name = "teddy-cli"
-version = "0.1.17.dev1343"
+version = "0.1.17.dev1345"
 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.dev1343 → teddy_cli-0.1.17.dev1345}/src/teddy_executor/adapters/outbound/terminal_quit_key_listener.py

@@ -16,12 +16,12 @@ from __future__ import annotations
 import importlib
 import os
 import select
-import signal
 import sys
 import threading
 from typing import Any, Optional, cast
 
 from teddy_executor.core.ports.outbound.quit_key_listener import QuitCallback
+from teddy_executor.core.utils.interrupt_guard import raise_interrupt
 from teddy_executor.core.utils.stdin_ownership import is_stdin_owned
 from teddy_executor.core.utils.terminal import restore_cooked_mode
 
@@ -150,8 +150,13 @@ class TerminalQuitKeyListener:
             self._trigger()
 
     def _trigger(self) -> None:
-        """Invoke the injected hook, or self-deliver SIGINT by default."""
+        """Invoke the injected hook, or self-deliver SIGINT by default.
+
+        The default branch uses the shared ``raise_interrupt`` primitive so
+        the installed guard handler runs on every platform. ``os.kill`` would
+        terminate the process on Windows before the handler runs.
+        """
         if self._on_quit is not None:
             self._on_quit()
             return
-        os.kill(os.getpid(), signal.SIGINT)
+        raise_interrupt()

{teddy_cli-0.1.17.dev1343 → teddy_cli-0.1.17.dev1345}/src/teddy_executor/container.py

@@ -1,7 +1,5 @@
 from __future__ import annotations
 
-import os
-import signal
 import time
 
 import punq
@@ -41,10 +39,13 @@ def _record_quit_source(container: punq.Container) -> None:
     default `Ctrl+C`; the self-delivered SIGINT then drives the shared guard's
     already-tested WAITING/EXECUTING branch unchanged.
     """
-    from teddy_executor.core.utils.interrupt_guard import InterruptGuard
+    from teddy_executor.core.utils.interrupt_guard import (
+        InterruptGuard,
+        raise_interrupt,
+    )
 
     container.resolve(InterruptGuard).record_source("q")
-    os.kill(os.getpid(), signal.SIGINT)
+    raise_interrupt()
 
 
 def _register_services(container: punq.Container) -> None:

{teddy_cli-0.1.17.dev1343 → teddy_cli-0.1.17.dev1345}/src/teddy_executor/core/utils/interrupt_guard.py

@@ -121,3 +121,15 @@ class InterruptGuard:
         finally:
             self._executing = False
             self._first_signal_at = None
+
+
+def raise_interrupt() -> None:
+    """Deliver SIGINT in-process so the installed handler runs on every platform.
+
+    ``os.kill(os.getpid(), signal.SIGINT)`` terminates the process on Windows
+    through ``TerminateProcess`` instead of invoking the Python SIGINT handler,
+    which suppresses the interrupt notice. ``signal.raise_signal`` uses the
+    process-level CRT raise path and reaches the handler from the main thread
+    and from a reader thread on every platform.
+    """
+    signal.raise_signal(signal.SIGINT)

{teddy_cli-0.1.17.dev1343 → teddy_cli-0.1.17.dev1345}/src/teddy_executor/resources/config/prompts/architect.md

@@ -30,7 +30,7 @@ Follow these phases and steps in order. Keep track of your progress in your Stat
 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.
 4. **Architecture Maintenance:**
-   Update the Component and Boundary Map and Key Architectural Decisions in `docs/architecture/ARCHITECTURE.md` to reflect the design.
+   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:**

{teddy_cli-0.1.17.dev1343 → teddy_cli-0.1.17.dev1345}/src/teddy_executor/resources/templates/ARCHITECTURE.md

@@ -22,6 +22,14 @@ This section defines foundational engineering practices. Each entry MUST be a sp
   `docs/architecture/BOUNDARY/LAYER/TYPE/name.md` -> Source path: `src/{pkg}/BOUNDARY/LAYER/TYPE/name.ext` -> Test path: `tests/suites/TEST_TYPE/BOUNDARY/LAYER/TYPE/test_name.ext`
 - **Makefile Commands:** The `Makefile` is the canonical entry point for the version control workflow and on-demand test runs: `make test` (full suite), `make commit '<msg>'` (local commit with advisory auto-fix and unskippable post-commit test gate), `make push` (rebase and push), `make ci-watch` (CI monitoring), and `make probe '<reason>'` (Remote Probing Protocol). See [docs/templates/makefile.md](docs/templates/makefile.md).
 
+## Ubiquitous Language
+
+The canonical domain vocabulary. All documentation, component names, tests, and agent prompts must use these terms consistently.
+
+**Template format:** `- **Term:** Concise definition and operational boundary.`
+
+- **TermName:** Definition of the core domain concept and its operational boundaries.
+
 ## Component & Boundary Map
 
 Single source of truth for system structure, organized by architectural layer.
@@ -56,27 +64,6 @@ 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.