docs: correct stale generated-behavior claims (FK→422, field constraints, non-User identity, jobs concurrency) - #308
Merged
Conversation
…aints exist, non-User identity, jobs concurrency (D1/D2/C1/R1)
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.
Docs↔codegen conformance sweep, stale-doc bucket — the code is correct, the manual had fallen behind shipped behavior. Each fix confirmed against the code first.
08-database.md/05-errors.md/13-error-codes.md: a FK violation is 422 JC0422 (shipped runtime: db_error maps a client-supplied FK-constraint violation to 500 JC0510 (unique→409, FK→500) — client fault surfaces as a server error #296), not 500 JC0510.09-validation.md: field constraints (min/max/min_len/max_len) have existed since Design contract: field length/range constraints (min/max/min_len/max_len) — requested by every eval app across 3 rounds #80/0.6.5 across 4 surfaces; the doc claimed 'no field constraints yet'.00-designing.md: a non-Userauth identity IS supported with full owner-scoping (Generalize per-user owner-scoping beyond the literal user_id fk via an opt-in auth.identity (0.7 contract surface) #150); the doc claimed it MUST beUser.15-jobs.md: generated jobs concurrency is 2, not 4.Docs-only, no code, no version bump. Found by the docs↔codegen sweep.