Summary
pdd/prompts/agentic_bug_orchestrator_python.prompt is the spec for implementing pdd/agentic_bug_orchestrator.py. On main this file is currently absent, while tests still treat the on-disk prompt as the source of truth for per-step timeout configuration.
This issue tracks restoring the prompt file (full spec, not a stub) in a small, focused PR so history and review stay separate from unrelated work (e.g. dependency-graph / architecture validation changes).
Why this matters
- CI / tests: tests/test_agentic_bug_orchestrator.py::test_prompt_file_timeout_spec_matches_code_dict loads pdd/prompts/agentic_bug_orchestrator_python.prompt, parses the BUG_STEP_TIMEOUTS = { ... } block, and asserts it matches BUG_STEP_TIMEOUTS in pdd/agentic_bug_orchestrator.py (integer keys 1–12, no stale keys like 5.5, etc.).
- Single source of truth: The prompt documents orchestrator behavior (steps, worktree rules, etc.); the timeout dict in that prompt is explicitly meant to stay aligned with the Python module.
Summary
pdd/prompts/agentic_bug_orchestrator_python.prompt is the spec for implementing pdd/agentic_bug_orchestrator.py. On main this file is currently absent, while tests still treat the on-disk prompt as the source of truth for per-step timeout configuration.
This issue tracks restoring the prompt file (full spec, not a stub) in a small, focused PR so history and review stay separate from unrelated work (e.g. dependency-graph / architecture validation changes).
Why this matters