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 unscopedconventional-commit-msgdeprecated 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
01M5KSFV4RW9JN5HP1Y1HV2RXZ— head4f062341350af2ada5e6c4566635983ff6857bd2Review — j4k-oss/conventional-commit-msg @
b28bbaa36eScope: diff against base tree
0886d6613886Status: 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: 01M5KSGAZKSQND7QJZ5T5W8VG4
Accounting: complete
Slot health: healthy