merge: resolve esbuild.config.js conflict with upstream/main

Adopt upstream's packages: "bundle" + code splitting approach
which supersedes our removal of external: ["@vegamo/deepcode-core"].

Author: dengmik-commits

.deepcode/AGENTS.md

@@ -0,0 +1,4 @@
+# VS Code Marketplace publish token
+# Generate at: https://dev.azure.com/vegamo/_usersSettings/tokens
+# Permission required: Marketplace → Publish
+VSCE_PAT=

.env.example

@@ -20,6 +20,10 @@ out/
 # TypeScript build info files
 *.tsbuildinfo
 
+# Environment variables
+.env
+.env.local
+
 # Generated files
 packages/cli/src/generated/
 packages/core/src/generated/

.gitignore

@@ -1,13 +1,14 @@
 # 版本发布
 
-Deep Code 使用两个脚本管理 monorepo 的版本发布流程：
+Deep Code 使用三个脚本管理 monorepo 的版本发布流程：
 
 | 脚本 | 命令 | 用途 |
 |------|------|------|
 | `scripts/version.js` | `npm run release:version` | 升级所有 workspace 包的版本号 + 重新生成 lockfile |
-| `scripts/prepare-package.js` | `npm run prepare:package` | 构建 + 质量检查 + 发布到 npm + git commit & tag |
+| `scripts/prepare-package.js` | `npm run prepare:package` | 构建 CLI + 质量检查 + 发布到 npm + git commit & tag |
+| `scripts/prepare-vscode.js` | `npm run prepare:vscode` | 构建 VSCode 扩展 + 质量检查 + 发布到 VS Code 市场 + git commit & tag |
 
-两者配合使用，先升版本号，再发布。
+发布流程：先升版本号，再分别发布 CLI 和 VSCode 扩展。
 
 ---
 
@@ -105,7 +106,7 @@ git tag v0.1.32
 
 ## prepare:package — 构建并发布到 npm
 
-完成质量检查、构建、发布两个 npm 包，并自动创建 git commit 和 tag。
+完成质量检查、构建、发布 CLI 到 npm，并自动创建 git commit 和 tag。
 
 ### 基本用法
 
@@ -122,7 +123,7 @@ npm run prepare:package -- <version> [options]
 | `--dry-run` | 预演模式，不实际执行任何写操作 |
 | `--force` | 跳过 main 分支检查，允许从其他分支发布 |
 
-### 执行流程（9 步）
+### 执行流程（8 步）
 
 | 步骤 | 操作 | 说明 |
 |------|------|------|
@@ -131,10 +132,9 @@ npm run prepare:package -- <version> [options]
 | 3 | 更新版本号 | 同时更新 `packages/core` 和 `packages/cli` 的 version |
 | 4 | 质量检查 | `npm run check`（typecheck + eslint + prettier） |
 | 5 | 测试 | `npm run test --workspaces` |
-| 6 | 构建 | `npm run build`（core tsc + cli esbuild bundle） |
-| 7 | 发布 core | `npm publish --workspace=@vegamo/deepcode-core --access public` |
-| 8 | 发布 cli | 将 cli 的 `@vegamo/deepcode-core` 依赖从 `file:../core` 临时改为 `^<version>`，发布后恢复 |
-| 9 | Git commit & tag | `chore(release): v<version>` + `git tag v<version>` |
+| 6 | 构建 | `npm run build`（core tsc + esbuild 将 core 及所有依赖内联到 `dist/cli.js`） |
+| 7 | 发布 CLI | 往 `dist/` 写入 `dependencies: {}` 的 package.json，从 `dist/` 目录执行 `npm publish` |
+| 8 | Git commit & tag | `chore(release): v<version>` + `git tag v<version>` |
 
 ### 完整示例
 
