chore(sync): record CLAUDE.md and the bench scaling as skipped - #439
Merged
Conversation
Two contiguous upstream commits, both deliberately not taken, batched per PORTING.md §6 step 4b. No code changes. nuxt/ui@6f82268b `chore: add CLAUDE.md importing AGENTS.md` — skip. We have `AGENTS.md` and no `CLAUDE.md`, so it would apply cleanly, and would still be wrong: `CLAUDE.md` is in our `.gitignore` at line 51, under a `# AI` heading, alongside `.claude/settings.local.json`, `.claude/channels/` and `.claude/debug/`. The company it keeps settles it — this fork classifies the file as per-developer Claude Code state, not tracked instructions. Porting it would mean deleting that line and reversing a standing decision, which a sync port is not the place to do. The trade-off is named rather than hidden. Upstream's comment says Claude Code auto-loads only `CLAUDE.md`, so our tracked `AGENTS.md` is not loaded automatically and each developer supplies their own ignored copy. If that is judged a mistake it should be changed on its own merits — `.gitignore` line 51 and this commit — not carried in as a port. nuxt/ui@3d2129d2 `test(bench): scale tv benchmarks past codspeed's noise floor` — skip. It wraps every bench body in a 100-iteration loop because CodSpeed runs them under an instruction-counting simulator on runners that alternate between Intel and AMD. We have the file, but this fork does not run CodSpeed: `bench` is a plain `vitest bench --project vue`, no workflow invokes it, and nothing compares runs across machines. The change would buy nothing, cost a hundredfold longer local run, and add a comment describing CI we do not have. Worth taking the day benchmarks are wired into CI. Also refreshes `.sync/dep-parity.json` to the new cursor, per §6. Neither commit touches a manifest, so only the cursor line moves and all 148 versions are identical. Verify (CI=true): lint and the `test/utils` suite (495 tests, 25 files). Documentation and ledger only; nothing executable changes.
This was referenced Aug 19, 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
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.
First two of six in the current queue. Both deliberately not taken; adjacent, so batched per
PORTING.md§6 step 4b. No code changes.1.
nuxt/ui@6f82268b—add CLAUDE.md importing AGENTS.md→ skipThree lines adding a tracked
CLAUDE.mdthat importsAGENTS.md. We haveAGENTS.md(156 lines) and noCLAUDE.md, so it would apply cleanly — and would still be wrong:CLAUDE.mdis in our.gitignoreat line 51. The company it keeps settles it: this fork classifies the file as per-developer Claude Code state, not as tracked instructions. Porting the commit would mean deleting that line and reversing a standing decision — not something a sync port should do on its own authority.The trade-off is named rather than hidden: upstream's comment says Claude Code auto-loads only
CLAUDE.md, so our trackedAGENTS.mdis not loaded automatically, and each developer supplies their own ignored copy. If that is judged a mistake, it is a two-line change —.gitignoreline 51 plus this commit — and it should be made on its own merits.2.
nuxt/ui@3d2129d2—scale tv benchmarks past codspeed's noise floor→ skipWraps every
benchbody in a 100-iteration loop, because CodSpeed runs them under an instruction-counting simulator and GitHub's runners alternate between Intel and AMD, so sub-millisecond bodies collect phantom regressions.We have
test/bench/tv.bench.tsand the change would apply cleanly. But this fork does not run CodSpeed:benchis a plainvitest bench --project vue, no workflow invokes it, and nothing compares runs across machines.So it would buy nothing, cost a hundredfold longer local run, and add a comment describing CI we do not have. Worth taking the day benchmarks are wired into CI — and taking the comment with it.
A larger finding, surfaced by the first one
Checking why
CLAUDE.mdwas ignored led togit log -S 'CLAUDE.md' -- .gitignore→b55bd3e7, a deps port. Its body never mentionsCLAUDE.md, but it does say:Five other ledger entries say the same. That is what prompted #438: the
aiv6 line was a deliberate, repeatedly reaffirmed deferral rather than drift, deferred for exactly the DeepSeek provider coupling that #425 then broke. Recorded in both logs here, and as a §2 invariant in #438.Ledger
cursor→3d2129d2. Both entries added withdecision: skipand the reasoning in.sync/log/..sync/dep-parity.jsonrefreshed to the new cursor per the §6 step from #429 — neither commit touches a manifest, so only the cursor line moves and all 148 versions are identical.Verify (
CI=true)lintand thetest/utilssuite (495 tests, 25 files). Documentation and ledger only; nothing executable changes.Remaining in the queue:
ae2bd5eb(Splitter, adopting),2beb2345+a630c943(showcase, no-ops),14ac2438(ProgressGroup plus the--percentfix for the existingProgress).Generated by Claude Code