Bump rails-ai-context from 5.24.0 to 5.25.0

[dependabot]

Bumps rails-ai-context from 5.24.0 to 5.25.0.

Release notes

Sourced from rails-ai-context's releases.

v5.25.0

Added

• sprockets-rails, sprockets, sorcery and clearance join the notable gem table, so rails_get_gems lists them and the rails_get_config assets and auth lines name them from the lockfile rather than from a loaded constant.

Fixed

Defects found by a second survey round over the whole surface, and the duplicated mechanisms behind them.

• max_view_total_size and max_view_file_size said they capped view reads. Only doctor reads either one, as the threshold for its view-size warning; the config comments and the docs rows now say that.
• excluded_concerns hid a concern from a model's list but not from the catalogue. rails_get_concern and the rails_get_active_support concern registry still listed and counted a concern the key names; all three now apply the same predicate.
• An in-Gemfile app's .rails-ai-context.yml was inert. The generated initializer holds a configure block, and the YAML was skipped whenever one had run, so a booted command took the defaults while --no-boot read the file and the two disagreed (45 tools against 43 with skip_tools set). Precedence is a merge: the file is applied once, before config/initializers, so an initializer may assign a key or edit it in place and both survive; a later call from the standalone binary or the CLI's boot path is a no-op. A block wins the keys it assigns wherever it lives, so one in config/application.rb or an environment file, which runs before the load, keeps them too.
• The static tier named the app after its directory. onboard and every generated context file were headed "mastodon" for an app that declares module Mastodon. The name now comes from the module enclosing class Application < Rails::Application in config/application.rb, and falls back to the directory only when that file names nothing.
• The static tier counted every class under app/models as a model. Namespace modules, form objects, filters and plain service classes were listed and rendered as models of a table (Mastodon answered 195 models against 117 booted). A static model is now a class whose superclass chain reaches ApplicationRecord, a namespaced *ApplicationRecord or ActiveRecord::Base, STI subclasses included.
• An unreadable .rails-ai-context.yml aborted the boot. A directory or a file the process cannot read at that path raised out of the engine initializer; it now warns and keeps the defaults, the way broken YAML does.
• A model under a per-connection abstract base was missing from the static list. The multi-database shape - class AnimalsRecord < ApplicationRecord; self.abstract_class = true in its own file, then class Dog < AnimalsRecord - dropped every model on that connection from the static list, the count and the schema listing. An abstract base is still walked so

... (truncated)

Changelog

Sourced from rails-ai-context's changelog.

[5.25.0] - 2026-09-03

Added

• sprockets-rails, sprockets, sorcery and clearance join the notable gem table, so rails_get_gems lists them and the rails_get_config assets and auth lines name them from the lockfile rather than from a loaded constant.

Fixed

Defects found by a second survey round over the whole surface, and the duplicated mechanisms behind them.

• max_view_total_size and max_view_file_size said they capped view reads. Only doctor reads either one, as the threshold for its view-size warning; the config comments and the docs rows now say that.
• excluded_concerns hid a concern from a model's list but not from the catalogue. rails_get_concern and the rails_get_active_support concern registry still listed and counted a concern the key names; all three now apply the same predicate.
• An in-Gemfile app's .rails-ai-context.yml was inert. The generated initializer holds a configure block, and the YAML was skipped whenever one had run, so a booted command took the defaults while --no-boot read the file and the two disagreed (45 tools against 43 with skip_tools set). Precedence is a merge: the file is applied once, before config/initializers, so an initializer may assign a key or edit it in place and both survive; a later call from the standalone binary or the CLI's boot path is a no-op. A block wins the keys it assigns wherever it lives, so one in config/application.rb or an environment file, which runs before the load, keeps them too.
• The static tier named the app after its directory. onboard and every generated context file were headed "mastodon" for an app that declares module Mastodon. The name now comes from the module enclosing class Application < Rails::Application in config/application.rb, and falls back to the directory only when that file names nothing.
• The static tier counted every class under app/models as a model. Namespace modules, form objects, filters and plain service classes were listed and rendered as models of a table (Mastodon answered 195 models against 117 booted). A static model is now a class whose superclass chain reaches ApplicationRecord, a namespaced *ApplicationRecord or ActiveRecord::Base, STI subclasses included.
• An unreadable .rails-ai-context.yml aborted the boot. A directory or a file the process cannot read at that path raised out of the engine initializer; it now warns and keeps the defaults, the way broken YAML does.
• A model under a per-connection abstract base was missing from the static list. The multi-database shape - class AnimalsRecord < ApplicationRecord; self.abstract_class = true in its own file, then class Dog < AnimalsRecord - dropped every model on that connection from the static list, the count and the schema listing. An abstract base is still walked so

... (truncated)

Commits

• c8cdab7 Merge pull request #159 from crisnahine/deepening-round-two
• 32d9a4c release: v5.25.0 - the second deepening survey, proven on Mastodon
• a150e09 merge round 13: abstract bases stay in the walk, the config file applies once...
• 7133250 the tool listing example asserts a tool is present
• 7e373e5 a preset claims the introspectors key for the block
• 1c0708d the unused configured_via_block predicate goes
• 1bf04ed a nested configure keeps the outer block recording
• a1e088c the config file applies once, before the initializers
• bb02293 the abstract check says why both tiers drop one
• ebbec48 the config doc says to assign a key, not mutate it
• Additional commits viewable in compare view

[dependabot]

Superseded by #202.