fix(1.0-readiness): the scope declaration counted 3 open issues; there are 31

G3a's third evidence bullet said "the three open at the cut" and named #304,
#305, #306. That count came from a summary listing only the three NEWEST. The
declaration was ratified on it.

The substance mostly survives — the bulk are CLI surfaces over existing
vocabulary, roadmap FRs already tiered post-1.0, or additions to shipped
features. But "no open issue needs new vocabulary" was asserted over a
population 10x larger than the one read, which is not a claim that was earned.

The corrected bullet names the one exception rather than sweeping it in: #202
(`@required` is global to the object, so a response object populated by two
producers cannot express it) touches the semantics of a SHIPPED attribute and
has no design yet, so whether its fix is additive is not yet knowable. The
likely shape is additive — a way to express per-producer required-ness ALONGSIDE
`@required` rather than a redefinition — but the bullet explicitly does not
claim that. It records #202 as considered, so a future reader does not have to
wonder whether it was missed.

The correction is left inline rather than silently rewritten, because a
declaration whose evidence changed should show that it changed.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01At3v6M6uqECZ2Sb5eUv6YY

Author: dmealing

docs/1.0-readiness.md

@@ -232,9 +232,22 @@ Status legend: ✅ done · 🔶 in progress · ⬜ not started · ❓ **[RATIFY]
        (TS web only), FR-028's object↔JSON parity + `meta export`, and FR-030's serializer
        SPI. FR-037 R3/R4/R5 and the FR-038 stub generator are explicitly additive
        (`spec/roadmap.md`). **No breaking change is chartered anywhere.**
-    3. **No open issue needs new vocabulary.** The three open at the cut — `meta why`
-       (#306), enforcing the already-shipped `@deprecated` (#305), and `meta fmt` (#304) —
-       are CLI surfaces and enforcement over vocabulary that already exists.
+    3. **The open issues are additive, with ONE named exception to watch.** 31 are open.
+       The bulk are CLI surfaces over existing vocabulary (`meta why` #306, `@deprecated`
+       enforcement #305, `meta fmt` #304), roadmap FRs already tiered post-1.0 (#159 and
+       #200 say so in their titles), or additions to shipped features (#222 extends #207's
+       filter). **The exception is [#202](https://github.com/metaobjectsdev/metaobjects/issues/202)**
+       — `@required` is global to the object, and a response object populated by two
+       producers cannot express it. That touches the semantics of a SHIPPED attribute and
+       has no design yet, so whether its fix is additive is not yet knowable. The likely
+       shape is additive (a way to express per-producer required-ness alongside
+       `@required`, not a redefinition of it), but **this bullet does not claim that** —
+       it names #202 as the one open item that could force a non-additive change, so a
+       future reader sees it was considered rather than missed.
+
+       *Correction (2026-09-07): this bullet first said "the three open issues," a count
+       taken from a summary listing only the three newest. There are 31. The audit above
+       is the corrected one.*
 
     ADR-0035 §1 already promises this by excluding reserved-but-unregistered vocabulary
     from the compat surface. G3a is where the project records that it **checked**, rather