mechanica 2.0.1 → 2.0.3

package/README.md

@@ -30,6 +30,37 @@ npm run export
 
 Prefer Bun? `bun create mechanica my-site`, then `bun install` and `bun run dev`.
 
+### With an AI coding agent
+
+Claude Code, Codex and similar agents can set the site up and build it for you. Open an empty folder in the agent and paste:
+
+```text
+Create a Mechanica site in this folder.
+
+1. Check for Node.js 20.19+ (`node -v`) or Bun (`bun -v`). If neither is
+   installed, ask me before installing Bun from https://bun.sh.
+2. Run `npm create mechanica@latest .` (or `bun create mechanica .`), install
+   the dependencies, and start the dev server in the background.
+3. Read AGENTS.md in the project and follow it for everything else.
+
+Then build: <describe your site>
+```
+
+To skip the pasting, install the skill once. It does the same setup and also handles a machine with no Node.js.
+
+Claude Code:
+
+```bash
+claude plugin marketplace add den59k/mechanica
+claude plugin install mechanica@mechanica
+```
+
+Codex: save [SKILL.md](https://github.com/den59k/mechanica/blob/main/plugins/mechanica/skills/create-mechanica-site/SKILL.md) as `~/.agents/skills/create-mechanica-site/SKILL.md`.
+
+Then ask the agent to create a Mechanica site.
+
+The starter's `AGENTS.md` teaches the agent how to write blocks and pages and how to check its work with screenshots, and points it at the documentation of the installed version. Run the agent on your own machine: the editor opens in your browser from the local dev server.
+
 ## A Mechanica project
 
 ```text
@@ -328,7 +359,9 @@ These drive a locally installed Chrome or Edge (or `--browser <path>`) and need
 | `mechanica shot <blockId \| /path>` | Screenshot a block or a page. Flags: `--width`, `--data`, `--out`, `--full`, `--server`, `--browser` |
 | `mechanica thumbs [--blocks]` | Regenerate page or block thumbnails for the editor |
 | `mechanica images` | Generate image dimensions and blur-up previews for `.mech/assets` (needs `sharp`; `--force` redoes all) |
-| `mechanica push` | Experimental: upload `dist/` to a Mechanica hosting backend |
+| `mechanica login` | Sign in to the Mechanica platform and save an access token for this machine (`--host`, `--token`) |
+| `mechanica link <slug>` | Point this repository at a site on the platform (`--create` makes the site) |
+| `mechanica push` | Publish the committed project to the platform: pull what was edited online, `git push`, build and upload the bundle when the code changed, wait for the deploy |
 
 ## Plugin options
 
@@ -357,7 +390,7 @@ From `mechanica`:
 - **Composables:** `usePages`, `usePagination`, `useFetch`, `useLocale`, `useLayout`, `usePageData` (the current page's path, `meta`, layout and locale), `useRouter`, `useRoute`
 - **Helpers:** `imagePosition`
 
-From `mechanica/plugin`: `mechanica` and the `PageProvider` type. From `mechanica/widgets`: `defineWidget` and `useWidgetServices` (uploads and the image picker inside widget editors). `mechanica/editor` and `mechanica/composer` are loaded by the plugin in development; you don't import them.
+From `mechanica/plugin`: `mechanica` and the `PageProvider` type. From `mechanica/widgets`: `defineWidget` and `useWidgetServices` (uploads and the image picker inside widget editors). `mechanica/editor` and `mechanica/composer` are loaded by the plugin in development; you don't import them. From `mechanica/export`: `exportBuilt(projectDir, options)`, which statically renders an already built project (`dist/` + `.mech/`) without running a build and resolves to `{ pages, warnings }` — for render services that receive a prebuilt bundle; `options.outDir` sets where the site is written, and `options.fetchJson` replaces how `useFetch` requests are made.
 
 ## Upgrading from 1.x
 

package/bin/mechanica.js

@@ -10,6 +10,8 @@ const entry = process.versions.bun && existsSync(srcEntry) ? '../src/cli/cli.ts'
 const { run } = await import(entry)
 
 run(process.argv.slice(2)).catch((error) => {
-  console.error(error)
+  // A plain Error is a message for the user (bad usage, a refused push);
+  // anything else is a bug worth its stack trace.
+  console.error(error?.constructor === Error ? `mechanica: ${error.message}` : error)
   process.exit(1)
 })

package/dist/chunks/{ImagePickerDialog-6skSAzJh.js → ImagePickerDialog-DJGhtW3r.js}

@@ -6,7 +6,7 @@ var _plugin_vue_export_helper_default = (sfc, props) => {
 	return target;
 };
 //#endregion
-//#region \0svg-glob:C:\Users\Den\Desktop\CURVES\mechanica\packages\mechanica\src\editor\icons
+//#region \0svg-glob:/home/runner/work/mechanica/mechanica/packages/mechanica/src/editor/icons
 var contents = {
 	"align-center": `<path d="M4 6h16M7 12h10M6 18h12"/>`,
 	"align-left": `<path d="M4 6h16M4 12h10M4 18h13"/>`,

package/dist/chunks/{editor-B0r4EOIM.js → editor-JV0Nhfw4.js}

@@ -1,4 +1,4 @@
-import { a as renderCrop, c as useDialog, d as _plugin_vue_export_helper_default, i as readImageSize, l as VIcon_default, n as VDialog_default, r as analyzeImageFile, s as dialogKey, t as ImagePickerDialog_default } from "./ImagePickerDialog-6skSAzJh.js";
+import { a as renderCrop, c as useDialog, d as _plugin_vue_export_helper_default, i as readImageSize, l as VIcon_default, n as VDialog_default, r as analyzeImageFile, s as dialogKey, t as ImagePickerDialog_default } from "./ImagePickerDialog-DJGhtW3r.js";
 import { Fragment, Teleport, Transition, computed, createBlock, createCommentVNode, createElementBlock, createElementVNode, createSlots, createTextVNode, createVNode, defineComponent, inject, mergeProps, nextTick, normalizeClass, normalizeStyle, onBeforeUnmount, onErrorCaptured, onMounted, openBlock, provide, reactive, ref, renderList, renderSlot, resolveDynamicComponent, shallowRef, toDisplayString, unref, vShow, watch, withCtx, withDirectives, withKeys, withModifiers } from "vue";
 import { deepEqual, getDefaultValue } from "mechanica-shared";
 import { unfoldSchema } from "compact-json-schema";