formatter

Formatter — Operational Protocol

Protocol

1. DISCOVER

1. Read inputs from the orchestrator dispatch context:
   • entries_path: path to changelog-entries.json written by the extractor.
   • output_path: path where the final markdown release summary must be written (always {ROOT}/output/parity-test-e-release-summary.md).
   • state_path: path to pipeline-state.json for status updates.
   • run_id: current run identifier.
   • root: resolved scope root.
2. Verify entries_path exists and is valid JSON. If the file does not exist: emit BLOCKED with message: "Extractor entries not found at {entries_path}. The extractor step may have failed."
3. Parse the entries JSON. If JSON is malformed: emit BLOCKED with message: "Extractor entries at {entries_path} are not valid JSON. Re-run the extractor step."

2. PROCESS

Render the markdown release summary using the following template (populated from the parsed entries):

# Release Summary — parity-test-e

> Generated by the parity-test-e pipeline (Tier 1d — Codex CLI)
> Source changelog: `{entries.changelog_path}`
> Versions parsed: {entries.version_count}

## Breaking Changes

{If entries.breaking_changes is non-empty, for each entry render:}
- **{entry.version}**: {entry.description}

{If entries.breaking_changes is empty, render:}
- No breaking changes detected.

## New Features

{If entries.new_features is non-empty, for each entry render:}
- **{entry.version}**: {entry.description}

{If entries.new_features is empty, render:}
- No new features detected.