@webjsdev/cli 0.10.52 → 0.10.54

package/templates/.claude/hooks/block-prose-punctuation.sh

@@ -6,16 +6,18 @@
 #
 #   1. U+2014 em-dash, anywhere.
 #   2. Space-hyphen-space " - " in PROSE contexts (comment lines, markdown
-#      lines, headings, blockquotes). Math expressions in code like
+#      lines, headings, blockquotes, a JSON "description" / "title" /
+#      "displayName" string value, and a column-0 YAML front-matter
+#      description: / title: / displayName: line). Math expressions in code like
 #      `Math.abs(a - b)` or `arr.length - 1` are NOT flagged.
-#   3. Space-semicolon-space " ; " in PROSE contexts. JS / CSS statement
-#      terminators (`;\n`) are NOT flagged.
+#   3. Space-semicolon-space " ; " in the same PROSE contexts as rule 2.
+#      JS / CSS statement terminators (`;\n`) are NOT flagged.
 #   4. Code-shaped left-hand side immediately followed by a colon and prose:
 #        - `<code>foo()</code>:` (markdown code-LHS in docs)
 #        - `<my-tag>:` (custom-element tag with hyphen)
 #        - Inline comment `// foo(): description`
 #
-# Why this exists: see AGENTS.md "Invariants", item 10. These patterns
+# Why this exists: see AGENTS.md "Invariants", item 11. These patterns
 # confuse AI agents that try to parse the prose as TypeScript / shorthand-
 # method / object-literal syntax, and trip humans reading API docs.
 #
@@ -46,8 +48,13 @@ if [ -z "$new_content" ]; then
   exit 0
 fi
 
+# Every match below reads from a here-string, never a pipe. `grep -q` exits on
+# the first match, which closes a pipe under `printf`, and with `set -o pipefail`
+# that SIGPIPE became the pipeline status, so the rule silently skipped on any
+# payload past the pipe buffer (measured: 0 of 8 blocks at 128 KB).
+
 # --- 1. U+2014 em-dash --------------------------------------------------
-if printf '%s' "$new_content" | grep -q $'\xe2\x80\x94'; then
+if grep -q $'\xe2\x80\x94' <<< "$new_content"; then
   cat >&2 <<'EOF'
 BLOCKED: em-dash (U+2014) detected in this tool call.
 
@@ -57,7 +64,7 @@ restructured sentence. Do NOT replace it with " - " or " ; " or a
 trailing colon on code: those are also banned. See rule 2 / 3 / 4
 below for the alternatives.
 
-Rule: AGENTS.md, Invariants section, item 10.
+Rule: AGENTS.md, Invariants section, item 11.
 Hook: .claude/hooks/block-prose-punctuation.sh.
 EOF
   exit 2
@@ -81,25 +88,42 @@ block_pause_hyphen=0
 # `*` (markdown bold-start would have a letter after, distinguishable),
 # followed by prose with `\w+ - \w+` pattern. Specifically: catch lines
 # like `// foo - bar`, ` * foo - bar`, `* foo - bar`.
-if printf '%s\n' "$new_content" | grep -qE '^[[:space:]]*(//|\*)[[:space:]].*[A-Za-z`)>][[:space:]]-[[:space:]][A-Za-z`(<]'; then
+if grep -qE '^[[:space:]]*(//|\*)[[:space:]].*[A-Za-z`)>][[:space:]]-[[:space:]][A-Za-z`(<]' <<< "$new_content"; then
   block_pause_hyphen=1
 fi
 
 # Markdown heading " - " pause: line starts with `#` followed by prose
 # and ` - ` pattern.
-if printf '%s\n' "$new_content" | grep -qE '^#{1,6}[[:space:]].*[A-Za-z`)>][[:space:]]-[[:space:]][A-Za-z`(<]'; then
+if grep -qE '^#{1,6}[[:space:]].*[A-Za-z`)>][[:space:]]-[[:space:]][A-Za-z`(<]' <<< "$new_content"; then
   block_pause_hyphen=1
 fi
 
 # Markdown blockquote " - " pause: line starts with `>` followed by prose
 # and ` - ` pattern. (Single `>` blockquote, not table.)
