fix: rename organization

[hyorman]

No description provided.

[Copilot]

Pull request overview

Renames the monorepo’s published package scope from @copilot-proxy/* to @hyorman/*, updating documentation, imports, and workspace metadata so the CLI/extension consume the newly named core package.

Changes:

• Rename NPM package names for core and cli (and update all corresponding imports/mocks/docs).
• Update VS Code extension and CLI to depend on @hyorman/copilot-proxy-core.
• Add root-level publishing scripts for VS Code and combined publishing.

Reviewed changes

Copilot reviewed 14 out of 15 changed files in this pull request and generated 1 comment.

Show a summary per file

File	Description
readme.md	Updates install/docs references to the new scoped package names.
packages/vscode/test/extension.models.test.ts	Updates Vitest mock import path to renamed core package.
packages/vscode/src/vscodeBackend.ts	Switches core import path and updates header comment reference.
packages/vscode/src/toolConvert.ts	Switches core import path and updates comment reference.
packages/vscode/src/extension.ts	Switches core import path.
packages/vscode/package.json	Updates devDependency name to renamed core package.
packages/core/src/index.ts	Updates package header comment to new name.
packages/core/package.json	Renames the published core package to the new scope.
packages/cli/test/sdkBackend.test.ts	Updates mocks/types/imports to renamed core package.
packages/cli/src/sdkBackend.ts	Switches core import path.
packages/cli/src/main.ts	Switches core import path.
packages/cli/package.json	Renames the published CLI package and updates dependency name.
packages/cli/README.md	Updates CLI docs/install commands to new package name.
package.json	Adds publish scripts (VS Code + aggregate) and keeps publishing flows in root.
package-lock.json	Updates workspace-linked package names/entries to the new scope.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

The publish:vscode script runs build:check but never runs the extension build (esbuild) before vsce publish. Since there is no vscode:prepublish hook in packages/vscode/package.json, this can publish without an up-to-date out/extension.js. Update the script to run npm run build -w packages/vscode (or reuse package:vscode) before publishing.

Suggested change

	"publish:vscode": "npm run sync-versions && npm run build:check -w packages/vscode && npx @vscode/vsce publish --no-dependencies --allow-all-proposed-apis",
	"publish:vscode": "npm run sync-versions && npm run build:check -w packages/vscode && npm run build:vscode && npx @vscode/vsce publish --no-dependencies --allow-all-proposed-apis",