create-hozu 0.7.0 → 0.8.0

package/templates/guide.md

@@ -3,24 +3,12 @@
 A web app built with Hozu (`@hozu/*`). Hozu is not in your training data.
 
 ## Before writing code
-- __READ__
-- Changing existing code: read `__SKILL__/changing.md` first.
+- __READ__ It has the change loop, the commands and the rules no diagnostic checks.
 - The files in `__SKILL__/` are the whole API. Do not read the framework source in `node_modules/@hozu`.
-
-## The loop
-```
-__RUN__ hozu add feature tasks --page / --with detail,toggle,filter,remove   # then edit the texts it lists
-                                          # add auth to the list for sign-in and per-user data
-__RUN__ hozu map                           # outline of the app with file:line, before a change
-__RUN__ hozu check                         # after every change: types, rules, contracts
-__RUN__ hozu check --update-lock           # only to accept a clean, intended behaviour change
-__RUN__ hozu get / --select button --forms  # try pages without a server: text, attributes, forms
-__RUN__ hozu post / --field title=Ship --next /   # submit a form like a browser
-__RUN__ hozu browse / --do 'click Save'     # real browser, no server: errors, widgets, text after steps
-```
 __NOTE__
 ## Rules
 - After `hozu add feature`, do not print the generated files: edit the texts it lists; `hozu map` shows the rest.
 - Apply the fix each diagnostic gives; do not work around a rule.
-- Every behaviour change comes with a contract change.
-- Do not edit `__SKILL__/`: `__RUN__ hozu skill` rewrites it for the installed Hozu version.
+- `__RUN__ hozu get` and `__RUN__ hozu browse` run the same app as `npm start`; do not start a server to check.
+- Do not edit `__SKILL__/` or the text between the `hozu` markers: `__RUN__ hozu skill` rewrites both for the
+  installed Hozu version.

package/skill/changing.md

@@ -1,45 +0,0 @@
-# Changing a Hozu app
-
-Keep the loop short: map once, edit everything, check once, verify once.
-
-## 1. Read
-- The change request.
-- `pnpm exec hozu map`: every route, query, mutation, event, state, view and contract, each with its `file:line`.
-  Open only the lines the change touches. *model* is `model.ts` (schemas, events, effects, `fn`s, the machine),
-  *views* is `views.ts` (views, contracts); `feature.ts` lists both modules, so new exports need no registration.
-- The API is in `SKILL.md`. `hozu docs recipes` has worked steps for an enum field in the add form, a bulk action
-  button, a detail field and a detail page; `hozu docs <topic>` for anything else.
-
-## 2. What to touch
-| Change | Touch |
-|---|---|
-| New UI-only state (a tab) | model: the context field and its initial value, an event, an `on` whose `assign` sets it → views: the control (no contract: it only copies a value). |
-| Filter / sort / page in the URL | the route's `search` schema (with a default) → links with `ui.link(route, params, { key: value })` → read `search.key` in the view. If the page also filters as you type, `seed: ({ search }) => ({ key: search.key })` on the view and read `ctx.key` only. |
-| A per-item action stored on the server (pin, archive, star) | model: a field on the item, an event, a mutation that `invalidates` the list tag, `on(Event, { target: 'pinning', assign: (e) => { ctx.target = e.id } })` and a state with `invoke` → views: the per-item form from `hozu docs patterns` → server: store it and sort in the list resolver. These transitions only copy values: no contract. |
-| A control that works in every mode | `machine({ on: [...] })` instead of repeating it per state. |
-| New page | `routes.ts` → a view with `route` in `views.ts` → `ui.page(...)` in `hozu.config.ts` (`head`, and `entries` when the route has params). |
-
-Whenever the machine changes:
-- A transition that decides something (a guard, `navigate`, or a `fn` in its values) needs a contract; HZ016
-  prints each missing one ready to paste. Transitions that only copy values are reviewed through the lock.
-- States with `invoke` drop unhandled events by themselves. Other states must handle or `ignore` every event their
-  visible controls send; HZ005 prints the missing entries.
-
-## 3. Check (once, after all edits)
-```
-pnpm exec hozu check
-```
-Fix what it reports. When the behaviour change is intended, run `pnpm exec hozu check --update-lock`: HZ018 shows
-each changed transition as `was: … now: …`, and accepting it updates the lock.
-
-## 4. Verify (once, no server needed)
-- **Pages:** `pnpm exec hozu get / /items/i1` prints the status, title, alerts and visible text.
-- **Attributes and forms:** `--select button` (or `'[role=alert]'`, `a[href]`, `#id`) prints elements with their
-  attributes, e.g. `aria-pressed`; `--forms` lists each form's fields and buttons. Never start a server for this.
-- **Forms:** `pnpm exec hozu post / --field title=A --field priority=high --next /items` fills the form like a
-  browser (other fields keep their defaults). It follows the redirect, then runs the next steps in the same
-  process.
-- **Chaining:** chain what must share data, e.g. `--next 'POST / title=a'` (fields as `a=1&b=2`) or
-  `--next /items/i3`.
-- **A form with only a button:** `--button 'Clear done'`, or `--next 'POST / @Clear done'`. With one form per item,
-  `--field id=t2` picks the item's form.

package/skill/example/serve.ts

@@ -1,14 +0,0 @@
-import { createServer } from '@hozu/adapter-node'
-import { buildProject } from '@hozu/core/ir'
-import { compileStyles } from '@hozu/css'
-import project from './hozu.config.ts'
-import { createResolvers } from './server.ts'
-
-const port = Number(process.env.PORT ?? 3000)
-const build = buildProject(project, { sources: false })
-
-createServer({
-  build,
-  styles: await compileStyles(build),
-  resolvers: createResolvers(),
-}).listen(port, () => console.log(`Bookmarks on http://localhost:${port}`))

package/templates/app/serve.ts

@@ -1,14 +0,0 @@
-import { createServer } from '@hozu/adapter-node'
-import { buildProject } from '@hozu/core/ir'
-import { compileStyles } from '@hozu/css'
-import project from './hozu.config.ts'
-import { createResolvers } from './server.ts'
-
-const port = Number(process.env.PORT ?? 3000)
-const build = buildProject(project, { sources: false })
-
-createServer({
-  build,
-  styles: await compileStyles(build),
-  resolvers: createResolvers(),
-}).listen(port, () => console.log(`__NAME__ on http://localhost:${port}`))

package/templates/app/server.ts

@@ -1,6 +0,0 @@
-import { resolvers } from '@hozu/data'
-import project from './hozu.config.ts'
-
-export function createResolvers() {
-  return resolvers(project, () => [])
-}