plutonium 0.55.0 → 0.56.1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: ecf3e56a7d08f87ee2e77af368b4059655aeea666fcfefcf238256ae8564a9e8
-  data.tar.gz: d70895506dda46cafc6933b9a972261365cdbddaff728e6eb8ad84bb3857ce0a
+  metadata.gz: 17f6996a0503aeccb6070cb0c379d09bfd253e2356a839745368bcaf0110e377
+  data.tar.gz: 0603760cfc2a10d6bedaa4b225b33fc5cf5b632a36829c4e6c9e9c4ce7b7971b
 SHA512:
-  metadata.gz: d8e6d17854893f67732bfb97ecc7cf744501d5469df99bfd0c3e5c9b8f39d16818c93c270e586f6cd486c4559465db33e4e3cdfb6fff0fa9dfb7d3cf027678ef
-  data.tar.gz: af4b9df9e92dd343c6db4d73d39d3cfcad6a08fc3a9ce74ad47afabfb25056c0bccc7e8a924ac3a6070e4767a7e05e69d012cff6073732c04bae425bc33dd894
+  metadata.gz: b77a88b0c0e04b5a9e143c88b292ec305f7d5c8ef74efe3e0891f20c772e63eef35383a7785338863f4cd9a942c5b76c94c1fa6fedc2995c41da8df680f1e390
+  data.tar.gz: 7dd9fd4420c8145227929c4f6ec434520c6701ea387767d9395bb74b413d2e99ce451611c89797604a1cf5a62bb51368a4aa2f5c79d1b698a1c11842979dcb29

data/.claude/skills/plutonium/SKILL.md

@@ -127,7 +127,7 @@ Meta-generators (`pu:saas:setup`) propagate flags to the generators they chain.
 
 1. **Load the bootstrap bundle** (or the targeted skill from the router table).
 2. **Generate** — `rails g pu:res:scaffold Model field:type ... --dest=main_app`.
-3. **Migrate** — `rails db:migrate`.
+3. **Migrate** — `rails db:prepare`.
 4. **Connect** — `rails g pu:res:conn Model --dest=portal_name`.
 5. **Customize** — edit definition / policy as needed.
 6. **Verify** — hit the route in the browser.

data/.claude/skills/plutonium-app/SKILL.md

@@ -62,7 +62,7 @@ rails generate pu:pkg:portal admin --auth=user
 
 # 4. First resource
 rails generate pu:res:scaffold Post user:belongs_to title:string 'content:text?' --dest=main_app
-rails db:migrate
+rails db:prepare
 
 # 5. Connect resource to portal
 rails generate pu:res:conn Post --dest=admin_portal

data/.claude/skills/plutonium-auth/SKILL.md

@@ -279,7 +279,7 @@ rails g pu:profile:setup date_of_birth:date bio:text \
 rails generate pu:profile:install bio:text avatar:attachment 'timezone:string?' \
   --dest=customer
 