-if printf '%s\n' "$new_content" | grep -qE '^>[[:space:]].*[A-Za-z`)>][[:space:]]-[[:space:]][A-Za-z`(<]'; then
+if grep -qE '^>[[:space:]].*[A-Za-z`)>][[:space:]]-[[:space:]][A-Za-z`(<]' <<< "$new_content"; then
   block_pause_hyphen=1
 fi
 
 # HTML / markdown <p>, <li>, <td> body " - " pause: line contains a
 # closing HTML tag from a prose context, then prose-style ` - `.
-if printf '%s\n' "$new_content" | grep -qE '<(p|li|td|h[1-6]|strong|em|blockquote)[^>]*>[^<]*[A-Za-z`)>][[:space:]]-[[:space:]][A-Za-z`(<]'; then
+if grep -qE '<(p|li|td|h[1-6]|strong|em|blockquote)[^>]*>[^<]*[A-Za-z`)>][[:space:]]-[[:space:]][A-Za-z`(<]' <<< "$new_content"; then
+  block_pause_hyphen=1
+fi
+
+# JSON prose-value " - " pause: a string assignment whose KEY is one of the
+# three prose-bearing keys this project's JSON uses. Scoping to the key is what
+# keeps this off semver ranges, script commands, urls, paths and globs, every
+# one of which lives under a different key. Shape, not file path: the Bash
+# payload carries no file_path, so a heredoc writing a manifest is covered too.
+if grep -qE '^[[:space:]]*"(description|title|displayName)"[[:space:]]*:[[:space:]]*".*[A-Za-z`)>][[:space:]]-[[:space:]][A-Za-z`(<]' <<< "$new_content"; then
+  block_pause_hyphen=1
+fi
+
+# YAML front-matter " - " pause, same three keys. Anchored at column 0 with no
+# leading whitespace, which is what confines it to document front matter: every
+# nested YAML mapping is indented, including the workflow-input `description:`
+# values in .github/workflows/release.yml.
+if grep -qE '^(description|title|displayName):[[:space:]].*[A-Za-z`)>][[:space:]]-[[:space:]][A-Za-z`(<]' <<< "$new_content"; then
   block_pause_hyphen=1
 fi
 
@@ -118,13 +142,17 @@ restructured phrasing.
   Bad:  <li>Foo - bar.</li>
   Good: <li>Foo, with bar.</li>
 
+  Bad:  "description": "A library - for things"
+  Good: "description": "A library for things"
+
 Plain hyphens are still fine in compound words (`AI-first`), CLI
 flags (`--http2`), filenames, ranges, and math expressions in code
 (`arr.length - 1`, `Math.abs(a - b)`). The hook only flags the
 ` < word > - < word > ` pause-pattern in prose contexts (comments,
-markdown headings, blockquotes, HTML prose tags).
+markdown headings, blockquotes, HTML prose tags, and a JSON or
+front-matter description / title / displayName value).
 
-Rule: AGENTS.md, Invariants section, item 10.
+Rule: AGENTS.md, Invariants section, item 11.
 Hook: .claude/hooks/block-prose-punctuation.sh.
 EOF
   exit 2
@@ -134,19 +162,29 @@ fi
 # Same prose-context guard as #2.
 block_pause_semicolon=0
 
-if printf '%s\n' "$new_content" | grep -qE '^[[:space:]]*(//|\*)[[:space:]].*[A-Za-z`)][[:space:]];[[:space:]][A-Za-z`(]'; then
+if grep -qE '^[[:space:]]*(//|\*)[[:space:]].*[A-Za-z`)][[:space:]];[[:space:]][A-Za-z`(]' <<< "$new_content"; then
   block_pause_semicolon=1
 fi
 
