[nicourrutia98]

Summary

The package name in package.json was an authoring error:

• The GitHub org is Opita-Code (with 'code')
• The npm org is opitacode (with 'code') — verified: npm org ls opitacode --json returns {"nicourrutia98": "owner"}
• But the package name was @opita/ocais (without 'code')

This PR aligns the package name with both orgs for brand consistency.

Changes (22 files, 54 insertions, 54 deletions, no source code changes)

• package.json: name field
• package-lock.json: sync name (lockfile)
• src/*.ts: 8 JSDoc comments only (no runtime imports affected — all real imports use relative paths)
• dist/: regenerated via npm run build (TypeScript preserves JSDoc in .js and .d.ts)
• README.md, CHANGELOG.md, docs/migration-v1-to-v2.md, pr-body.md: example imports
• openspec/changes/2026-07-09-v3-auth-expansion/*.md: historical research artifacts (Phase 0 docs)

Verification

• npm ci: 4 packages, 0 vulnerabilities, runs npm run build via prepare
• npm test: 132/132 pass (was 128/129 before; the 1 fail was a missing zod devDep that npm ci fixed)
• npm pack --dry-run: tarball contains all 4 critical files verified by publish-guard.yml:
  • dist/index.js
  • dist/index.d.ts
  • dist/lambda/sse-writer.js
  • dist/providers/openai-compatible.js

Out of scope

• v3.0.0 npm publish (handled separately in SPEC-417, will be a tag v3.0.0 after this PR merges)
• Cognito JWKS consumer migration in opita-account-ui (separate spec)

Refs

• SPEC-417 (dark-memory, project_id=opita-stream-platform): tracks the publish flow
• Original authoring error: see PR fix(publish): include dist/ in npm tarball + add publish-guard CI #2 (fix(publish): include dist/ in npm tarball) which shipped v2.0.0 with the wrong name