Repository navigation
feat(content): publish sealed Content snapshot APIs - #25
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Owners can create a Content API from a reviewed saved HTML preview, open its sealed draft in API Studio and explicitly publish a registered REST GET route. A current pinned runtime credential receives the literal document, escaped HTML and provenance. Later source edits or deletion do not change that snapshot.
Creation uses labelled forms and an exact six-key request. Other members cannot share or manage this owner-only API or its credentials/jobs. Stale reviews require explicit review; unconfirmed delivery blocks blind creation retry. This memory latch does not promise crash-safe idempotency. GraphQL Content APIs and live collection queries follow separately.
Validation:
All three exact-head CI jobs pass for reviewed head
84c434a524a6f737e3a548f9638c068b33e8d7a8. No tag, new public executable or deployment is published. These checks do not certify production capacity or native-language accuracy.Source delivery merged as
598cf847ff83454c0afe583e8d5b71e16846587dwith the reviewed tree unchanged. All three main CI jobs passed before the remote and local delivery branches were deleted. Unrelated local main history was preserved.