chore(drive): transfer npm ownership and trusted publishing

Problem

The adopted opencode-drive package remains independently versioned at 1.4.3, but cannot safely publish from anomalyco/opencode yet.

Current facts:

• npm has one maintainer: jlongster.
• Trusted publishing/provenance points to anomalyco/opencode-drive/.github/workflows/publish.yml.
• The first destination release is 1.4.4 (pending special-key patch after 1.4.3).
• Bare v1.4.4 tags collide with OpenCode tags; use opencode-drive-v1.4.4.
• Packed @opencode-ai/client: workspace:* currently rewrites to a version that must exist publicly before consumers can install Drive.
• OpenCode's global publisher must never rewrite Drive's independent version.

The workspace package is intentionally marked private until these gates are complete. See packages/drive/RELEASING.md.

Acceptance

• James adds the destination operator as npm owner, or updates trust himself.
• npm trusted publisher targets anomalyco/opencode and dedicated publish-drive.yml.
• Dedicated workflow uses GitHub-hosted runner, Node 24, npm OIDC, id-token: write, and namespaced tags.
• @opencode-ai/client packed dependency is available on npm.
• Packed tarball installs in a clean consumer; every export and installed CLI are verified.
• opencode-drive@1.4.4 provenance points to the destination repository/workflow.
• Old workflow is disabled after successful cutover.

Start with packages/drive/RELEASING.md and inspect the existing Drive publishing workflow before creating or reviewing dedicated publish-drive.yml. Verify the listed npm ownership, OIDC, namespaced-tag, dependency, tarball, provenance, and old-workflow cutover requirements; the work is done when opencode-drive@1.4.4 publishes successfully from the destination repository.