Repository navigation
docs(upstream-sync): add v0.46.0 and record the whole-file explore hole - #222
Merged
Merged
Conversation
Content-header generated detection shipped, so the entry's table, the header's release range, and its title all move to five tiers through v0.46.0. The still-open section now carries what the explore review turned up, because it is the kind of thing a future port would otherwise rediscover: the whole-file rule returns a complete section before any budget or focus logic runs, and its line and character thresholds are independent. A 63-line file over the character cap therefore falls through to clustering and can be rejected whole, so an explicitly named symbol answers with 615 bytes and no sections — the same empty result CG-38 exists to prevent, by a route a clustering-only fix leaves open.
Codecov Report✅ All modified and coverable lines are covered by tests. @@ Coverage Diff @@
## main #222 +/- ##
=======================================
Coverage 95.31% 95.31%
=======================================
Files 141 141
Lines 78022 78022
=======================================
Hits 74367 74367
Misses 3655 3655 🚀 New features to boost your workflow:
|
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.
Follow-up to #219, now that content-header detection has shipped as
v0.46.0.Ledger updated
The 2026-08-20 entry's shipped table gains
v0.46.0(#220, content-header generated detection, upstream #1500 +57e0854), and the header's release range plus the entry title move from four tiers throughv0.45.0to five tiers throughv0.46.0.A defect recorded ahead of its port
The still-open section previously said the
exploreepic and content-header detection were both unshipped. One of those is now done, and the review of the other surfaced something worth writing down rather than leaving in a plan file:engine.rs's whole-file rule returns a complete section before any budget, ceiling, or focus logic exists — and its two thresholds are independent:So a file can pass the line gate, fail the character gate, fall through to clustering, and then be rejected whole. Measured:
615 bytes with zero sections is byte-identical to the original CG-38 defect, reached by a different route — and a
MIN_WINDOWfocus slice would have fit comfortably. It matters because a fix that only funds headroom inside the clustering path leaves this hole open, and a test that oversizes only line count will never reach it.Recording it here means the next person to touch
explorebudgeting finds it without re-deriving it, whether or not the current Tier 5 plan lands.Docs only: one file,
oxfmtidempotent, tracked parity unchanged at1.5.0.