[doublesharp]

Change

The repository moved from doublesharp to the 0xdoublesharp organization.

• Docs checker: scripts/check-docs.py recognized the repository's own GitHub blob links only under /doublesharp/bin-packing/. After the move it would have treated them as external links and skipped them, and it would have stopped re-pinning the binding READMEs to the release version. It now takes the owner and name from [workspace.package].repository, as release-note pinning already did. New tests cover both paths.
• Publishing metadata: the workspace repository, plus repository.url in bindings/node and bindings/wasm. In the publish job, napi create-npm-dirs copies the Node package's repository into the six platform packages (confirmed in @napi-rs/cli 3.6.1's source), so they follow. npm provenance requires this URL to match the publishing repository.
• Links: README images, the binding READMEs, the issue and pull request templates, CONTRIBUTING.md and the v0.6.0 release notes.
• Publish job: CARGO_REGISTRY_TOKEN no longer comes from a secret in the job-level env. A rust-lang/crates-io-auth-action@v1 step runs before the first publish step (the job already has id-token: write), and its short-lived token goes only to cargo publish. If the crates.io trusted publisher is missing, the job stops before npm receives a partial release. docs/releasing.md is updated to match.

Before the next release, the bin-packing crate needs a crates.io trusted publisher for 0xdoublesharp/bin-packing and workflow ci.yml.

Verification

• python3 -m unittest discover -s scripts/tests: 54 passed. The two new docs tests and the updated one fail against the old checker.
• python3 -B scripts/check-docs.py: generated docs and local links passed, and the new-owner links are now checked as local files.
• taplo fmt --check, typos and actionlint passed.
• cargo metadata --no-deps --locked shows the new repository URL.
• Not run locally: the full ./scripts/check-quality.sh (clippy, tests, doctests, Rust doc examples). No Rust sources changed, and CI's Quality gate runs the script on this PR.

Checklist

• I followed AGENTS.md
  and CONTRIBUTING.md.
• I ran ./scripts/check-quality.sh and recorded the result above. It runs in CI's Quality gate; see Verification.
• I added regression coverage and ran relevant feature or binding checks,
  or explained why they do not apply.
• I updated affected public docs, examples, and binding declarations,
  or explained why they do not apply.

🤖 Generated with Claude Code