-if printf '%s\n' "$new_content" | grep -qE '^#{1,6}[[:space:]].*[A-Za-z`)][[:space:]];[[:space:]][A-Za-z`(]'; then
+if grep -qE '^#{1,6}[[:space:]].*[A-Za-z`)][[:space:]];[[:space:]][A-Za-z`(]' <<< "$new_content"; then
   block_pause_semicolon=1
 fi
 
-if printf '%s\n' "$new_content" | grep -qE '^>[[:space:]].*[A-Za-z`)][[:space:]];[[:space:]][A-Za-z`(]'; then
+if grep -qE '^>[[:space:]].*[A-Za-z`)][[:space:]];[[:space:]][A-Za-z`(]' <<< "$new_content"; then
   block_pause_semicolon=1
 fi
 
-if printf '%s\n' "$new_content" | grep -qE '<(p|li|td|h[1-6]|strong|em|blockquote)[^>]*>[^<]*[A-Za-z`)][[:space:]];[[:space:]][A-Za-z`(]'; then
+if grep -qE '<(p|li|td|h[1-6]|strong|em|blockquote)[^>]*>[^<]*[A-Za-z`)][[:space:]];[[:space:]][A-Za-z`(]' <<< "$new_content"; then
+  block_pause_semicolon=1
+fi
+
+# JSON prose-value " ; " pause, same three keys as rule 2.
+if grep -qE '^[[:space:]]*"(description|title|displayName)"[[:space:]]*:[[:space:]]*".*[A-Za-z`)][[:space:]];[[:space:]][A-Za-z`(]' <<< "$new_content"; then
+  block_pause_semicolon=1
+fi
+
+# YAML front-matter " ; " pause, column-0 anchored like rule 2.
+if grep -qE '^(description|title|displayName):[[:space:]].*[A-Za-z`)][[:space:]];[[:space:]][A-Za-z`(]' <<< "$new_content"; then
   block_pause_semicolon=1
 fi
 
@@ -161,10 +199,14 @@ two sentences (period) or with a conjunction (", and", ", but", ", so").
   Good: // Forms work. Links work too.
   Good: // Forms work, and links work too.
 
+  Bad:  "description": "Forms work ; links work too."
+  Good: "description": "Forms work. Links work too."
+
 Semicolons stay fine inside code (JS statement terminators, CSS
-declarations) since those are not flagged.
+declarations) since those are not flagged. Only the space-surrounded
+form is banned, so an ordinary English semicolon is untouched.
 
-Rule: AGENTS.md, Invariants section, item 10.
+Rule: AGENTS.md, Invariants section, item 11.
 Hook: .claude/hooks/block-prose-punctuation.sh.
 EOF
   exit 2
@@ -175,7 +217,7 @@ fi
 # lowercase prose. The `)</code>:` shape is unambiguous: this is markdown,
 # not code, AND the inner code ends in `()` so the colon visually parses
 # as a return-type annotation.
-if printf '%s' "$new_content" | grep -qE '\)</code>:[[:space:]][a-z]'; then
+if grep -qE '\)</code>:[[:space:]][a-z]' <<< "$new_content"; then
   cat >&2 <<'EOF'
 BLOCKED: code-LHS colon-then-prose detected ("<code>foo()</code>: ...").
 
@@ -186,7 +228,7 @@ parses as a TypeScript return-type annotation. Rewrite verb-led.
   Good: <code>repeat()</code> is the keyed list directive
   Good: <code>startServer()</code> creates an HTTP(S) server
 
-Rule: AGENTS.md, Invariants section, item 10.
+Rule: AGENTS.md, Invariants section, item 11.
 Hook: .claude/hooks/block-prose-punctuation.sh.
 EOF
   exit 2
@@ -195,7 +237,7 @@ fi
 # --- 4b. Custom-element-tag <my-tag>: prose ------------------------------
 # HTML reserves hyphenated tag names for custom elements (W3C spec), so
 # `<x-y>:` is unambiguous prose, never JSX / TS / CSS.
