@open-press/cli 0.8.0 → 1.1.0

package/package.json

@@ -1,8 +1,8 @@
 {
   "name": "@open-press/cli",
-  "version": "0.8.0",
+  "version": "1.1.0",
   "type": "module",
-  "description": "Scaffolder for open-press — AI-first fixed-layout document workspaces.",
+  "description": "Command line interface for OpenPress workspaces.",
   "license": "MIT",
   "author": "quan0715",
   "homepage": "https://github.com/quan0715/open-press#readme",
@@ -24,14 +24,15 @@
     "ai-first",
     "scaffold",
     "init",
-    "cli"
+    "cli",
+    "render",
+    "pdf"
   ],
   "bin": {
     "open-press": "dist/cli.js"
   },
   "files": [
     "dist",
-    "template",
     "README.md"
   ],
   "publishConfig": {
@@ -41,7 +42,7 @@
     "node": ">=20"
   },
   "dependencies": {
-    "tar": "^7.5.0"
+    "@open-press/core": "1.1.0"
   },
   "devDependencies": {
     "@types/node": "^25.8.0",
@@ -49,9 +50,9 @@
     "typescript": "^6.0.3"
   },
   "scripts": {
-    "sync:template": "node scripts/sync-template.mjs",
-    "build": "pnpm sync:template && tsup",
+    "build": "tsup",
     "dev": "tsup --watch",
-    "typecheck": "tsc --noEmit"
+    "typecheck": "tsc --noEmit",
+    "test": "pnpm build && node --test tests/*.test.mjs"
   }
 }

package/template/core/AGENTS.md

@@ -1,126 +0,0 @@
-# Working on this open-press workspace
-
-This directory is an **open-press workspace** scaffolded by
-`@open-press/cli`. You (the agent) own:
-
-- `document/` — chapters (MDX), components, theme, media. The actual content.
-- `package.json` / `openpress.config.mjs` — project metadata + build config.
-- `.agents/skills/` — agent skills installed by `npx skills` (auto-refreshed via `npx open-press upgrade`).
-
-The rest of the tree is the open-press framework copied at scaffold time
-(`engine/`, `src/`, `vite.config.ts`, etc). Treat it as vendored — don't
-hand-edit unless the user explicitly asks; the next `npx open-press upgrade`
-will rewrite it.
-
-## Quick reference
-
-```bash
-npm run dev                  # workbench at http://127.0.0.1:5173/?dev=1
-npm run openpress:validate   # structural checks
-npm run openpress:render     # full render through chromium
-npm run openpress:pdf        # write document.pdf
-npm run openpress:export     # write public/openpress/document.json
-npm run openpress:deploy     # deploy via the configured adapter
-npx open-press doctor        # current vs latest version + pending migrations
-npx open-press upgrade       # apply the upgrade flow (see below)
-```
-
-## When the user asks to upgrade
-
-Triggers: "升級 / 套件更新 / upgrade open-press / apply latest design /
-update to vX.Y.Z" etc.
-
-**Follow the upgrade SOP, do NOT manually diff template versions:**
-
-1. `npx open-press doctor` — confirm current vs latest, count pending
-   migrations.
-2. Ask the user "go ahead?" — briefly mention what will change (deps,
-   skills, migrations to read).
-3. `npx open-press upgrade` — refreshes `@open-press/core`, refreshes
-   installed skills, **fetches migration notes for each pending version
-   into `.openpress/migrations/<version>.md`** and lists the paths.
-4. For each migration file listed, read it fully. Each has a
-   `Document-level changes` section with `rg` find + rewrite rules.
-   Apply to `document/` with user confirmation.
-5. Verify:
-   ```bash
-   npm run openpress:validate
-   npm run openpress:render
-   ```
-   Fix anything broken using the migration notes.
-6. Report to the user: starting version → ending version, what was
-   applied, anything that needed manual judgement.
-
-**Anti-pattern**: running `npx @open-press/cli@latest init` somewhere
-and manually diffing against the workspace. The migration notes are the
-authoritative source for what changed; fresh templates ship default
-content that does not apply to a customised workspace.
-
-## When the user says "I changed X but the page didn't update"
-
-Common cause: **the reader renders from a static `public/openpress/document.json`,
-not from your live MDX / theme files.** Vite Hot Reload covers React UI
-chrome (workbench panels, inspector, navigation) but it does **not**
-regenerate `document.json`. So edits to:
-
-- `document/chapters/**/*.mdx` (prose)
-- `document/index.tsx` (Press tree, Cover/BackCover JSX)
-- `document/components/**/*.tsx` (Page, openers, custom components)
-- `document/theme/**` style files that affect pagination capacity
-- `openpress.config.mjs` metadata (title, captionNumbering, …)
-
-…all need a re-export before the workbench / public viewer reflect
-the change:
-
-```bash
-npm run openpress:export   # regenerate public/openpress/document.json
-# then refresh the browser
-```
-
-Quick rules of thumb:
-
-- Pure CSS edits under `document/theme/` that don't move blocks → HMR
-  is enough (CSS is hot-replaced).
-- Anything that affects content, pagination, or metadata → re-export.
-- `npm run openpress:render` is `export` + extra asset sync; either
-  works to refresh the JSON.
-
-**Agent SOP**: after applying any non-CSS edit to `document/`, run
-`npm run openpress:export` before telling the user "done". If they ask
-"why didn't my change show up?", check whether `document.json` was
-regenerated since the edit.
-
-## When the user reports a render / paginate issue
-
-Press Tree paginates at build time. Common things to check:
-
-1. `npm run openpress:export` then inspect
-   `public/openpress/document.json` for `source.warnings` (chain
-   overflow, missing chains, etc.).
-2. `npm run openpress:validate` for structural issues
-   (missing entries, broken anchors).
-3. `npm run dev` and use the workbench inspector to find which MDX
-   block / Frame element is misbehaving — comments and inline
-   annotations work directly from there.
-
-## Skills
-
-This workspace ships agent skills under `.agents/skills/`. If your
-platform supports skills (Claude Code, Cursor, Codex, Cline, Gemini
-CLI, …), prefer invoking them over re-reading this file:
-
-- `openpress` — operate the workspace (CLI, validate, export, render,
-  PDF, deploy, search/replace, comments, upgrades, routing).
-- `openpress-writing` — writing-time rules for MDX prose.
-- `openpress-design` — theme tokens, layout, page surfaces.
-- `openpress-deploy` — deployment workflows.
-- `openpress-init` — scaffolding new workspaces.
-- Plus any style-pack-specific skills installed by the user.
-
-Skills are kept in sync by `npx skills upgrade` (run automatically
-inside `npx open-press upgrade`).
-
-## Reporting issues
-
-- Issues / questions: https://github.com/quan0715/open-press/issues
-- Source: https://github.com/quan0715/open-press

