[PHASE 4] Release Agent Coverage Hardening

[ashleyshaw]

Summary

Improve the release agent so it participates in the coverage programme and enforces the expected release-time checks.

Action

• Action Type: Create
• Target File: scripts/agents/release.agent.js

Proposed Test Content

This phase covers tasks 4.1 to 4.10 from the source README:

• review the release agent control flow
• add coverage-aware checks and guardrails
• validate release output formatting and deterministic state transitions
• document coverage-related release constraints and rollout notes
• add tests for the new release-agent paths

Scope & Applicability

• Type: Automation and release hardening
• Affected Areas: release agent checks, release gating, rollout/rollback documentation
• Audience: maintainers, developers, QA

Parent Issue

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

Acceptance Criteria

• Release-agent behaviour is adjusted without breaking existing release flows.
• Coverage-aware checks are enforced where needed.
• Tests cover the new release-agent behaviour.
• Rollout and rollback notes are documented.
• Change is documented in the project change log.
• PR uses correct branch prefix (test/).

Additional Context

This phase protects the final release path from bad or incomplete coverage state.

---

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-999