plutonium 0.68.0 → 0.70.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: a01423b0e39c2e985ec24ea8663cf53377817ff24814c95ce89270806f51b878
-  data.tar.gz: cbe95fbf1cd307e3b07cccf24cda7db7293dc15676c0ee288fe076d37102cb15
+  metadata.gz: 36351840fe45e3c1d51694397c480dc641bb6edb4b7d32b38149b2af742d317a
+  data.tar.gz: dad970de51f6f04a961cae9bf4c50ea35f6b76601371cae3787b3c5e3031dfbf
 SHA512:
-  metadata.gz: a2034d1af622ec4bfbc4c6ac00c46ed63f4a7ea6ed878ebc78b9666b109cf572dff20f60da0bc9f5e5adafdb992e76deb292c4ec08146684e3828732daf2ced7
-  data.tar.gz: '09f8b0ef419d7adf5df3057a271ed4659140e4308c4b7ea5ea5965554256e2c609314ecb6cd33893629773b9fab97f735b1e16872f08bb8784445cc80049a214'
+  metadata.gz: d42e71c6b6c9a94643af9f394f9467283d0465ef25cb1862a3be8dc0a9f8b94f4592398f55a1816a55fd9e1d1412b6112a0cb11fc842c1366ecba27963f7b34a
+  data.tar.gz: 88f941e7429c0ef0469d104de914a6e872153a64317f2177329c7f34acbc9b90895846f351fe8d38f77f52fa8198e70ea4512b3eebe728710835f1849b556c8f

data/.claude/skills/plutonium-async-interactions/SKILL.md

