Bump version

Author: gltanaka

CHANGELOG.md

@@ -1,14 +1,46 @@
+## v0.0.98 (2025-12-31)
+
+### Feat
+
+- Add check for suspicious single-letter files during release process
+- Add cloud execution support for pdd test command
+
 ## v0.0.97 (2025-12-30)
 
 ### Feat
 
-- Enhance CLI Python prompt to display examples used for grounding
-- Add diagnostic logging for Issue #186 (C, E, T files)
-- Enhance cloud execution and syntax validation
+- **CLI Examples Display:** After each command step, the CLI now displays examples used for grounding (slug and title), helping users know what to use in `<pin>` or `<exclude>` tags.
+
+- **Suspicious Files Diagnostic Logging (Issue #186):** Added `_detect_suspicious_files()` in `agentic_fix.py` to detect and log when single-character files (C, E, T) are created during agentic operations. Logs include timestamp, context, directory, file sizes, and stack trace. Persistent log saved to `~/.pdd/suspicious_files.log`.
+
+- **Cloud Example Generation:** Added cloud execution support to `context_generator_main` via async `_run_cloud_generation()` function. Uses JWT authentication with automatic local fallback on cloud failure.
+
+- **Improved Syntax Repair:** Rewrote `_validate_and_fix_python_syntax()` with a binary search algorithm to find the longest valid Python prefix when LLM output contains trailing JSON garbage (e.g., `"explanation":` metadata).
+
+### Fix
+
+- **Nested asyncio.run() Bug (PR #204):** Fixed `pdd example` command failing to make cloud calls due to nested asyncio.run() error. The issue occurred because `CloudConfig.get_jwt_token()` uses asyncio.run() internally, causing conflicts when called from within an async context. Fixed by acquiring JWT token before entering the async context. (Thanks Jiamin Cai!)
+
+- **HTTPStatusError Response Text:** Fixed error handling to check for empty `.text` instead of checking if response exists (response is always present on HTTPStatusError).
+
+- **Test Overwrite Bug:** Fixed sync bug that would overwrite existing tests. Now uses append mode when merging with existing tests via the `--merge` flag.
+
+- **CLI Test Fixture:** Fixed test fixture checking for "install_completion" instead of "install-completion" (Click converts underscores to hyphens in command names).
 
 ### Refactor
 
-- Update prompts to support existing test files as lists
+- **Existing Tests as Lists:** Changed `existing_tests` parameter from string path to list of paths in prompts, enabling multiple test files to be concatenated for context.
+
+- **Test File Organization:** Moved `tests/test_core_cli.py` to `tests/core/test_cli.py` for better module organization.
+
+### Docs
+
+- Clarified `existing_tests` parameter behavior in `cmd_test_main_python.prompt`, documenting that it accepts a list of test file paths.
+
+### Tests
+
+- Added regression tests for nested asyncio.run() bug in `test_context_generator_main.py`.
+- Updated `test_cmd_test_main.py` with coverage for test file append mode and existing_tests list handling.
 
 ## v0.0.96 (2025-12-29)
 

Makefile

@@ -585,7 +585,33 @@ publish:
 check-deps:
 	@python scripts/check_deps.py
 
-release: check-deps
+# Issue #186: Detect suspicious single-letter files (C, E, T)
+# These files sometimes appear during release operations
+# Files are logged but NOT removed so we can debug when it happens
+.PHONY: check-suspicious-files
+check-suspicious-files:
+	@echo "Checking for suspicious single-letter files (Issue #186)..."
+	@SUSPICIOUS=$$(find . -maxdepth 1 -type f \( -name 'C' -o -name 'E' -o -name 'T' -o -name '?' -o -name '??' \) ! -name '.*' 2>/dev/null); \
+	if [ -n "$$SUSPICIOUS" ]; then \
+		echo "⚠️  SUSPICIOUS FILES DETECTED:"; \
+		echo "$$SUSPICIOUS"; \
+		echo "Logging to ~/.pdd/suspicious_files.log"; \
+		mkdir -p ~/.pdd; \
+		echo "" >> ~/.pdd/suspicious_files.log; \
+		echo "============================================================" >> ~/.pdd/suspicious_files.log; \
+		echo "Timestamp: $$(date -Iseconds)" >> ~/.pdd/suspicious_files.log; \
+		echo "Context: make check-suspicious-files" >> ~/.pdd/suspicious_files.log; \
+		echo "Directory: $$(pwd)" >> ~/.pdd/suspicious_files.log; \
+		echo "Files: $$SUSPICIOUS" >> ~/.pdd/suspicious_files.log; \
+		for f in $$SUSPICIOUS; do \
+			echo "  File: $$f, Size: $$(stat -f%z "$$f" 2>/dev/null || stat -c%s "$$f" 2>/dev/null) bytes, Modified: $$(stat -f%Sm "$$f" 2>/dev/null || stat -c%y "$$f" 2>/dev/null)" >> ~/.pdd/suspicious_files.log; \
+		done; \
+		echo "Files left in place for debugging."; \
+	else \
+		echo "No suspicious files found."; \
+	fi
+
+release: check-deps check-suspicious-files
 	@echo "Preparing release"
 	@CURRENT_VERSION=$$(sed -n '1,120s/^version[[:space:]]*=[[:space:]]*"\([0-9.]*\)"/\1/p' pyproject.toml | head -n1); \
 	CURRENT_TAG="v$$CURRENT_VERSION"; \
@@ -600,6 +626,8 @@ release: check-deps
 		echo "Publishing new version"; \
 		$(MAKE) publish; \
 	fi
+	@# Post-release cleanup check (Issue #186)
+	@$(MAKE) check-suspicious-files
 
 analysis:
 	@echo "Running regression analysis"

README.md

@@ -1,6 +1,6 @@
 # PDD (Prompt-Driven Development) Command Line Interface
 
-![PDD-CLI Version](https://img.shields.io/badge/pdd--cli-v0.0.97-blue) [![Discord](https://img.shields.io/badge/Discord-join%20chat-7289DA.svg?logo=discord&logoColor=white)](https://discord.gg/Yp4RTh8bG7)
+![PDD-CLI Version](https://img.shields.io/badge/pdd--cli-v0.0.98-blue) [![Discord](https://img.shields.io/badge/Discord-join%20chat-7289DA.svg?logo=discord&logoColor=white)](https://discord.gg/Yp4RTh8bG7)
 
 ## Introduction
 
@@ -285,7 +285,7 @@ export PDD_TEST_OUTPUT_PATH=/path/to/tests/
 
 ## Version
 
-Current version: 0.0.97
+Current version: 0.0.98
 
 To check your installed version, run:
 ```

context/cmd_test_main_example.py

@@ -1,108 +1,100 @@
-# test_cli_example.py
-
-"""
-This example demonstrates how to integrate the 'cmd_test_main' function into a
-Click-based command line interface (CLI). It shows how to accept CLI arguments,
-then invoke the command to generate or enhance unit tests.
-
-Usage:
-  1. Create a CLI script like this with the code below.
-  2. Run it from the command line, for instance:
-     $ python test_cli_example.py test ./prompt.txt ./my_code.py --output ./tests/test_my_code.py
-
-Required Arguments:
-  - prompt_file: Path to the text file that generated the code (e.g., a GPT prompt).
-  - code_file: Path to the source code file to be tested.
-
-Optional Arguments:
-  - --output: Path to save the newly generated or enhanced test file. Defaults to an auto-generated path if omitted.
-  - --language: Programming language override if you want to force tests in a certain language.
-  - --coverage-report: Path to an existing coverage report. If provided, requires --existing-tests to enhance tests.
-  - --existing-tests: Path to an existing test file to merge or enhance.
-  - --target-coverage: Desired test coverage percentage (float). Only used if --coverage-report is set.
-  - --merge: Flag to merge new tests into the existing tests specified by --existing-tests.
-
-Returns:
-  - A tuple (generated_test_code: str, total_cost: float, model_name: str)
-"""
-
+import os
 import click
-from pdd.cmd_test_main import cmd_test_main  # Adjust import to match your package structure
+from pathlib import Path
+from rich.console import Console
 
+# Import the function to be tested
+# Note: In a real package structure, this would be: from pdd.cmd_test_main import cmd_test_main
+# We assume the pdd package is installed or in the python path.
+from pdd.cmd_test_main import cmd_test_main
 
-@click.group()
-@click.option("--verbose", is_flag=True, default=False, help="Enable verbose logging.")
-@click.option("--strength", default=0.7, type=float, help="Controls AI generation strength.")
-@click.option("--temperature", default=0.7, type=float, help="Controls AI generation creativity.")
-@click.option("--force", is_flag=True, default=False, help="Force overwrite of existing files.")
-@click.option("--quiet", is_flag=True, default=False, help="Suppress non-error output.")
-@click.pass_context
-def cli(ctx, verbose, strength, temperature, force, quiet):
+# Setup console for output
+console = Console()
+
+def run_example():
+    """
+    Demonstrates how to use cmd_test_main to generate unit tests for a simple calculator module.
     """
-    Top-level CLI group. Sets up shared context for all subcommands.
+    # 1. Setup paths and directories
+    base_dir = Path("./output")
+    base_dir.mkdir(exist_ok=True)
 
-    Global Options:
-      --verbose, --strength, --temperature, --force, --quiet
+    prompt_file = base_dir / "calculator_python.prompt"
+    code_file = base_dir / "calculator.py"
+    output_test_file = base_dir / "test_calculator.py"
+
+    # 2. Create dummy input files
+    # Create a prompt file
+    prompt_content = """
+    Task: Create a simple calculator module.
+    Requirements:
+    - Implement add(a, b)
+    - Implement subtract(a, b)
     """
-    ctx.ensure_object(dict)
-    ctx.obj["verbose"] = verbose
-    ctx.obj["strength"] = strength
-    ctx.obj["temperature"] = temperature
-    ctx.obj["force"] = force
-    ctx.obj["quiet"] = quiet
+    prompt_file.write_text(prompt_content, encoding="utf-8")
 
+    # Create the corresponding code file
+    code_content = """
+def add(a, b):
+    return a + b
 
-@cli.command()
-@click.pass_context
-@click.argument("prompt_file", type=click.Path(exists=True))
-@click.argument("code_file", type=click.Path(exists=True))
-@click.option("--output", type=click.Path(), default=None, help="Output path for generated tests.")
-@click.option("--language", type=str, default=None, help="Override detected programming language.")
-@click.option("--coverage-report", type=click.Path(exists=True), default=None,
-              help="Path to a coverage report for enhancing tests.")
-@click.option("--existing-tests", type=click.Path(exists=True), default=None,
-              help="Existing test file to merge or build upon.")
-@click.option("--target-coverage", type=float, default=None, help="Desired coverage percentage.")
-@click.option("--merge", is_flag=True, default=False, help="Merge new tests into existing tests.")
-def test(
-    ctx,
-    prompt_file,
-    code_file,
-    output,
-    language,
-    coverage_report,
-    existing_tests,
-    target_coverage,
-    merge,
-):
+def subtract(a, b):
+    return a - b
     """
-    Generate or enhance unit tests for the provided code.
+    code_file.write_text(code_content, encoding="utf-8")
 
-    Examples:
-      python test_cli_example.py test prompt.txt my_code.py --output tests/test_my_code.py
-      python test_cli_example.py test prompt.txt my_code.py --coverage-report coverage.xml --existing-tests tests/test_my_code.py --merge
+    console.print("[bold green]Created input files:[/bold green]")
+    console.print(f"  Prompt: {prompt_file}")
+    console.print(f"  Code:   {code_file}")
 
-    """
-    # Note: strength and temperature parameters can be passed explicitly to override ctx.obj values.
-    # This is useful when orchestrators need to pass specific values.
-    generated_tests, total_cost, model_name = cmd_test_main(
+    # 3. Mock the Click Context
+    # cmd_test_main expects a click.Context object with specific obj keys
+    ctx = click.Context(click.Command("test"))
+    ctx.obj = {
+        "verbose": True,
+        "force": True,      # Force overwrite without prompting
+        "quiet": False,
+        "local": True,      # Force local execution for this example
+        "context": None,    # Optional context override
+        "confirm_callback": None
+    }
+
+    # 4. Define arguments for cmd_test_main
+    # Note: We set strength/temperature here, but they can also be resolved from config
+    strength = 0.5
+    temperature = 0.0
+    
+    console.print("\n[bold blue]Running cmd_test_main...[/bold blue]")
+
+    # 5. Call the function
+    # This will generate the test code, save it to output_test_file, and return details
+    unit_test_code, total_cost, model_name = cmd_test_main(
         ctx=ctx,
-        prompt_file=prompt_file,
-        code_file=code_file,
-        output=output,
-        language=language,
-        coverage_report=coverage_report,
-        existing_tests=existing_tests,
-        target_coverage=target_coverage,
-        merge=merge,
-        # Optional: pass strength=0.8 or temperature=0.5 to override ctx.obj values
+        prompt_file=str(prompt_file),
+        code_file=str(code_file),
+        output=str(output_test_file),
+        language="python",       # Explicitly set language
+        coverage_report=None,    # Not using coverage report mode
+        existing_tests=None,     # Not augmenting existing tests
+        target_coverage=None,
+        merge=False,
+        strength=strength,
+        temperature=temperature
     )
 
-    # Provided for demonstration. You can print or further process the returned data.
-    click.echo(f"Generated Tests:\n{generated_tests}")
-    click.echo(f"Total Cost: ${total_cost:.6f}")
-    click.echo(f"Model Used: {model_name}")
-
+    # 6. Display results
+    console.print("\n[bold green]Execution Complete![/bold green]")
+    console.print(f"Model Used: {model_name}")
+    console.print(f"Estimated Cost: ${total_cost:.6f}")
+    console.print(f"Test file saved to: {output_test_file}")
+    
+    console.print("\n[bold]Generated Test Code Preview (first 5 lines):[/bold]")
+    preview = "\n".join(unit_test_code.splitlines()[:5])
+    console.print(preview)
 
 if __name__ == "__main__":
-    cli()
+    # Ensure PDD_PATH is set if your environment requires it for config resolution
+    if "PDD_PATH" not in os.environ:
+        os.environ["PDD_PATH"] = os.getcwd()
+        
+    run_example()

examples/hello/repo_root

@@ -1 +1 @@
-Subproject commit 5547071b64416d2f003789cd163fc105105e5141
+Subproject commit 5410d97a393dbf10f91ae2ed99866cb0002b6d3c

pdd/__init__.py

@@ -1,6 +1,6 @@
 """PDD - Prompt Driven Development"""
 
-__version__ = "0.0.97"
+__version__ = "0.0.98"
 
 # Strength parameter used for LLM extraction across the codebase
 # Used in postprocessing, XML tagging, code generation, and other extraction