@@ -152,9 +152,9 @@ npm run prepare:package -- 0.1.32 --dry-run
 npm run prepare:package -- 0.1.32 --force
 ```
 
-### 关于 file:../core 依赖
+### 关于 Core 打包策略
 
-CLI 包的 `@vegamo/deepcode-core` 依赖在开发时使用 `"file:../core"`（monorepo 本地链接）。发布到 npm 时，脚本会自动将其替换为 `"^<version>"`，发布完成后恢复为 `file:../core`。这个过程对用户透明，无需手动处理。
+CLI 的 `package.json` 中保留 `"@vegamo/deepcode-core": "file:../core"` 用于本地开发（IDE 类型检查、monorepo 工作区解析）。构建时 esbuild 使用 `packages: "bundle"` 将 core 的全部代码及其运行时依赖（`openai`、`ejs`、`zod` 等）内联到单个 `dist/cli.js` 文件中。发布时脚本往 `dist/` 写入 `dependencies: {}` 的 `package.json`，从 `dist/` 目录发布，因此发布的 CLI 包零运行时依赖。`@vegamo/deepcode-core` 不再作为独立 npm 包发布。
 
 ### 发布后
 
@@ -173,6 +173,58 @@ npx @vegamo/deepcode-cli --version
 
 ---
 
+## prepare:vscode — 构建并发布 VSCode 扩展到市场
+
+完成质量检查、构建、发布 VSCode 扩展到 VS Code Marketplace，并自动创建 git commit 和 tag。
+
+### 前置条件
+
+需要 Azure DevOps Personal Access Token（PAT）用于市场认证：
+
+1. 访问 https://dev.azure.com/vegamo/_usersSettings/tokens 生成 token
+2. 设置环境变量 `VSCE_PAT=<token>`
+
+### 基本用法
+
+```bash
+VSCE_PAT=<token> npm run prepare:vscode -- <version> [options]
+```
+
+### 参数
+
+| 参数 | 说明 |
+|------|------|
+| `<version>` | **必填**，要发布的 semver 版本号 |
+| `--dry-run` | 预演模式，不实际执行任何写操作 |
+| `--force` | 跳过 main 分支检查，允许从其他分支发布 |
+
+### 执行流程（7 步）
+
+| 步骤 | 操作 | 说明 |
+|------|------|------|
+| 1 | Git 检查 | 工作区必须 clean，必须在 main 分支 |
+| 2 | VSCE_PAT 检查 | 环境变量必须已设置 |
+| 3 | 更新版本号 | 同时更新 `packages/core`、`packages/cli`、`packages/vscode-ide-companion` 的 version |
+| 4 | 质量检查 | `npm run check`（typecheck + eslint + prettier） |
+| 5 | 测试 | `npm run test --workspaces` |
+| 6 | 构建 | `npm run build:vscode`（core tsc + esbuild 打包扩展 + 拷贝模板 + vsce package） |
+| 7 | 发布 | `vsce publish <version> --no-dependencies` 发布到 VS Code Marketplace |
+
+### 完整示例
+
+```bash
+# 发布正式版
+VSCE_PAT=xxx npm run prepare:vscode -- 0.1.32
+
+# 发布预发布版
+VSCE_PAT=xxx npm run prepare:vscode -- 0.1.32-beta.1
+
+# 预演（不实际发布）
+npm run prepare:vscode -- 0.1.32 --dry-run
+```
+
+---
+
 ## 典型发布流程
 
 一个完整的版本发布通常按以下步骤进行：
@@ -191,18 +243,22 @@ git diff
 git add -A
 git commit -m "chore(release): v0.1.32"
 
-# 5. 构建 + 质量检查 + 发布
+# 5. 构建 + 质量检查 + 发布 CLI
 npm run prepare:package -- 0.1.32
 
-# 6. 推送到 remote
+# 6. 发布 VSCode 扩展
+VSCE_PAT=xxx npm run prepare:vscode -- 0.1.32
+
+# 7. 推送到 remote
 git push && git push --tags
 ```
 