@@ -19,7 +19,7 @@ For everything about the interaction itself (inputs, validation, outcomes, `exec
 - **Permissions are re-derived at perform time, never replayed from dispatch.** The job rebuilds `(initiator, tenant)` from the row and re-checks the policy scope and predicate per target, immediately before each `perform_on`. A permission revoked mid-run stops applying to what's left. Both failure directions (scope, predicate) fail closed (refuse/report), never open.
 - **Register `Run` as a resource per portal.** Its show page IS the progress page, and other resources' index pages get a "runs in progress" banner for free. Nothing renders without registration.
 - **Read `outcome`, never bare `state`, when displaying a run's result.** A `:continue` run that under-applied still has `state == "completed"`; only `outcome` says `"completed_with_errors"`.
-- **Long work must call `heartbeat!`.** `stall_after` measures SILENCE, and the executor only writes per target, so opaque `perform` writes nothing at all between claim and finish. An opaque run longer than `stall_after` is reaped and, having no `handled_target_ids`, re-run from scratch. Call `heartbeat!` inside the loop. It also raises `StaleObjectError` if another worker took the run over, which for opaque work is the only way to find out.
+- **Long work must call `heartbeat!`.** `stall_after` measures SILENCE, and the executor only writes per target, so opaque `perform` writes nothing at all between claim and finish. The same holds for `pre_check`. An opaque run longer than `stall_after` is reaped and, having no `handled_target_ids`, re-run from scratch. Call `heartbeat!` inside the loop. It also raises `StaleObjectError` if another worker took the run over, which for opaque work is the only way to find out.
 - **A crashed/stalled run does not auto-heal.** Nothing revisits a `"running"` row on its own. `pu:async_interactions:install` schedules `Plutonium::Interaction::Async::ReapJob` for you when Solid Queue is in the bundle; otherwise (or on another scheduler) you must schedule it yourself. Unscheduled, a crash mid-batch leaves that row stuck forever.
 
 ---
@@ -114,6 +114,44 @@ end
 
 `backend:` and `uploader:` come off the attribute's `input` declaration, exactly as in a wizard step: `input :import_file, as: :uppy, uploader: Catalog::ImportUploader`. The uploader's `Attacher.validate` rules run when the interaction validates, so a bad file **fails the form** rather than surfacing as a run failure the submitter never sees. Where no `backend:` is declared: `config.async_interactions.attachment_backend` → `config.attachment_backend` → auto-detect.
 
+## Checking input before processing (`pre_check`)
+
+For checks too slow for the request (every row of a large file, lookups per row), define `pre_check` in the run. It runs in the job before any work; `reject` records a problem and keeps going (`return` yourself where nothing after it makes sense):
+
+```ruby
+# require "csv" at the top of the file
+async do
+  def pre_check                     # targeted runs: def pre_check(records)
+    each_row do |row, line|
+      reject "line #{line}: title is missing" if row["title"].blank?
+    end
+  rescue CSV::MalformedCSVError => e
+    reject "the file is not valid CSV: #{e.message}"
+  end
+
+  def perform                       # one transaction: an opaque run restarts from scratch after a reap
+    Task.transaction { each_row { |row, _line| Task.create!(title: row["title"]) } }
+  end
+
+  private
+
+  # Whole file, UTF-8, BOM stripped: the stored file comes back as binary.
+  def each_row
+    text = attachment(:import_file).download.force_encoding(Encoding::UTF_8).delete_prefix("\uFEFF")
+    CSV.parse(text, headers: true).each.with_index(2) do |row, line|   # header is line 1
+      yield row, line unless row.fields.all?(&:blank?)
+    end
+  end
+end
+```
+
+- Any rejection: run ends `failed`, `outcome == "rejected"`, problems on the progress page, no work done.
+- An exception in `pre_check` is a plain `failed`, not `rejected`. A wrong-arity `pre_check` fails the run naming the expected signature.
+- `config.async_interactions.max_rejections` (default 100) caps stored problems; the rest become one "and N more problems were found" entry.
+- It re-runs on resume, so it must only read (a resumed targeted run skips it once a target was applied). Long checks must `heartbeat!`.
+- `reject` outside `pre_check` raises.
+- Full version: `docs/reference/behavior/async-interactions.md`, "Checking input before processing".
+
 ## Registering the Run resource
 
 Use the generator, per portal. Never hand-write the route/controller:
@@ -144,7 +182,8 @@ Registering gets you, for free:
 
 - **Progress page.** The show page IS the progress page, self-polling while `pending`/`running`, and stops carrying the poll once settled (a finished run is a static page, not an eternal background request per viewer).
 - **Self-refreshing index.** The runs index polls on the same terms, one frame around the whole collection, armed only while some run is still working. One request per interval whatever the page size, and it re-fetches the current URL so filters, sort and page survive. No action needed on your part.
-- **Running banner.** Any OTHER registered resource's index lists in-progress runs targeting it, above the collection, scoped through the same `authorized_resource_scope` every cross-resource read uses (a run in another tenant can't surface). If a `resource_class` is registered in a portal that never registered `Run`, the banner is skipped there instead of raising while building a link to a nonexistent route. No action needed on your part.
+- **Running banner.** Any OTHER registered resource's index lists in-progress runs targeting it, above the collection, plus the viewer's own runs that finished within `config.async_interactions.recent_runs_window` (default 10 minutes, at most 5) with their outcome, so a fast or rejected run is still visible after the dispatch redirects back to the index. Both are scoped through the same `authorized_resource_scope` every cross-resource read uses (a run in another tenant can't surface). If a `resource_class` is registered in a portal that never registered `Run`, the banner is skipped there instead of raising while building a link to a nonexistent route. No action needed on your part.
+- **`interaction_label`.** A block-declared run (`<Interaction>::Run`) is titled by its interaction's label (`"Archive all (async) #19"`): its `presents label:`, else the class name without the `Interaction` suffix. A standalone run class falls back to its own name. An action-level `label:` or `plutonium.actions.*` translation does NOT reach the run (it does not know which action started it), so label the interaction with `presents label:` when the button and the run should match. The show page/table read `interaction_label` rather than the STI `type`.
 - **`target_label`.** The show page/table read `run.target_label` (`model_name.human`, e.g. `"Post"`) rather than the raw `target_type` string (`"Blogging::Post"`).
 - **Tenant scoping via `associated_with`.** Filters on the tenant the run was dispatched in (recorded on the row), because the two tenant columns are polymorphic and the generic object-graph scope can't walk them.
 

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

@@ -1358,6 +1358,19 @@ default_sort :created_at, :desc
 default_sort { |scope| scope.order(featured: :desc, created_at: :desc) }
 ```
 
+## Pagination count
+
+Each index page load runs a `COUNT(*)` for the total. On a table with millions of rows that count can take longer than the page query itself. Cap it or turn it off per resource:
+
+```ruby
+class TransactionDefinition < ResourceDefinition
+  pagination count: 10_000   # count at most 10,000 rows; past that the total reads "10000+"
+  pagination count: false    # no COUNT query; previous/next navigation only
+end
+```
+
+The global default is `config.pagination = {count: :exact}`. A cap stops counting early only when many rows match: a filter that matches few rows still scans for them, so index the filtered column. Pages past the cap are out of range. To decide per request, override the private `pagination_count` method in the controller.
+
 ## URL Parameters
 
 ```

data/.ruby-version

@@ -1 +1 @@
-3.4.1
+4.0.9

data/CHANGELOG.md

@@ -2,6 +2,43 @@
 
 All notable changes to this project will be documented in this file.
 
+## [0.70.0] - 2026-10-26
+
+### Bug Fixes
+
+- Color meta badges from the field's declared colors
+
+### Features
+
+- Pin links above the icon rail's footer with footer_menu
+- Show a menu item's trailing badge in the icon rail
+- Cap or skip the index COUNT with pagination count: ([#188](https://github.com/radioactive-labs/plutonium-core/issues/188))
+
+### Miscellaneous Tasks
+
+- Move to Ruby 4.0.9 and test on 3.4 and 4.0 ([#187](https://github.com/radioactive-labs/plutonium-core/issues/187))
+- Compress docs images and shrink the logo ([#189](https://github.com/radioactive-labs/plutonium-core/issues/189))
+
+## [0.69.0] - 2026-10-15
+
+### Bug Fixes
+
+- Link collection pages without a record back to the resource index in breadcrumbs
+- Vendor Font Awesome 4 so its .sr-only stops overriding Tailwind utilities
+- Answer turbo-stream redirects with a stream visit, held to the open-redirect check
+- Perform opaque runs dispatched from a resource index
+
+### Features
+
+- Drop the Interaction suffix from default labels
+- Name runs by their interaction, show progress as one cell
+- Check a run's input before processing with pre_check
+- Clear finished SolidQueue jobs and gate VACUUM on free pages in pu:lite:maintenance
+
+### Miscellaneous Tasks
+
+- Update gemfiles
+
 ## [0.68.0] - 2026-10-14
 
 ### Bug Fixes

data/CLAUDE.md

@@ -323,6 +323,17 @@ mode, icon rail collapsed (`localStorage.theme = 'light'`,
 generated titles read as broken data). Crop dead space with `magick`. Store under
 `docs/public/images/<section>/`.
 
+Compress every PNG before committing: `docs/` ships inside the gem, so each
+screenshot is in every install.
+
+```bash
+pngquant --quality=80-95 --speed 1 --strip --skip-if-larger --ext .png --force <file>.png
+```
+
+Reuse an existing image rather than copying it into a second folder. Full-size
+brand sources live in `brand/` (excluded from the gem); `app/assets/plutonium.png`
+is the 512px compressed copy.
+
 ## Settled Decisions (do not re-litigate)
 
 - **SQLite for the dummy app** across all environments; production is multi-db

data/SECURITY.md

@@ -12,7 +12,7 @@ please upgrade before reporting an issue to confirm it still reproduces.
 
 | Version | Supported          |
 | ------- | ------------------ |
-| Latest release (`0.68.x`) | :white_check_mark: |
+| Latest release (`0.70.x`) | :white_check_mark: |
 | Older releases | :x: |
 
 ## Reporting a Vulnerability