[cdn-caching] Describe PPR state by category, not raw proxy values - #132
Merged
Conversation
Remove the internal ppr_state proxy values (page/shell/blocking) from the PPR state table and present the three states by their user-facing category: Static, Partial, and Dynamic. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Melkeydev
approved these changes
Aug 5, 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
2 participants
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.
What
Follow-up to #128. Updates the PPR state table in the
cdn-cachingskill to drop the rawppr_stateproxy values (page,shell,blocking) and describe the three states purely by their user-facing category:ppr_stateThe surrounding prose is updated to match (a Partial serve, not a
shellhit).Why
Users see PPR state categorized as (fully) static, partial, and (fully) dynamic. The raw
page/shell/blockingvalues are internal proxy terms and don't belong in user-facing skill guidance.Notes
ppr_statefield name, prompt signals, and retrieval entries from [cdn-caching] Add PPR state (ppr_state) to the skill #128 are unchanged, so the generated manifests are untouched.bun test→ 929 pass, 0 fail.bun run validate→ passed (pre-existing workflow warning only).🤖 Generated with Claude Code