-也可以简化为两步（`prepare:package` 会自动 commit 和 tag）：
+也可以简化为三步（`prepare:package` 和 `prepare:vscode` 各自自动 commit 和 tag）：
 
 ```bash
 npm run release:version -- patch
 npm run prepare:package -- 0.1.32
+VSCE_PAT=xxx npm run prepare:vscode -- 0.1.32
 git push && git push --tags
 ```
 

RELEASE.md

@@ -1,13 +1,14 @@
 # Release
 
-Deep Code uses two scripts to manage version releases in the monorepo:
+Deep Code uses three scripts to manage version releases in the monorepo:
 
 | Script | Command | Purpose |
 |--------|---------|---------|
 | `scripts/version.js` | `npm run release:version` | Bump all workspace package versions + regenerate lockfile |
-| `scripts/prepare-package.js` | `npm run prepare:package` | Build + quality checks + publish to npm + git commit & tag |
+| `scripts/prepare-package.js` | `npm run prepare:package` | Build CLI + quality checks + publish to npm + git commit & tag |
+| `scripts/prepare-vscode.js` | `npm run prepare:vscode` | Build VSCode extension + quality checks + publish to VS Code Marketplace + git commit & tag |
 
-Use them together: bump version first, then publish.
+Release flow: bump version first, then publish CLI and VSCode extension separately.
 
 ---
 
@@ -105,7 +106,7 @@ git tag v0.1.32
 
 ## prepare:package — Build and Publish to npm
 
-Runs quality checks, builds, publishes both npm packages, and automatically creates a git commit with tag.
+Runs quality checks, builds, publishes the CLI to npm, and automatically creates a git commit with tag.
 
 ### Basic Usage
 
@@ -122,7 +123,7 @@ npm run prepare:package -- <version> [options]
 | `--dry-run` | Preview mode, no actual writes |
 | `--force` | Skip main branch check, allow publishing from other branches |
 
-### Execution Flow (9 Steps)
+### Execution Flow (8 Steps)
 
 | Step | Action | Description |
 |------|--------|-------------|
@@ -131,10 +132,9 @@ npm run prepare:package -- <version> [options]
 | 3 | Update versions | Updates `packages/core` and `packages/cli` version fields |
 | 4 | Quality checks | `npm run check` (typecheck + eslint + prettier) |
 | 5 | Tests | `npm run test --workspaces` |
-| 6 | Build | `npm run build` (core tsc + cli esbuild bundle) |
-| 7 | Publish core | `npm publish --workspace=@vegamo/deepcode-core --access public` |
-| 8 | Publish cli | Temporarily changes cli's `@vegamo/deepcode-core` dep from `file:../core` to `^<version>`, restores after publish |
-| 9 | Git commit & tag | `chore(release): v<version>` + `git tag v<version>` |
+| 6 | Build | `npm run build` (core tsc + esbuild inlines core and all deps into `dist/cli.js`) |
+| 7 | Publish CLI | Writes `dist/package.json` with `dependencies: {}`, runs `npm publish` from `dist/` |
+| 8 | Git commit & tag | `chore(release): v<version>` + `git tag v<version>` |
 
 ### Examples
 
