teddy-cli 0.1.17.dev1276__tar.gz → 0.1.17.dev1277__tar.gz

{teddy_cli-0.1.17.dev1276 → teddy_cli-0.1.17.dev1277}/PKG-INFO

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

@@ -1,6 +1,6 @@
 [project]
 name = "teddy-cli"
-version = "0.1.17.dev1276"
+version = "0.1.17.dev1277"
 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.dev1276 → teddy_cli-0.1.17.dev1277}/src/teddy_executor/resources/config/prompts/prototyper.xml

@@ -18,18 +18,18 @@
         <step n="2" name="Iteration Loop">Iterate until internal workings are deeply understood and all Technical and Functional unknowns are resolved. If an unexpected failure occurs, isolate it using a focused sub-prototype. Update Key Unknowns with any emerging uncertainties.</step>
       </phase>
 
-      <phase n="3" name="Documentation">
-        <goal>Translate verified findings into buildable slices, component designs, and specifications.</goal>
-        <step n="1" name="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.</step>
-        <step n="2" name="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 a non-breaking parallel change: expand, migrate, contract. Ensure all contract changes include matching harness deliverables.</step>
-      </phase>
-
-      <phase n="4" name="Alignment">
+      <phase n="3" name="Alignment">
         <goal>Present prototype findings and demo to the user for explicit validation and approval.</goal>
         <step n="1" name="Showcase Presentation">Message the user to present findings in clear prose. For Technical unknowns, provide raw assertion evidence or benchmarks. For Functional unknowns, provide copy-pasteable execution commands and list adjustable knobs. Present the updated slice deliverables and component specifications.</step>
         <step n="2" name="Approval Gate">Await explicit user approval before proceeding to the Conclusion phase. If the user requests changes, refine the prototypes and artifacts, re-run verification, and re-align.</step>
       </phase>
 
+      <phase n="4" name="Documentation">
+        <goal>Translate verified findings into buildable slices, component designs, and specifications.</goal>
+        <step n="1" name="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 a non-breaking parallel change: expand, migrate, contract. Ensure all contract changes include matching harness deliverables.</step>
+        <step n="2" name="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.</step>
+      </phase>
+
       <phase n="5" name="Conclusion">
         <goal>Clean workspace, commit changes, push, and hand off to the Developer.</goal>
         <step n="1" name="Cleanup">Delete scratch files and unapproved probes, preserving only the approved prototype directory under `spikes/prototypes/{scope-slug}/`.</step>

{teddy_cli-0.1.17.dev1276 → teddy_cli-0.1.17.dev1277}/src/teddy_executor/resources/templates/ci.md

@@ -15,8 +15,8 @@ The CI pipeline consists of two parallel jobs:
 - **Blocking:** If this job fails, the CI pipeline is marked as failed.
 
 ### Job 2: Non-Blocking Quality Checks
-- Runs the pre-commit hooks in two explicit passes: the fast hooks (formatters, `detect-secrets`, merge-conflict check) at the default `pre-commit` stage, then the heavy hooks (type checkers, security/dependency scanners, and the repository-wide structural checkers) at the non-default `manual` stage.
-- The heavy hooks are scoped to the `manual` stage so they never slow down the local pre-commit loop; CI invokes both stages explicitly.
+- Runs granular quality checks in separate steps with `if: success() || failure()`, ensuring that all checks execute and report their outcomes even if an earlier check fails.
+- Scopes heavy checks (type checkers, security/dependency scanners, structural checkers) to the non-default `manual` stage so they never slow down the local pre-commit loop.
 - Excludes sandboxes (`spikes/`) and third-party dependencies.
 - **Non-Blocking:** Configured with `continue-on-error: true` so quality failures do not block the pipeline.
 
@@ -97,16 +97,32 @@ jobs:
       - name: Install dependencies
         run: {runner} sync --frozen
 
-      # Quote any step name that contains a colon. An unquoted YAML plain
-      # scalar cannot contain ": " (colon+space) — it would be parsed as a
-      # nested mapping and fail the entire workflow.
-      - name: "Run Pre-commit Hooks (fast: formatters, secrets)"
+      # Each check runs with `if: success() || failure()` so all checks run
+      # even if an earlier check fails.
+      - name: "Secrets Check (detect-secrets)"
+        if: success() || failure()
         run: |
-          {runner} pre-commit run --all-files
+          {runner} pre-commit run detect-secrets --all-files
 
-      - name: "Run Pre-commit Hooks (heavy: types, security, structural)"
+      - name: "Code Formatting (ruff format)"
+        if: success() || failure()
         run: |
-          {runner} pre-commit run --all-files --hook-stage manual
+          {runner} pre-commit run ruff-format --all-files
+
+      - name: "Linter (ruff check)"
+        if: success() || failure()
+        run: |
+          {runner} pre-commit run ruff-lint --all-files
+
+      - name: "Type Checker (mypy)"
+        if: success() || failure()
+        run: |
+          {runner} pre-commit run mypy --all-files --hook-stage manual
+
+      - name: "Security Audit (bandit & pip-audit)"
+        if: success() || failure()
+        run: |
+          {runner} pre-commit run bandit pip-audit --all-files --hook-stage manual
 ```
 
 ## Debug Workflow (Remote Probing Protocol)