Bring Test Coverage to 95%

[stranske]

Why

Ensure that test coverage exceeds 95% for all program files.

Scope

Add test coverage for any program functionality with test coverage under 95% or for essential program functionality that does not currently have test coverage

Non-Goals (optional)

Increasing test coverage for the workflow pipeline or non-python files

Tasks

• Run soft coverage and prepare a list of the files with lowest coverage from least coverage on up for any file with less than 95% test coverage or any file with significant functionality that isn't covered.
• Increase test coverage incrementally for one set of related issues or 1 file below at a time
  • scripts/ci_cosmetic_repair.py
  • scripts/verify_codex_bootstrap.py
  • scripts/verify_trusted_config.py
  • scripts/workflow_smoke_tests.py
  • scripts/sync_tool_versions.p
  • scripts/sync_test_dependencies.py
  • scripts/ci_metrics.py
  • scripts/ci_history.py
  • scripts/run_multi_demo.py
  • .github/scripts/restore_branch_snapshots.py
  • .github/scripts/gate_summary.py
  • .github/scripts/health_summarize.py
  • .github/scripts/parse_chatgpt_topics.py
  • .github/scripts/decode_raw_input.py`

Acceptance criteria

• Test coverage exceeds 95% for each file

[github-actions]

Branch codex/issue-3572 created from phase-2-dev.

Option 1 (Invite) is enforced on issue events. PR creation is disabled by design so you are the PR author. Codex only engages on human-authored PRs.

Please open the PR as the author so Codex can work on it:

• Compare link: https://github.com/stranske/Trend_Model_Project/compare/phase-2-dev...codex/issue-3572?expand=1
• Suggested title: Codex bootstrap for #3572
• Suggested body (copy/paste):

### Keepalive: ON

### Source Issue #3572: Bring Test Coverage to 95%

Base: phase-2-dev
Head: codex/issue-3572

Source: https://github.com/stranske/Trend_Model_Project/issues/3572

> ## Why
> Ensure that test coverage exceeds 95% for all program files.
> 
> ## Scope
> Add test coverage for any program functionality with test coverage under 95% or for essential program functionality that does not currently have test coverage
> 
> ## Non-Goals (optional)
> Increasing test coverage for the workflow pipeline or non-python files
> 
> ## Tasks
> - Run soft coverage and prepare a list of the files with lowest coverage from least coverage on up for any file with less than 95% test coverage or any file with significant functionality that isn't covered.
> - Increase test coverage incrementally for one set of related issues or 1 file below at a time
>   - __init__.py
>   - data.py
>   - presets.py
>   - harness.py
>   - regimes.py
>   - pipeline.py
>   - validators.py
>   - run_analysis.py
>   - market_data.py
>   - signal_presets.py
>   - frequency.py
>   - signals.py
>   - bootstrap.p
>   - risk.py
>   - bundle.py
>   - cli.py
>   - optimizer.py
>   - model.py
>   - engine.py
> 
> ## Acceptance criteria
> - Test coverage exceeds 95% for each file
> - Essential functions for the program have full test coverage

@codex start

Codex, please derive and propose:
- Scope / key constraints
- Acceptance criteria / definition of done
- Initial task checklist to iterate through

Use the issue details above to draft the plan, then proceed with implementation.

---

Once the plan is posted, comment the snippet below to start execution and enable keepalive:

The following block should be pasted as a separate PR comment:

```markdown
@codex use the scope, acceptance criteria, and task list so the keepalive workflow continues nudging until everything is complete. Work through the tasks, checking them off only after each acceptance criterion is satisfied, but check during each comment implementation and check off tasks and acceptance criteria that have been satisfied and repost the current version of the initial scope, task list and acceptance criteria each time that any have been newly completed.