fix: add missing metadata fields to package.json

[BWM0223]

Adds missing bugs metadata to package.json.

Fixes npm tooling unable to resolve package metadata.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 8796144

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: b9a63308-b861-4505-a131-5fd96617a0ff

📥 Commits

Reviewing files that changed from the base of the PR and between 441bc69 and 8796144.

📒 Files selected for processing (1)

• package.json

---

📝 Walkthrough

Summary by CodeRabbit

• Chores
  • Added repository issues URL to package metadata, enabling users to easily locate and report bugs through package information.

Walkthrough

This PR adds a bugs field to package.json with a URL pointing to the GitHub repository's issues page. The addition is a standard npm package metadata field that directs users to the project's bug tracker.

Changes

Package bugs metadata

Layer / File(s)	Summary
Bugs field in package.json package.json	The bugs object with a URL field pointing to https://github.com/stephansama/packages/issues is added to the package manifest.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

A little field so small and neat,
Makes bug reports complete,
"bugs.url" now points the way,
To issues found each day! 🐰✨

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The pull request description is present but minimal; it lacks the required checklist items specified in the repository template (merging latest changes, conflict resolution, branch verification, linting, and testing).	Add the required checklist from the template verifying that latest changes are merged, conflicts resolved, branch points to main, eslint passes, and all unit tests pass.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately describes the main change: adding missing metadata fields to package.json, which aligns with the changeset that adds a bugs field.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[gemini-code-assist]

Code Review

This pull request updates the root package.json file to include a bugs field pointing to the repository's issue tracker. There are no review comments, so I have no feedback to provide.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.