#1 chore: repoint links and package metadata to machine-made

Why

The repository moved to machine-made/vscode-diff-next. GitHub redirects git and web URLs, but package metadata and docs still name the old owner. This PR points them at the new owner. It also removes a local Windows user path from a script usage example.

Scope

File	Change
package.json	repository.url, bugs.url and homepage use machine-made/vscode-diff-next.
README.md	CI badge, GitHub badge, Releases link, the link to the sibling extension and the repository row of the sibling table use the new owner.
SECURITY.md	The private vulnerability report link uses the new owner.
docs/RELEASING.md	The link to the sibling release guide and the two gh secret set ... -R commands (VSCE_PAT, OVSX_PAT) name the new owner.
update-extension.ps1	The -Workspace usage example now reads C:\path\to\vscode-diff-next.
LICENSE, NOTICE	The author name now reads "Ricardo Frantz".

The package has no qna field. The Marketplace builds that link from repository, so no new field is needed.

The CI and release workflows use github.repository, so they follow the move without a change.

Kept on purpose

• publisher: RicardoFrantz and the Marketplace item id RicardoFrantz.diff-next. These are registry identities, not GitHub owners. A change would create a new extension and orphan current installs.
• The RicardoFrantz.pdf-preview-next id in the README and NOTICE, and the publisher text in the README.
• The RicardoFrantz.diff-next strings in update-extension.ps1, update-extension.sh, .github/workflows/release.yml and the CHANGELOG.md entry for the first release.
• The sample paths in scripts/smoke-paths.js (C:\Users\Test\repo, /home/u/proj). They are test inputs, not real home paths.
• Git history.

Verification

Check	How it ran	Result
Install	npm ci (Node 22, npm 10)	Fails on the committed lockfile: 16 resolved entries (8 packages, listed twice) point to registry.npmmirror.com, which returns 403 here. With those entries temporarily switched to registry.npmjs.org (not committed), it passes: 390 packages, 18 s. The integrity hashes are unchanged.
Lint	npm run lint	Pass, 8 s
Compile	npm run compile	Pass, 6 s
Smoke	npm run smoke (5 scripts)	All five pass, 2 s
Package contents	npx @vscode/vsce ls	Exit 0, 54 files
Package	npx @vscode/vsce package (output outside the repo)	Exit 0, 56 files, 950.56 KB
Audit	npm audit --omit=dev --audit-level=high	Exit 1: 2 critical findings in simple-git 3.36.0 and @simple-git/argv-parser (advisory GHSA-v5rq-49vh-5v5c). Not related to this PR. The CI audit step will report the same.

A search for ricardofrantz (case-insensitive) across the tree now finds only the kept items above.

I did not touch the lockfile or the dependencies. Both findings above (mirror URLs in package-lock.json, the simple-git advisory) deserve their own change.

After merge

1. Publish a patch release to the VS Code Marketplace. The listing shows the new Repository, Issues and Homepage links only after a new version is published.
2. Keep publisher RicardoFrantz. Check that the VSCE_PAT secret and the marketplace-publish environment (with its reviewers) exist on machine-made/vscode-diff-next before the release run. OVSX_PAT is optional: the extension is not on Open VSX.
3. The repository has the Issues tab switched off today. The bugs link on the Marketplace listing points at /issues, so switch Issues on in the repository settings or the link leads to a 404.

https://claude.ai/code/session_016vMfdfTLtvm4G2UANfJw8q

---

Generated by Claude Code