feat(content): publish typed GraphQL snapshots

[mysbryce]

Content API creation now offers GraphQL alongside REST. Owners explicitly create and publish a reviewed rich-text snapshot, then call its generated POST route with a query key pinned to the current release. Queries select typed document nodes, escaped HTML and decimal-string provenance from the saved snapshot.

The closed schema preserves both rich-text versions and literal content. Runtime delivery rechecks the original key, current owner authority and publication generation after GraphQL execution. Studio shows the fixed schema and a usable query, with translated, compact creation controls. Existing REST snapshots and ordinary generated modules retain their compiler versions.

Validation:

• Core: types, build, formatting and 416 backend tests with 9,640 assertions.
• Bundled Chromium: all 81 E2E cases with the supported two-worker override; local default-four candidate failures remain documented.
• Complete preview: 1,364 masked images, 52 receipts and all 1,341 prior canonical metadata entries preserved. Individually reviewed all 40 affected originals.
• Windows portable: all 11 tests with 1,265 assertions, including sealed GraphQL publication after source deletion and restart. Individually reviewed all 14 copied-executable originals; that GUI journey covers REST, CMS REST and the toolbar. Runtime inputs and original notice bytes verified.
• Clean source bundle: all 1,056 indexed files and 24,501,925 payload bytes verified against commit 75288ad0e024e50afea0c95c01c374a70bc5820e.

This source delivery remains below 1.0.0. Live collection queries, Content client exports, mutations, subscriptions, snapshot draft tests and rollback have separate roadmap gates. No new public executable release is included.