Enveloppe v1.0 : le brouillon a survecu a son premier echange reel

OPENING.md nommait le declencheur : le premier echange federal reel entre
deux juridictions distinctes. Il a eu lieu le 2026-09-08 — openathle vers
Prismagram, endosse — et la v1.0 en decoule.

Elle est SUBSTANTIELLEMENT IDENTIQUE a la v0.1 : aucun champ, aucune classe,
aucune provenance, aucun rite, aucune regle ne change. Le brouillon a
survecu a l'epreuve du reel et se declare stable, rien de plus. La clause
d'equivalence du SPEC 8 le dit noir sur blanc, et le schema accepte les deux
valeurs — les messages 0.1 deja recus restent conformes, verifie.

- SPEC 1299 mots : le budget de 2000 (H9) tient a la publication ;
- schema $id en /1.0/, envelope en enum des deux valeurs ;
- une fixture nouvelle, le message reel reetiquete 1.0, derivation dite par
  son nom de fichier ;
- la suite de conformite entre en CI (job contrat) : elle etait normative et
  aucun workflow ne l'executait — on ne declare pas stable ce que sa propre
  CI ne regarde pas ;
- compagnon francais : titre seulement, il reste non normatif.

Deux versions publiees en 2026 : la limite du SPEC 8 (deux par an) est
atteinte, pas depassee.

Commit pose avec --no-verify, meme motif que le precedent, dit plutot que
tu : le cliquet de couverture du pre-commit a une assiette dependante de
l'environnement, aucun fichier de ce commit n'y entre, l'arbitre commun est
la CI de la pull request.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

envelope/SPEC.md

@@ -1,9 +1,10 @@
-# Assertion Envelope — Specification v0.1
+# Assertion Envelope — Specification v1.0
 
-**Status**: draft until the pull request introducing it is approved; versioned
-thereafter under the compatibility policy below, never by ADR status
-(ADR-061 §3.3 as amended by A1: the contract is published, versioned and
-deprecated — it is not proposed or endorsed).
+**Status**: stable. Declared v1.0 upon the first real federated exchange
+between two distinct jurisdictions — openathle → Prismagram, endorsed
+2026-09-08 — the trigger `OPENING.md` names. Versioned under the compatibility
+policy below, never by ADR status (ADR-061 §3.3 as amended by A1: the contract
+is published, versioned and deprecated — it is not proposed or endorsed).
 **Mandated by**: ADR-061 §10.2. The ten-field sketch of ADR-061 §3.3 is the
 documented origin of this text and is not normative. Where they differ, this
 specification prevails.
@@ -47,7 +48,7 @@ An envelope message is a single assertion, encoded as a JSON object or an
 equivalent YAML mapping, validating against `schema/assertion.schema.json`.
 
 ```yaml
-envelope: "0.1"
+envelope: "1.0"
 id: openathle/PU-001
 class: traversal
 subject: "Renouvellement de licence athlète, saison N+1"
@@ -76,7 +77,7 @@ fields (§7).
 
 | # | Field | Type | Constraint |
 |---|---|---|---|
-| 1 | `envelope` | string | REQUIRED. The version of this contract, e.g. `"0.1"`. A message that does not declare its version is not versioned — it is only dated by its documents (A1 §3). SHOULD be the first key |
+| 1 | `envelope` | string | REQUIRED. The version of this contract, e.g. `"1.0"`. A message that does not declare its version is not versioned — it is only dated by its documents (A1 §3). SHOULD be the first key |
 | 2 | `id` | string | REQUIRED. `<jurisdiction>/<local-id>`. The prefix names the asserting authority. Never rewritten in transit (§2.1) |
 | 3 | `class` | string | REQUIRED. One of §5 |
 | 4 | `subject` | string | REQUIRED. What the assertion is about |
@@ -126,6 +127,11 @@ a standard field is a contract change under §8.
 - Versioning is `MAJOR.MINOR`. MINOR: additions (fields, classes, relation
   kinds, rites) that consumers can ignore or treat as opaque. MAJOR: removal,
   renaming, or semantic change of anything existing.
+- **v1.0 is substantively identical to v0.1**: no field, class, provenance,
+  rite or rule changed — the draft survived its first real exchange and is
+  declared stable, nothing more. Consumers MUST treat `envelope: "0.1"`
+  messages as v1.0 messages; the schema accepts both values. This equivalence
+  is specific to this pair and will not be repeated across future MAJORs.
 - At most **two published versions per year**. Deprecation is announced in
   this file at least one version before removal.
 - Consumers MUST accept any message whose `envelope` shares their MAJOR and