teddy-cli 0.1.17.dev1270__tar.gz → 0.1.17.dev1272__tar.gz

{teddy_cli-0.1.17.dev1270 → teddy_cli-0.1.17.dev1272}/PKG-INFO

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

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

@@ -52,7 +52,7 @@ NOTES:
       2. Commit Message: Use Conventional Commits '<type>(<scope>): <description>' wrapped in single quotes. Use imperative mood. Append ! for breaking changes.
       3. Execution: Run `make commit '<type>(<scope>): <description>'` to stage, run the local pre-commit hooks, and commit. `make commit` stages ALL local changes, including currently unstaged ones (`git add .`). The target commits WITHOUT `--no-verify`, so Git's own pre-commit hook is a real local gate; the post-commit test gate always runs and is unaffected.
       4. Post-conditions: All tests MUST pass — the post-commit hook runs the full suite and reverts the commit on failure; this gate is unskippable and MUST NEVER be bypassed. The pre-commit stage is advisory (its failures do not block the local commit), but if it reported non-trivial quality-gate issues (e.g. file length), you MUST make a follow-up cleanup commit that resolves them before resuming feature work. Triage any resulting `[DEBT]` per the Technical Debt Triage policy — there is no `## Technical Debt` holding pen.
-      5. Push at Conclusion: In the Conclusion phase, run `make push` to rebase onto the remote, push, and report the CI results. `make push` answers ONE question only: did this push turn a BLOCKING gate red? The pushed RUN's own conclusion is authoritative — it already folds in `continue-on-error`, so a non-blocking job (e.g. the CI `Quality Checks` job) can NEVER block the session. Only when the run-level conclusion is `failure` does attribution run: the base run (`origin/main` before the push) is classified as green, red, job-less, or absent, and a base that exists but is job-less is NOT green. A failure your push introduced (base green/absent/job-less -> new red) is YOUR regression (exit 1, fix before concluding); a failure already on the base (base red -> new red) is pre-existing (report and continue). Tests MUST always be fixed. A non-blocking quality result MUST be triaged per the Technical Debt Triage policy — fixed in-flight or explicitly scheduled into a slice or milestone — and MUST NOT be silently accepted.
+      5. Push at Conclusion: In the Conclusion phase, run `make push` to rebase onto the remote, push, and report the CI results. `make push` answers ONE question only: did this push turn a BLOCKING gate red? The pushed RUN's own conclusion is authoritative — it already folds in `continue-on-error`, so a non-blocking job (e.g. the CI `Quality Checks` job) can NEVER block the session. Only when the run-level conclusion is `failure` does attribution run: the base run (`origin/main` before the push) is classified as green, red, job-less, or absent, and a base that exists but is job-less is NOT green. A failure your push introduced (base green/absent/job-less -> new red) is YOUR regression (exit 1, fix before concluding); a failure already on the base (base red -> new red) is pre-existing (report and continue). `make push` prints each failing step's NAME, its run id, and that step's (bounded) log details; when a failure needs deeper investigation, read the FULL step log with `make logs <run-id> '<step-name>'`. Tests MUST always be fixed. A non-blocking quality result MUST be triaged per the Technical Debt Triage policy — fixed in-flight or explicitly scheduled into a slice or milestone — and MUST NOT be silently accepted.
     </rule>
 
     <rule n="7" name="Standardized Plan Types">

{teddy_cli-0.1.17.dev1270 → teddy_cli-0.1.17.dev1272}/src/teddy_executor/resources/config/prompts/developer.xml

@@ -13,7 +13,7 @@
     <workflow>
       <description>The Iterative Delivery Cycle. You MUST execute this full cycle (including VCP) for EACH individual deliverable separately.</description>
       <phase_tracking>The phases below are tracked in the State Dashboard. Use these exact phase names in the dashboard's WORKFLOW list.</phase_tracking>
