j4k-oss/askpplx
Watch
2
0
Fork
You've already forked askpplx
 0
Code Issues Pull requests Releases 3 Packages 1 Activity Actions

docs: say why the @j4k-oss registry mapping is required #4

Merged
jercik merged 1 commit from docs/npm-scope-ownership into main 2026-10-23 07:20:53 +00:00
Conversation 2 Commits 1 Files changed 2 +3 -3
jercik commented 2026-10-23 07:09:23 +00:00
Owner

The @j4k-oss scope on npmjs is now ours and holds no packages, so the README no longer calls its owner unconfirmed or says npm could fetch another owner's package. The registry mapping is still required, because without it npm looks on npmjs, finds nothing, and fails with a 404. The README also calls the unscoped askpplx deprecated instead of frozen.

AGENTS.md is regenerated from align 9.0.6. The only change is the same reason in the repoq rule.

🤖 Generated with Claude Code

The `@j4k-oss` scope on npmjs is now ours and holds no packages, so the README no longer calls its owner unconfirmed or says `npm` could fetch another owner's package. The registry mapping is still required, because without it `npm` looks on npmjs, finds nothing, and fails with a 404. The README also calls the unscoped `askpplx` deprecated instead of frozen. `AGENTS.md` is regenerated from align 9.0.6. The only change is the same reason in the repoq rule. 🤖 Generated with [Claude Code](https://claude.com/claude-code)
docs: say why the @j4k-oss registry mapping is required
All checks were successful
Checks / pr-flow-canary (pull_request) Has been skipped
Details
Checks / reuse (pull_request) Successful in 4s
Details
commit-msg / commitlint (pull_request) Successful in 13s
Details
Checks / quality-checks (24.15.0) (pull_request) Successful in 42s
Details
Checks / quality-checks (26.5.0) (pull_request) Successful in 42s
Details
Review / Review (pull_request_target) Successful in 7m0s
Details
f2c81821fb
 
The @j4k-oss scope on npmjs is now ours and holds no packages. The
registry mapping is still required because every @j4k-oss package exists
only on the Forge: without it, npm looks on npmjs, finds nothing, and
fails with a 404. The unscoped npmjs packages are deprecated.

Regenerate AGENTS.md from align 9.0.6 for the matching repoq rule.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
forgejo-actions commented 2026-10-23 07:16:22 +00:00

Review 01M5KSFPBDES7WC83987EETYFC — head f2c81821fb5fc7977c75a94d18cd9890b8ed1915

Review — j4k-oss/askpplx @ c9006f4640

Scope: diff against base tree 880e05a461fb
Status: dispatched — coverage complete (5/5 slots terminal)
Facts: current review-wide projection

Computed under:

{
  "abandonment": "abandonment-v1",
  "anchor_recipe": 1,
  "batch_policy": "batch-v1",
  "coverage": "coverage-v3",
  "dispatch_policy": "dispatch-v2",
  "grounder_version": 1,
  "grounding_read_rule": "grounding-read-v1",
  "promotion_policy": "promotion-v1",
  "report": "report-v4",
  "tally": "tally-v1",
  "triage_settle": "triage-settle-v2"
}

Findings (0)

No findings survived.

Reviewed:

  • restated-sets (whole/default): no-claims
  • module-design (whole/default): no-claims
  • general-bug (whole/default): no-claims
  • writing-quality (whole/default): claims-emitted
  • project-docs (whole/default): no-claims
  • test-trimming: skipped-by-dispatch — no tests changed; docs-only diff
  • unix-cli: skipped-by-dispatch — only prose in markdown docs changed; no CLI code or behavior
  • use-effect: skipped-by-dispatch — no React code changed
  • react: skipped-by-dispatch — no React code changed

Other claims

  • grounding-pending (0)
  • ungrounded (0)
  • rejected (0)
  • duplicate-of (0)
  • unadjudicated (1)
    • 01M5KSRXWXJ65YRHJSDABAYBCC low — The installation introduction states the registry restriction twice

Coverage

Coverage pass: 01M5KSGBPX31PB75BZ4KJ74QGB
Accounting: complete
Slot health: healthy

