@christianirack/create-brainllm 0.1.0 → 0.4.0

package/README.md

@@ -10,18 +10,31 @@ npm run dev
 
 Runs the same pinned BRAINLLM compiler and installs the generated app dependencies. Pass `-- --no-install` to skip dependency installation.
 
-<p align="center"><img src="https://raw.githubusercontent.com/chrisifm/BRAINLLM/main/docs/site/assets/logo.png" width="88" alt="BRAINLLM brain mark"></p>
+<p align="center"><img src="https://raw.githubusercontent.com/chrisifm/BRAINLLM/v0.4.0/docs/site/assets/logo.png" width="88" alt="BRAINLLM brain mark"></p>
 
 # BRAINLLM
 
-### The web compiler for LLMs.
+### 🦀 The web compiler for LLMs, built in Rust. Blazing fast.
 
 **Your LLM owns the frontend. Give it a language built for the job.**
 
-![BRAINLLM — The web compiler for LLMs](https://github.com/chrisifm/BRAINLLM/raw/main/docs/site/assets/cover.png)
+> **Written in Rust, from parser to minifier.** One native binary, no toolchain to install. Warm production builds
+> in **~34 ms**, about **4.5× faster than React + Vite** on [our open benchmark](#show-me-the-numbers).
 
-BRAINLLM gives coding agents a compact language, a single specification and a compiler that tells them how to fix
-mistakes. The model builds the frontend. You set the direction, inspect the result and decide what ships.
+<p align="center">
+  <img src="https://img.shields.io/badge/built%20with-Rust-dea584?logo=rust&logoColor=white" alt="Built with Rust">
+  <a href="https://chrisifm.github.io/BRAINLLM/"><img src="https://img.shields.io/badge/website-chrisifm.github.io%2FBRAINLLM-0071e3" alt="Website"></a>
+  <a href="https://www.npmjs.com/package/@christianirack/brainllm"><img src="https://img.shields.io/npm/v/@christianirack/brainllm?color=cb3837" alt="npm version"></a>
+  <a href="https://github.com/chrisifm/BRAINLLM/blob/v0.4.0/LICENSE"><img src="https://img.shields.io/github/license/chrisifm/BRAINLLM" alt="License"></a>
+</p>
+
+<p align="center"><a href="https://chrisifm.github.io/BRAINLLM/"><img src="https://raw.githubusercontent.com/chrisifm/BRAINLLM/v0.4.0/docs/site/assets/cover.png" alt="BRAINLLM — The web compiler for LLMs. Open the website: chrisifm.github.io/BRAINLLM"></a></p>
+
+<p align="center"><b>🌐 <a href="https://chrisifm.github.io/BRAINLLM/">chrisifm.github.io/BRAINLLM</a></b></p>
+
+BRAINLLM gives coding agents a compact language, a single specification and a native compiler written in Rust that
+tells them how to fix mistakes. The model builds the frontend. You set the direction, inspect the result and decide
+what ships.
 
 `.brain` components compile to direct-DOM JavaScript and scoped CSS. The Rust toolchain handles parsing, checking,
 code generation, bundling and minification. The agent can operate it through the CLI or MCP.
@@ -30,14 +43,14 @@ code generation, bundling and minification. The agent can operate it through the
 a confusing diagnostic. The agent can turn that finding into a tested proposal and, when configured, push it
 automatically to a review branch. Maintainers decide what merges.
 
-**[Visit the site](https://chrisifm.github.io/BRAINLLM/)** · **[Build your first app](#give-your-agent-its-first-task)** · **[Read the spec](https://github.com/chrisifm/BRAINLLM/blob/main/SPEC.md)** · **[See the benchmarks](#show-me-the-numbers)** · **[Contribute](#build-the-tool-your-agent-needs)**
+**[Visit the site](https://chrisifm.github.io/BRAINLLM/)** · **[Build your first app](#give-your-agent-its-first-task)** · **[Read the spec](https://github.com/chrisifm/BRAINLLM/blob/v0.4.0/SPEC.md)** · **[See the benchmarks](#show-me-the-numbers)** · **[Contribute](#build-the-tool-your-agent-needs)**
 
 ## A frontend language with the model in mind
 
 An agent writing your app needs a contract it can follow and feedback it can act on. BRAINLLM makes that loop
 explicit: read the spec, generate a component, check it, apply the fix, test the result.
 
-![An agent reads the BRAINLLM contract, writes a component and uses compiler feedback to validate the app](https://github.com/chrisifm/BRAINLLM/raw/main/docs/site/assets/agent-loop.png)
+![An agent reads the BRAINLLM contract, writes a component and uses compiler feedback to validate the app](https://github.com/chrisifm/BRAINLLM/raw/v0.4.0/docs/site/assets/agent-loop.png)
 
 - **Less to guess.** `brain spec` defines the supported language. One component format, a prescribed project
   structure and generators keep the model working inside a known contract.
@@ -56,6 +69,7 @@ agent has to reconstruct while preserving code that a developer can read and rev
 | Capability | What it does for the app-building loop |
 |---|---|
 | A served language contract | `brain spec` gives the model the implemented syntax and conventions |
+| Task playbooks | `brain guide <topic>` (also MCP `brain_guide`): steps, checks, common mistakes and an example per task (views, data, forms, server, SEO, accessibility, WebMCP, tests, i18n, performance) |
 | Components and reactive state | `.brain` files combine markup, BrainScript and scoped styles; `sig`, `drv` and `fx` express updates |
 | Forms and data | Form validation, HTTP resources and server contracts give common app behavior a documented path |
 | Routes and layouts | Views, layouts, loaders and guards put navigation and access checks into the project structure |
@@ -64,7 +78,7 @@ agent has to reconstruct while preserving code that a developer can read and rev
 | Verification and delivery | Tests, `brain doctor` and the production build make validation part of the workflow |
 | Tested compiler improvements | Isolated proposals, validation gates and optional review-branch pushes let the agent contribute fixes |
 
-Use [SPEC.md](https://github.com/chrisifm/BRAINLLM/blob/main/SPEC.md), the served `brain spec` and [EVOLUTION.md](https://github.com/chrisifm/BRAINLLM/blob/main/docs/EVOLUTION.md) for exact contracts and limits.
+Use [SPEC.md](https://github.com/chrisifm/BRAINLLM/blob/v0.4.0/SPEC.md), the served `brain spec` and [EVOLUTION.md](https://github.com/chrisifm/BRAINLLM/blob/v0.4.0/docs/EVOLUTION.md) for exact contracts and limits.
 
 ## Where it fits in the frontend stack
 
@@ -123,8 +137,8 @@ stack. Builds run serially on a shared machine. Variance matters: inspect the ra
 The output strategies differ (including SSR, client rendering and an Astro React island); this comparison measures
 production build duration for this fixture, not universal app performance or feature equivalence.
 
-Read the [expanded method, versions, payloads and results](https://github.com/chrisifm/BRAINLLM/blob/main/bench/build/expanded.md). The original three-stack
-[historical results](https://github.com/chrisifm/BRAINLLM/blob/main/bench/build/results/summary.md) remain available unchanged. Use `bench/build/expanded.mjs`
+Read the [expanded method, versions, payloads and results](https://github.com/chrisifm/BRAINLLM/blob/v0.4.0/bench/build/expanded.md). The original three-stack
+[historical results](https://github.com/chrisifm/BRAINLLM/blob/v0.4.0/bench/build/results/summary.md) remain available unchanged. Use `bench/build/expanded.mjs`
 with the documented frozen binary and scratch-directory setup to reproduce this seven-stack run.
 
 **Ask your agent to challenge the result:**
@@ -147,11 +161,11 @@ numbers support it. Do not upload results or publish anything automatically.
 Clean up only the temporary resources this run created.
 ```
 
-A separate [cache-key microbenchmark](https://github.com/chrisifm/BRAINLLM/blob/main/bench/build/results/compiler-cache-lookup.json) measured **43.3× faster key
+A separate [cache-key microbenchmark](https://github.com/chrisifm/BRAINLLM/blob/v0.4.0/bench/build/results/compiler-cache-lookup.json) measured **43.3× faster key
 lookup** after removing an unnecessary parse: 10,000 lookups of a 1,050-byte input. That number measures this
 internal operation only. It is not a full-build speedup or a webpack comparison.
 
-The [benchmark report](https://github.com/chrisifm/BRAINLLM/blob/main/bench/REPORT.md) also tracks agent-generated apps, browser behavior, payload size and
+The [benchmark report](https://github.com/chrisifm/BRAINLLM/blob/v0.4.0/bench/REPORT.md) also tracks agent-generated apps, browser behavior, payload size and
 failure recovery. Historical LLM results describe their frozen model/spec/compiler runs; they do not guarantee
 that a new prompt or compiler revision will pass. This project is open to developers and researchers who want to
 investigate how language design and compiler feedback affect agent behavior. Bring a hypothesis and a reproducer.
@@ -175,7 +189,7 @@ what each result actually establishes.
 
 Browser tooling and the preview supervisor currently require macOS or Linux. Screenshot baselines need stable browser,
 font and app-data inputs. Runtime mount-time/heap budgets remain planned; the compiler rejects those settings rather
-than pretending to measure them. See the [implemented contract](https://github.com/chrisifm/BRAINLLM/blob/main/SPEC.md) and [tool internals](https://github.com/chrisifm/BRAINLLM/blob/main/docs/INTERNALS.md).
+than pretending to measure them. See the [implemented contract](https://github.com/chrisifm/BRAINLLM/blob/v0.4.0/SPEC.md) and [tool internals](https://github.com/chrisifm/BRAINLLM/blob/v0.4.0/docs/INTERNALS.md).
 
 ## Give your agent its first task
 
@@ -259,11 +273,21 @@ With a source installation, use the installed `brain` commands directly. That wo
 Cargo installs `brain` into its bin directory; make sure that directory is on your `PATH`. Stop the dev server with
 Ctrl+C. From the app directory, run `brain doctor` to validate it and `brain build` to create production output.
 For an MCP client in an npm-created app, use command `npx` with arguments `["brain", "mcp"]` and the app as its
-working directory. With a source installation, use the installed `brain` executable and argument `mcp`. Follow that client's configuration instructions; merely copying a prompt does not grant tool access.
+working directory. New apps include `.mcp.json` for Claude Code and `.cursor/mcp.json` for Cursor, plus
+`CLAUDE.md` importing `AGENTS.md`. Install the pinned dependency, restart the client and verify `brain_spec` appears.
+Client trust/approval settings still apply; configuration alone does not prove a live connection.
+
+For an existing app, run `brain agent setup` to merge local registrations, or
+`claude mcp add --scope project brain -- npx --no-install brain mcp` for Claude Code alone.
+`brain agent setup --hooks` also installs optional Claude Code edit-time check feedback, preserving existing hooks.
+The hook checks the app after `.brain`, `.jsbrain` and `.cssbrain` edits; it does not run tests or download packages.
+Use `brain mcp --profile minimal` for six core tools, or `--profile backend` for resource/job contracts and generators.
+With a source installation, change the registration to command `brain` and arguments `["mcp"]`.
+Other clients use their own MCP settings. See [the backend/agent contract](https://github.com/chrisifm/BRAINLLM/blob/v0.4.0/docs/BACKEND.md).
 
 </details>
 
-For an existing frontend, start with the [migration workflow](https://github.com/chrisifm/BRAINLLM/blob/main/docs/MIGRATION.md). Its read-only planner recognizes
+For an existing frontend, start with the [migration workflow](https://github.com/chrisifm/BRAINLLM/blob/v0.4.0/docs/MIGRATION.md). Its read-only planner recognizes
 React, Angular, Vue, Svelte, Next and Nuxt projects. Port one tested route or component at a time, preserve its
 behavior and keep a rollback path. It is an incremental workflow, not an automatic transpiler.
 
@@ -281,7 +305,7 @@ behavior and keep a rollback path. It is an incremental workflow, not an automat
 ```
 
 The compiler handles signal reads and writes. Derived values update when their inputs change. Styles can live in
-the same file and are scoped to the component. The [served spec](https://github.com/chrisifm/BRAINLLM/blob/main/SPEC.md) defines the supported syntax.
+the same file and are scoped to the component. The [served spec](https://github.com/chrisifm/BRAINLLM/blob/v0.4.0/SPEC.md) defines the supported syntax.
 
 ## Readable intent. Lean browser output.
 
@@ -289,7 +313,7 @@ An internal function named `back_to_home` can become a short identifier in produ
 on scope and the other names in the module. Keep meaningful names where the agent reasons about the code; let the
 compiler shorten eligible bindings in what the browser receives.
 
-This example comes from the [minifier's scope regression tests](https://github.com/chrisifm/BRAINLLM/blob/main/crates/brain-min/src/mangle.rs):
+This example comes from the [minifier's scope regression tests](https://github.com/chrisifm/BRAINLLM/blob/v0.4.0/crates/brain-min/src/mangle.rs):
 
 ```js
 // Before
@@ -324,29 +348,29 @@ BRAINLLM includes protections at several stages of the app loop:
   tests and diagnostics; failed stages remain visible to the agent.
 
 These are implemented mechanisms, not a promise to catch every bug or repair every failure. The agent still needs
-to test the user's workflow. See [runtime behavior in the spec](https://github.com/chrisifm/BRAINLLM/blob/main/SPEC.md#errors-at-runtime),
-[component boundaries](https://github.com/chrisifm/BRAINLLM/blob/main/runtime/brain-guard.js) and [compiler diagnostics](https://github.com/chrisifm/BRAINLLM/blob/main/crates/brain-check/).
+to test the user's workflow. See [runtime behavior in the spec](https://github.com/chrisifm/BRAINLLM/blob/v0.4.0/SPEC.md#errors-at-runtime),
+[component boundaries](https://github.com/chrisifm/BRAINLLM/blob/v0.4.0/runtime/brain-guard.js) and [compiler diagnostics](https://github.com/chrisifm/BRAINLLM/blob/v0.4.0/crates/brain-check/).
 
 ## Build the tool your agent needs
 
 **Build with it. Let your LLM make it better.**
 
-![An LLM turns an observed problem into an isolated fix, runs validation and submits a contribution for human review](https://github.com/chrisifm/BRAINLLM/raw/main/docs/site/assets/improvement-loop.png)
+![An LLM turns an observed problem into an isolated fix, runs validation and submits a contribution for human review](https://github.com/chrisifm/BRAINLLM/raw/v0.4.0/docs/site/assets/improvement-loop.png)
 
 A failed compilation can become a regression test. A repeated slow step can become a benchmark. A fix made while
 building your app can become a contribution that helps the next developer and their agent.
 
 Found a compiler gap while building an app? Turn the smallest reproducible case into a regression test and a
-contribution. BRAINLLM includes an [evolution workflow](https://github.com/chrisifm/BRAINLLM/blob/main/docs/EVOLUTION.md) for isolated proposals, validated compiler
+contribution. BRAINLLM includes an [evolution workflow](https://github.com/chrisifm/BRAINLLM/blob/v0.4.0/docs/EVOLUTION.md) for isolated proposals, validated compiler
 binaries and reversible activation. Configured automatic pushes go to review branches; merges require the
 principal author's review. This is an explicit development workflow, not a compiler that silently rewrites itself
-on every build. Read the [agent improvement playbook](https://github.com/chrisifm/BRAINLLM/blob/main/docs/AGENT-IDEAS.md) for an opt-in prompt and concrete ideas
+on every build. Read the [agent improvement playbook](https://github.com/chrisifm/BRAINLLM/blob/v0.4.0/docs/AGENT-IDEAS.md) for an opt-in prompt and concrete ideas
 to investigate.
 
 Human developers and LLM contributors are welcome. Useful first contributions include reproducible compiler bugs,
 behavior-preserving migration examples, clearer diagnostics and performance improvements with before/after data.
 
-1. Read [CONTRIBUTING.md](https://github.com/chrisifm/BRAINLLM/blob/main/CONTRIBUTING.md) and the relevant [internals](https://github.com/chrisifm/BRAINLLM/blob/main/docs/INTERNALS.md).
+1. Read [CONTRIBUTING.md](https://github.com/chrisifm/BRAINLLM/blob/v0.4.0/CONTRIBUTING.md) and the relevant [internals](https://github.com/chrisifm/BRAINLLM/blob/v0.4.0/docs/INTERNALS.md).
 2. Make a focused change with a regression test and synthetic sample data.
 3. Run `bash scripts/verify.sh`. It builds the CLI and checks Rust, runtime, tooling, diagnostic fixtures, privacy
    and repository language. Verification also requires ripgrep.
@@ -357,7 +381,7 @@ Never include app secrets, private source or customer data in a contribution.
 
 ## Know what you are adopting
 
-BRAINLLM is **0.1.0**. Start with a small app or an isolated route and test the behavior you need. Features marked
+BRAINLLM is **0.4.0** (see [CHANGELOG.md](https://github.com/chrisifm/BRAINLLM/blob/v0.4.0/CHANGELOG.md)). Start with a small app or an isolated route and test the behavior you need. Features marked
 as planned in the source specification are not a supported promise; `brain spec` serves the implemented contract.
 Third-party React, Angular and Vue components do not become BRAINLLM components automatically. Benchmark wins in
 build time do not imply that every runtime workload is faster.
@@ -366,15 +390,15 @@ build time do not imply that every runtime workload is faster.
 
 | You want to… | Start here |
 |---|---|
-| Give an agent the project context | [llms.txt](https://github.com/chrisifm/BRAINLLM/blob/main/llms.txt) |
-| Write an app | [SPEC.md](https://github.com/chrisifm/BRAINLLM/blob/main/SPEC.md) and `brain spec` |
-| Migrate an existing frontend | [Migration guide](https://github.com/chrisifm/BRAINLLM/blob/main/docs/MIGRATION.md) |
-| Improve the compiler while using it | [Evolution workflow](https://github.com/chrisifm/BRAINLLM/blob/main/docs/EVOLUTION.md) and [agent ideas](https://github.com/chrisifm/BRAINLLM/blob/main/docs/AGENT-IDEAS.md) |
-| Understand the implementation | [Internals](https://github.com/chrisifm/BRAINLLM/blob/main/docs/INTERNALS.md) and [crates](https://github.com/chrisifm/BRAINLLM/blob/main/crates/) |
-| Inspect examples and reproduce measurements | [Examples](https://github.com/chrisifm/BRAINLLM/blob/main/examples/) and [benchmarks](https://github.com/chrisifm/BRAINLLM/blob/main/bench/) |
-| Contribute a change | [Contributor guide](https://github.com/chrisifm/BRAINLLM/blob/main/CONTRIBUTING.md) |
+| Give an agent the project context | [llms.txt](https://github.com/chrisifm/BRAINLLM/blob/v0.4.0/llms.txt) |
+| Write an app | [SPEC.md](https://github.com/chrisifm/BRAINLLM/blob/v0.4.0/SPEC.md) and `brain spec` |
+| Migrate an existing frontend | [Migration guide](https://github.com/chrisifm/BRAINLLM/blob/v0.4.0/docs/MIGRATION.md) |
+| Improve the compiler while using it | [Evolution workflow](https://github.com/chrisifm/BRAINLLM/blob/v0.4.0/docs/EVOLUTION.md) and [agent ideas](https://github.com/chrisifm/BRAINLLM/blob/v0.4.0/docs/AGENT-IDEAS.md) |
+| Understand the implementation | [Internals](https://github.com/chrisifm/BRAINLLM/blob/v0.4.0/docs/INTERNALS.md) and [crates](https://github.com/chrisifm/BRAINLLM/blob/v0.4.0/crates/) |
+| Inspect examples and reproduce measurements | [Examples](https://github.com/chrisifm/BRAINLLM/blob/v0.4.0/examples/) and [benchmarks](https://github.com/chrisifm/BRAINLLM/blob/v0.4.0/bench/) |
+| Contribute a change | [Contributor guide](https://github.com/chrisifm/BRAINLLM/blob/v0.4.0/CONTRIBUTING.md) |
 
-Released under the [MIT license](https://github.com/chrisifm/BRAINLLM/blob/main/LICENSE).
+Released under the [MIT license](https://github.com/chrisifm/BRAINLLM/blob/v0.4.0/LICENSE).
 
 Created and maintained by **Christian Irack Flores Maldonado**, principal author.
 [ingenieria.dev](https://ingenieria.dev) · [irack.mx](https://irack.mx) · [christian@irack.mx](mailto:christian@irack.mx)
@@ -386,5 +410,5 @@ Every merged contribution helps the next developer and their agent. Thank you to
 
 [<img src="https://avatars.githubusercontent.com/u/1562002?v=4" width="48" height="48" alt="chrisifm">](https://github.com/chrisifm) [chrisifm](https://github.com/chrisifm)
 
-Attribution is refreshed through a reviewed pull request. [How it works](https://github.com/chrisifm/BRAINLLM/blob/main/docs/CONTRIBUTORS.md).
+Attribution is refreshed through a reviewed pull request. [How it works](https://github.com/chrisifm/BRAINLLM/blob/v0.4.0/docs/CONTRIBUTORS.md).
 <!-- contributors:end -->

package/THIRD_PARTY_NOTICES.txt

@@ -0,0 +1,211 @@
+web-features 3.44.0
+Source: https://github.com/web-platform-dx/web-features
+Official npm archive: https://registry.npmjs.org/web-features/-/web-features-3.44.0.tgz
+Published: 2026-10-22T16:30:26.001Z
+Data SHA-256: 72577e8df9c8abe8a8af86a03bc161ac06be21488d76857f157c7f83f017f706
+The license below is reproduced from package/LICENSE.txt in the integrity-verified official npm archive.
+Only the trailing blank line is omitted.
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.
+
+Native compiler dependency licenses accompany each platform package in THIRD_PARTY_NOTICES.txt, CARGO_NOTICES.txt, CARGO_DEPENDENCIES.json RUST_STD_COPYRIGHT.html and RUST_TOOLCHAIN_COPYRIGHT.html. Launcher/initializer/runtime-only packages do not embed a Rust compiler binary.

package/package.json

@@ -1,20 +1,65 @@
 {
   "name": "@christianirack/create-brainllm",
-  "version": "0.1.0",
-  "description": "npm create @christianirack/brainllm <app>: a new BRAINLLM app with its brain version pinned.",
+  "version": "0.4.0",
+  "description": "npm create @christianirack/brainllm <app>: a new BRAINLLM app (the Rust-powered full-stack web compiler for LLMs and AI agents) with its brain version pinned.",
   "bin": {
     "create-brainllm": "bin/create.js"
   },
   "files": [
     "bin",
-    "README.md"
+    "README.md",
+    "THIRD_PARTY_NOTICES.txt"
   ],
   "engines": {
     "node": ">=22"
   },
   "dependencies": {
-    "@christianirack/brainllm": "0.1.0"
+    "@christianirack/brainllm": "0.4.0"
   },
+  "keywords": [
+    "create",
+    "starter",
+    "template",
+    "scaffold",
+    "llm",
+    "ai",
+    "ai-agents",
+    "coding-agent",
+    "agentic",
+    "claude-code",
+    "cursor",
+    "mcp",
+    "model-context-protocol",
+    "frontend",
+    "front-end",
+    "backend",
+    "back-end",
+    "fullstack",
+    "full-stack",
+    "cli",
+    "command-line",
+    "developer-tools",
+    "design-system",
+    "css",
+    "testing",
+    "e2e",
+    "postgresql",
+    "jwt",
+    "web-framework",
+    "framework",
+    "compiler",
+    "rust",
+    "fast",
+    "performance",
+    "react-alternative",
+    "vite-alternative",
+    "signals",
+    "reactive",
+    "components",
+    "ssr",
+    "spa",
+    "web"
+  ],
   "license": "MIT",
   "author": "Christian Irack Flores Maldonado <christian@irack.mx> (https://ingenieria.dev)",
   "repository": {