-if printf '%s' "$new_content" | grep -qE '<[a-z][a-z0-9]*(-[a-z0-9]+)+([[:space:]][^>]*)?>:[[:space:]][a-z]'; then
+if grep -qE '<[a-z][a-z0-9]*(-[a-z0-9]+)+([[:space:]][^>]*)?>:[[:space:]][a-z]' <<< "$new_content"; then
   cat >&2 <<'EOF'
 BLOCKED: custom-element-tag colon-then-prose detected ("<my-tag>: ...").
 
@@ -206,7 +248,7 @@ webjs bans `<my-tag>: <prose>` in comments and docs. Rewrite verb-led.
   Bad:  // <ui-dialog-content>: the centered panel.
   Good: // <ui-dialog-content> is the centered panel.
 
-Rule: AGENTS.md, Invariants section, item 10.
+Rule: AGENTS.md, Invariants section, item 11.
 Hook: .claude/hooks/block-prose-punctuation.sh.
 EOF
   exit 2
@@ -216,7 +258,7 @@ fi
 # Match comment-line prefix (`//` or leading `*`) before `\w+(...): ` and
 # lowercase prose. Avoids TS return-type annotations because those never
 # appear inside comment lines.
-if printf '%s\n' "$new_content" | grep -qE '^[[:space:]]*(//|\*)[[:space:]][^(]*[A-Za-z_][A-Za-z0-9_]*\([^)]*\):[[:space:]][a-z]'; then
+if grep -qE '^[[:space:]]*(//|\*)[[:space:]][^(]*[A-Za-z_][A-Za-z0-9_]*\([^)]*\):[[:space:]][a-z]' <<< "$new_content"; then
   cat >&2 <<'EOF'
 BLOCKED: comment-line code-LHS colon-then-prose detected ("// foo(): ...").
 
@@ -227,7 +269,7 @@ webjs bans `xyz(): <prose>` inside comments and JSDoc. Rewrite verb-led.
   Bad:  // closest(): null if the click wasn't inside a frame
   Good: // closest() returns null when the click wasn't inside a frame
 
-Rule: AGENTS.md, Invariants section, item 10.
+Rule: AGENTS.md, Invariants section, item 11.
 Hook: .claude/hooks/block-prose-punctuation.sh.
 EOF
   exit 2

package/templates/gallery/app/icon.ts

@@ -1,9 +1,14 @@
-// app/icon.ts serves /icon (the dynamic favicon). The default export is a
+// app/icon.ts serves /icon (a dynamic favicon). The default export is a
 // (possibly async) server function; returning a Response lets you set the exact