-rails db:migrate
+rails db:prepare
 
 rails generate pu:profile:conn --dest=customer_portal
 ```

data/.claude/skills/plutonium-resource/SKILL.md

@@ -29,7 +29,7 @@ For tenancy / `associated_with` / `relation_scope`, load [[plutonium-tenancy]].
 1. Pick destination: `--dest=main_app` or `--dest=package_name`.
 2. Run `rails g pu:res:scaffold ResourceName field:type ... --dest=<dest>`.
 3. Review the generated migration — add cascade deletes, composite indexes, defaults.
-4. `rails db:migrate`.
+4. `rails db:prepare`.
 5. `rails g pu:res:conn ResourceName --dest=<portal_name>`.
 6. Customize the policy's `permitted_attributes_for_*` as needed.
 7. Open the portal route in the browser.
@@ -484,7 +484,7 @@ end
 | Text | `:string`, `:text`, `:email`, `:url`, `:tel`, `:password` |
 | Rich Text | `:markdown` (EasyMDE) |
 | Numeric | `:number`, `:integer`, `:decimal`, `:range` |
-| Boolean | `:boolean` |
+| Boolean | `:toggle` / `:switch` (switch — **default** for boolean columns), `:boolean` (plain checkbox) |
 | Date/Time | `:date`, `:time`, `:datetime` |
 | Selection | `:select`, `:slim_select`, `:radio_buttons`, `:check_boxes` |
 | Files | `:file`, `:uppy`, `:attachment` |
@@ -493,7 +493,26 @@ end
 
 ### Display Types (show / index)
 
-`:string`, `:text`, `:email`, `:url`, `:phone`, `:markdown`, `:number`, `:integer`, `:decimal`, `:boolean`, `:date`, `:time`, `:datetime`, `:association`, `:attachment`
+`:string`, `:text`, `:email`, `:url`, `:phone`, `:markdown`, `:number`, `:integer`, `:decimal`, `:boolean`, `:badge`, `:currency`, `:color`, `:date`, `:time`, `:datetime`, `:association`, `:attachment`
+
+#### Auto-inferred display formatting
+
+These render automatically — declare an `as:` only to override or pass options:
+
+| Column | Renders as | Notes |
+|--------|-----------|-------|
+| `boolean` | Yes/No pill (`:boolean`) | green "Yes" / neutral "No". Override labels: `true_label:`, `false_label:` |
+| `enum` | colored status badge (`:badge`) | known statuses (active, pending, failed…) auto-colored; unknown values get a stable decorative color |
+| `has_cents` decimal | currency (`:currency`) | delimited, 2 decimals, **no symbol** unless you add `unit:` |
+
+```ruby
+display :status, as: :badge, colors: {archived: :neutral, vip: :accent}  # override per-value color
+display :price,  as: :currency, unit: "£"                                # literal symbol
+display :price,  as: :currency, unit: :currency_symbol                   # Symbol → read off the record (per-row)
+display :active, as: :boolean,  true_label: "Live", false_label: "Off"
+```
+
+Badge color keys: `:neutral`, `:primary`, `:secondary`, `:success`, `:danger`, `:warning`, `:info`, `:accent`.
 
 ## Field Options
 
@@ -1031,6 +1050,10 @@ action :name,
   collection_record_action: true,
   bulk_action: true,
 
+  # Conditional visibility — display-only toggle, NOT authorization (see below).
+  # `-> { false }` keeps the route live but hides the button (e.g. API-only).
+  condition: -> { params[:beta] == "1" },
+
   # Grouping
   category: :primary,               # :primary, :secondary, :danger
   position: 50,
@@ -1043,6 +1066,36 @@ action :name,
   size:  :lg                        # :sm / :md / :lg / :xl / :auto / :full — overrides definition's modal size
 ```
 
