teddy-cli 0.1.16.dev1173__tar.gz → 0.1.16.dev1174__tar.gz

{teddy_cli-0.1.16.dev1173 → teddy_cli-0.1.16.dev1174}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.5
 Name: teddy-cli
-Version: 0.1.16.dev1173
+Version: 0.1.16.dev1174
 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.16.dev1173 → teddy_cli-0.1.16.dev1174}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "teddy-cli"
-version = "0.1.16.dev1173"
+version = "0.1.16.dev1174"
 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.16.dev1173 → teddy_cli-0.1.16.dev1174}/src/teddy_executor/adapters/inbound/session_cli_handlers.py

@@ -695,7 +695,7 @@ def _persist_editor_choice(config_service: IConfigService, value: str) -> None:
 # here -- now what?" without the ambiguous word "listed": add it to PATH, or
 # enter an absolute path (which ``which()`` resolves as a direct path even when
 # the binary is off-PATH). Single-sourced so both branches stay in lockstep
-# (see docs/project/specs/editor-validation-and-discovery.md §4).
+# (see the editor-validation spec §4).
 _EDITOR_SETUP_TIP = (
     "Tip: Don't see your editor? Make sure it's available in your PATH, "
     "or enter its absolute path below."

{teddy_cli-0.1.16.dev1173 → teddy_cli-0.1.16.dev1174}/src/teddy_executor/resources/templates/PROJECT.md

@@ -19,6 +19,7 @@ Defines the high-level artifact lifecycle and conventions for project management
 - **Artifact Lifecycle:** How work flows (e.g., Spec → Milestone → Slice).
 - **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).
 
 ## Roadmap
 
@@ -53,4 +54,9 @@ Tracks known technical debt for future cleanup.
 
 **Format:** `- [Description including context and location of the debt item.]`
 
+**Logging Hygiene (MUST):**
+- **Never re-log the same debt.** If a debt item recurs across commits, fold the new occurrence into the existing entry — do NOT append a new bullet.
+- **Prefer fixing directly over logging.** Only log debt that genuinely cannot be resolved in the moment. Do not log-then-resolve a defect that could be fixed immediately.
+- **Never log resolved items.** Do not add "informational" or "completed" entries.
+
 **Deletion Policy:** When a technical debt item is addressed (the underlying issue is resolved in a completed milestone/slice), the entry MUST be deleted from this section. Do not mark it as "completed" or "resolved" — remove it entirely. Git history serves as the permanent record.