@fugood/bricks-project 2.24.0-beta.4 → 2.24.0-beta.40

package/compile/util.ts

@@ -1,6 +1,8 @@
 import { makeId } from '../utils/id'
 
 type ScriptConfig = {
+  title?: string
+  note?: string
   inputs: Record<string, string>
   enable_async: boolean
   trigger_mode?: 'auto' | 'manual'

package/package.json

@@ -1,16 +1,18 @@
 {
   "name": "@fugood/bricks-project",
-  "version": "2.24.0-beta.4",
+  "version": "2.24.0-beta.40",
   "main": "index.ts",
   "scripts": {
+    "typecheck": "tsc --noEmit",
     "build": "bun scripts/build.js"
   },
   "dependencies": {
-    "@fugood/bricks-cli": "^2.24.0-beta.4",
+    "@fugood/bricks-cli": "^2.24.0-beta.40",
     "@huggingface/gguf": "^0.3.2",
     "@iarna/toml": "^3.0.0",
     "@modelcontextprotocol/sdk": "^1.15.0",
     "@toon-format/toon": "^2.1.0",
+    "@types/bun": "^1.3.9",
     "@types/escodegen": "^0.0.10",
     "@types/lodash": "^4.17.12",
     "acorn": "^8.13.0",
@@ -19,5 +21,7 @@
     "lodash": "^4.17.4",
     "uuid": "^8.3.1"
   },
-  "gitHead": "f5f65204e7259449b4cf7dbc35597e5e3d0b1425"
+  "peerDependencies": {
+    "oxfmt": "^0.36.0"
+  }
 }

package/package.json.bak

@@ -0,0 +1,27 @@
+{
+  "name": "@fugood/bricks-ctor",
+  "version": "2.24.0-beta.40",
+  "main": "index.ts",
+  "scripts": {
+    "typecheck": "tsc --noEmit",
+    "build": "bun scripts/build.js"
+  },
+  "dependencies": {
+    "@fugood/bricks-cli": "^2.24.0-beta.40",
+    "@huggingface/gguf": "^0.3.2",
+    "@iarna/toml": "^3.0.0",
+    "@modelcontextprotocol/sdk": "^1.15.0",
+    "@toon-format/toon": "^2.1.0",
+    "@types/bun": "^1.3.9",
+    "@types/escodegen": "^0.0.10",
+    "@types/lodash": "^4.17.12",
+    "acorn": "^8.13.0",
+    "escodegen": "2.1.0",
+    "fuse.js": "^7.0.0",
+    "lodash": "^4.17.4",
+    "uuid": "^8.3.1"
+  },
+  "peerDependencies": {
+    "oxfmt": "^0.36.0"
+  }
+}

package/skills/bricks-design/LICENSE.txt

@@ -0,0 +1,180 @@
+                                 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
+
+   This skill is a derivative work based on:
+   https://github.com/anthropics/skills/blob/main/skills/frontend-design/SKILL.md
+   Copyright Anthropic, PBC. Licensed under the Apache License, Version 2.0.

package/skills/bricks-design/SKILL.md

@@ -0,0 +1,66 @@
+---
+name: bricks-design
+description: Create distinctive, production-grade BRICKS application interfaces with high design quality. Use this skill when the user asks to build BRICKS canvases, screens, layouts, or applications. Generates creative, polished BRICKS code that avoids generic aesthetics.
+license: Complete terms in LICENSE.txt (Apache-2.0, based on github.com/anthropics/skills)
+---
+
+This skill guides creation of distinctive, production-grade BRICKS application interfaces that avoid generic aesthetics. Implement working code with exceptional attention to visual design and creative choices.
+
+The user provides interface requirements: a screen, layout, application, or component to build. They may include context about the purpose, audience, platform, or technical constraints.
+
+## Design Thinking
+
+Before coding, understand the context and commit to a **bold** aesthetic direction:
+- **Purpose**: What problem does this interface solve? Who uses it? What platform(s)?
+- **Tone**: Pick a strong direction: brutally minimal, maximalist, retro-futuristic, organic/natural, luxury/refined, playful, editorial/magazine, brutalist/raw, art deco/geometric, soft/pastel, industrial/utilitarian, etc. Use these for inspiration but design one true to the aesthetic.
+- **Constraints**: Target platform (mobile, TV, desktop, kiosk), screen dimensions, accessibility needs.
+- **Differentiation**: What makes this UNFORGETTABLE? What's the one thing someone will remember?
+
+**CRITICAL**: Choose a clear conceptual direction and execute it with precision. Bold maximalism and refined minimalism both work — the key is intentionality, not intensity.
+
+Then implement working BRICKS TypeScript code that is:
+- Production-grade and functional
+- Visually striking and memorable
+- Cohesive with a clear aesthetic point-of-view
+- Meticulously refined in every detail
+
+## Aesthetics Guidelines
+
+### Typography
+Choose fonts that are beautiful, unique, and interesting. Avoid defaulting to system fonts — opt for distinctive choices that elevate the interface. Pair a characterful display font with a refined body font. Create clear typographic hierarchy through weight, size, spacing, and alignment. Use auto-scaling (`fontSizeVector`) when text should fill its container proportionally.
+
+### Color & Theme
+Commit to a cohesive palette. Dominant colors with sharp accents outperform timid, evenly-distributed palettes. Use gradients for rich, atmospheric surfaces — multi-stop linear gradients create far more depth than flat fills. Use Data nodes as a shared color store for consistency across bricks.
+
+### Motion & Animation
+Focus on high-impact moments: one well-orchestrated canvas enter with staggered standby reveals creates more delight than scattered micro-interactions. Use spring animations for natural, bouncy UI elements. Use composed animations (parallel/sequence) for coordinated entrance choreography. Reserve looping animations (`breatheStart`) for attention-drawing elements — overuse dulls their impact.
+
+### Spatial Composition
+Absolute positioning gives total control — use it creatively. Overlap bricks. Create asymmetric layouts. Use generous negative space OR controlled density. Break grid expectations. Consider rotation for diagonal flow and perspective. Vary scale dramatically between elements for visual tension.
+
+### Depth & Atmosphere
+Create atmosphere through layered elements rather than flat solid colors:
+- **Gradients** with multiple color stops for rich backgrounds
+- **Shadows** for elevation and hierarchy
+- **Blur effects** (blur, progressive blur, liquid glass) for glass morphism on native platforms
+- **Opacity layering** — stack semi-transparent rects for texture and depth
+- **Border details** — per-side colors, styles, and widths for decorative framing
+
+### Interactive Polish
+Design interactions that feel tactile and responsive:
+- Scale/opacity animations on press for physical feedback
+- Focus states for TV/controller navigation
+- Outlet-driven switches for state-dependent visual changes
+- Deliberate long-press patterns for secondary actions
+
+## What to NEVER Do
+
+- **No generic aesthetics**: Avoid the same tired palette, the same safe layout, the same system font on every screen. Each design should feel distinct and intentional.
+- **No flat sameness**: Don't make every canvas look like the same template with different text. Vary spatial composition, color weight, animation timing, and typographic scale.
+- **No placeholder layouts**: Don't just center everything in a grid. Use the absolute positioning system to create spatial interest — overlap, offset, scale contrast.
+
+Vary between light and dark themes, different fonts, different aesthetics across generations. NEVER converge on common choices across designs.
+
+**IMPORTANT**: Match implementation complexity to the aesthetic vision. Maximalist designs need elaborate animations, layered rects, and rich gradients. Minimalist designs need restraint, precision in spacing, and carefully chosen typography. Elegance comes from executing the vision well.
+
+Remember: The agent is capable of extraordinary creative work. Don't hold back — show what can truly be created when thinking outside the box and committing fully to a distinctive vision.

package/skills/bricks-project/SKILL.md

@@ -1,9 +1,9 @@
 ---
-name: bricks-project
+name: bricks-ctor
 description: Advanced BRICKS configuration knowledge. Covers Standby Transition, Automations (E2E testing), Data Calculation (JS sandbox libraries), Local Sync, Remote Data Bank, Media Flow, and Buttress (remote inference). Triggers on multi-device sync, cloud data, media assets, AI offloading, E2E testing, or canvas transitions.
 ---
 
-# BRICKS Project - Advanced Features
+# BRICKS Ctor - Advanced Features
 
 This skill covers advanced BRICKS features not in the main project instructions.
 

package/skills/bricks-project/rules/animation.md

@@ -8,7 +8,7 @@ BRICKS Animation system for animating brick transforms and opacity. Animations a
 Standard duration-based animation with easing.
 
 ```typescript
-import { makeId } from 'bricks-project'
+import { makeId } from 'bricks-ctor'
 
 const fadeIn: AnimationDef = {
   __typename: 'Animation',

package/skills/bricks-project/rules/architecture-patterns.md

@@ -37,6 +37,13 @@ Built-in commands for direct state and UI changes.
 ### Data Calculation (Priority 4)
 ONLY for deriving, formatting, or aggregating values from other data. Not for orchestration, side effects, or flow control.
 
+## Entity Aliases
+
+Set `alias` on entities to give them a stable, human-readable name:
+- Code generation uses alias as the variable name (e.g., `alias: 'submitBtn'` → `export const submitBtn`)
+- At runtime, devtools MCP tools accept alias instead of short ID and selectors can match by alias. Note: bricks-ctor does not directly interact with devtools MCP — aliases here primarily affect code generation
+- Aliases must be unique across the application — duplicates are excluded from resolution
+
 ## Flow Decomposition
 
 When the user describes a complex flow, decompose it BEFORE writing code:

package/skills/bricks-project/rules/automations.md

@@ -4,15 +4,16 @@ E2E testing and scheduled execution for BRICKS applications. Simulates user beha
 
 ## Automation Types
 
-| Type | Description |
-|------|-------------|
-| `launch` | Run on application launch (restarts app when run manually) |
-| `anytime` | Execute anytime via manual trigger |
-| `cron` | Scheduled execution using crontab expressions |
+| Type      | Description                                                |
+| --------- | ---------------------------------------------------------- |
+| `launch`  | Run on application launch (restarts app when run manually) |
+| `anytime` | Execute anytime via manual trigger                         |
+| `cron`    | Scheduled execution using crontab expressions              |
 
 ## Simulation Actions
 
 Automations can simulate:
+
 - **Brick Press**: Tap/click on bricks
 - **Key Events**: Key up/down for keyboard input
 - **HTTP Request**: API calls
@@ -21,6 +22,7 @@ Automations can simulate:
 ## Assertions
 
 Automations can validate:
+
 - **Brick Exists**: Check if brick is rendered
 - **Event Triggered**: Verify event from Brick/Generator/Canvas
 - **Canvas Changed**: Confirm canvas navigation
@@ -33,14 +35,14 @@ Automations can validate:
 ```typescript
 const testLoginFlow: AutomationTest = {
   __typename: 'AutomationTest',
-  id: 'test-login-flow',
+  id: makeId('test'),
   title: 'Test Login Flow',
   timeout: 30000,
   trigger_type: 'launch',
   cases: [
     {
       __typename: 'TestCase',
-      id: 'wait-login-canvas',
+      id: makeId('test_case'),
       name: 'Wait for login canvas',
       run: ['wait_until_canvas_change', () => mainSubspace, () => loginCanvas, 5000],
       exit_on_failed: true,
@@ -51,7 +53,7 @@ const testLoginFlow: AutomationTest = {
     },
     {
       __typename: 'TestCase',
-      id: 'press-username',
+      id: makeId('test_case'),
       name: 'Press username input',
       run: ['brick_press', () => mainSubspace, () => usernameInput],
       exit_on_failed: true,
@@ -62,7 +64,7 @@ const testLoginFlow: AutomationTest = {
     },
     {
       __typename: 'TestCase',
-      id: 'assert-username',
+      id: makeId('test_case'),
       name: 'Assert username value',
       run: ['assert_property', () => mainSubspace, () => usernameData, 'testuser'],
       exit_on_failed: true,
@@ -73,7 +75,7 @@ const testLoginFlow: AutomationTest = {
     },
     {
       __typename: 'TestCase',
-      id: 'press-login',
+      id: makeId('test_case'),
       name: 'Press login button',
       run: ['brick_press', () => mainSubspace, () => loginButton],
       exit_on_failed: true,
@@ -84,7 +86,7 @@ const testLoginFlow: AutomationTest = {
     },
     {
       __typename: 'TestCase',
-      id: 'wait-dashboard',
+      id: makeId('test_case'),
       name: 'Wait for dashboard',
       run: ['wait_until_canvas_change', () => mainSubspace, () => dashboardCanvas, 10000],
       exit_on_failed: true,
@@ -100,25 +102,58 @@ const testLoginFlow: AutomationTest = {
 
 ## Test Methods
 
-| Method | Signature | Description |
-|--------|-----------|-------------|
-| `brick_press` | `[subspace, brick, options?]` | Simulate brick press |
-| `brick_exists` | `[subspace, brick, frame?]` | Check brick exists |
-| `wait_until_brick_exists` | `[subspace, brick, timeout?, frame?]` | Wait for brick |
-| `wait_until_event_trigger` | `[subspace, sender, eventKey, timeout?]` | Wait for event |
-| `wait_until_canvas_change` | `[subspace, canvas, timeout?]` | Wait for canvas |
-| `keydown` | `[keyCode, pressedKey?, flags?]` | Key down event |
-| `keyup` | `[keyCode, pressedKey?, flags?]` | Key up event |
-| `http_request` | `[url, options?]` | HTTP request |
-| `assert_property` | `[subspace, property, value]` | Assert data value |
-| `wait_until_property_change` | `[subspace, property, value, timeout?]` | Wait for value |
-| `execute_action` | `[subspace, handler, action, params?, options?]` | Execute action |
-| `match_screenshot` | `[name, threshold?, maxRetry?]` | Screenshot compare |
-| `delay` | `[subspace?, property?, defaultValue?]` | Delay execution |
+| Method                       | Signature                                        | Description          |
+| ---------------------------- | ------------------------------------------------ | -------------------- |
+| `brick_press`                | `[subspace, brick, options?]`                    | Simulate brick press |
+| `brick_exists`               | `[subspace, brick, frame?]`                      | Check brick exists   |
+| `wait_until_brick_exists`    | `[subspace, brick, timeout?, frame?]`            | Wait for brick       |
+| `wait_until_event_trigger`   | `[subspace, sender, eventKey, timeout?]`         | Wait for event       |
+| `wait_until_canvas_change`   | `[subspace, canvas, timeout?]`                   | Wait for canvas      |
+| `keydown`                    | `[keyCode, pressedKey?, flags?]`                 | Key down event       |
+| `keyup`                      | `[keyCode, pressedKey?, flags?]`                 | Key up event         |
+| `http_request`               | `[url, options?]`                                | HTTP request         |
+| `assert_property`            | `[subspace, property, value]`                    | Assert data value    |
+| `wait_until_property_change` | `[subspace, property, value, timeout?]`          | Wait for value       |
+| `execute_action`             | `[subspace, handler, action, params?, options?]` | Execute action       |
+| `match_screenshot`           | `[name, threshold?, maxRetry?]`                  | Screenshot compare   |
+| `delay`                      | `[subspace?, property?, defaultValue?]`          | Delay execution      |
+
+### execute_action Params
+
+The `params` object in `execute_action` uses **runtime event property keys** from `event-props.ts`, NOT the action config `input` names from type definitions.
+
+```typescript
+// CORRECT — use runtime event property key
+run: ['execute_action', () => subspace0, bricks.bInput.id, 'BRICK_TEXT_INPUT_SET_TEXT',
+  { BRICK_TEXT_INPUT_TEXT: 'hello' }]
+
+// WRONG — action config input name doesn't work in automation
+run: ['execute_action', () => subspace0, bricks.bInput.id, 'BRICK_TEXT_INPUT_SET_TEXT',
+  { text: 'hello' }]
+```
+
+Reference `event-props.ts` for the correct runtime keys (e.g., `BRICK_TEXT_INPUT_TEXT`, `GENERATOR_MQTT_PAYLOAD`).
+
+### Prefer UI Interactions Over Direct Generator Calls
+
+For realistic E2E testing, prefer simulating user actions (set text input + press button) over calling generator actions directly:
+
+```typescript
+// GOOD — simulates real user behavior
+{ run: ['execute_action', () => sub, bricks.bInput.id, 'BRICK_TEXT_INPUT_SET_TEXT',
+    { BRICK_TEXT_INPUT_TEXT: 'hello' }] },
+{ run: ['brick_press', () => sub, () => bricks.bSendBtn] },
+{ run: ['wait_until_property_change', () => sub, () => data.dPayload, 'hello', 10000] },
+
+// AVOID — bypasses UI, doesn't test the full flow
+{ run: ['execute_action', () => sub, generators.gClient.id, 'GENERATOR_MQTT_PUBLISH',
+    { topic: 'test', payload: 'hello', qos: '0' }] },
+```
 
 ## Recording Automations
 
 In BRICKS Editor Preview mode:
+
 1. Perform operations normally
 2. Open menu (right-bottom corner)
 3. Select "Record Events as Automation"
@@ -127,12 +162,15 @@ In BRICKS Editor Preview mode:
 ## Running Automations
 
 ### Manual Run
+
 `Menu` → `Automations` → Select automation → `Run`
 
 ### On Launch
+
 `Bind Device` → `Select Automation` (only `launch` or `cron` types)
 
 ### Scheduled (Cron)
+
 `Bind Device` → `Cron Automation` (allows multi-select)
 
 Use [crontab.guru](https://crontab.guru) to build cron expressions.
@@ -144,7 +182,7 @@ Visual regression testing with screenshot comparison:
 ```typescript
 {
   __typename: 'TestCase',
-  id: 'screenshot-dashboard',
+  id: makeId('test_case'),
   name: 'Match dashboard screenshot',
   run: ['match_screenshot', 'dashboard-initial-state', 0.01, 3],
   exit_on_failed: true,
@@ -156,6 +194,7 @@ Visual regression testing with screenshot comparison:
 ```
 
 Screenshots can be stored:
+
 - Local file system
 - Media Flow workspace
 
@@ -165,11 +204,18 @@ First run captures baseline. Use "Run with Update" to update baseline.
 
 Automations work with Modules. Use Manual Run in Preview mode for module testing.
 
+## Important Notes
+
+- **Automation map key**: Always use `'AUTOMATION_MAP_DEFAULT'` as the automation map ID (not `makeId()`). The preview test runner reads from `automationMap['AUTOMATION_MAP_DEFAULT']?.map`.
+- **Valid makeId types**: Use `'test'` for AutomationTest, `'test_case'` for TestCase, `'test_var'` for TestVariable. Do NOT use `'automation_test'` or `'automation_test_map'`.
+- **handler in execute_action**: Pass the entity's `.id` string (e.g., `bricks.bInput.id`), not a getter function.
+
 ## Best Practices
 
 1. **Test culture**: Create automations for every significant flow
 2. **CI/CD integration**: Use `launch` automations for deployment validation
-3. **Incremental waits**: Use `EXPECT_*` steps with appropriate timeouts
+3. **Incremental waits**: Use `wait_until_property_change` with appropriate timeouts
 4. **Visual testing**: Add screenshot comparisons for critical UI states
 5. **Cron monitoring**: Schedule health checks for production displays
 6. **Isolation**: Each automation should be independent and idempotent
+7. **UI-first testing**: Simulate real user interactions (text input, button press) rather than calling generators directly

package/skills/bricks-project/rules/buttress.md

@@ -14,8 +14,9 @@ When mobile devices or embedded systems lack hardware for local AI inference (LL
 
 ## Supported Generators
 
-- [LLM (GGML)](generator_LLM) - Local Large Language Model inference
-- [Speech-to-Text (GGML)](generator_SpeechInference) - Local Speech-to-Text inference
+- LLM (GGML) (LlmMlx.ts) - Local Large Language Model inference with GGML
+- LLM (MLX) (LlmGgml.ts) - Local Large Language Model inference with MLX
+- Speech-to-Text (GGML) (SpeechToTextGgml.ts) - Local Speech-to-Text inference with GGML
 
 ## Client Configuration
 
@@ -39,7 +40,7 @@ In generator properties, configure Buttress settings:
 ## Generator Configuration Example
 
 ```typescript
-import { makeId } from 'bricks-project'
+import { makeId } from 'bricks-ctor'
 
 const llmGenerator: GeneratorLLM = {
   __typename: 'Generator',
@@ -50,10 +51,12 @@ const llmGenerator: GeneratorLLM = {
   property: {
     modelUrl: 'https://huggingface.co/ggml-org/gemma-3-12b-it-qat-GGUF/resolve/main/gemma-3-12b-it-qat-q4_0.gguf',
     contextSize: 8192,
-    buttressEnabled: true,
-    buttressUrl: 'http://192.168.1.100:2080',
-    buttressFallbackType: 'use-local',
-    buttressStrategy: 'prefer-best',
+    buttressConnectionSettings: {
+      enabled: true,
+      url: 'http://192.168.1.100:2080',
+      fallbackType: 'use-local',
+      strategy: 'prefer-best',
+    },
   },
   events: {},
   switches: [],

package/skills/bricks-project/rules/data-calculation.md

@@ -7,7 +7,7 @@ Transform and compute Data Bank values using JavaScript scripts.
 JavaScript code executed in a sandbox with access to inputs and outputs.
 
 ```typescript
-import { makeId } from 'bricks-project'
+import { makeId } from 'bricks-ctor'
 
 const calculation: DataCalculationScript = {
   __typename: 'DataCalculationScript',

package/skills/bricks-project/rules/local-sync.md

@@ -49,7 +49,7 @@ const subspace: Subspace = {
 ### Data Local Sync
 
 ```typescript
-import { makeId } from 'bricks-project'
+import { makeId } from 'bricks-ctor'
 
 const data: Data = {
   __typename: 'Data',
@@ -65,7 +65,7 @@ const data: Data = {
 ### Generator Local Sync
 
 ```typescript
-import { makeId } from 'bricks-project'
+import { makeId } from 'bricks-ctor'
 
 const generator: GeneratorTimer = {
   __typename: 'Generator',

package/skills/bricks-project/rules/media-flow.md

@@ -21,7 +21,7 @@ Use `Generator Media Flow` to:
 Quick setup: Create new Property with `As Media Resource file list?` option.
 
 ```typescript
-import { makeId } from 'bricks-project'
+import { makeId } from 'bricks-ctor'
 
 const mediaListGenerator: GeneratorMediaFlow = {
   __typename: 'Generator',
@@ -52,7 +52,7 @@ Link Data properties to Media Flow for asset selection:
 | `lottie-file-uri` | Lottie animation selector |
 
 ```typescript
-import { makeId } from 'bricks-project'
+import { makeId } from 'bricks-ctor'
 
 const backgroundImage: Data = {
   __typename: 'Data',
@@ -84,7 +84,7 @@ Assets with these kinds are **preloaded** during application launch.
 Connect Generator Media Flow output to Brick Slideshow:
 
 ```typescript
-import { makeId, linkData } from 'bricks-project'
+import { makeId, linkData } from 'bricks-ctor'
 
 const slideshow: BrickSlideshow = {
   __typename: 'Brick',