Turn generated-content fast path ON by default (Workstream C follow-up) - #2039
Draft
jung-thomas wants to merge 1 commit into
Draft
Turn generated-content fast path ON by default (Workstream C follow-up)#2039jung-thomas wants to merge 1 commit into
jung-thomas wants to merge 1 commit into
Conversation
…Workstream C 3.6/3.8)
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.
Draft — for work tomorrow. Makes the slug-targeted generated-content fast path the default. It's built + PROD-proven (2026-08-25: warm fetch ~56s → ~11s, 1404 tutorials reused, one regenerated) but currently opt-in (
content-cacheinputdefault: false).Plan doc in this PR:
openspec/changes/slug-targeted-delta-rebuild/content-cache-default-on.md.What this needs
hugo/publicfor a changed slug + sample reused pages, byte-for-byte; wire into CI. Must be green before flipping the default.content-cacheinputdefault: false → true(keep-f content-cache=falseopt-out) and fix the repository_dispatch path —CONTENT_CACHE_FAST_PATHat:419 reads only:378). Prime the sidecar on full rebuilds too so hotfixes stay warm.inputs.content-cache, so repository_dispatch (the real author hotfix trigger) always resolvesfalseand never gets the fast path. Computefast_path = (effective_mode=='slug-targeted') && (content-cache!='false')in the "Determine effective rebuild mode" step and reference it for both the env var (:419) and the cache SAVEif:(rebuild-content-qa.yml(task 3.8).Verify before merge
fast path ENABLED; negative test confirms a parser/feed change forces full regen.Safety
decideFastPathalready fails open — fast path fires ONLY when slug-targeted + valid sidecar + feed-fingerprint match; else full regen. Full/catalog runs never use it. Rollback:-f content-cache=falseor revert the default flip.No code changes yet — this PR carries the plan; implementation lands tomorrow.