create-rigline-plugin 1.0.0-alpha.5 → 1.0.0-alpha.6

package/README.md

@@ -29,6 +29,11 @@ Then:
 
 and *Developer: Reload Webviews*.
 
+The workspace declares `@rigline/core` — the engine, which carries the `rigline-engine` command its
+`build` and `codegen` scripts run — and never `rigline`, which is the layer a *user* installs to
+fetch that engine. `pnpm rigline <verb>` here is a script forwarding to the engine in your own
+`node_modules`, so the loop above needs nothing installed globally.
+
 `generated.ts` ships as a placeholder so a fresh scaffold typechecks before `codegen` has ever run.
 Once you run `codegen` it holds the identifiers *your* extension version actually has; commit it,
 and the diff when you run against a newer extension is how you find out what moved.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "create-rigline-plugin",
-  "version": "1.0.0-alpha.5",
+  "version": "1.0.0-alpha.6",
   "description": "Scaffold a workspace for Claude Code VS Code extension plugins",
   "keywords": [
     "rigline",
@@ -32,10 +32,10 @@
     "create-rigline-plugin": "./dist/index.js"
   },
   "devDependencies": {
-    "@rigline/plugin-api": "1.0.0-alpha.5"
+    "@rigline/plugin-api": "1.0.0-alpha.6"
   },
   "scripts": {
-    "build": "tsc -p tsconfig.build.json",
+    "build": "node ../../scripts/clean-dist.mjs && tsc -p tsconfig.build.json",
     "typecheck": "tsc -p tsconfig.json"
   }
 }

package/template/README.md

@@ -51,9 +51,9 @@ says rather than resolving its own.
 ## Publishing
 
 A plugin is published as an ordinary npm package carrying `rigline.json` and its built entry, and
-installed with `rigline add <name>`. Nothing about publishing is special: `rigline build` bundles
-everything the entry imports, so a published plugin has no runtime dependency to install, and
-`@rigline/plugin-api` stays a *devDependency*.
+installed with `rigline add <name>`. Nothing about publishing is special: `rigline-engine build`
+bundles everything the entry imports, so a published plugin has no runtime dependency to install,
+and both `@rigline/core` and `@rigline/plugin-api` stay *devDependencies*.
 
 `.github/workflows/release.yml` does it from CI, with no npm token stored anywhere: GitHub
 authenticates to npm over OIDC, and what the workflow does is *stage* — a version nobody can

package/template/package.json

@@ -5,14 +5,15 @@
   "packageManager": "pnpm@12.3.4",
   "engines": { "node": ">=22.12.0" },
   "scripts": {
-    "codegen": "rigline codegen",
+    "rigline": "rigline-engine",
+    "codegen": "rigline-engine codegen",
     "build": "pnpm -r build",
     "typecheck": "pnpm -r typecheck",
     "test": "vitest run"
   },
   "devDependencies": {
+    "@rigline/core": "__RIGLINE_RANGE__",
     "@rigline/plugin-api": "__RIGLINE_RANGE__",
-    "rigline": "__RIGLINE_RANGE__",
     "rolldown": "^1.2.8",
     "typescript": "^7.0.2",
     "vitest": "^5.0.0"

package/template/plugins/__NAME__/package.json

@@ -8,11 +8,11 @@
   "publishConfig": { "access": "public" },
   "files": ["dist", "rigline.json"],
   "scripts": {
-    "build": "rigline build",
+    "build": "rigline-engine build",
     "typecheck": "tsc -p tsconfig.json"
   },
   "devDependencies": {
-    "@rigline/plugin-api": "__RIGLINE_RANGE__",
-    "rigline": "__RIGLINE_RANGE__"
+    "@rigline/core": "__RIGLINE_RANGE__",
+    "@rigline/plugin-api": "__RIGLINE_RANGE__"
   }
 }

package/template/plugins/__NAME__/src/index.test.ts

@@ -4,7 +4,7 @@
  * Verification splits three ways, and knowing which tier a question belongs to is most of writing
  * a test that is worth having. A pure function is this tier. Whether a decoration lands in the
  * right place, survives a re-render, or costs the row a line of height is a question about the app,
- * and only the app can answer it: build, `rigline add`, reload the webview, look.
+ * and only the app can answer it: `pnpm build`, `pnpm rigline add`, reload the webview, look.
  */
 import { describe, expect, it } from "vitest";
 import { badgeText } from "./index.ts";