-// content type, so an inline SVG needs no asset file. For a favicon that never
-// changes, put a static file in public/ instead (e.g. public/favicon.ico) and
-// delete this route. Generate it dynamically (per-theme, per-tenant) when the
-// mark must be computed at request time.
+// content type, so an inline SVG needs no asset file. Generate it dynamically
+// (per-theme, per-tenant) when the mark must be computed at request time.
+//
+// This is the DEMO of that surface, not the gallery's own favicon. A metadata
+// route is not auto-linked: the framework emits `<link rel="icon">` only from
+// metadata.icons, so the gallery declares the static WebJs brand mark from
+// public/ there (see app/layout.ts) and this route stays browsable at /icon.
+// For a favicon that never changes, that static path is the one to copy; drop
+// this route when your app has no request-time mark to compute.
 export default function Icon() {
   const svg = `<svg xmlns="http://www.w3.org/2000/svg" width="32" height="32" viewBox="0 0 32 32">
     <rect width="32" height="32" rx="7" fill="#1e2226"/>

package/templates/gallery/modules/directives/components/directive-demo.ts

@@ -31,7 +31,10 @@ export class DirectiveDemo extends WebComponent {
   // A controlled value (for `live`) and a key (for `keyed`).
   private text = signal('type here');
   private variant = signal(0);
-  // A handle to the input node, attached by `ref` in the browser.
+  // A handle to the input node, attached by `ref` in the browser. A ref rather
+  // than a `querySelector` because the template already owns the node, so the
+  // handle flows out of `render()` instead of being re-found by a selector that
+  // could match someone else's markup (or nothing at all after a rename).
   private inputRef = createRef<HTMLInputElement>();
   // Created ONCE (not per render), so `until` keeps the resolved value across
   // re-renders instead of flashing back to the fallback each time.

package/templates/gallery/modules/gallery/components/gallery-nav.ts

@@ -6,6 +6,11 @@
 // active item from location.pathname, so the highlight follows soft-nav. SSR is
 // still correct: `render()` reads the `current` prop (the pathname the layout
 // passes) for the first paint, and the client takes over from location after.
+// The document LISTENER below is the legitimate case, not a reach across the
+// app: the router has no element to dispatch from, and the handler reads only
+// location.pathname and writes only this module's own signal, so it queries
+// nothing outside itself. Querying the document for another file's markup is
+// the shape to avoid.
 import { WebComponent, prop, html, signal } from '@webjsdev/core';
 import { FEATURE_GROUPS } from '#modules/gallery/nav.ts';
 

package/templates/gallery/modules/gallery/nav.ts

@@ -63,7 +63,7 @@ export const FEATURE_GROUPS: NavGroup[] = [
     items: [
       { href: '/features/caching', title: 'Caching', blurb: 'export const revalidate caches the page HTML per URL, with the safety rule for when a shared cache is allowed.' },
       { href: '/features/env', title: 'Env vars', blurb: 'The server-only vs WEBJS_PUBLIC_ boundary, read during SSR so secrets never reach the browser.' },
-      { href: '/features/rate-limit', title: 'Rate limiting', blurb: 'The rateLimit() middleware scoped to one endpoint, returning a 429 with Retry-After past the window.' },
+      { href: '/features/rate-limit', title: 'Rate limiting', blurb: 'The rateLimit() middleware scoped to one endpoint, returning a 429 with Retry-After once the interval resets.' },
       { href: '/features/file-storage', title: 'File storage', blurb: 'A no-JS multipart upload streamed into the FileStore, then served back through a streaming route.' },
       { href: '/features/service-worker', title: 'Service worker', blurb: 'The opt-in offline enhancement, registered from a browser-only lifecycle hook (never a page or layout).' },
     ],
@@ -75,5 +75,14 @@ export const EXAMPLES: NavItem[] = [
   { href: '/examples/todo', title: 'Optimistic todo', blurb: 'A whole app composing several features: the declarative optimistic() list API, progressive-enhancement forms, accessible labels, the modules split, and SQLite.' },
 ];
 
-/** Flattened single-feature list (for the home card grid). */
-export const FEATURES: NavItem[] = FEATURE_GROUPS.flatMap((g) => g.items);
+/**
+ * Flattened single-feature list (for the home card grid).
+ *
+ * This is a function, not a `const` initialised by a top-level `.flatMap()`
+ * call. A top-level call is a module side effect, so the const form pinned
+ * every page importing this module into the browser bundle, even a home page
+ * with no client behaviour at all. Call it inside the render function.
+ */
+export function featureList(): NavItem[] {
+  return FEATURE_GROUPS.flatMap((g) => g.items);
+}

package/templates/gallery/modules/todo/actions/submit-todo.server.ts

@@ -21,6 +21,13 @@ import { deleteTodo } from './delete-todo.server.ts';
 // control's visible label), and a bound submitter cannot carry its own
 // `name`/`value`, which is exactly the channel `name="intent"` uses below.
 //
+// Third thing to know: no `formaction` url is emitted, because the identity
+// travels in the body instead. So the submission targets whatever the FORM
+// targets, and a form declaring `action="/x"` sends its buttons there. The
+// action still runs when `/x` is a PAGE route; against a `route.ts` or another
+// origin the identity is ignored and nothing runs, which the dev-time client
+// guard reports at submit time.
+//
 // With JS the component intercepts the submit and calls the underlying action
 // directly for the optimistic path, so this runs only with JS off.
 export async function submitTodo(formData: FormData) {

package/templates/test/hello/e2e/hello.test.ts

@@ -20,6 +20,13 @@ import { createServer } from 'node:net';
 // minimal structural types keep the file typed in the meantime; swap them for
 // the real imports once puppeteer-core is in package.json. Reaching for `any`
 // here would silently un-type every call below.
+//
+// They also stay in force when the package IS present, which is the case a
+// generated app usually hits, since @web/test-runner pulls puppeteer-core in
+// transitively. The real Page / Browser are far richer than these, so letting
+// them flow in would fail against the narrow shapes here for the goto return
+// type and the event-handler signature. The single import below is the one
+// boundary where that is resolved, and it is the only suppressed line.
 type Page = {
   // goto resolves an HTTPResponse this file never reads, and modelling that
   // type would mean re-declaring puppeteer's. Returning void is the honest
@@ -30,6 +37,10 @@ type Page = {
   removeAllListeners(event: string): void;
 };
 type Browser = { newPage(): Promise<Page>; close(): Promise<void> };
+// The module's own default export, narrowed to the one call this file makes.
+type Puppeteer = {
+  launch(opts: { executablePath?: string; headless?: boolean; args?: string[] }): Promise<Browser>;
+};
 
 let browser: Browser, page: Page, serverProcess: ChildProcess, baseUrl: string;
 
@@ -46,9 +57,23 @@ function freePort(): Promise<number> {
 }
 
 before(async () => {
-  let puppeteer;
+  let puppeteer: Puppeteer | undefined;
+  // The next line is where the optional dependency enters, and what it reports
+  // depends on whether puppeteer-core is installed: an unresolved specifier
+  // when it is absent, a type mismatch against the structural shapes above
+  // when it is present. Suppressing it keeps the rest of the file checked
+  // against those shapes either way.
+  //
+  // It is deliberately ts-ignore rather than the expect-error directive, whose
+  // name is spelled out here rather than written, because a comment line
+  // starting with that token IS a live directive to tsc even inside prose. The
+  // expect-error form is wrong on its own merits too: it errors when there is
+  // nothing to suppress, so it would break whenever the package resolves
+  // cleanly.
+  // @ts-ignore
   try { puppeteer = (await import('puppeteer-core')).default; }
   catch { console.log('# Skipping: puppeteer-core not installed'); return; }
+  if (!puppeteer) return;
 
   const port = await freePort();
   baseUrl = `http://localhost:${port}`;

package/templates/.cursor/hooks/nudge-uncommitted.sh

@@ -1,38 +0,0 @@
-#!/bin/bash
-#
-# Cursor afterFileEdit hook.
-#
-# Counterpart of .claude/hooks/nudge-uncommitted.sh. After each
-# file edit, counts uncommitted changes in the working tree.
-# When the count crosses a threshold (default 4, override with
-# WEBJS_COMMIT_NUDGE_THRESHOLD), injects a reminder via the
-# top-level additional_context field (snake_case, unlike Claude
-# Code's nested hookSpecificOutput.additionalContext).
-#
-# Soft nudge. Exit 0 always. Skipped on main/master and outside
-# a git work tree.
-
-set -e
-
-THRESHOLD="${WEBJS_COMMIT_NUDGE_THRESHOLD:-4}"
-
-if ! git rev-parse --is-inside-work-tree >/dev/null 2>&1; then
-  exit 0
-fi
-
-BRANCH=$(git symbolic-ref --short HEAD 2>/dev/null || echo "")
-if [ "$BRANCH" = "main" ] || [ "$BRANCH" = "master" ]; then
-  exit 0
-fi
-
-cat /dev/stdin >/dev/null 2>&1 || true
-
-CHANGED=$(git status --porcelain 2>/dev/null | wc -l | tr -d ' ')
-
-if [ -z "$CHANGED" ] || [ "$CHANGED" -lt "$THRESHOLD" ]; then
-  exit 0
-fi
-
-REASON="You have ${CHANGED} uncommitted changes on '${BRANCH}'. The webjs convention is small, focused commits per logical unit (one feature, one fix, one rename, one doc rewrite). Before continuing with more edits, group the current changes into a meaningful commit. See AGENTS.md \"Git workflow\" for the rule and the rationale. To raise the threshold for this hook in long-running tasks, set WEBJS_COMMIT_NUDGE_THRESHOLD."
-
-jq -n --arg ctx "$REASON" '{ additional_context: $ctx }'

package/templates/.cursor/hooks.json

@@ -1,8 +0,0 @@
-{
-  "version": 1,
-  "hooks": {
-    "afterFileEdit": [
-      { "command": ".cursor/hooks/nudge-uncommitted.sh" }
-    ]
-  }
-}

package/templates/.cursorrules

@@ -1,21 +0,0 @@
-# WebJs app rules (Cursor)
-
-Cursor reads `AGENTS.md` natively. This file points you at it and the agent
-skill, and carries the commit rule.
-
-- **Read `AGENTS.md` first, then `.agents/skills/webjs/SKILL.md`** (the guide to
-  building a WebJs app; it routes to focused references under
-  `.agents/skills/webjs/references/`). These are required context, not optional
-  reading: WebJs is not React, Next, or Lit, so gather this context before you
-  write code.
-- **Study the shipped examples, then clear them and build.** The scaffold ships
-  a browsable showcase to learn the real idioms from (a full-stack app ships a
-  UI feature gallery, the api template ships a backend-features showcase). Read
-  the parts that match your task, run `npm run gallery:clear` to shed the
-  showcase and reset to a clean base, then grow the app in place: add routes
-  under `app/`, features under `modules/<feature>/`, and keep server-only code
-  behind `.server.ts`. `AGENTS.md` carries the full template-specific playbook.
-- **Use the wired-up database (Drizzle)** for persistence. Never a JSON file, an
-  in-memory array, or localStorage.
-- **Commit per logical unit** as soon as it is complete, and never commit to
-  `main`.

package/templates/.gemini/hooks/nudge-uncommitted.sh

@@ -1,42 +0,0 @@
-#!/bin/bash
-#
-# Gemini CLI AfterTool hook.
-#
-# Counterpart of .claude/hooks/nudge-uncommitted.sh. After each
-# write_file or replace, counts uncommitted changes in the working
-# tree. When the count crosses a threshold (default 4, override
-# with the WEBJS_COMMIT_NUDGE_THRESHOLD env var), injects a
-# reminder via hookSpecificOutput.additionalContext (same shape
-# as Claude Code).
-#
-# Soft nudge. Does NOT block the edit (exit 0). Skipped on
-# main/master and outside a git work tree.
-
-set -e
-
-THRESHOLD="${WEBJS_COMMIT_NUDGE_THRESHOLD:-4}"
-
-if ! git rev-parse --is-inside-work-tree >/dev/null 2>&1; then
-  exit 0
-fi
-
-BRANCH=$(git symbolic-ref --short HEAD 2>/dev/null || echo "")
-if [ "$BRANCH" = "main" ] || [ "$BRANCH" = "master" ]; then
-  exit 0
-fi
-
-cat /dev/stdin >/dev/null 2>&1 || true
-
-CHANGED=$(git status --porcelain 2>/dev/null | wc -l | tr -d ' ')
-
-if [ -z "$CHANGED" ] || [ "$CHANGED" -lt "$THRESHOLD" ]; then
-  exit 0
-fi
-
-REASON="You have ${CHANGED} uncommitted changes on '${BRANCH}'. The webjs convention is small, focused commits per logical unit (one feature, one fix, one rename, one doc rewrite). Before continuing with more edits, group the current changes into a meaningful commit. See AGENTS.md \"Git workflow\" for the rule and the rationale. To raise the threshold for this hook in long-running tasks, set WEBJS_COMMIT_NUDGE_THRESHOLD."
-
-jq -n --arg ctx "$REASON" '{
-  hookSpecificOutput: {
-    additionalContext: $ctx
-  }
-}'