@@ -152,9 +152,9 @@ npm run prepare:package -- 0.1.32 --dry-run
 npm run prepare:package -- 0.1.32 --force
 ```
 
-### About the file:../core Dependency
+### About the Core Bundling Strategy
 
-The CLI package uses `"file:../core"` for the `@vegamo/deepcode-core` dependency during development (monorepo local link). When publishing to npm, the script automatically replaces it with `"^<version>"` and restores it after publishing. This is transparent — no manual handling required.
+The CLI's `package.json` keeps `"@vegamo/deepcode-core": "file:../core"` for local development (IDE type checking, monorepo workspace resolution). At build time, esbuild uses `packages: "bundle"` to inline all of core's code and its runtime dependencies (`openai`, `ejs`, `zod`, etc.) into a single `dist/cli.js` file. At publish time, the script writes a `dist/package.json` with `dependencies: {}` and publishes from the `dist/` directory, so the published CLI package has zero runtime dependencies. `@vegamo/deepcode-core` is no longer published as a separate npm package.
 
 ### After Publishing
 
@@ -173,6 +173,58 @@ npx @vegamo/deepcode-cli --version
 
 ---
 
+## prepare:vscode — Build and Publish VSCode Extension to Marketplace
+
+Runs quality checks, builds, publishes the VSCode extension to the VS Code Marketplace, and automatically creates a git commit with tag.
+
+### Prerequisites
+
+Requires an Azure DevOps Personal Access Token (PAT) for marketplace authentication:
+
+1. Generate a token at https://dev.azure.com/vegamo/_usersSettings/tokens
+2. Set the environment variable `VSCE_PAT=<token>`
+
+### Basic Usage
+
+```bash
+VSCE_PAT=<token> npm run prepare:vscode -- <version> [options]
+```
+
+### Arguments
+
+| Argument | Description |
+|----------|-------------|
+| `<version>` | **Required**. Semver version to publish |
+| `--dry-run` | Preview mode, no actual writes |
+| `--force` | Skip main branch check, allow publishing from other branches |
+
+### Execution Flow (7 Steps)
+
+| Step | Action | Description |
+|------|--------|-------------|
+| 1 | Git check | Working tree must be clean, must be on main branch |
+| 2 | VSCE_PAT check | Environment variable must be set |
+| 3 | Update versions | Updates `packages/core`, `packages/cli`, and `packages/vscode-ide-companion` version fields |
+| 4 | Quality checks | `npm run check` (typecheck + eslint + prettier) |
+| 5 | Tests | `npm run test --workspaces` |
+| 6 | Build | `npm run build:vscode` (core tsc + esbuild bundle extension + copy templates + vsce package) |
+| 7 | Publish | `vsce publish <version> --no-dependencies` to VS Code Marketplace |
+
+### Examples
+
+```bash
+# Publish stable release
+VSCE_PAT=xxx npm run prepare:vscode -- 0.1.32
+
+# Publish pre-release
+VSCE_PAT=xxx npm run prepare:vscode -- 0.1.32-beta.1
+
+# Dry run (no actual publish)
+npm run prepare:vscode -- 0.1.32 --dry-run
+```
+
+---
+
 ## Typical Release Flow
 
 A complete version release follows these steps:
@@ -191,18 +243,22 @@ git diff
 git add -A
 git commit -m "chore(release): v0.1.32"
 
-# 5. Build + quality check + publish
+# 5. Build + quality check + publish CLI
 npm run prepare:package -- 0.1.32
 
-# 6. Push to remote
+# 6. Publish VSCode extension
+VSCE_PAT=xxx npm run prepare:vscode -- 0.1.32
+
+# 7. Push to remote
 git push && git push --tags
 ```
 
-Or simplified to two steps (`prepare:package` auto-commits and tags):
+Or simplified to three steps (`prepare:package` and `prepare:vscode` each auto-commit and tag):
 
 ```bash
 npm run release:version -- patch
 npm run prepare:package -- 0.1.32
+VSCE_PAT=xxx npm run prepare:vscode -- 0.1.32
 git push && git push --tags
 ```
 

RELEASE_en.md

@@ -28,6 +28,7 @@
     "test": "npm run test --workspaces --if-present",
     "release:version": "node scripts/version.js",
     "prepare:package": "node scripts/prepare-package.js",
+    "prepare:vscode": "node scripts/prepare-vscode.js",
     "prepare": "husky && npm run build && npm run bundle"
   },
   "devDependencies": {
@@ -43,6 +44,7 @@
     "husky": "^9.1.7",
     "lint-staged": "^17.0.4",
     "prettier": "^3.8.3",
+    "react-devtools-core": "^7.0.1",
     "tsx": "^4.21.0",
     "typescript": "^6.0.3",
     "typescript-eslint": "^8.59.2"