@agent-native/core 0.146.1 → 0.146.3

package/docs/content/docs-components.mdx

@@ -191,6 +191,113 @@ Each card is a `###` heading (optionally linked) followed by the description. Ca
 
 ---
 
+## Notice
+
+<Notice tone="risk" title="Bold, not subtle">
+
+Use `Notice` when a `Callout` would be too easy to skim past — something the reader must not miss, like a destructive action or a hard requirement. It shares the same five tones as `Callout` (`info`, `decision`, `risk`, `warning`, `success`) but renders as a filled card with an icon and optional title instead of a left-border note.
+
+</Notice>
+
+```mdx
+<Notice tone="risk" title="Bold, not subtle">
+
+Use `Notice` when a `Callout` would be too easy to skim past — something the reader must not miss, like a destructive action or a hard requirement.
+
+</Notice>
+```
+
+`title` is optional — omit it for a shorter card with just the icon and body. Leave a blank line between the opening tag and the body, same as `Callout`. Reach for `Callout` first; use `Notice` only when a subtle left-border note isn't enough attention.
+
+---
+
+## Banner
+
+<Banner
+  tone="warning"
+  body="This page describes the v9 API. See [Migrating to v10](/docs/migrating-v10) for what changed."
+/>
+
+```mdx
+<Banner
+  tone="warning"
+  body="This page describes the v9 API. See [Migrating to v10](/docs/migrating-v10) for what changed."
+/>
+```
+
+`Banner` is self-closing — `body` is a flat attribute (kept short and single-purpose on purpose), not markdown children. Place it right under a page's title or a section heading — deprecated, beta, moved, version-scoped. For content the reader needs to actually read (not just notice), use `Notice` or `Callout` instead.
+
+---
+
+## Accordion
+
+<Accordion>
+
+### Do I need Toolkit to use Core?
+
+No. Toolkit is optional shared UI — Core works standalone.
+
+### Can I mix Templates and Toolkit?
+
+Yes, most first-party templates already do.
+
+### Where do I ask questions?
+
+The `#agent-native` Discord channel, linked in the site header.
+
+</Accordion>
+
+```mdx
+<Accordion>
+
+### Do I need Toolkit to use Core?
+
+No. Toolkit is optional shared UI — Core works standalone.
+
+### Can I mix Templates and Toolkit?
+
+Yes, most first-party templates already do.
+
+</Accordion>
+```
+
+Same authoring shape as `Steps`/`Cards` — a `### Question` heading per item followed by its answer — but each item renders collapsed behind native `<details>`. Best for FAQ-style content where most readers only need one or two entries, not a full top-to-bottom read.
+
+---
+
+## Badge
+
+<Badge label="Beta" color="orange" icon="rocket" />
+
+<Badge label="Deprecated" color="red" />
+
+<Badge label="v9.1+" color="blue" shape="pill" />
+
+<Badge label="Server-only" color="gray" stroke />
+
+```mdx
+<Badge label="Beta" color="orange" icon="rocket" />
+
+<Badge label="Deprecated" color="red" />
+
+<Badge label="v9.1+" color="blue" shape="pill" />
+
+<Badge label="Server-only" color="gray" stroke />
+```
+
+A small status chip for the top of a page or section. Self-closing, block-level only — **not** embeddable mid-sentence (the docs MDX pipeline only recognizes a custom component when its tag opens its own line, so `text <Badge label="x"/> more text` renders as literal text, not a chip). Place it on its own line, typically right after a heading. Leave a blank line between adjacent Badges (or any two block components) — without one, the scanner can't tell where one ends and the next begins and falls back to rendering literal text.
+
+| Prop       | Values                                                                                                                                                 |
+| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| `color`    | `gray` · `blue` · `green` · `yellow` · `orange` · `red` · `purple` · `white` · `surface` · `white-destructive` · `surface-destructive`                 |
+| `size`     | `xs` · `sm` · `md` · `lg`                                                                                                                              |
+| `shape`    | `rounded` (default) · `pill`                                                                                                                           |
+| `icon`     | one of a curated set — `circle-check`, `circle-info`, `alert-triangle`, `alert-octagon`, `ban`, `clock`, `star`, `flame`, `sparkles`, `lock`, `rocket` |
+| `stroke`   | `true` for an outlined, transparent-background variant                                                                                                 |
+| `disabled` | `true` to dim it for an inactive/unavailable state                                                                                                     |
+
+---
+
 ## Comparison
 
 <Comparison>
@@ -478,14 +585,18 @@ Like `TabsBlock`, `Columns` is self-closing with a single JSON `columns` attribu
 
 ## When to use which component
 
-| Situation                                 | Component                            |
-| ----------------------------------------- | ------------------------------------ |
-| Reader must not miss something            | `Callout` (warning / info / success) |
-| Sequential procedure with titled steps    | `Steps`                              |
-| Navigation or feature overview grid       | `Cards`                              |
-| Before vs. after, old vs. new (prose)     | `Comparison`                         |
-| Same task in multiple tools or frameworks | `Tabs`                               |
-| Side-by-side code (labeled columns)       | `Columns`                            |
-| Project directory structure               | `FileTree`                           |
-| Inline keyboard shortcut                  | `[[Key]]`                            |
-| Architecture or flow diagram              | Mermaid fence                        |
+| Situation                                             | Component                            |
+| ----------------------------------------------------- | ------------------------------------ |
+| Reader must not miss something, inline in prose       | `Callout` (warning / info / success) |
+| Reader must not miss something, standalone            | `Notice`                             |
+| Deprecated/beta/version notice at page or section top | `Banner`                             |
+| Status or version tag at page or section top          | `Badge`                              |
+| Sequential procedure with titled steps                | `Steps`                              |
+| FAQ-style content, one answer at a time               | `Accordion`                          |
+| Navigation or feature overview grid                   | `Cards`                              |
+| Before vs. after, old vs. new (prose)                 | `Comparison`                         |
+| Same task in multiple tools or frameworks             | `Tabs`                               |
+| Side-by-side code (labeled columns)                   | `Columns`                            |
+| Project directory structure                           | `FileTree`                           |
+| Inline keyboard shortcut                              | `[[Key]]`                            |
+| Architecture or flow diagram                          | Mermaid fence                        |

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@agent-native/core",
-  "version": "0.146.1",
+  "version": "0.146.3",
   "description": "Framework for agent-native application development — where AI agents and UI share SQL state, actions, and context",
   "homepage": "https://github.com/BuilderIO/agent-native#readme",
   "bugs": {
@@ -413,7 +413,7 @@
     "yjs": "^13.6.31",
     "zod": "^4.3.6",
     "@agent-native/recap-cli": "0.5.3",
-    "@agent-native/toolkit": "^0.13.4"
+    "@agent-native/toolkit": "^0.13.5"
   },
   "devDependencies": {
     "@ai-sdk/anthropic": "^3.0.71",