fix(spec): PROTOCOL_VERSION 13.0.0 → 14.0.0 — re-lockstep with the released major#2769
Merged
Conversation
…leased package major The #2736 version release bumped @objectstack/spec to 14.0.0 but the handshake constant was not regenerated, so protocol-version.test.ts fails on main for every branch (drift guard doing its job). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
📓 Docs Drift CheckThis PR changes 1 package(s): 93 hand-written doc(s) reference the affected code and may need an implementation-accuracy re-verification:
|
os-zhuang
added a commit
that referenced
this pull request
Jul 10, 2026
…to-sync, D11 honest marking (#2800) FLS (permission-zoo audit): the runtime evaluator matches field-permission keys by <object>.<field> prefix — a bare `budget` key matches NOTHING, so the showcase contributor's declared budget masking was a silent runtime no-op (the earlier "FLS proof" was actually the spent_within_budget validation rule rejecting a tiny budget). Fixed at every layer: the zoo keys are qualified (showcase_project.budget …); a new D7 lint rule `security-fls-unqualified-key` (error + fix-it) rejects bare keys at compile time — the exact plausible-but-wrong shape AI authoring produces; and the permission-zoo dogfood now proves the served pipeline denies a contributor's budget write while allowing ordinary field edits. Release: `changeset version` now chains scripts/sync-protocol-version.mjs, regenerating the PROTOCOL_VERSION handshake constant from the spec package major. Release PRs opened by changesets/action with the default GITHUB_TOKEN never trigger CI (GitHub anti-recursion), so the lockstep guard could only fire AFTER a release merged — fixing the value at version time closes the drift class that broke main at 14.0.0 (#2769). D11: `externalSharingModel` has no runtime consumer yet (authoring lint + Studio badges only). Its liveness entry moves from the bespoke `authorable` status to the documented `planned` + authorWarn (enforce-or-mark), and the sharing docs, design doc, and showcase comments now state explicitly that external-principal evaluation lands with the principal-taxonomy phase (#2696). ADR-0091 (grant lifecycle) was already authored and accepted upstream — no duplicate draft. Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
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.
The #2736 changesets release bumped
@objectstack/specto 14.0.0 without regenerating thePROTOCOL_VERSIONhandshake constant, so the lockstep guard (protocol-version.test.ts) fails on main for EVERY branch right now. One-line re-sync; the 3 protocol-version tests pass.No changeset: version-constant sync for an already-released major (the release itself carried the changesets).
🤖 Generated with Claude Code