plutonium 0.56.0 → 0.56.2

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: fdb3a70cfc50828cc986040543d72e8e576497deffb3304aac601b113c507370
-  data.tar.gz: 7901dd81e5a9f11519224695071e1fe76c3121e8d311d1b1d6d7445fb2179667
+  metadata.gz: 7932a8a7af49201798eaf8727c03857ab7b7b3490a7ce049acd89cf8efeeda38
+  data.tar.gz: 4a268a9cd14ae441ca664c249a3b602f2509aa63f38b9e76a4fd06b0d56fc3a3
 SHA512:
-  metadata.gz: 3d89dc0f91a27bb0e0e1ac5503cb11059d35309767fa006c200216819e0c123d6d2a558a03ac162964527b992fabc974184d5f357f3b0389405f2c63a13bdfed
-  data.tar.gz: 584146030273aeac56b898049f4f9e6a05f364c1b334bdca4ef2e044288548f1277c4d419cf7051504d36e0fd32ffbe48a4540c03f7b80f08405f43b4a0313ab
+  metadata.gz: eea920321f823c316c2ba4aa226e56e614fc0fc39790ee6ac9dd1893fc2a028d4165782823aab2bb8b4285bdbe868fbb43c68553df2eff74784ce04a6de98bff
+  data.tar.gz: 713961bf18c70042aa361e948a72caa918d67e0636f2b632715809f7e48c1d4aa41efe77e4517469d0e6ab8c13270965b9558a59d27e98264149646c5b757ea0

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.
@@ -1050,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,
@@ -1062,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/CHANGELOG.md

@@ -1,3 +1,22 @@
+## [0.56.2] - 2026-06-05
+
+### 🐛 Bug Fixes
+
+- *(generators/update)* Run skills sync in unbundled env
+- *(ui/pagination)* Prevent large page numbers from overflowing buttons
+## [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

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).