[PHASE 5] Utility Edge-Case Coverage

[ashleyshaw]

Summary

Add tests for utility helpers and boundary conditions so the coverage target is not inflated by fragile paths.

Action

• Action Type: Create
• Target File: scripts/utils/__tests__/

Proposed Test Content

This phase covers tasks 5.1 to 5.12 from the source README:

• identify utility helpers with the biggest gaps
• cover normal and invalid-input paths
• cover date/time, path/file, parsing, serialisation, and logging helpers
• rerun coverage on the utility slice and document the result

Scope & Applicability

• Type: Utility and edge-case coverage
• Affected Areas: shared helper functions, boundary conditions, error propagation
• Audience: maintainers, developers, QA

Parent Issue

• Parent Issue: [EPIC] Test Coverage Implementation Programme #932

Acceptance Criteria

• Utility helpers with the largest gaps are covered.
• Boundary and invalid-input paths are covered.
• Coverage measurements improve without brittle tests.
• The phase is documented and reproducible.
• Change is documented in the project change log.
• PR uses correct branch prefix (test/).

Additional Context

This phase is the main catch-all for non-agent helper coverage debt.

---

Definition of Ready (DoR)

• Purpose, scope, and audience defined
• Target file and action type specified
• Acceptance criteria listed
• Estimate added (if applicable)

Definition of Done (DoD)

• All acceptance criteria met and verified
• Changelog entry prepared for PR
• Test passes all required scenarios and environments
• Documentation updated (if needed)
• PR uses correct branch prefix (test/)
• Approved by at least one maintainer

[linear-code]

LS-1000