package调整

Author: inschrift-spruch-raum

.agents/skills/dsh-plugin-release/SKILL.md

@@ -28,7 +28,7 @@ grep -R -n -E '@your-scope/dsh-plugin-template|plugin-template|Plugin Authors|li
 
 Review every match. Also reject template-only `src/README.md` in a completed plugin repository; it belongs only in `plugin-template`. This template does not permit repository-relative `link:`, `file:`, repository-external source, or repository-external project-reference paths. Registry packages and runtime host peers are package dependencies, not filesystem inputs; every consumer must resolve the ready-made build from the repository's own manifest and lockfile.
 
-Confirm the explicitly selected package name, version, description, license, repository metadata, Node engine, package manager, Cordis plugin id, invariant package name, bundle rows, README examples, and lockfile all describe the same package. The package name may be scoped or unscoped; compare the exact name rather than requiring the template's `@scope/dsh-` prefix.
+Confirm the explicitly selected package name, version, description, keywords, license, repository metadata, Node engine, package manager, Cordis plugin id, invariant package name, bundle rows, README examples, and lockfile all describe the same package. The package name may be scoped or unscoped; compare the exact name rather than requiring the template's `@scope/dsh-` prefix.
 
 If `pnpm-workspace.yaml` declares `patchedDependencies`, verify every project-root patch path exists under `patches/`, targets the exact installed version, has a documented reason, and is available during a clean install. A DSH host patch under `patches/` must be a self-contained diff with a documented pinned host snapshot, regenerated and applied through `scripts/extract-patch.mjs` and `scripts/patch.sh` (configured in `patches/host-patch.config.json`), and must not appear in the published package's `files`. If no dependency or DSH-host patch is declared or planned, do not require `patches/` or patch-only scripts; their absence is the expected state.
 

.agents/skills/dsh-plugin-scaffold/SKILL.md

@@ -36,7 +36,7 @@ Preserve the pinned Node, pnpm, Cordis, TypeScript, Vitest, and tsdown ranges fr
 
 Update identity deliberately in these owners:
 
-- `package.json`: `name`, `description`, optional repository metadata, exports/files, and `private` according to the distribution plan;
+- `package.json`: `name`, `description`, `keywords`, `license`, optional repository metadata, exports/files, and `private` according to the distribution plan;
 - `src/index.ts`: module name, exported `name`, and Loader-facing exports;
 - the source, configuration, invariant, contract, and focused test owners named by the target package;
 - `tsconfig*.json`, `tsdown*.ts`, and `scripts/*` when present: local compiler, bundle, declaration, generated-asset, and artifact-contract topology;

README.md

@@ -56,7 +56,7 @@ The template's sample skeleton still uses `src/index.ts`, `src/config.ts`, `src/
 
 1. Replace package identity in `package.json`, the Loader owner, configuration/runtime/invariant owners, focused test owners, bundle metadata, TypeScript metadata, `README.md`, and `AGENTS.md` as applicable. The sample skeleton names these owners explicitly; a deliberate replacement must update the package's local documentation and static-analysis configuration too.
 2. Choose and record the exact npm package name before replacing identity. It may be scoped or unscoped (for example, `comem`); do not assume the template's `@your-scope/dsh-` prefix. Use the selected name verbatim in `package.json`, bundle rows, invariant registration, exports, tests, and documentation. Replace the template package name `@your-scope/dsh-plugin-template` and plugin ids only in those identity owners. Do not perform a global replacement inside `.agents/skills/`; its generic examples and marker checks must remain reusable.
-3. Update `description`, `LICENSE`, and `cordis.patch.yml`.
+3. Update `description`, `keywords`, `LICENSE`, and `cordis.patch.yml`.
 4. Add only the DSH host services used by the implementation to the package contract and composition patch. Keep source and build dependencies resolvable from this repository's `node_modules`; host-provided runtime APIs remain consumer-supplied peers.
 5. Replace the empty invariant installer when the package owns an authoritative event or mutable data relationship.
 6. Implement activation and host-boundary behavior in the actual runtime/service owners, moving cohesive capabilities into project-specific modules as needed. Keep `src/index.ts` limited to Loader metadata and public re-exports when that matches the package, and scope registrations through `ctx.effect()`, `ctx.on()`, or registry disposers.
