janela 0.11.0 → 0.13.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 2079a652eafc71edc8c31227d2c09ef8e795a38da68b8ec6c18de89732a54f97
-  data.tar.gz: b024b3337cd75f63619ff8cb844a6887e2b4ecb0bf7cb510ceb2fea789537b03
+  metadata.gz: 76a888911baddb25729442ecf07cf8975467f05792eb1881d1a6c9ec1c3d05e9
+  data.tar.gz: e3718fafdaf889aed3fd4459b722e5ed0db5b39ecffb771cb4c5599c34c0bfb9
 SHA512:
-  metadata.gz: 949892c698668e8a170d5c2dedadeff080f62aee007cf86a89537c62eb304fd75fa479e4d4eb9635e18619794e3003541d90035711e6aa1304771d4f84a1d954
-  data.tar.gz: e445c3469c68b7f9b5e20d384bbd0589b0ec98f5beeacdbbb48b0f371e0f67771448d42b8240dc859c5fe11e5459d66b57f7652cb2106e56346adb49fd453693
+  metadata.gz: 3cb99e213c2afbf7e7a570fe4c02b34f1c07fb6d7dc70e0d0fad4753c50264a3466e6f7661c52fb545a4ffa6b50a8fb1b63a6eed5e3ecbd4dd6b7670f21ed9ec
+  data.tar.gz: d9fbcebdd34dd825aeb98c98dc449ce92be38b50b1839e83c838730c0c5e9c3258e42d8410d818702032642496688279c0a9e1c361621d228d50dd7e92b9ea6d

data/CHANGELOG.md