+### Conditional Actions (`condition:`)
+
+Like `condition:` on inputs/displays/columns — define an action but render its **button** only when a runtime proc is truthy. The action and its route stay live either way; `condition:` only toggles the UI.
+
+Headline use case: **expose an action's endpoint without a button** — one you call from the API, a webhook, or another service. Hide it with an always-falsy condition; the route still works:
+
+```ruby
+# Defined and callable (API / programmatic), but no button anywhere:
+action :sync_inventory, interaction: SyncInventoryInteraction, condition: -> { false }
+
+# Per-record display state — object is the row/shown record:
+action :reopen, interaction: ReopenInteraction, condition: -> { object.closed? }
+
+# View/request-level toggle (feature flag, beta mode):
+action :preview, interaction: PreviewInteraction, condition: -> { params[:beta] == "1" }
+```
+
+Inside the proc, `object`/`record` is the contextual record — the row/shown record for **record** and **collection-record** actions, **nil** for **resource** and **bulk** actions (guard with `object&.…` if shared). Every other call delegates to the **view context**: `current_user`, `current_parent`, `params`, `request`, `allowed_to?`, `resource_record!`, etc. `object` is evaluated per row in tables/grids, so per-record show/hide works there.
+
+🚨 **`condition:` is NOT authorization — it only hides the button.** A hidden action still has a live route; anyone with the URL can trigger it. "Who may run this" belongs in the policy:
+
+```ruby
+# 🚫 WRONG — does not stop non-admins; the route is live.
+action :wipe, interaction: WipeInteraction, condition: -> { current_user.admin? }
+# ✅ RIGHT — authorization in the policy, enforced regardless of condition:
+def wipe? = current_user.admin?
+```
+
+The two compose: an action's button shows only when the policy permits **and** the condition is truthy; execution is gated by the policy alone. Use `object` in `condition:` for per-record *display*; use the policy for per-record *authorization*.
+
 `Action#with(...)` — actions are frozen value objects; clone with overrides:
 
 ```ruby

data/.claude/skills/plutonium-ui/SKILL.md

@@ -252,6 +252,7 @@ render field(:title).wrapped(class: "col-span-full") { |f| f.input_tag }
 | `input_tag` | text (auto-detected type) |
 | `string_tag`, `text_tag`, `number_tag`, `email_tag`, `password_tag`, `url_tag`, `tel_tag`, `hidden_tag` | standard HTML inputs |
 | `checkbox_tag`, `select_tag`, `radio_button_tag` | standard |
+| `toggle_tag` / `switch_tag` | switch-styled boolean (`as: :toggle` / `:switch`) — default for boolean columns; `as: :boolean` for a plain checkbox |
 
 ### Plutonium-enhanced tags
 
@@ -513,6 +514,16 @@ rails generate pu:eject:layout
 
 These copy `_resource_header.html.erb`, `_resource_sidebar.html.erb`, and `layouts/resource.html.erb` into the portal so you can edit them directly.
 
+## Navigation menu items
+
+The sidebar/icon-rail menu is built with `Phlexi::Menu::Builder` in `_resource_sidebar.html.erb`. Extra options on `item` are spread onto the rendered `<a>`, so an item can opt into `target` / `rel` / `data:` / `aria:`:
+
+```ruby
+m.item "Inbox", url: inbox_path, icon: Icon, target: "_blank", rel: "noopener", data: {turbo_frame: "_top"}
+```
+
+Applies to both shells (icon-rail leaf, parent flyout trigger, and flyout children; classic sidebar). Framework `class`/`data`/`aria` win on conflict — `class:` merges with the base classes, and on a parent trigger `data:`/`aria:` merge with the flyout wiring so options can't break the toggle. Phlexi's reserved `:active` key is never emitted as an attribute.
+
 ## Custom layout class (Phlex)
 
 ```ruby
