Add npm support metadata for Linear packages

[yanziwei]

Summary

Add standard npm homepage and bugs metadata to packages/sdk/package.json for @linear/sdk and to packages/import/package.json for @linear/import.

The published packages already expose repository and MIT license metadata, but npm metadata does not expose homepage or bugs fields. This points package consumers to the relevant README and the public issue tracker.

Validation

• node -e "const p=require('./packages/sdk/package.json'); if(p.homepage!=='https://github.com/linear/linear/tree/master/packages/sdk#readme') throw new Error('homepage mismatch'); if(p.bugs?.url!=='https://github.com/linear/linear/issues') throw new Error('bugs mismatch'); console.log(JSON.stringify({name:p.name,homepage:p.homepage,bugs:p.bugs,repository:p.repository}, null, 2));"
• node -e "const p=require('./packages/import/package.json'); if(p.homepage!=='https://github.com/linear/linear/tree/master/packages/import#readme') throw new Error('homepage mismatch'); if(p.bugs?.url!=='https://github.com/linear/linear/issues') throw new Error('bugs mismatch'); console.log(JSON.stringify({name:p.name,homepage:p.homepage,bugs:p.bugs,repository:p.repository}, null, 2));"
• git diff --check
• npm pack --dry-run --ignore-scripts --json from packages/sdk
• npm pack --dry-run --ignore-scripts --json from packages/import

Scope

Manifest metadata only. No runtime code, dependency, generated output, or lockfile changes.

[changeset-bot]

⚠️ No Changeset found

Latest commit: b6e41d8

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