@@ -5,6 +5,45 @@ All notable changes to this project will be documented in this file.
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [0.13.0] - 2026-10-02
+
+### Changed
+
+- **The vitral theme draws charts in its own colours.** Bars, doughnut slices and pie slices were the stained glass accent for the first and Janela's neutral set for the other seven; vitral now sets all eight, as soft glass tones: a muted blue, sage, lavender, plum, clay, teal, ochre and dusty rose, with the grey of lead came for anything past the eighth. A first version in saturated jewel tones was rejected by eye as a rainbow against the pale tiles, so these sit at about half the chroma and lean on differences in lightness. They were chosen as an ordered set and checked together, with adjacent colour-vision separation of 12.4 (the target is 8) and adjacent normal-vision separation of 15.8 (the floor is 15). Slot 1 is a softer blue of vitral's own; `--janela-accent` stays the stronger blue for what is selected. A host that uses vitral and has set its own `--janela-series-N` keeps them. No action needed (ADR 026, #67).
+
+### Fixed
+
+- **The engine's own chart partial compiles through Herb.** Rails 8.2 renders HTML templates through Herb, which refuses ERB that writes an attribute's name or sits in attribute position, and `janela/queries/_query.html.erb` did both for the chart's canvas. It is now one `tag.canvas` call that renders the same attributes, so a host on the 8.2 defaults is not broken by Janela's own template. A host that has copied that partial keeps its copy, which Herb will reject if it still has ERB in an attribute position: `bin/rails app:herb:check` on Rails 8.2 lists any. No action needed otherwise.
+- **The doctor no longer calls `Janela::PanesController` a stale name.** It reported an error that the name "is now `Janela::QueriesController`", true from 0.7 until 0.12 added a `Janela::PanesController` back as the stored-pane form's controller, which owns `pane_params`. A host patching that form was told to move the patch to a controller with no `pane_params`, which would have silently stopped its extra pane param saving, and the error failed `janela:doctor` until the check was silenced. It is now a warning that says what the name means today. The check is still silenced by `stale-identifiers`, and `Janela::SnapshotPanesController` is unchanged (#74).
+
+### Added
+
+- **Tools for an agent: `Janela::Tools`.** An agent in a host had no way to read or arrange a dashboard except by writing `Janela::Frame` and `Janela::Pane` rows from a console. `Janela::Tools.new(scope:)` is plain Ruby with a name, a description and a JSON schema for each of `describe_vocabulary`, `list_frames`, `get_frame` and `read_pane`, and with `write: true`, `add_pane`, `update_pane`, `remove_pane` and `move_pane`. `scope:` is required and takes a model class and returns a relation, the answer `policy_scope` gives, so a read or a change reaches only what the caller may see; leaving it out raises `Janela::Unscoped` when the tools are built. Janela registers nothing, serves nothing and depends on no MCP library: [docs/agents.md](docs/agents.md) shows the adapter for the official Ruby SDK, which Janela's own tests run. No action needed (ADR 053, #73).
+
+- **The doctor notices a skipped migration, not only a missing table.** `bin/rails janela:doctor` reported a missing `janela_panes` and said nothing when the table was there but a release had added a column to it, so a host that upgraded and did not run `db:migrate` was told all was well, and met an error the first time a pane form or a stored pane read `height`, `prominence` or `companions`. A new `unmigrated-columns` check lists the missing columns by table and names the two commands. It can be silenced by that name like any other (ADR 021, ADR 035).
+
+## [0.12.0] - 2026-10-01
+
+### Added
+
+- **A table can carry companion columns.** `janela_pane Order, :expedited_rate, by: :customer, companions: [:orders, :region]`, or the same on a stored pane from the pane form, adds up to three columns beside the label, each a measure or a dimension the model declares, under a new header row. A measure companion is its own number, formatted as it declares: a rate can sit beside the count behind it, which answers whether 75% came from four reviews or forty. A dimension companion shows a value only where every row of that label's group shares one and is blank where they differ, because the alternatives were measured and wrong: grouping by it showed a label twice, and picking one showed an arbitrary value as fact. Order, limit, filters and clicking a label stay the primary measure's; only a table draws companions, a stored snapshot shows the base table, and a time pane may carry measures but not dimensions. Each companion is one more query, hence at most three. It travels in the pane URL as `companions[]=`. Stored panes need a migration; see `UPGRADING.md` (ADR 051, #34).
+
+- **A single value can say how prominent it is.** `janela_pane Order, :orders, prominence: 3`, or the same on a stored pane from the pane form, takes one of three steps: 1 is a footnote at `1.25rem`, 2 is what every value already is at `2rem`, and 3 is the hero number at `3.5rem`. The label stays small at every step. Until now every headline number was the same size, so a host that wanted one count larger wrote CSS against `janela-value-number` for each pane, and a stored pane could not say it at all. (The issue also asked for default typography and a hideable label; both had already shipped, with #15 and #26.) With none set nothing changes, and a table, a chart and a ring ignore one. The step travels in the pane URL as `?prominence=`. Stored panes need a migration; see `UPGRADING.md` (ADR 050, #31).
+
+- **A `ratio:` measure, for the share of rows where a boolean column is true.** `measure :expedited_rate, ratio: :expedited` reads as `31.2%` in a table cell, a single value and a chart tooltip, and orders, gap fills, cross-filters and snapshots like any other measure. Averaging a boolean column never worked: ActiveRecord casts the answer back to `true`, and it does so for 0% as well, so no rate could read as anything else. Janela refused that, correctly, and the refusal had nowhere to point; it now names `ratio:`. A row where the column is null is left out of the average, as SQL's `AVG` leaves it, and is not counted as a no. The number stored, ordered and compared is the fraction (`0.3119`); only the text is a percentage, to one decimal place unless you declare `precision:`. A ratio takes no `prefix:` or `suffix:` (it raises, so `31.2%%` cannot happen) and no condition form (ADR 038, #27).
+
+- **A value and (none) can be selected together.** With a chart or table of A, B and (none), Ctrl or Cmd click on (none) beside A now shows the rows that are A or have nothing, where before selecting (none) cleared A. A plain click still replaces the selection, and Ctrl or Cmd click on (none) again takes it out. It is the union of the two in the URL you already have, `q[channel_in][]=web&q[channel_null]=1`, and the same for a `where:` or `default_where` naming both. That pair used to return no rows at all, because Ransack ANDs what it is given, so nothing that worked depended on it. Two exclusions, `not_in` with `not_null`, still mean neither (ADR 049, #69).
+
+- **A chart pane can say how tall it is.** `janela_pane Order, :revenue, by: :placed_on, as: :line, height: 2`, or the same on a stored pane from the pane form, takes one of five steps from about 96px to about 448px, drawn as a box of that height around the chart with the chart filling it. Until now a chart was twice its width up to a cap of 20rem, and a host could lower it from outside but not set it, so a stored frame's only way to a shorter row of charts was to swap them for tables. With no height nothing changes, and a ring, a table or a single value ignores one, so switching a pane's renderer never invalidates it. The step travels in the pane URL as `?height=`. Stored panes need a migration; see `UPGRADING.md` (ADR 047, #24).
+
+### Changed
+
+- `Measure#sql_alias` is now `Measure#order_by`, because a ratio has no column alias to name and is ordered by its expression. Internal, with one call site in the gem, so nothing a host declares changes; a fork that called it will need the new name (ADR 038).
+
+### Fixed
+
+- **A Sprockets host on importmap-rails no longer gets a 500 from `javascript_importmap_tags`.** Janela declared its stylesheets precompilable and never its JavaScript, so on Sprockets the first page that rendered the importmap raised `AssetNotPrecompiledError: Asset janela/frame_controller.js was not declared to be precompiled in production`, in development as much as production, and no setting turns it into a warning. The engine now declares the four assets its importmap pins, for a host that uses importmap: a Sprockets host that bundles its own JavaScript is untouched, and so is a Propshaft one. If you worked around it with a manifest entry of your own, you can delete it, and nothing breaks if you leave it (ADR 004, #14).
+
 ## [0.11.0] - 2026-09-30
 
 ### Added
@@ -18,7 +57,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 ### Changed
 
 - **A range in the URL no longer narrows the time pane it names.** `q[placed_on_gteq]` and `q[placed_on_lt]` from a reader now scope every other pane and leave a time pane on that dimension showing its whole series with the range marked, where before it narrowed that pane's own series. A range a host fixes with `where:` or `default_where` still narrows it. See `UPGRADING.md` (ADR 045).
-- **A bar chart's bars are no longer all one colour.** Each bar is now drawn in the palette colour for its position, so a host that has seen every bar in `--janela-accent` will see the first bar in the accent and the rest in new colours. A line chart is unchanged. To keep the old look, set `--janela-series-2` to `--janela-series-8` to your accent; see `UPGRADING.md` (ADR 046).
+- **A bar chart's bars are no longer all one colour.** Each bar is now drawn in the palette colour for its position, so a host that has seen every bar in `--janela-accent` will see the first bar in the accent and the rest in new colours. A line chart is unchanged. To keep the old look, set `--janela-series-2` to `--janela-series-8`, and `--janela-series-other`, to your accent; see `UPGRADING.md` (ADR 046).
 
 ### Fixed
 
@@ -234,6 +273,8 @@ First alpha, installed from GitHub for testing in a single host application.
 - Only models that declare a `janela` block are addressable over HTTP.
 - ADRs 001 to 004 in `docs/decisions/`, shipped inside the gem.
 
+[0.13.0]: https://github.com/retail-tasker/janela/releases/tag/v0.13.0
+[0.12.0]: https://github.com/retail-tasker/janela/releases/tag/v0.12.0
 [0.11.0]: https://github.com/retail-tasker/janela/releases/tag/v0.11.0
 [0.10.0]: https://github.com/retail-tasker/janela/releases/tag/v0.10.0
 [0.9.0]: https://github.com/retail-tasker/janela/releases/tag/v0.9.0

data/README.md

@@ -6,7 +6,7 @@ PowerBI-style dashboards and cross-filtering slicers, native to Rails and Active
 
 ## First principle
 
-Janela is a PowerBI-style library built on Ruby and Stimulus, meant to drop onto any Ruby on Rails application. No JS framework, no build step of its own, no separate frontend app. Just a gem you add to an existing Rails app's Gemfile and two Stimulus controllers that ship with it.
+Janela is a PowerBI-style library built on Ruby and Stimulus, meant to drop onto any Ruby on Rails application. No JS framework, no build step of its own, no separate frontend app. Just a gem you add to an existing Rails app's Gemfile and two Stimulus controllers that ship with it, plus an optional third for the theme.
 
 ## Why
 
@@ -14,7 +14,7 @@ Every Rails BI option today is one of:
 
 - **SQL-first** (Blazer). Powerful, but the query is a black box to your models and associations.
 - **Admin-panel-first** (RailsAdmin, ActiveAdmin, Motor Admin, Avo). Association-aware filtering, but built for CRUD, not for composing multiple charts that filter each other.
-- **A dead end for cross-filtering**. None of the above let clicking one chart re-scope every other chart on the page. That's the actual PowerBI/Tableau slicer experience, and nothing in the Rails ecosystem does it as a first-class citizen.
+- **A dead end for cross-filtering**. None of the above are built around clicking one chart to re-scope every other chart on the page. That's the PowerBI/Tableau slicer experience, and it's what Janela is for.
 
 Janela's bet: the same dashboard definition should serve two audiences without being two systems.
 
@@ -23,11 +23,11 @@ Janela's bet: the same dashboard definition should serve two audiences without b
 
 ## Installation
 
-Janela is an alpha on [rubygems.org](https://rubygems.org/gems/janela). It has two halves, a gem and an npm package:
+Janela is an alpha on [rubygems.org](https://rubygems.org/gems/janela). It is a gem, plus a JavaScript package installed from GitHub if your app bundles its JavaScript. An app on importmap-rails needs only the gem. It needs Rails 8.0+ and Ruby 3.3+ (see Requirements below).
 
 ```ruby
 # Gemfile
-gem "janela", "~> 0.11"
+gem "janela", "~> 0.13"
 ```
 
 ```ruby
@@ -35,6 +35,15 @@ gem "janela", "~> 0.11"
 mount Janela::Engine => "/dashboards"   # or /reports, or wherever you like
 ```
 
+Janela reads nothing until your `ApplicationController` says what a visitor may see, so the first visit to `/dashboards` raises `Janela::Unscoped` without it. An app with nothing to hide answers once:
+
+```ruby
+# app/controllers/application_controller.rb
+private def policy_scope(model) = model.all
+```
+
+If you use stored frames or snapshots, run `bin/rails janela:install:migrations && bin/rails db:migrate` (see Frames below), and finish with `bin/rails janela:doctor`, which checks the install and says what to fix. The rest of this section is the JavaScript.
+
 Then register the two Stimulus controllers. How depends on how your app ships JavaScript.
 
 **With jsbundling (esbuild, bun, webpack):**
@@ -55,7 +64,7 @@ The chart controller imports `chart.js`, which is a peer dependency: add `chart.
 
 **With importmap-rails:**
 
-Nothing to install. The engine pins `janela/frame_controller`, `janela/chart_controller` and a vendored `chart.js` for you (your own `chart.js` pin wins if you have one). Register the controllers:
+Nothing to install. The engine pins `janela/frame_controller`, `janela/chart_controller` and a vendored `chart.js` for you (your own `chart.js` pin wins if you have one), and declares them precompilable, so it works the same on Propshaft and on Sprockets. Register the controllers:
 
 ```js
 // app/javascript/application.js
@@ -158,6 +167,14 @@ Precision defaults to what the schema already says. Counting rows has no decimal
 
 Formatting is rendering, never rounding. The number itself reaches a snapshot and an order clause at full precision, so a snapshot taken last month reads back under a format you declare today.
 
+**The share of rows where something is true** is a ratio, and it has a measure of its own, because averaging a boolean column does not work: ActiveRecord casts the answer back to `true` (so even 0% reads as `true`), and Janela refuses it.
+
+```ruby
+measure :expedited_rate, ratio: :expedited                       # 31.2%
+```
+
+It takes a boolean column, leaves rows where the column is null out of the average (as SQL's `AVG` does) rather than counting them as no, and orders, gap fills, cross-filters and snapshots like any other measure. The number it stores is the fraction, `0.3119`, and only the text a reader sees is a percentage, to one decimal place unless you declare `precision:`. It takes no `prefix:` or `suffix:`, since it is always a percentage, and it takes no condition (`ratio: { status: "paid" }`): where a column is not already a yes or no fact, a dimension gives you the split (ADR 038).
+
 Then query them:
 
 ```ruby
@@ -211,6 +228,12 @@ A pane with no `by:` is the measure's single total, the KPI tile. `limit: 10` ke
 
 A doughnut or a pie is drawn on the server as SVG with a legend of buttons beside it, so it is in the page before any JavaScript runs and can be operated from the keyboard through the legend. Bars, doughnut slices and pie slices are drawn in a palette of eight colours by position, first to eighth, and every value after the eighth in one neutral, so a ring suits a handful of values: `limit: 8` keeps it readable. A ring cannot show a negative value, so a pane with one is drawn as a table and says so. The palette is `--janela-series-1` to `--janela-series-8` and `--janela-series-other` in [docs/theming.md](docs/theming.md) (ADR 046).
 
+**Height.** A bar or line chart is drawn at twice its width, up to 20rem, unless the pane says how tall it is: `height: 1` to `height: 5`, from about 96px to about 448px at the default spacing (`janela_pane Order, :revenue, by: :placed_on, as: :line, height: 2`). Five steps rather than pixels, the same as `span` and `gap`, so a stored pane takes it too, from the pane form, and a host that wants an exact figure sets it against `janela-h-2` in its own CSS. With no height nothing changes. A ring, a table and a single value ignore one (ADR 047).
+
+**Prominence.** A single value is `2rem` unless the pane says how much it matters: `prominence: 1` is a footnote at `1.25rem`, `2` is what it already is, and `3` is the hero number at `3.5rem` (`janela_pane Order, :orders, prominence: 3`). Three steps rather than a length, the same as `span` and `height`, so a stored pane takes it too, from the pane form. The label stays small at every step. With none set nothing changes, and a table, a chart and a ring ignore one (ADR 050).
+
+**Companion columns.** A table can carry up to three more columns beside its label, each a measure or a dimension the model declares: `janela_pane Order, :expedited_rate, by: :customer, companions: [:orders, :region]` reads as customer, expedited rate, orders and region, under a header row. A measure companion is its own number, formatted as it declares, so a rate can sit beside the count behind it: 75% of four and 75% of forty are different things to act on. A dimension companion shows a value only where every row of that label's group shares one, and is blank where they differ, since grouping by it would show a label twice and picking one would show an arbitrary value as fact. Order, limit, filters and clicking a label are the primary measure's and are unchanged. Only a table draws companions, a stored snapshot shows the base table, and a time pane may carry measures but not dimensions. Each companion is one more query, which is why it is three at most (ADR 051).
+
 **Reconfiguring a pane in place**, a renderer toggle, a granularity switcher, a "show top 20" control, takes two things: name the pane with `id:`, then ask the frame to repoint it.
 
 ```erb
@@ -308,7 +331,7 @@ The engine serves an index and a page per frame at the mount root, so you can in
 
 No model's route key is all digits, so a frame id and a pane URL cannot be confused. Both pages read through `policy_scope(Janela::Frame)`, so a frame your scope does not return is a 404 rather than a page, and so is a pane row under it.
 
-These pages render in Janela's own minimal layout, which loads the gem's stylesheet and nothing else. It does not load Turbo or Stimulus, because those come from your bundler and the engine cannot name them. So Janela's own pages are correct, styled, **static** dashboards: every pane is rendered inline and the numbers are right, filters in the URL apply, and nothing cross-filters when you click. A chart pane needs Chart.js, so on these pages it draws nothing; put a frame on your own page, where your JavaScript is, for the interactive version.
+These pages render in Janela's own minimal layout, which loads the gem's stylesheet and nothing else. It does not load Turbo or Stimulus, because those come from your bundler and the engine cannot name them. So Janela's own pages are correct, styled, **static** dashboards: every pane is rendered inline and the numbers are right, filters in the URL apply, and nothing cross-filters when you click. A chart pane needs Chart.js, so on these pages it renders as its table (ADR 018); put a frame on your own page, where your JavaScript is, for the interactive version. Each page links back to your application's root, which you can rename in your own locale file under `janela.actions.home`.
 
 The noun in the headings is `Janela::Frame.model_name.human`, so rename it in your own locale file rather than in a setting:
 
@@ -349,9 +372,9 @@ A host with no tenancy defines nothing, gets a nil owner, and is correct: nothin
 
 ### Filters and clicks
 
-The dashboard's filters live in the page URL as the same `q[...]` parameters, so a reload keeps them and a filtered dashboard is a link you can send: `/reports/orders?q[status_in][]=paid` renders filtered before any JavaScript runs. A pane ignores filters on its own dimension, so clicking a value re-scopes the rest of the dashboard rather than collapsing the pane you clicked. Time panes re-scope with the others but are not click sources yet; drill-down is the next decision. Every selected value is marked `aria-pressed="true"` on tables and drawn solid against faded siblings on charts, so it can be styled and read.
+The dashboard's filters live in the page URL as the same `q[...]` parameters, so a reload keeps them and a filtered dashboard is a link you can send: `/reports/orders?q[status_in][]=paid` renders filtered before any JavaScript runs. A pane ignores filters on its own dimension, so clicking a value re-scopes the rest of the dashboard rather than collapsing the pane you clicked. Clicking a bucket on a time pane filters the others to the range it covers. Every selected value is marked `aria-pressed="true"` on tables and drawn solid against faded siblings on charts, so it can be styled and read.
 
-**Selecting more than one.** Ctrl or Cmd click adds a value to the selection and takes it out again, leaving the rest alone, which is how every list in every operating system already behaves. A plain click selects one value and replaces whatever was selected, or clears the dimension if that value was the only one. It works the same on a chart. All of it works from the keyboard too: a value is a real `<button>`, so Enter is a click and Ctrl or Cmd with Enter adds. `Escape` clears the frame's filters, and those are the only two keys Janela binds, both only while focus is inside the frame, because a single letter belongs to your application and to any text field on the page (ADR 024). A pane with no matching rows renders a `.janela-empty` paragraph. A group whose dimension is null is labelled `(none)` and filters with Ransack's null predicate rather than an empty string. Only models that declare a `janela` block can be requested over HTTP.
+**Selecting more than one.** Ctrl or Cmd click adds a value to the selection and takes it out again, leaving the rest alone, which is how every list in every operating system already behaves. A plain click selects one value and replaces whatever was selected, or clears the dimension if that value was the only one. It works the same on a chart. The (none) group, the rows that have nothing there, is a member of the selection like any value: Ctrl or Cmd click it beside a value and the panes show the rows that have that value or nothing (`q[channel_in][]=web&q[channel_null]=1`), where `not_in` and `not_null` together still mean neither (ADR 049). All of it works from the keyboard too: a value is a real `<button>`, so Enter is a click and Ctrl or Cmd with Enter adds. `Escape` clears the frame's filters, and those are the only two keys Janela binds, both only while focus is inside the frame, because a single letter belongs to your application and to any text field on the page (ADR 024). A pane with no matching rows renders a `.janela-empty` paragraph. A group whose dimension is null is labelled `(none)` and filters with Ransack's null predicate rather than an empty string. Only models that declare a `janela` block can be requested over HTTP.
 
 ### Pane URLs
 
@@ -404,7 +427,7 @@ Render a stored pane the same way you render a live one:
 <%= janela_snapshot_pane @snapshot, Order, :revenue, by: :status, as: :bar %>
 ```
 
-Inside a dashboard a pane is a Turbo Frame and carries no layout at all. Opened directly it renders in Janela's own minimal layout, which deliberately loads no assets, because the gem cannot know your asset names or whether you bundle. A direct pane link therefore shows its numbers unstyled, and a chart pane shows nothing, since the chart needs Stimulus.
+Inside a dashboard a pane is a Turbo Frame and carries no layout at all. Opened directly it renders in Janela's own minimal layout, which loads the gem's stylesheet and none of your JavaScript, because the gem cannot know your asset names or whether you bundle. A direct pane link therefore shows its numbers styled, and a bar or line chart draws nothing, since the chart needs Stimulus. A table and a ring (which is drawn as SVG on the server) still show.
 
 To make direct pane links styled and chart-capable, give Janela a small layout of your own that loads your assets and nothing else:
 
@@ -473,25 +496,19 @@ Scoping is automatic when you use Pundit: `Janela::ApplicationController` calls
 
 **Multi tenancy** has its own guide: [docs/multi-tenancy.md](docs/multi-tenancy.md). It covers what goes through your scope, worked wiring for Pundit, acts_as_tenant and CanCanCan, what owns a frame the analyst creates, and what rows a scheduled snapshot freezes.
 
-### The pages Janela serves
+### Giving an agent access
 
-Mounting the engine gives you an index of frames and a page per frame with no
-work at all, which is enough to navigate on the day you install it:
+Frames and panes are rows, so an agent can arrange a dashboard if it has tools. Janela gives you the tool definitions as plain Ruby and leaves the registering to you, because your application knows who is asking and Janela does not (ADR 053):
 
-```
-/insights      every frame your policy scope returns
-/insights/3    one frame
-```
+```ruby
+tools = Janela::Tools.new(scope: ->(model) { policy_scope(model) })   # read only
+tools = Janela::Tools.new(scope: ->(model) { policy_scope(model) }, write: true)
 
-Both go through your `policy_scope`, so a frame another tenant owns is a 404. Each page carries a link back to your application's root, so they are not a dead end; rename it in your own locale file under `janela.actions.home`, or override the engine's layout if you want your whole navigation there.
+Janela::Tools.all          # name, description, input_schema, read_only
+tools.call("read_pane", pane_id: 4)
+```
 
-These pages load Janela's own stylesheet and nothing of yours, because the gem
-cannot know your asset names or bundler. Two consequences worth knowing. They
-do not cross-filter, since that needs Stimulus. And a pane whose row asks for a
-chart renders as its **table** here, because there is no chart runtime on the
-page and a table needs nothing: the same frame rendered in your own page with
-`janela_frame(@frame)` draws the chart. A renderer is a viewing choice, not part
-of the pane (ADR 018).
+`scope:` is required and is the same answer your `policy_scope` gives, so an agent reads and changes only what the person it acts for can. The read tools list the vocabulary and frames and read a pane's values. The write tools add, change, remove and move panes, and are off unless asked for. Janela serves no MCP endpoint, edits no configuration and depends on no MCP library; [docs/agents.md](docs/agents.md) shows the few lines that register them with the official Ruby SDK.
 
 ### Checking an installation
 
@@ -544,11 +561,11 @@ Deliberately out of scope: natural-language query, a separate data warehouse, a
 
 ## Status
 
-**v0.11.0 alpha.** The measures/dimensions DSL, time dimensions, cross-filtering with multi-selection, bar, line, doughnut and pie charts, pane URLs, shareable dashboard URLs, snapshots, database-backed frames found by owner and key, panes that hold words or a host partial as well as a query, a host-fixed filter no click can remove and a frame's own permanent one beside it, STI subclasses, the engine's own pages for reading and editing them and the optional vitral theme work and are covered by unit and real-browser tests, with the classes a theme may target documented in [Theming Janela](docs/theming.md). Not yet built: a visual editor, drill-down on time panes, other chart types. [Vista](docs/roadmap.md), the roadmap, says what 1.0 means and which of these are in it; open work is in [GitHub Issues](https://github.com/retail-tasker/janela/issues).
+**v0.13.0 alpha.** The measures/dimensions DSL, time dimensions, cross-filtering with multi-selection, bar, line, doughnut and pie charts, pane URLs, shareable dashboard URLs, snapshots, database-backed frames found by owner and key, panes that hold words or a host partial as well as a query, a host-fixed filter no click can remove and a frame's own permanent one beside it, STI subclasses, the engine's own pages for reading and editing them, tools an agent can use to read and arrange a dashboard, and the optional vitral theme work and are covered by unit and real-browser tests, with the classes a theme may target documented in [Theming Janela](docs/theming.md). Not yet built: a visual editor, and narrowing a time pane's own granularity by clicking one of its buckets (a click on a bucket does filter the others). [Vista](docs/roadmap.md), the roadmap, says what 1.0 means and which of these are in it; open work is in [GitHub Issues](https://github.com/retail-tasker/janela/issues).
 
 ## Development
 
-Janela is a Rails engine. It ships with a minimal host application in `test/dummy` that mounts the engine at `/janela`, so the gem is always developed and tested against a real Rails app with a real (SQLite) database.
+Janela is a Rails engine. It ships with a minimal host application in `test/dummy` that mounts the engine at `/dashboards`, so the gem is always developed and tested against a real Rails app with a real (SQLite) database.
 
 After checking out the repo, run `bin/setup` to install dependencies. Then:
 
@@ -561,7 +578,13 @@ bin/rails console     # console inside the dummy app, engine loaded
 
 ## Contributing
 
-Bug reports and pull requests are welcome on GitHub at https://github.com/retail-tasker/janela. Pull requests are reviewed on the merits of the diff, whether a person or an agent wrote them. Contributors are expected to adhere to the [code of conduct](https://github.com/retail-tasker/janela/blob/main/CODE_OF_CONDUCT.md).
+Bug reports and pull requests are welcome on GitHub at https://github.com/retail-tasker/janela. Pull requests are reviewed on the merits of the diff, whether a person or an agent wrote them. [CONTRIBUTING.md](https://github.com/retail-tasker/janela/blob/main/CONTRIBUTING.md) says how to run the tests, when a change needs a decision record first, and what to write down for the people who upgrade. Contributors are expected to adhere to the [code of conduct](https://github.com/retail-tasker/janela/blob/main/CODE_OF_CONDUCT.md).
+
+## Support and security
+
+Janela is pre-1.0 and its public surface can still move between releases, with an upgrade note each time. Issues and pull requests are read when the maintainers can get to them; there is no support contract and no promised response time.
+
+To report a vulnerability, use the private form described in [SECURITY.md](https://github.com/retail-tasker/janela/blob/main/SECURITY.md) and not a public issue. Releases are cut by the two maintainers and published from a protected workflow; the steps are in [RELEASING.md](https://github.com/retail-tasker/janela/blob/main/RELEASING.md).
 
 ## License
 

data/UPGRADING.md

@@ -12,6 +12,57 @@ bin/rails janela:doctor
 
 It reads your application and lists what still needs changing.
 
+## 0.12.0 to 0.13.0
+
+No migration, and nothing you must change. Two things you may see.
+
+**The doctor treats `Janela::PanesController` as a warning.**
+
+0.7 renamed it to `Janela::QueriesController`, and 0.12 added a
+`Janela::PanesController` back as the stored-pane form's controller, which owns
+`pane_params`. The doctor used to call every mention of the name an error. It now
+warns, and says what the name means today. If you patch the form's
+`pane_params`, leave it where it is. If you patched how a query renders, that
+patch belongs on `Janela::QueriesController`.
+
+**A host that copied `janela/queries/_query.html.erb` should check it.**
+
+Rails 8.2 renders HTML templates through Herb, which refuses ERB that writes an
+attribute's name or sits in attribute position. Janela's own copy of the partial
+no longer does either, so it compiles. A copy of yours keeps the old markup,
+which Herb will reject if it has ERB in an attribute position. On Rails 8.2:
+
+```bash
+bin/rails herb:check
+```
+
+lists what it rejects. On earlier Rails there is nothing to do.
+
+**Optional: tools for an agent.**
+
+`Janela::Tools` gives an agent the tools to read and arrange a dashboard. It is
+not on unless you build it, and nothing registers itself. See
+[docs/agents.md](docs/agents.md).
+
+## 0.11.0 to 0.12.0
+
+One migration step, if you use stored frames.
+
+**Take the pane migrations.**
+
+A pane can now carry a chart height (ADR 047), a single value a
+prominence (ADR 050) and a table companion columns (ADR 051).
+`janela_panes` gains a nullable `height`, a nullable `prominence` and a
+nullable JSON `companions`:
+
+```bash
+bin/rails janela:install:migrations
+bin/rails db:migrate
+```
+
+Every existing pane keeps all three nil and is drawn exactly as before. If you
+never use stored frames, there is nothing to do.
+
 ## 0.10.0 to 0.11.0
 
 No migration. Two things you may see.
@@ -44,7 +95,7 @@ in `--janela-series-2` to `--janela-series-8`, and every bar after the
 eighth in `--janela-series-other`. Until now every bar was the accent.
 Line charts are unchanged.
 
-If you want the old look, set the seven to your accent:
+If you want the old look, set the other eight to your accent:
 
 ```css
 :root {
@@ -530,6 +581,11 @@ Most applications do not.
 `Janela::Pane` is reserved for a database record in a later release,
 which is why the runtime object had to give the name up.
 
+`Janela::PanesController` was renamed in this table, and 0.12 added a
+`Janela::PanesController` back: the stored-pane form's controller, which owns
+`pane_params`. The doctor warns about the name without calling it an error,
+because only you know which one your code means.
+
 If you override Janela's view, move your copy from
 `app/views/janela/panes/` to `app/views/janela/queries/`.
 

data/app/assets/javascripts/janela/chart_controller.js

@@ -9,7 +9,7 @@ Chart.register(...registerables)
 // chart is destroyed on disconnect and rebuilt on connect.
 export default class extends Controller {
   static values = { type: String, labels: Array, values: Array, filters: Object, title: String,
-                    selected: Array, formatted: Array }
+                    selected: Array, formatted: Array, fixedHeight: Boolean }
 
   connect() {
     this.chart = new Chart(this.element, {
@@ -26,6 +26,11 @@ export default class extends Controller {
       },
       options: {
         animation: false,
+        // A pane with a height is drawn into a box of that height, and the
+        // aspect ratio has to be off for the chart to fill it (ADR 047). It
+        // is decided here, when the chart is made: patched onto a chart built
+        // with it on, it draws at the wrong size.
+        maintainAspectRatio: !this.fixedHeightValue,
         scales: { y: { beginAtZero: true } },
         // A line is clicked anywhere along its x position rather than on
         // the exact pixel of a point, which on a dense series is a few

data/app/assets/javascripts/janela/frame_controller.js

@@ -81,22 +81,32 @@ export default class extends Controller {
     if (range) return this.toggleRange(range)
 
     const additive = event.ctrlKey || event.metaKey || event.detail?.additive === true
-    const filters = { ...this.filtersValue }
-    const selected = this.valuesFor(filters, key).includes(String(value))
+    const held = this.filtersValue
+    const filters = { ...held }
+    const isNone = key.endsWith("_null")
+    const base = key.replace(/_(in|null|eq)$/, "")
+    const valueKey = isNone ? `${base}_in` : key
+    const heldValues = this.valuesFor(held, valueKey)
+    const holdsNone = this.valuesFor(held, `${base}_null`).length > 0
+    const selected = isNone ? holdsNone : heldValues.includes(String(value))
 
-    // The null group asks for rows that have nothing there, so it cannot be
-    // combined with a value: Ransack ands its conditions, and the pair matches
-    // no row at all. It is exclusive within its dimension instead.
     this.clearDimension(filters, key)
 
-    if (key.endsWith("_null")) {
-      if (!selected) filters[key] = "1"
+    // The null group is one more member of the selection, so a plain click
+    // replaces all of it and Ctrl or Cmd adds to it, values and null alike.
+    // Read together the two mean the union, which is the server's to say
+    // (ADR 049). Until then it was exclusive, because ANDed they match no row.
+    let values = additive ? heldValues : []
+    let none = additive ? holdsNone : false
+    if (isNone) {
+      none = !selected
     } else {
-      let values = additive ? this.valuesFor(this.filtersValue, key) : []
       values = selected ? values.filter((each) => each !== String(value)) : [ ...values, String(value) ]
-      if (values.length) filters[key] = [ ...new Set(values) ].sort()
     }
 
+    if (values.length) filters[valueKey] = [ ...new Set(values) ].sort()
+    if (none) filters[`${base}_null`] = "1"
+
     this.filtersValue = filters
   }
 

data/app/assets/stylesheets/janela.css

@@ -82,6 +82,11 @@
 .janela-value { margin: 0; display: flex; flex-direction: column; gap: calc(var(--janela-space) * 1); }
 .janela-value-label { font-size: 0.85rem; opacity: 0.7; }
 .janela-value-number { font-size: 2rem; font-weight: 600; font-variant-numeric: tabular-nums; }
+/* How prominent a single value is (ADR 050). Step 2 is what every value is
+   without one. The label stays the same small size at every step. */
+.janela-prominence-1 .janela-value-number { font-size: 1.25rem; }
+.janela-prominence-2 .janela-value-number { font-size: 2rem; }
+.janela-prominence-3 .janela-value-number { font-size: 3.5rem; }
 
 /* Words in a stored frame (ADR 039). A heading and paragraphs, spaced by the
    same unit as everything else and otherwise left to the page. */
@@ -92,7 +97,12 @@
 table.janela-pane { width: 100%; border-collapse: collapse; }
 table.janela-pane caption { text-align: left; font-weight: 600; margin-bottom: calc(var(--janela-space) * 2); }
 table.janela-pane td { padding: calc(var(--janela-space) * 1.5) 0; border-top: 1px solid var(--janela-line); }
-table.janela-pane td:last-child { text-align: right; font-variant-numeric: tabular-nums; }
+table.janela-pane td:not(:first-child) { text-align: right; font-variant-numeric: tabular-nums; }
+/* A companion column (ADR 051): a header row names the columns, a measure's
+   numbers sit right like the primary's, and a dimension's fact is a word and
+   sits left. */
+table.janela-pane th { text-align: right; font-size: 0.85rem; font-weight: 600; opacity: 0.7; padding-bottom: calc(var(--janela-space) * 1); }
+table.janela-pane th:first-child, table.janela-pane th.janela-fact, table.janela-pane td.janela-fact { text-align: left; font-variant-numeric: normal; }
 table.janela-pane button {
   font: inherit;
   color: inherit;
@@ -108,6 +118,18 @@ table.janela-pane button[aria-pressed="true"] { background: var(--janela-accent)
 .janela-chart-title { font-weight: 600; margin-bottom: calc(var(--janela-space) * 2); }
 canvas.janela-chart { width: 100% !important; max-height: 20rem; }
 
+/* A pane with a height draws its chart into a box of fixed size (ADR 047), five
+   steps of the spacing unit so a theme that moves the unit moves them. Step 4
+   is the 20rem the cap allows a chart anyway. The cap stops applying inside a
+   box, where the box is the size. */
+.janela-chart-box { position: relative; }
+.janela-chart-box canvas.janela-chart { max-height: none; }
+.janela-h-1 { height: calc(var(--janela-space) * 24); }
+.janela-h-2 { height: calc(var(--janela-space) * 40); }
+.janela-h-3 { height: calc(var(--janela-space) * 56); }
+.janela-h-4 { height: calc(var(--janela-space) * 80); }
+.janela-h-5 { height: calc(var(--janela-space) * 112); }
+
 /* A chart pane is a <figure>, and a browser gives a figure 40px of margin
    either side. Harmless in a wide column and most of a narrow one. */
 figure.janela-pane { margin: 0; }

data/app/assets/stylesheets/vitral.css

@@ -69,6 +69,27 @@
      janela.css draws agree with the parts this one does. */
   --janela-line: var(--vitral-came-soft);
   --janela-accent: rgb(40, 110, 205);
+
+  /* The colours a bar, a doughnut slice or a pie slice is drawn in, by
+     position (ADR 046, ADR 026). Soft glass rather than bright: a first
+     version in saturated jewel tones read as a rainbow against the pale tiles,
+     so these sit at about half the chroma and lean on differences in lightness
+     to keep neighbours apart (the plum and the dusty rose are the darker ones).
+     Chosen as an ordered set and run through the palette checker: adjacent
+     colour vision separation 12.4 (target 8) and adjacent normal vision
+     separation 15.8 (floor 15). The order is what keeps neighbours apart, so a
+     reorder has to be re-checked. Slot 1 is a softer blue of its own and not
+     the accent, which stays the stronger blue for what is selected. The neutral
+     past the eighth is the grey of lead came. */
+  --janela-series-1: #608fcb;
+  --janela-series-2: #56ab81;
+  --janela-series-3: #a492da;
+  --janela-series-4: #91507d;
+  --janela-series-5: #be774e;
+  --janela-series-6: #159da9;
+  --janela-series-7: #c29e51;
+  --janela-series-8: #994b59;
+  --janela-series-other: #8794a6;
 }
 
 /* Opt in, because a theme that repaints a host's <body> uninvited is not a

data/app/controllers/janela/panes_controller.rb

@@ -76,8 +76,8 @@ module Janela
       end
 
       def pane_params
-        params.expect(pane: [ :kind, :model, :measure, :dimension, :renderer, :granularity, :limit, :span, :title,
-                              :heading, :body, :link, :partial ])
+        params.expect(pane: [ :kind, :model, :measure, :dimension, :renderer, :granularity, :limit, :height, :prominence, :span, :title,
+                              :heading, :body, :link, :partial, { companions: [] } ])
       end
 
       def build_pane(choice)

data/app/controllers/janela/queries_controller.rb

@@ -8,6 +8,9 @@ module Janela
         renderer: params.fetch(:as, "table"),
         granularity: params[:granularity],
         limit: params[:limit],
+        height: params[:height],
+        prominence: params[:prominence],
+        companions: params[:companions],
         filters: filters,
         fixed: fixed_filters
       )

data/app/controllers/janela/snapshot_queries_controller.rb

@@ -13,6 +13,9 @@ module Janela
         renderer: params.fetch(:as, "table"),
         granularity: params[:granularity],
         limit: params[:limit],
+        height: params[:height],
+        prominence: params[:prominence],
+        companions: params[:companions],
         snapshot: snapshot
       )
 

data/app/helpers/janela/frames_helper.rb

@@ -26,8 +26,15 @@ module Janela
     # so a host that changes the query in place (a renderer, granularity or
     # limit control) keeps one stable frame for Turbo to reconcile into
     # rather than a different id every time the query changes (ADR 029).
-    def janela_pane(model, measure, by: nil, as: :table, granularity: nil, limit: nil, id: nil)
-      query = { as: (as unless as.to_s == "table"), granularity: granularity, limit: limit,
+    #
+    # prominence: is one of three steps for a single value, and height: one of
+    # five for a chart. Both travel in the pane's URL for the same reason.
+    # height: is one of five steps, and travels in the pane's URL because the
+    # server draws the pane from it again on every cross-filter. It is not part
+    # of the frame's id: how tall a pane is does not say which query it is
+    # (ADR 047, ADR 029).
+    def janela_pane(model, measure, by: nil, as: :table, granularity: nil, limit: nil, height: nil, prominence: nil, companions: nil, id: nil)
+      query = { as: (as unless as.to_s == "table"), granularity: granularity, limit: limit, height: height, prominence: prominence, companions: companions.presence,
                 where: @janela_fixed_filters.presence }.compact
       base = janela_routes.pane_path(model.model_name.route_key, measure, by, **query)
 
@@ -39,8 +46,9 @@ module Janela
 
     # A pane as it was when the snapshot was taken: same shape as janela_pane,
     # not part of the live frame's filter state (ADR 009).
-    def janela_snapshot_pane(snapshot, model, measure, by: nil, as: :table, granularity: nil, limit: nil)
-      query = { as: (as unless as.to_s == "table"), granularity: granularity, limit: limit }.compact
+    def janela_snapshot_pane(snapshot, model, measure, by: nil, as: :table, granularity: nil, limit: nil, height: nil, prominence: nil, companions: nil)
+      query = { as: (as unless as.to_s == "table"), granularity: granularity, limit: limit, height: height,
+                prominence: prominence, companions: companions.presence }.compact
       src = janela_routes.snapshot_pane_path(snapshot, model.model_name.route_key, measure, by, **query)
 
       turbo_frame_tag Query.turbo_frame_id(model: model, measure: measure, by: by, as: as, granularity: granularity, limit: limit, snapshot: snapshot),

data/app/models/janela/pane.rb

@@ -5,6 +5,14 @@ module Janela
   # invent a query or reach a model nobody exposed.
   class Pane < ActiveRecord::Base
     SPANS = (1..12).freeze
+
+    # How tall a bar or line chart is drawn, or nil for what it always was
+    # (ADR 047). Five steps rather than pixels: a stored integer selects a class
+    # that is already written (ADR 016).
+    HEIGHTS = Query::HEIGHTS
+
+    # How prominent a single value is drawn (ADR 050).
+    PROMINENCES = Query::PROMINENCES
     LIMITS = (1..1000).freeze
     # A form cannot offer a thousand options, and these are the row counts a
     # dashboard actually asks for. Any limit inside LIMITS is still valid.
@@ -30,6 +38,10 @@ module Janela
     validates :kind, inclusion: { in: KINDS }
     validates :span, inclusion: { in: SPANS }
     validates :limit, inclusion: { in: LIMITS }, allow_nil: true
+    validates :height, inclusion: { in: HEIGHTS }, allow_nil: true
+    validates :prominence, inclusion: { in: PROMINENCES }, allow_nil: true
+    before_validation :normalise_companions
+    validate :companions_are_declared
     validates :measure, presence: true, if: :query?
     validate :declared_by_a_janela_block, if: :query?
     validate :holds_no_query, unless: :query?
@@ -72,7 +84,7 @@ module Janela
     # instead (ADR 018).
     def query(filters: {}, fixed: {}, renderer: self.renderer)
       Query.new(definition: definition, measure: measure.to_sym, dimension: dimension.presence&.to_sym,
-                renderer: renderer, granularity: granularity, limit: limit, filters: filters, fixed: fixed,
+                renderer: renderer, granularity: granularity, limit: limit, height: height, prominence: prominence, companions: companions, filters: filters, fixed: fixed,
                 default: frame.default_for(definition.model), title: title)
     end
 
@@ -107,6 +119,25 @@ module Janela
     end
 
     private
+      # A multiple select sends an empty string beside its choices, and an empty
+      # selection is nothing rather than an empty list.
+      def normalise_companions
+        self.companions = Array(companions).map(&:to_s).reject(&:blank?).presence
+      end
+
+      # The same rules a URL is held to, from the same place, so a row cannot
+      # name what a request could not (ADR 051).
+      def companions_are_declared
+        return if companions.blank? || !query? || measure.blank? || Query::RENDERERS.exclude?(renderer.to_s)
+
+        Query.new(definition: definition, measure: measure.to_sym, dimension: dimension.presence&.to_sym,
+                  renderer: renderer, companions: companions)
+      rescue Janela::BadRequest => error
+        errors.add(:companions, error.message)
+      rescue Janela::Error
+        nil # an unknown model is reported by its own validation
+      end
+
       def panes_above
         frame.panes.where(position: ...position).order(:position)
       end