package/templates/.gemini/settings.json

@@ -1,15 +0,0 @@
-{
-  "hooks": {
-    "AfterTool": [
-      {
-        "matcher": "write_file|replace",
-        "hooks": [
-          {
-            "type": "command",
-            "command": ".gemini/hooks/nudge-uncommitted.sh"
-          }
-        ]
-      }
-    ]
-  }
-}

package/templates/.github/copilot-instructions.md

@@ -1,9 +0,0 @@
-# Copilot instructions
-
-This is a thin bridge to the single source. GitHub Copilot always reads this
-file; in VS Code it reads `AGENTS.md` directly only when `chat.useAgentsMdFile`
-is enabled, so this bridge keeps Copilot pointed at the instructions regardless.
-
-The instructions for this app live in `AGENTS.md` (the cross-agent source) and
-the skill at `.agents/skills/webjs/SKILL.md`. Read `AGENTS.md` first, then the
-skill (it routes to focused references on demand).

package/templates/.opencode/plugins/nudge-uncommitted.ts

@@ -1,62 +0,0 @@
-/**
- * OpenCode commit-frequency nudge plugin.
- *
- * Counterpart of the Claude Code, Gemini CLI, and Cursor hooks in
- * `.claude/hooks/`, `.gemini/hooks/`, and `.cursor/hooks/`. After
- * each edit/write tool call, counts uncommitted changes in the
- * working tree. When the count crosses a threshold (default 4,
- * override with the WEBJS_COMMIT_NUDGE_THRESHOLD env var), appends
- * a reminder to the tool result so the agent sees it on the next
- * turn.
- *
- * Soft nudge by design. Does NOT block the edit. The goal is to
- * keep the agent honest about the "commit per logical unit" rule,
- * not to interrupt valid work.
- *
- * Skipped on main/master (different guard rules cover that) and
- * outside a git work tree.
- *
- * Auto-discovered by OpenCode at startup. No opencode.json entry
- * needed. Lives in .opencode/plugins/ at the project root.
- *
- * Docs: https://opencode.ai/docs/plugins/
- */
-import type { Plugin } from "@opencode-ai/plugin";
-
-export const NudgeUncommitted: Plugin = async ({ $ }) => {
-  const THRESHOLD = Number(process.env.WEBJS_COMMIT_NUDGE_THRESHOLD ?? 4);
-
-  return {
-    "tool.execute.after": async (input, output) => {
-      if (input.tool !== "edit" && input.tool !== "write") return;
-
-      let branch = "";
-      try {
-        branch = (await $`git symbolic-ref --short HEAD`.text()).trim();
-      } catch {
-        return; // not in a git work tree
-      }
-      if (branch === "main" || branch === "master") return;
-
-      let changed = 0;
-      try {
-        const out = (await $`git status --porcelain`.text()).trim();
-        changed = out === "" ? 0 : out.split("\n").length;
-      } catch {
-        return;
-      }
-      if (changed < THRESHOLD) return;
-
-      const reason =
-        `[webjs] You have ${changed} uncommitted changes on '${branch}'. ` +
-        `The webjs convention is small, focused commits per logical unit ` +
-        `(one feature, one fix, one rename, one doc rewrite). Before ` +
-        `continuing with more edits, group the current changes into a ` +
-        `meaningful commit. See AGENTS.md "Git workflow" for the rule ` +
-        `and the rationale. To raise the threshold for this hook in ` +
-        `long-running tasks, set WEBJS_COMMIT_NUDGE_THRESHOLD.`;
-
-      output.output = output.output ? `${output.output}\n\n${reason}` : reason;
-    },
-  };
-};

package/templates/GEMINI.md

@@ -1,11 +0,0 @@
-# GEMINI.md
-
-Gemini CLI reads `GEMINI.md`, not `AGENTS.md`, by default, so this file is a
-thin bridge to the single source.
-
-The instructions for this app live in `AGENTS.md` (the cross-agent source) and
-the skill at `.agents/skills/webjs/SKILL.md`. Read `AGENTS.md` first, then the
-skill (it routes to focused references on demand).
-
-To have Gemini read `AGENTS.md` directly instead of this bridge, add it to
-`context.fileName` in `.gemini/settings.json`.