Promote the output contract to version 1.0 #90

New issue

Closed

opened 2026-07-01 00:53:38 +00:00 by manlycucumber · 0 comments

manlycucumber commented

2026-07-01 00:53:38 +00:00

(Migrated from github.com)

Problem

The output contract has evolved through 0.x. It must be stamped 1.0 with frozen field semantics so API consumers can rely on it long-term.

Acceptance criteria

Contract version is set to 1.0 in output
All fields are documented as stable
A migration note covers any 0.x to 1.0 changes
Snapshot tests pin the 1.0 shape

Notes

Future additions must be additive within 1.x.

## Problem The output contract has evolved through 0.x. It must be stamped 1.0 with frozen field semantics so API consumers can rely on it long-term. ## Acceptance criteria - [ ] Contract version is set to 1.0 in output - [ ] All fields are documented as stable - [ ] A migration note covers any 0.x to 1.0 changes - [ ] Snapshot tests pin the 1.0 shape ## Notes Future additions must be additive within 1.x.