# Step 1: progress-logging

## Read First
- /AGENTS.md
- /PLAN.md
- /PROGRESS.md
- /docs/HARNESS.md
- /docs/IMPLEMENTATION_PLAN.md
- /docs/CONVERSION_POLICY.md
- /phases/6-cli-runtime-resume/step0.md

## Task
Implement progress reporting and stderr/local log behavior for chunk-level conversion.

Progress should summarize chunk success/failure without writing warnings or errors into Markdown content.

## Sprint Contract
- Done means: CLI/runtime tests can observe progress events and log file output in temp locations.
- Hard thresholds: Markdown chunks remain free of warning/error logs; failure summaries include chunk ids; logs use deterministic local paths from Phase 1.
- Files owned: `src/pdftomd/runtime.py`, CLI integration/tests, `PROGRESS.md`, phase index.
- Dependencies: CLI entrypoint and output/cache contracts.

## Acceptance Criteria
```powershell
python scripts\validate_workspace.py
.\venv\python.exe -m pytest tests
```

## Verification
1. Run the acceptance commands.
2. Confirm stderr/log behavior is tested separately from Markdown output.
3. Update `PROGRESS.md` and this phase index.

## Do Not
- Do not write runtime logs inside generated Markdown.
- Do not require a real PDF conversion for progress unit tests.
- Do not create persistent logs outside temp dirs in tests.