docs: state Node authority boundary honestly - #44
Merged
Conversation
added 2 commits
August 19, 2026 13:05
- Rewrite Next.js quickstart to explicitly state createNextApiHandler is not fail-closed - Update API reference for createNextApiHandler to document the continuation defect - Update Integration section to call out the critical defect - Add the continuation-after-503 defect to ADR-001 implementation status - Clarify coreEnvelope/trustedPolicyDigest as application-provided values
This was referenced Aug 19, 2026
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
1 participant
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.
Summary
createForwarderandcreateNextApiHandlerexportsVerification
npm run format:checknpm run typechecknpm test -- --runInBand(177 tests passed)npm run verify:package(24 shipped files verified)git diff --checkScope
This resolves only the documentation/metadata authority-boundary portion of #30. It intentionally does not close NOD-002: the canonical Core envelope contract, shared fixtures, missing-envelope behavior, substituted-model revalidation, digest evidence, and CI conformance remain open.