package/template/core/CHANGELOG.md

@@ -1,215 +0,0 @@
-# @open-press/core
-
-## 0.8.0
-
-### Minor Changes
-
-- **Workbench architecture**: the monolithic `workbench.tsx` is split into a modular structure under `workbench/{shell,panels,actions,inspector,mentions,project,document}/`. New panels: `DeploymentControl`, `SearchControl`, `PendingCommentsPanel`, `DocumentPanel`, `ProjectEntryPanel`, plus `WorkbenchShell` and `InlineInspectorLayer`.
-- **Module reorganization**: source tree split into typed subdirectories:
-  - `app/`: `OpenPressApp`, `OpenPressRuntime` (replaces the old `App.tsx` + `renderer.tsx`)
-  - `document-model/`: `anchorMap`, `documentIndexes`, `documentTypes`, `objectEntityModel`, `projectIdentity`, `reactDocumentMetadata`
-  - `reader/`: `PublicReaderPage`, `ReaderNavigationPanel`, `useReaderRuntime`, registry/route/scroll/state helpers
-  - `shared/`: `frameScheduler`, `runtimeMode`, `Panel`, `numberUtils`
-- **Object-entity model**: `Frame` and `MdxArea` now expose `data-openpress-object-id`. New `document-model/objectEntityModel` defines the id format.
-- **`MediaFigure` / `ImageFigure`**: new core primitives that accept `src/alt/caption` and resolve relative paths to `/openpress/media/...` automatically.
-- **`<Sections>` default page**: `page` prop becomes optional; when omitted the built-in `DefaultSectionPage` renders the standard manuscript frame.
-- **Engine helpers**: new `engine/react/{http-json,object-entities,source-edit-endpoint}.mjs` and `engine/runtime/{file-walk,path-utils}.mjs` runtime helpers. `engine/runtime/source-text-tools` exports TypeScript definitions.
-- **Dev endpoints**: vite plugin wires `/__openpress/search` and `/__openpress/source-edit` middlewares for the new workbench search + inline editing flows.
-- **Inline source editor**: ships the `InlineSourceEditorLayer` UI on top of `useInlineDocumentEditor` + `/__openpress/source-edit`. The hook now uses a `MutationObserver` so newly inserted blocks become editable, and routes mouse clicks through `focus()` to preserve selection on `contenteditable` boundaries. Workbench wires `sourceEditorTarget` state into the layer.
-- **Table editing in the source pipeline**: table captions are emitted as standalone source blocks (`kind=element`, `name=caption`, `layout="attached"`) with `data-openpress-block-id`/`data-openpress-object-id` markers and preserved source positions; the allocator treats `layout="attached"` blocks as non-paginable. `applySourceBlockTableCellEditToText` (in `engine/runtime/source-text-tools`) accepts a `cellIndex` so the inline source editor can target a single `<td>`.
-- **Reader pagination**: arrow-key pagination now defers to the user's active text selection. Shift-arrow / mouse-drag selections no longer get swallowed by the page-turn shortcut.
-- **Page zoom + spread layout**: new `reader/pageViewportScaleModel` + `usePageViewportScale` hook drive a `--openpress-page-viewport-scale` CSS variable on the page container; the workbench toolbar exposes a `PageZoomControl` dropdown with fit-width / fit-page / fixed percentages plus a one-page / two-page spread toggle.
-- **Inspector cell-precision comments**: `CommentDraft` gains an optional `targetObjectId` so a comment can point at a sub-block (e.g. a single table cell) while still attributing the source position to its enclosing block. `formatInspectorHint` carries the value through to the wire hint.
-- **Shared `WorkbenchDialog` shell**: portal + backdrop + header (eyebrow / title / title-meta / close) + optional footer. `DeploymentControl`, `SearchControl`, and `ProjectPreviewDialog` all render through this shell now, replacing the prior per-dialog scaffolding under `openpress-deploy-dialog-*` / `openpress-search-dialog-*` / `openpress-project-preview-dialog__*`.
-- **`WorkbenchControlPanel` registry**: `HtmlWorkbench` now accepts an `extraControlPanels?: WorkbenchPanel[]` prop and renders the right-side panel from a `{ id, render }` registry. Built-in panels (pending comments, project entry) ship as the first entries.
-- **Workbench state hooks**: extract `useDeploymentWorkbench` and `useInspectorComments` from `HtmlWorkbench`; `useReaderRuntime` is split into focused sub-hooks (`usePanelState`, `useReaderScrollAnchor`, `useReaderHashSync`, `useReaderKeyboardNav`).
-- **`InlineInspectorLayer` memoization**: now wrapped in `React.memo` with a stable `geometryVersion` prop so the geometry / event listeners no longer rebuild on every parent render.
-- **Panels open lazily**: `usePanelState` now defaults both panels closed, so the reader opens with a clean stage; resize never auto-opens them.
-
-### Patch Changes
-
-- Inspector: fix comment-marker count and multi-target marker rendering.
-- Inspector: object-entity id helpers consolidate in `document-model/objectEntityModel` instead of being duplicated inside `Frame`, `MdxArea`, manuscript `TocArea`, and `PublicReaderPage`.
-- Inline editor: `useInlineDocumentEditor` exposes `onDocumentEdited`; `OpenPressApp` re-loads `/openpress/document.json` after a successful inline edit so derived indexes stay in sync.
-- Dev: reset Vite optimizer cache so workspace-side dependencies are picked up.
-- Workbench dialog: viewport-aware width + max-height so a big media preview doesn't blow up the dialog to full screen.
-- Project composer: add `/apply-comments` to the skill mention list so pending comment resolution can be invoked from the workbench.
-- Carries forward the 0.7.1 measurement + pagination fixes (font/image readiness, relative media src inlining, list-per-item paging, `OPENPRESS_DEBUG_ALLOC`, academic-paper starter body overflow).
-
-### Breaking Changes
-
-- `FrameContext.consumeArea(chainId)` return type changes from `ReactNode | null` to `{ indexInFrame: number; blocks: ReactNode | null }`. Custom `Frame` consumers must read `.blocks`.
-- `App` export is renamed to `OpenPressApp` and now lives under `@open-press/core/app`. The old `renderer.tsx` is replaced by `OpenPressRuntime`.
-- `data-openpress-mdx-area-empty` is now always emitted (`"true"` / `"false"`). Selectors that relied on the attribute being absent need updating.
-- Reader `ViewMode` collapses to `"paged"` only — the legacy `"reading"` flow mode is removed. Use `usePageViewportScale` for free-scaling instead.
-- Several internal module paths moved into subdirectories (`document-model/`, `reader/`, `shared/`, `workbench/...`). Consumers that deep-imported from the openpress source must switch to the new barrels.
-- Shared dialog scaffolding (backdrop, container, header, close button) moved from per-dialog class families (`openpress-deploy-dialog-backdrop`, `__panel`, `__panel header`, `__close`, etc.) to the shared `openpress-workbench-dialog*` family. Per-dialog modifier classes (`openpress-deploy-dialog`, `openpress-search-dialog`, `openpress-project-preview-dialog`) are still applied for dialog-specific styling. Selectors that targeted the old scaffolding names (notably `*-backdrop` and `__panel`) need updating; selectors that combine the modifier class with new `__heading` / `__footer` / `__close` modifiers continue to work.
-
-## 0.7.1
-
-### Patch Changes
-
-- Measurement pipeline + pagination fixes:
-
-  - **Measurement**: wait on `document.fonts.ready`, image `load`/`error` + `decode()`,
-    and two `requestAnimationFrame` ticks before sampling block heights so figures
-    no longer under-measure on cold loads.
-  - **Measurement**: inline relative `media/`, `./media/`, and `/openpress/media/`
-    image sources during the SSR measurement pass (previously only the absolute
-    `/openpress/media/...` form was rewritten, leaving relative refs as broken).
-  - **MDX compile**: split bullet/numbered lists into per-item paginable blocks
-    so long lists can break across pages without losing ordered numbering.
-  - **Debug**: new `OPENPRESS_DEBUG_ALLOC` env var prints per-iteration allocator
-    state (mdxArea capacities, block heights, pagination hints, warnings).
-  - **Academic-paper starter**: `<MdxArea overflow="extend">` on the body and the
-    single-column `.reader-page--content .page-body` override removed so content
-    paginates naturally with the new allocator.
-
-## 0.7.0
-
-### Minor Changes
-
-- 718d2d1: **Press Tree render architecture** — full refresh of the React export pipeline (clean break, no v0.5 compatibility).
-
-  The render kernel no longer knows about `cover`, `toc`, `chapter`, or `back-cover` as built-in concepts. Workspaces describe their document as a React tree using three primitives:
-
-  - `Press` — root composition boundary.
-  - `Frame` — a single fixed-layout surface (replaces `BasePage` and friends).
-  - `MdxArea` — a measurable slot consuming a content chain, with `overflow="extend|truncate|error"` control.
-
-  Sources are now declarative descriptors:
-
-  ```tsx
-  export const sources = {
-    story: mdxSource({ preset: "section-folders", root: "chapters" }),
-  };
-
-  export default function MyPress() {
-    return (
-      <Press>
-        <Cover />
-        <Toc source="story" />
-        <Sections source="story" page={Page} />
-        <BackCover />
-      </Press>
-    );
-  }
-  ```
-
-  Three `mdxSource()` presets: `section-folders` (existing convention), `section-files` (flat file-per-section), `file-list` (explicit ordering).
-
-  Manuscript helpers (`Toc`, `Sections`, `Chapters` alias) ship in `@open-press/core/manuscript`. `mdxSource()` lives in `@open-press/core/mdx`. Subpath exports keep the public surface tight without committing to separate npm packages.
-
-  `Toc` is implemented as a manuscript helper, not a core kernel special case. Registered sources generate a synthetic `toc:<sourceId>` chain; `TocArea` consumes it with the same allocation path as `MdxArea`.
-
-  Reader-side pagination is removed. The export pipeline writes final frame HTML into `document.json`; the reader displays that HTML and no longer mutates headings/captions, injects footers, or reflows pages at runtime. Page shell belongs to workspace components.
-
-  MDX source resolution now derives manuscript TOC entries from actual `##` / `###` headings, not folder slugs. Heading numbering is written during export as `data-chapter="01"` / `data-section="1.1"` attributes so themes can render numbering with CSS without reader-side mutation.
-
-  **Removed (no compatibility layer):**
-
-  - `BasePage`, `BaseCoverPage`, `BaseTocPage`, `BaseContentPage`, `BaseBackCoverPage`.
-  - Legacy named exports (`cover`, `toc`, `backCover`) from `document/index.tsx`.
-  - The `migrate-to-react` CLI command.
-  - Implicit chapter discovery as the only source mechanism.
-  - Legacy `chapter.tsx` meta/opener auto-discovery. Section openers are explicit workspace components in the Press tree.
-
-  The top-level purity gate remains: `config` must be data, `sources` must be pure `mdxSource()` descriptors, and filesystem/network/process side effects are rejected before module execution. Default-exported function bodies can contain normal React component logic, including hooks and `.map()`.
-
-  All `<Frame>` instances require a stable `frameKey`; source roots and file-list entries must stay inside `document/`.
-
-  **Workspace data attributes:**
-
-  - `data-frame-role` (new, opaque role like `"manuscript.content"`).
-  - `data-page-kind` (derived from role's last segment — reader CSS keeps using this).
-  - `data-section-id` replaces `data-chapter-slug` for section-scoped CSS.
-
-  **Migration:** Workspaces written for v0.5.x must rewrite `document/index.tsx` to default-export a Press component. Pre-1.0 minor bump is acceptable per repo policy; no production deployments exist to break.
-
-  See `docs/superpowers/specs/2026-05-23-press-tree-render-architecture-design.md` for full design rationale.
-
-## 0.6.0
-
-### Minor Changes
-
-- f8fdecd: Third bundled pack: `academic-paper`.
-
-  A single-column A4 academic / research paper starter — serif title block, abstract band, index terms, numbered sections (I, II, III), italic sub-sections (A, B, C), `[N]` numeric references, sample chapters derived from the IEEE conference template structure (Introduction, Methods, Results & Discussion, Acknowledgment, References).
-
-  ```bash
-  npx @open-press/cli init my-paper --pack academic-paper
-  ```
-
-  Suitable for: draft / preprint / iteration. Not suitable for camera-ready IEEE / ACM submission — those still need LaTeX with the publisher's class file.
-
-  Two-column body and other paged-document features (footnotes, cross-references with page numbers, running headers) are intentionally **out of scope for this release**. They'll be designed as a self-maintained engine evolution + multi-mode architecture in a separate spec round, rather than depending on a third-party pagination polyfill.
-
-- c490653: `@open-press/cli init` accepts third-party style packs via `--pack github:owner/repo`.
-
-  ```bash
-  # bundled (unchanged)
-  npx @open-press/cli init my-doc --pack editorial-monograph
-
-  # third-party (new)
-  npx @open-press/cli init my-thesis --pack github:quan0715/openpress-pack-nycu-thesis
-  npx @open-press/cli init my-paper --pack github:foo/their-pack#v1.2
-  ```
-
-  The cli fetches `starter/document/` from the named repo (default branch, or `#ref` for a specific branch/tag) and copies it into the new workspace. If the pack repo also publishes SKILL files at `skills/<name>/`, they're installed via `npx skills add <owner>/<repo>` after the framework skills, so the agent picks them up automatically.
-
-  Repo layout convention for third-party packs is documented in `docs/style-pack-authoring.md`. Empty-result extraction (the named repo exists but has no `starter/document/` at root) fails with a clear error pointing at the expected layout.
-
-  The two bundled packs (`editorial-monograph`, `claude-document`) keep their current short-name behaviour; only the cli's validator widened to accept the `github:` prefix.
-
-## 0.5.0
-
-### Minor Changes
-
-- 0169cba: Agent-driven upgrade flow.
-
-  **New commands:**
-
-  - `npx open-press doctor` — diagnose workspace against latest framework state. Reports `@open-press/core` version vs npm latest, installed skill count, and any pending `docs/migrations/<version>.md` notes between current and latest. `--json` for machine-readable output, `--no-cache` to bypass the 24h cache. Always exits 0 (informational only).
-
-  - `npx open-press upgrade` — orchestrate the upgrade. Runs `npm update @open-press/core` (when the workspace declares the dep) and `npx skills upgrade`, then surfaces the list of migration notes for the agent to read. **Does not auto-edit `document/` content** — the agent reads the surfaced `docs/migrations/<version>.md` notes and proposes edits to the user with confirmation. Use `--dry-run` to preview, `--no-deps` / `--no-skills` to target one layer.
-
-  **Dev startup notice:**
-
-  `open-press dev` now runs `doctor` before starting Vite. When the workspace is behind, a single line prints: `○ open-press: @open-press/core 0.4.0 → 0.5.0 · 1 migration note(s) — run npx open-press doctor for details.` Cached for 24h, network failure is silent, never blocks dev.
-
-  **Migration docs:**
-
-  - New `docs/migrations/_template.md` — each release with breaking changes ships a `docs/migrations/<version>.md` file with sections the agent reads.
-  - New `docs/migrations/0.4.0.md` — backfilled. Documents the SKILL fold (no document or CLI changes).
-
-  **SKILL update:**
-
-  `openpress` skill's "Updating An Existing Workspace" section rewritten around the new commands: detect (`doctor`), apply (`upgrade`), interpret migration notes, propose document edits with user confirmation. Concrete agent workflow + breaking-change reference table.
-
-### Patch Changes
-
-- 931d4ac: Support framework root dogfood workspaces and correct CLI script paths outside the core package root.
-
-## 0.4.0
-
-### Minor Changes
-
-- 3cb4939: Consolidate internal skills (13 → 11).
-
-  - `openpress-update` folded into `openpress` as an "Updating An Existing Workspace" section. The release-upgrade flow, pre-flight checks, breaking-change reference, and do-not list are now part of the system-operation skill where they naturally belong.
-  - `openpress-document-hierarchy` folded into `openpress-writing` as a "Hierarchy" section. Hierarchy decisions (H2/H3/H4 model, TOC depth, appendix placement, H4 granularity) and prose decisions happen in the same workflow; one skill, one routing decision.
-  - `references/data-structures-outline.md` moved from the hierarchy skill into `openpress-writing/references/`.
-
-  Lower maintenance surface: 2 fewer SKILL.md files to keep in sync, ~5 fewer cross-references to police. No content lost — same rules, fewer files.
-
-  User impact: agents already in workspaces with `openpress-update` or `openpress-document-hierarchy` SKILL files installed should run `npx skills upgrade` to refresh the catalog.
-
-## 0.3.0
-
-### Minor Changes
-
-- Initial monorepo release of `@open-press/cli` and `@open-press/core` on npm.
-
-  **@open-press/cli** (new): scaffolder for open-press workspaces. Run `npx @open-press/cli init <target> --pack <pack>` to create a fixed-layout document workspace from a bundled template. Supports `editorial-monograph` and `claude-document` style packs, metadata flags, and AI-agent skill installation under `.claude/skills/` and `.agents/skills/`.
-
-  **@open-press/core** (new): framework runtime, CLI engine, render pipeline, and document primitives. Consumed transitively by workspaces scaffolded via `@open-press/cli`. Exposes the `open-press` bin (dev / build / preview / validate / pdf / deploy / export).

package/template/core/README.md

@@ -1,40 +0,0 @@
-# @open-press/core
-
-Framework runtime, CLI engine, and Press Tree primitives for [open-press](https://github.com/quan0715/open-press) — an AI-first fixed-layout document workspace.
-
-Most users do **not** install this package directly. Instead, scaffold a workspace with the CLI:
-
-```bash
-npx @open-press/cli init my-doc --pack editorial-monograph
-```
-
-The scaffolded workspace contains a snapshot of this package.
-
-## Direct use
-
-If you want the runtime primitives in an existing project:
-
-```bash
-npm install @open-press/core
-```
-
-```tsx
-import {
-  Press,
-  Frame,
-  MdxArea,
-  BaseFigure,
-  BaseCallout,
-} from "@open-press/core";
-
-import { mdxSource } from "@open-press/core/mdx";
-import { Sections, Toc } from "@open-press/core/manuscript";
-```
-
-`document/index.tsx` default-exports a `<Press>` tree. `Frame` marks fixed-layout pages, `MdxArea` receives measured MDX blocks, and `mdxSource()` declares which MDX files participate in the render pipeline.
-
-The CLI bin (`open-press`) supports dev / build / preview / validate / pdf / deploy / export commands. It requires a workspace with `openpress.config.mjs` and the surrounding framework files (which the scaffolder installs).
-
-## License
-
-MIT — see [LICENSE](https://github.com/quan0715/open-press/blob/main/LICENSE).

package/template/core/engine/cli.mjs

@@ -1,96 +0,0 @@
-#!/usr/bin/env node
-
-import * as deployCmd from "./commands/deploy.mjs";
-import * as devCmd from "./commands/dev.mjs";
-import * as doctorCmd from "./commands/doctor.mjs";
-import * as exportCmd from "./commands/export.mjs";
-import * as initCmd from "./commands/init.mjs";
-import * as inspectCmd from "./commands/inspect.mjs";
-import * as pdfCmd from "./commands/pdf.mjs";
-import * as previewCmd from "./commands/preview.mjs";
-import * as replaceCmd from "./commands/replace.mjs";
-import * as renderCmd from "./commands/render.mjs";
-import * as searchCmd from "./commands/search.mjs";
-import * as typecheckCmd from "./commands/typecheck.mjs";
-import * as upgradeCmd from "./commands/upgrade.mjs";
-import * as validateCmd from "./commands/validate.mjs";
-import { parseOptions } from "./commands/_shared.mjs";
-import { loadConfig } from "./runtime/config.mjs";
-import { listStylePackSkills } from "./init.mjs";
-import { discoverWorkspace } from "./runtime/validation.mjs";
-
-const COMMANDS = {
-  init: initCmd,
-  validate: validateCmd,
-  inspect: inspectCmd,
-  search: searchCmd,
-  replace: replaceCmd,
-  export: exportCmd,
-  render: renderCmd,
-  dev: devCmd,
-  preview: previewCmd,
-  typecheck: typecheckCmd,
-  pdf: pdfCmd,
-  deploy: deployCmd,
-  doctor: doctorCmd,
-  upgrade: upgradeCmd,
-};
-
-const args = process.argv.slice(2);
-const command = args.shift();
-
-try {
-  const code = await main(command, args);
-  process.exitCode = code;
-} catch (error) {
-  console.error(error instanceof Error ? error.message : String(error));
-  process.exitCode = 1;
-}
-
-async function main(commandName, argv) {
-  if (!commandName || ["-h", "--help"].includes(commandName)) {
-    await printHelp();
-    return commandName ? 0 : 2;
-  }
-
-  const handler = COMMANDS[commandName];
-  if (!handler) {
-    console.error(`Unknown command: ${commandName}`);
-    await printHelp();
-    return 2;
-  }
-
-  if (handler.needsWorkspace === false) {
-    return handler.run({ argv });
-  }
-
-  const options = parseOptions(argv);
-  const root = await discoverWorkspace(options.path ?? ".");
-  const config = await loadConfig(root);
-  return handler.run({ root, config, options, recurse: main });
-}
-
-async function printHelp() {
-  const packs = await listStylePackSkills();
-  const skillList = packs.length ? packs.join(" | ") : "(none installed)";
-  console.log(`Usage: node engine/cli.mjs <command> [path] [options]
-
-Commands:
-  init <target> [--skill <name>] [--force]
-  validate
-  inspect [--json] [--no-build] [--dry-run]
-  search [path] <query> [--json] [--scope content|all]
-  replace [path] <from> <to> [--json] [--apply] [--scope content|all]
-  export
-  render --renderer react [--dry-run]
-  preview --renderer react [--host 127.0.0.1] [--port 5173] [--no-build] [--dry-run]
-  dev --renderer react [--host 127.0.0.1] [--port 5173] [--no-build] [--dry-run]
-  typecheck
-  pdf [--output <outputDir>/<pdf.filename>] [--no-build] [--dry-run]
-  deploy --confirm [--dry-run]
-  doctor [--json] [--no-cache]                          # version + skill staleness check
-  upgrade [--dry-run] [--no-deps] [--no-skills] [--json] # apply updates; agent-driven
-
-Style packs available for \`init --skill\`: ${skillList}
-`);
-}