The item was filed against a stale, shallow clone that predated commit
c00c482 (2026-10-26), which already did what it asked for a better
reason than I had: the GitHub org rename broke @flashylabs's GitHub
Packages scope resolution, and the fix published @flashyos/ledger
1.0.1 to public npm and updated package.json, .npmrc (removed) and
publish.yml to match. ClaimYour.Gold's dependency is confirmed already
updated too. Closed via revise()/status:done rather than deleted, per
backlog/1's own rule that a correction is appended, never edited away.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01VgrPGGUFKMq9zXBHnfcTgs
Summary
@flashynetworkis now claimed on npm (zero packages published). The estate decided this ledger moves there, but this repo has three disagreeing version numbers for one package:package.jsonsays1.0.0,ClaimYour.Golddepends on@flashylabs/ledger@^0.8.0(below what's committed, and that name 404s on public npm — only GitHub Packages has it), and@flashyos/ledger@1.0.1is live on public npm, published by hand outside this repo'spublish.yml, which still only knows how to publish@flashylabs/ledger.Filed as a
blocker-kindbacklog/1item (decays in 14 days, matching the format's own rule that a blocker can't sit stale) rather than left as a comment nobody can query: version reconciliation has to happen before.npmrc/publish.ymlcan target@flashynetwork/ledgerdirectly, or the rename just adds a fourth number.Filed via
@flashyos/backlog'sfile(), promoted to public viapromote({by: 'person/michael'}), emitted with the repo's ownvendor-backlog.mjs emit, validated withcheck— nothing hand-edited.Verified
node vendor-backlog.mjs check backlog.fragment.json→okGenerated by Claude Code