@@ -733,7 +744,8 @@ Ready-to-use styled components in `src/css/components.css`. **Prefer these over
 ### Inputs, cards, panels, tables, toolbars, empty states
 
 ```
-.pu-input / -invalid / -valid          .pu-label / -required          .pu-hint / .pu-error          .pu-checkbox
+.pu-input / -invalid / -valid          .pu-label / -required          .pu-hint / .pu-error          .pu-checkbox / .pu-toggle
+.pu-badge / -neutral / -primary / -secondary / -success / -danger / -warning / -info / -accent
 .pu-card / .pu-card-body
 .pu-panel-header / -title / -description
 .pu-table-wrapper / .pu-table / -header / -header-cell / -body-row / -body-row-selected / -body-cell / .pu-selection-cell
@@ -845,7 +857,7 @@ end
 
 ### Display theme keys
 
-`fields_wrapper`, `label`, `description`, `string`, `text`, `link`, `email`, `phone`, `markdown`, `json`.
+`fields_wrapper`, `label`, `description`, `string`, `text`, `link`, `email`, `phone`, `markdown`, `json`, `boolean`, `badge`, `currency`, `color`.
 
 ## Table theme
 
@@ -914,6 +926,7 @@ end
 - **Dark mode is `selector`, not `class`.** Toggle via `document.documentElement.classList.toggle('dark')`.
 - **Tokens are CSS variables, not Tailwind keys** — `bg-[var(--pu-surface)]`, not `bg-pu-surface`.
 - **`render_actions` is mandatory in custom `form_template`** — otherwise no submit button.
+- **Dropdowns (`resource-drop-down`) teleport their menu to `<body>` while open.** popper's `fixed` strategy alone is still clipped by a transformed + `overflow:hidden` ancestor (e.g. grid cards, app shells), so the controller reparents the open menu to `<body>` and restores it on close. Don't rely on the menu being a DOM child of its trigger while open.
 
 ---
 

data/CHANGELOG.md

@@ -1,3 +1,47 @@
+## [0.56.1] - 2026-06-05
+
+### 🚀 Features
+
+- *(actions)* Add display-only condition: to actions
+
+### 🐛 Bug Fixes
+
+- *(dummy)* Version-adapt kitchen_sinks migration
+
+### 📚 Documentation
+
+- Recommend db:prepare, firm up README, document conditional actions
+## [0.56.0] - 2026-06-05
+
+### 🚀 Features
+
+- *(ui)* Auto-rendered components for boolean, enum & money fields
+- *(generators/lite)* Add pu:lite:tune and pu:lite:maintenance for SQLite tuning + maintenance
+- *(ui)* Sidebar menu items accept arbitrary link attributes
+- *(ui)* Restore deleted nested rows + shared, polished removed bar
+- *(ui)* Type-aware grid cards + overhaul KitchenSink dummy resource
+
+### 🐛 Bug Fixes
+
+- *(generators/update)* Sync skills in a fresh process; pin post-install notice to 0.49.0
+- *(ui)* Native multi-selects render at a usable height
+- *(ui)* Dropdown menu teleports to <body> to escape overflow clipping
+- *(routing)* Force :resources route_type for has_many nested routes
+- *(ui)* Record-scoped commit URL for actions with record_action: false
+- *(api)* Serialize JSON values via as_json (ISO 8601 datetimes)
+- *(generators)* Add reading role to Rails Pulse connects_to config
+- *(actions)* Bind subject during interaction param extraction
+- *(ui)* Dirty-form-guard tracks edits via first-interaction baseline
+- *(ui)* Give the JSON form input dark-mode styling
+
+### 🧪 Testing
+
+- Fix stale generator assertions and drop committed dummy schema
+- *(dummy)* Add KitchenSink resource exercising every input/display type
+
+### ⚙️ Miscellaneous Tasks
+
+- Sync appraisal gemfile.lock files to v0.55.0
 ## [0.55.0] - 2026-06-03
 
 ### 🚀 Features

data/CONTRIBUTING.md

@@ -153,7 +153,7 @@ Use the dummy app:
 ```bash
 cd test/dummy
 rails g pu:res:scaffold TestModel name:string --dest=main_app
-rails db:migrate
+rails db:prepare
 bin/dev
 ```
 

data/README.md

@@ -2,8 +2,11 @@
 
 [![Gem Version](https://badge.fury.io/rb/plutonium.svg)](https://badge.fury.io/rb/plutonium)
 [![Ruby](https://github.com/radioactive-labs/plutonium-core/actions/workflows/main.yml/badge.svg)](https://github.com/radioactive-labs/plutonium-core/actions/workflows/main.yml)
+[![License: MIT](https://img.shields.io/badge/License-MIT-green.svg)](LICENSE.txt)
 
-Build production-ready Rails apps in minutes, not days. Convention-driven, fully customizable, and AI-ready. Plutonium picks up where Rails left off, adding application-level concepts that make building complex apps faster.
+**The Rails framework for things you should never write again.**
+
+Convention over configuration, extended to everything you keep rebuilding: **CRUD. Auth. Authorization. Multi-tenancy. Admin portals. Search, filters, bulk actions.** All generated. All customizable. All Rails.
 
 ## Quick Start
 
@@ -12,20 +15,36 @@ rails new myapp -a propshaft -j esbuild -c tailwind \
   -m https://radioactive-labs.github.io/plutonium-core/templates/plutonium.rb
 ```
 