@@ -93,7 +93,7 @@ pnpm test
 pnpm run build
 ```
 
-`lint` runs Oxlint with type-aware analysis and denies warnings for the configured source and test projects. `build` runs the configured source-to-artifact pipeline, including any declaration assembly or final artifact verifier owned by the package, and emits ready-to-pack output; it does not run an install-time lifecycle build.
+`lint` runs Oxlint with type-aware analysis and denies warnings for the configured source and test projects. `build` runs the configured source-to-artifact pipeline, including any declaration assembly or final artifact verifier owned by the package, and emits ready-to-pack output; it does not run an install-time lifecycle build. Extra arguments are passed through to tsdown, so `pnpm run build --sourcemap` emits source maps for local debugging; the default `build` emits none.
 
 The release artifact is built from the configured source owners before packing. Profile or consumer installation uses the ready-made `lib/` output and does not run `prepare`; `pnpm pack --dry-run --json` verifies the final archive contents.
 

README.zh.md

@@ -64,7 +64,7 @@ Turtle UI 的 chat、components、extension 目录描述的是那个产品,不
 
 1. 在 `package.json`、`src/index.ts`、`src/config.ts`、`src/runtime.ts`、`src/invariant.ts`、`tests/plugin.spec.ts`、`cordis.patch.yml`、TypeScript 包元数据、`README.md` 与 `AGENTS.md` 中替换包身份。
 2. 在替换身份前先明确完整的 npm 包名。包名可以是 scoped 或 unscoped（例如 `comem`），不要默认继承模板的 `@your-scope/dsh-` 前缀。将选定包名原样用于 `package.json`、bundle 行、invariant 注册、exports、测试和文档。只在上述身份属主中替换模板包名 `@your-scope/dsh-plugin-template` 和插件 id。不要对 `.agents/skills/` 做全局替换;它的通用示例与标记检查必须保持可复用。
-3. 更新 `description`、`LICENSE` 与 `cordis.patch.yml`。
+3. 更新 `description`、`keywords`、`LICENSE` 与 `cordis.patch.yml`。
 4. 只把实现用到的 DSH 宿主服务加入包契约与组合补丁。源码和构建依赖必须能从本仓库的 `node_modules` 解析。
 5. 当包拥有权威事件或可变数据关系时,替换空的 invariant installer。
 6. 在 `src/runtime.ts` 实现激活与宿主边界行为,按需把内聚能力移入项目专属的 `src/<feature>/` 目录。保持 `src/index.ts` 只含 Loader 元数据与公共 re-export,并通过 `ctx.effect()`、`ctx.on()` 或 registry disposer 限定注册范围。
@@ -101,7 +101,7 @@ pnpm test
 pnpm run build
 ```
 
-`pnpm install` 只解析本包声明的依赖。`lint` 使用启用类型感知分析的 Oxlint 并拒绝警告,检查配置的源码与测试工程。`build` 直接从 `src/` 编译 host entry,向 `lib/` 输出可直接打包的运行时 JavaScript 与声明,不运行安装期 lifecycle build。
+`pnpm install` 只解析本包声明的依赖。`lint` 使用启用类型感知分析的 Oxlint 并拒绝警告,检查配置的源码与测试工程。`build` 直接从 `src/` 编译 host entry,向 `lib/` 输出可直接打包的运行时 JavaScript 与声明,不运行安装期 lifecycle build。额外参数会透传给 tsdown,因此本地调试可用 `pnpm run build --sourcemap` 产出 source map;默认 `build` 不产 map。
 
 release 产物在打包前从 `src/` 构建。profile 或 consumer 安装消费现成的 `lib/` 输出，不运行 `prepare`；使用 `pnpm pack --dry-run --json` 检查最终归档内容。
 

package.json

@@ -1,6 +1,14 @@
 {
   "name": "@your-scope/dsh-plugin-template",
   "description": "Standalone Cordis plugin template for DeepSeek Harness",
+  "keywords": [
+    "cordis",
+    "cordis-plugin",
+    "deepseek-harness",
+    "dsh",
+    "dsh-plugin",
+    "plugin-template"
+  ],
   "license": "BSD-3-Clause",
   "publishConfig": {
     "access": "public"
@@ -15,10 +23,7 @@
     "#src/*": "./src/*.ts"
   },
   "files": [
-    "lib/**/*.js",
-    "lib/**/*.js.map",
-    "lib/**/*.d.ts",
-    "lib/**/*.d.ts.map",
+    "lib",
     "cordis.patch.yml",
     "README.md"
   ],
@@ -33,8 +38,8 @@
     },
     "./package.json": "./package.json"
   },
-  "main": "lib/index.js",
-  "types": "lib/index.d.ts",
+  "main": "./lib/index.js",
+  "types": "./lib/index.d.ts",
   "dsh": {
     "bundle": {
       "patch": "./cordis.patch.yml"

tsconfig.json

@@ -4,9 +4,7 @@
     "target": "ES2024",
     "module": "ESNext",
     "moduleResolution": "bundler",
-    "declaration": true,
     "sourceMap": true,
-    "declarationMap": true,
     "skipLibCheck": true,
     "esModuleInterop": true,
     "allowImportingTsExtensions": true,