-      <artifact_templates>When you create a project artifact, use the corresponding Markdown template from `docs/templates/` (e.g., `vertical-slice.md`, `case-file.md`, `task-brief.md`). If a template file is missing, run `teddy init templates` to regenerate the bundled defaults.</artifact_templates>
+      <artifact_templates>When you create a project artifact, use the corresponding Markdown template from `docs/templates/` (e.g., `vertical-slice.md`, `task-brief.md`). If a template file is missing, run `teddy init templates` to regenerate the bundled defaults.</artifact_templates>
 
       <phase n="1" name="Orientation">
         <goal>Foundation and scope verification.</goal>
@@ -108,7 +108,7 @@
             - Next slice un-designed (no slice `.md` exists) → Message the user to start a new session with the Architect to design the next slice JIT.
             - Next slice designed → Message the user to start a new session with the Prototyper (if unresolved `[ ]` Key Unknowns remain) or the Developer.
             - All slices complete in the Milestone → Message the user to start a new session with the Pathfinder to close the milestone and review the roadmap.
-          - If any step fails: Investigate root cause, then CREATE a Case File in `docs/project/debugging/` using the Case File blueprint and commit it. Message the user to start a new session with the Debugger, providing the Case File path as context. Do NOT return to Implementation.</step>
+          - If any step fails: Investigate the root cause yourself first. If the cause is isolated and the fix is clear, apply it and re-run Verification. If the root cause is still not obvious after your investigation, halt and Message the user (transition to BLOCKED 🔴) explaining what you attempted, what you observed, and what remains unclear — the user decides whether to invoke the Debugger. You MUST NOT create a Case File or start a Debugger session yourself. Do NOT return to Implementation.</step>
       </phase>
     </workflow>
 

{teddy_cli-0.1.17.dev1270 → teddy_cli-0.1.17.dev1272}/src/teddy_executor/resources/templates/makefile.md

@@ -137,7 +137,7 @@ The pushed RUN's own conclusion is authoritative: it already folds in `continue-
 - **all green / non-blocking** → PASSED → **exit 0**.
 - **job-less base** → NOT green: a base run that exists but carries zero jobs (an invalid-workflow failure) is treated as an unknown base and fails safe (block).
 
-When any step fails — blocking or not — the target also prints that step's log details via `gh run view <id> --log-failed` (ANSI/timestamp-stripped and indented), bounded to `DETAIL_LINES` lines (default 50), so the cause is visible without leaving the session.
+When any step fails — blocking or not — the target prints the failing step's name and its run id, then that step's log details (ANSI/timestamp-stripped and indented), bounded to `DETAIL_LINES` lines (default 50), and points to `make logs <run-id> '<step-name>'` for the full step log when needed.
 
 Attribution is deterministic: SHA → run → run-level + per-job conclusion (never "the latest run").
 
@@ -182,8 +182,9 @@ push:
 	  NEWFAIL=$$(gh run view "$$NEW" --json jobs --jq '[.jobs[] | select(.conclusion=="failure") | .name] | sort | join(",")'); \
 	  NEWSTEPS=$$(gh run view "$$NEW" --json jobs --jq '[.jobs[] | select(.conclusion=="failure") | .steps[]? | select(.conclusion=="failure") | .name] | sort | join(", ")'); \
 	  if [ -n "$$NEWSTEPS" ]; then \
-	    echo "$$WF: failing step(s): $$NEWSTEPS"; \
+	    echo "$$WF: failing step(s): $$NEWSTEPS (run $$NEW)"; \
 	    gh run view "$$NEW" --log-failed 2>/dev/null | awk -F'\t' '{ l=$$3; p=index(l,"Z "); if(p>0)l=substr(l,p+2); gsub(/\x1B\[[0-9;]*[a-zA-Z]/,"",l); gsub(/\^\[\[[0-9;]*[a-zA-Z]/,"",l); if(l ~ /^##\[group\]/ || l ~ /^##\[endgroup\]/) next; gsub(/^##\[error\]/,"Error: ",l); print l }' | tail -n $(DETAIL_LINES) | sed 's/^/    /'; \
+	    echo "  full log: make logs $$NEW '$$NEWSTEPS'"; \
 	  fi; \
 	  if [ "$$NEWCONC" != "failure" ]; then \
 	    if [ -n "$$NEWFAIL" ]; then \