-Then create your first resource:
+Then scaffold a resource, create a portal, and connect them:
 
 ```bash
 cd myapp
-rails g pu:res:scaffold Post title:string body:text --dest=main_app
-rails db:migrate
+
+# Scaffold a resource — model, migration, definition, policy
+rails g pu:res:scaffold Post title:string body:text published_at:datetime --dest=main_app
+rails db:prepare
+
+# Create a portal (web interface) and connect the resource to it
+rails g pu:pkg:portal app --public
+rails g pu:res:conn Post --dest=app_portal
+
 bin/dev
 ```
 
-Visit `http://localhost:3000` - you have a complete CRUD interface.
+Visit `http://localhost:3000/app/posts` — you have a complete CRUD interface.
 
-## What You Get
+## What You Stop Writing
 
-**Resource-oriented architecture** - Models, policies, definitions, and controllers that work together:
+Same scaffold command you already know. A very different surface area.
+
+```bash
+rails g scaffold Post ...              # Rails:     just CRUD
+rails g pu:res:scaffold Post ...       # Plutonium: full CRUD + search + filters + bulk actions
+```
+
+And it doesn't stop at scaffolds:
+
+**Resource-oriented architecture** — models, policies, definitions, and controllers that work together:
 
 ```ruby
 # Policy controls WHO can do WHAT
@@ -47,7 +66,7 @@ class PostDefinition < ResourceDefinition
 end
 ```
 
-**Packages for organization** - Split your app into feature packages and portals:
+**Packages and portals** — split your app into feature engines and themed web interfaces:
 
 ```bash
 rails g pu:pkg:package blogging      # Business logic
@@ -65,7 +84,7 @@ rails g pu:rodauth:account user
 **Multi-tenancy** with entity scoping:
 
 ```ruby
-# In portal engine
+# In a portal engine
 scope_to_entity Organization, strategy: :path
 # Routes become /organizations/:organization_id/posts
 ```
@@ -86,6 +105,13 @@ class PublishInteraction < ResourceInteraction
 end
 ```
 
+## Why Plutonium
+
+- **Convention over configuration** — extended to resources, policies, portals, and tenancy, not just routes and views.
+- **It's just Rails** — generated code lives in your repo. Edit it, override it, delete it. The "magic" is regular Ruby mixins you can read.
+- **Multi-tenant ready** — path or domain tenancy, scoped relations, invites and memberships out of the box.
+- **AI-readable** — predictable file layout and naming, plus built-in [Claude Code skills](.claude/skills) that teach AI assistants the patterns.
+
 ## Documentation
 
 Full documentation at **[radioactive-labs.github.io/plutonium-core](https://radioactive-labs.github.io/plutonium-core/)**
@@ -97,18 +123,14 @@ Full documentation at **[radioactive-labs.github.io/plutonium-core](https://radi
 
 ## Requirements
 
-- Ruby 3.2+
-- Rails 7.1+ (Rails 8 recommended)
+- Ruby 3.2.2+
+- Rails 7.2+ (Rails 8 recommended)
 - Node.js 18+
 
 ## Contributing
 
 See [CONTRIBUTING.md](CONTRIBUTING.md) for development setup and guidelines.
 
-## Status
-
-Plutonium is used in production but still evolving. APIs may change between minor versions. Pin your version in Gemfile.
-
 ## License
 
-MIT License - see [LICENSE](LICENSE).
+MIT License — see [LICENSE.txt](LICENSE.txt).