lens part arm unit status runs loss
restated-sets whole default no-claims 1 no
module-design whole default no-claims 1 no
general-bug whole default no-claims 1 no
writing-quality whole default claims-emitted 1 no
project-docs whole default no-claims 1 no
  • test-trimming — skipped-by-dispatch: no tests changed; docs-only diff
  • unix-cli — skipped-by-dispatch: only prose in markdown docs changed; no CLI code or behavior
  • use-effect — skipped-by-dispatch: no React code changed
  • react — skipped-by-dispatch: no React code changed
<!-- review:summary --> **Review** `01M5KSFPBDES7WC83987EETYFC` — head `f2c81821fb5fc7977c75a94d18cd9890b8ed1915` # Review — j4k-oss/askpplx @ c9006f464017 Scope: diff against base tree `880e05a461fb` Status: dispatched — coverage complete (5/5 slots terminal) Facts: current review-wide projection Computed under: ```json { "abandonment": "abandonment-v1", "anchor_recipe": 1, "batch_policy": "batch-v1", "coverage": "coverage-v3", "dispatch_policy": "dispatch-v2", "grounder_version": 1, "grounding_read_rule": "grounding-read-v1", "promotion_policy": "promotion-v1", "report": "report-v4", "tally": "tally-v1", "triage_settle": "triage-settle-v2" } ``` ## Findings (0) No findings survived. Reviewed: - restated-sets (whole/default): no-claims - module-design (whole/default): no-claims - general-bug (whole/default): no-claims - writing-quality (whole/default): claims-emitted - project-docs (whole/default): no-claims - test-trimming: skipped-by-dispatch — no tests changed; docs-only diff - unix-cli: skipped-by-dispatch — only prose in markdown docs changed; no CLI code or behavior - use-effect: skipped-by-dispatch — no React code changed - react: skipped-by-dispatch — no React code changed ## Other claims - grounding-pending (0) - ungrounded (0) - rejected (0) - duplicate-of (0) - unadjudicated (1) - `01M5KSRXWXJ65YRHJSDABAYBCC` low — The installation introduction states the registry restriction twice ## Coverage Coverage pass: 01M5KSGBPX31PB75BZ4KJ74QGB Accounting: complete Slot health: healthy | lens | part | arm | unit status | runs | loss | | --- | --- | --- | --- | --- | --- | | restated-sets | whole | default | no-claims | 1 | no | | module-design | whole | default | no-claims | 1 | no | | general-bug | whole | default | no-claims | 1 | no | | writing-quality | whole | default | claims-emitted | 1 | no | | project-docs | whole | default | no-claims | 1 | no | - test-trimming — skipped-by-dispatch: no tests changed; docs-only diff - unix-cli — skipped-by-dispatch: only prose in markdown docs changed; no CLI code or behavior - use-effect — skipped-by-dispatch: no React code changed - react — skipped-by-dispatch: no React code changed
🚀 1
jercik commented 2026-10-23 07:20:27 +00:00
Author
Owner

Unadjudicated claim 01M5KSRXWXJ65YRHJSDABAYBCC (low, "The installation introduction states the registry restriction twice"), checked against head f2c8182.

Confirmed. The sentence this PR adds ("@j4k-oss/askpplx exists only on the code.j4k.dev registry.") repeats the paragraph above it, which already says the package is published only on that registry. It is redundant wording, not a correctness defect, so it does not block this merge. Tracked in #5, which removes the sentence.

Unadjudicated claim `01M5KSRXWXJ65YRHJSDABAYBCC` (low, "The installation introduction states the registry restriction twice"), checked against head `f2c8182`. Confirmed. The sentence this PR adds ("`@j4k-oss/askpplx` exists only on the `code.j4k.dev` registry.") repeats the paragraph above it, which already says the package is published only on that registry. It is redundant wording, not a correctness defect, so it does not block this merge. Tracked in #5, which removes the sentence.
🚀 1
jercik merged commit 20f73f207a into main 2026-10-23 07:20:53 +00:00
jercik deleted branch docs/npm-scope-ownership 2026-10-23 07:20:53 +00:00
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Assignees
Clear assignees
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
j4k-oss/askpplx!4
No description provided.