docs: say why the @j4k-oss registry mapping is required #4
Loading…
Reference in a new issue
No description provided.
Delete branch "docs/npm-scope-ownership"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
The
@j4k-ossscope on npmjs is now ours and holds no packages, so the README no longer calls its owner unconfirmed or saysnpmcould fetch another owner's package. The registry mapping is still required, because without itnpmlooks on npmjs, finds nothing, and fails with a 404. The README also calls the unscopedworktree-removedeprecated instead of frozen.AGENTS.mdis regenerated from align 9.0.6. The only change is the same reason in the repoq rule.🤖 Generated with Claude Code
Review
01M5KSGKVA6FJDNZME6G54R3CR— head46e027ee4ecc27b7d86c5e26e476de1ef952a24dReview — j4k-oss/worktree-remove @
d12ab16f3aScope: diff against base tree
56a2efcd5babStatus: dispatched — coverage complete (5/5 slots terminal)
Facts: current review-wide projection
Computed under:
Findings (0)
No findings survived.
Reviewed:
Other claims
Coverage
Coverage pass: 01M5KSH4A6GGQM7C9J476QBTH5
Accounting: complete
Slot health: healthy