familia 2.0.0.pre18 → 2.0.0.pre21

data/CLAUDE.md

@@ -53,7 +53,7 @@ Add changelog fragment with each user-facing or documented change (optional but
 ### Known Issues & Quirks
 - **Reserved Keywords**: Cannot use `ttl`, `db`, `valkey`, `redis` as field names - use prefixed alternatives
 - **Empty Identifiers**: Cause stack overflow in key generation - validate before operations
-- **Connection Pool Race Conditions**: Thread safety issues under high concurrency
+- **Lazy Initialization Races**: Connection chains and field collections use lazy initialization without synchronization (generally safe due to Ruby GIL, but not guaranteed)
 
 ### Debugging
 - **Database command logging**: You can request real-time Database command monitoring from the user
@@ -105,30 +105,55 @@ class User < Familia::Horreum
 end
 ```
 
-**Good - use the `init` hook instead:**
+**Good - use the `init` hook to apply defaults (use `||=` not `=`):**
 ```ruby
 class User < Familia::Horreum
-  def init(email = nil)
-    @email = email  # Called after super, related fields work
+  field :objid
+  field :email
+
+  # Called after Horreum sets fields from kwargs
+  # IMPORTANT: Use ||= to apply defaults, not = to override
+  def init
+    @objid ||= SecureRandom.uuid  # Apply default only if not already set
+    _run_post_init_hooks          # Additional setup logic
   end
 end
+
+# This works correctly:
+user = User.new(email: 'test@example.com')
+user.objid      # → generated UUID (applied by init)
+user.email      # → 'test@example.com' (set by Horreum from kwargs)
 ```
 
-**Good - call super explicitly:**
+**Okay - if absolutely necessary, override and call super explicitly:**
 ```ruby
 class User < Familia::Horreum
   def initialize(email = nil, **kwargs)
-    super(**kwargs)  # ✓ Related fields initialized
-    @email = email
+    super # Initializes related fields here and also calls init
+    @email ||= generate_email if email.nil?
   end
 end
 ```
 
-**Why this matters**: Familia's `initialize` method calls `initialize_relatives` to set up DataType objects (lists, sets, etc.). Without calling `super`, these objects remain nil and you'll get helpful errors pointing to the missing super call.
+**Why this matters**: Familia's `initialize` method processes kwargs FIRST (setting fields), then calls `initialize_relatives` (setting up DataType objects), then calls your `init` hook. By the time `init` runs, kwargs have already been consumed and fields are set.
+
+**The ||= Pattern Explained**:
+```ruby
+# WRONG - overwrites what Horreum already set
+def init
+  @email = generate_email  # Overwrites the correct value
+end
+
+# RIGHT - applies default only if not already set
+def init
+  @email ||= email               # Preserves value Horreum set from kwargs
+  @email ||= 'default@example.com'  # Apply fallback default if still nil
+end
+```
 
 **When to use each approach:**
-- **Use `init` hook** (preferred): For simple initialization logic that doesn't need to intercept constructor arguments. The `init` method is called automatically after `super` with the same arguments passed to `new`.
-- **Use explicit `super`**: When you need full control over initialization order or need to transform arguments before passing to parent. Remember to pass `**kwargs` to preserve keyword argument handling.
+- **Use `init` hook with `||=`** (preferred): Apply defaults, run validations, setup callbacks - any logic that should run after field initialization. Follows standard ORM lifecycle hook patterns.
+- **Use explicit `super`**: Only when you need to intercept or transform arguments before Horreum processes them (rare).
 
 **DataType Definition**: Use class methods to define keystore database-backed attributes:
 ```ruby
@@ -166,3 +191,30 @@ end
 **Memory Efficiency**: Only non-nil values are stored in keystore database to optimize memory usage.
 
 **Thread Safety**: Data types are frozen after instantiation to ensure immutability.
+
+## Thread Safety Considerations
+
+### Current Thread Safety Status (as of 2025-10-21)
+
+Familia has **good thread safety** for standard multi-threaded environments:
+
+### Testing Thread Safety
+
+Thread safety tests are available in `try/thread_safety/`:
+- **100% passing** (56/56 tests)
+- **CyclicBarrier pattern** for maximum contention testing
+- **Test execution**: ~300ms for full suite with 1,000+ concurrent operations
+- **Production monitoring**: 10/10 monitoring tests passing
+
+Run thread safety tests:
+```bash
+bundle exec try --agent try/thread_safety/
+bundle exec try --agent try/unit/thread_safety_monitor_try.rb
+```
+
+### Best Practices for Thread-Safe Usage
+
+1. **Configure Once at Startup**: Module-level configuration should be set before threads spawn
+2. **Use Immutable DataTypes**: Leverage the fact that DataType instances are frozen
+3. **Test Under Concurrency**: Use the patterns in `try/thread_safety/` to verify thread safety
+4. **Enable Production Monitoring**: Use `Familia.start_monitoring!` to track contention in production

data/Gemfile

@@ -9,7 +9,7 @@ group :test do
   gem 'ruby-prof'
   gem 'stackprof'
   gem 'timecop', require: false
-  gem 'tryouts', '~> 3.6.0', require: false
+  gem 'tryouts', '~> 3.7.1', require: false
 end
 
 group :development, :test do
@@ -17,10 +17,10 @@ group :development, :test do
   gem 'irb', '~> 1.15.2', require: false
   gem 'redcarpet', require: false
   gem 'reek', require: false
-  gem 'rubocop', require: false
+  gem 'rubocop', '~> 1.81.1', require: false
   gem 'rubocop-performance', require: false
   gem 'rubocop-thread_safety', require: false
-  gem 'solargraph', require: false
+  gem 'ruby-lsp', require: false
   gem 'yard', '~> 0.9', require: false
 end
 

data/Gemfile.lock

@@ -1,8 +1,9 @@
 PATH
   remote: .
   specs:
-    familia (2.0.0.pre18)
+    familia (2.0.0.pre21)
       benchmark (~> 0.4)
+      concurrent-ruby (~> 1.3)
       connection_pool (~> 2.5)
       csv (~> 3.3)
       logger (~> 1.7)
@@ -15,14 +16,13 @@ GEM
   remote: https://rubygems.org/
   specs:
     ast (2.4.3)
-    backport (1.2.0)
     base64 (0.3.0)
     benchmark (0.4.1)
     bigdecimal (3.2.3)
     concurrent-ruby (1.3.5)
     connection_pool (2.5.3)
     csv (3.3.5)
-    date (3.4.1)
+    date (3.5.0)
     debug (1.11.0)
       irb (~> 1.10)
       reline (>= 0.3.8)
@@ -56,31 +56,19 @@ GEM
       dry-inflector (~> 1.0)
       dry-logic (~> 1.4)
       zeitwerk (~> 2.6)
-    erb (5.0.2)
+    erb (5.1.3)
     ffi (1.17.2)
     ffi (1.17.2-arm64-darwin)
     io-console (0.8.1)
-    irb (1.15.2)
+    irb (1.15.3)
       pp (>= 0.6.0)
       rdoc (>= 4.0.0)
       reline (>= 0.4.2)
-    jaro_winkler (1.6.1)
-    json (2.15.0)
-    kramdown (2.5.1)
-      rexml (>= 3.3.9)
-    kramdown-parser-gfm (1.1.0)
-      kramdown (~> 2.0)
+    json (2.15.1)
     language_server-protocol (3.17.0.5)
     lint_roller (1.1.0)
     logger (1.7.0)
-    mini_portile2 (2.8.9)
-    minitest (5.25.5)
-    nokogiri (1.18.10)
-      mini_portile2 (~> 2.8.2)
-      racc (~> 1.4)
-    nokogiri (1.18.10-arm64-darwin)
-      racc (~> 1.4)
-    observer (0.1.2)
+    minitest (5.26.0)
     oj (3.16.11)
       bigdecimal (>= 3.0)
       ostruct (>= 0.2)
@@ -91,10 +79,10 @@ GEM
       racc
     pastel (0.8.0)
       tty-color (~> 0.5)
-    pp (0.6.2)
+    pp (0.6.3)
       prettyprint
     prettyprint (0.2.0)
-    prism (1.5.1)
+    prism (1.6.0)
     psych (5.2.6)
       date
       stringio
@@ -104,9 +92,10 @@ GEM
       ffi (~> 1)
     rbs (3.9.5)
       logger
-    rdoc (6.14.2)
+    rdoc (6.15.1)
       erb
       psych (>= 4.0.0)
+      tsort
     redcarpet (3.6.1)
     redis (5.4.1)
       redis-client (>= 0.22.0)
@@ -121,22 +110,20 @@ GEM
     regexp_parser (2.11.3)
     reline (0.6.2)
       io-console (~> 0.5)
-    reverse_markdown (3.0.0)
-      nokogiri
     rexml (3.4.1)
-    rspec (3.13.1)
+    rspec (3.13.2)
       rspec-core (~> 3.13.0)
       rspec-expectations (~> 3.13.0)
       rspec-mocks (~> 3.13.0)
-    rspec-core (3.13.5)
+    rspec-core (3.13.6)
       rspec-support (~> 3.13.0)
     rspec-expectations (3.13.5)
       diff-lcs (>= 1.2.0, < 2.0)
       rspec-support (~> 3.13.0)
-    rspec-mocks (3.13.5)
+    rspec-mocks (3.13.7)
       diff-lcs (>= 1.2.0, < 2.0)
       rspec-support (~> 3.13.0)
-    rspec-support (3.13.4)
+    rspec-support (3.13.6)
     rubocop (1.81.1)
       json (~> 2.3)
       language_server-protocol (~> 3.17.0.2)
@@ -159,44 +146,26 @@ GEM
       lint_roller (~> 1.1)
       rubocop (~> 1.72, >= 1.72.1)
       rubocop-ast (>= 1.44.0, < 2.0)
+    ruby-lsp (0.26.1)
+      language_server-protocol (~> 3.17.0)
+      prism (>= 1.2, < 2.0)
+      rbs (>= 3, < 5)
     ruby-prof (1.7.2)
       base64
     ruby-progressbar (1.13.0)
-    solargraph (0.57.0)
-      backport (~> 1.2)
-      benchmark (~> 0.4)
-      bundler (~> 2.0)
-      diff-lcs (~> 1.4)
-      jaro_winkler (~> 1.6, >= 1.6.1)
-      kramdown (~> 2.3)
-      kramdown-parser-gfm (~> 1.1)
-      logger (~> 1.6)
-      observer (~> 0.1)
-      ostruct (~> 0.6)
-      parser (~> 3.0)
-      prism (~> 1.4)
-      rbs (>= 3.6.1, <= 4.0.0.dev.4)
-      reverse_markdown (~> 3.0)
-      rubocop (~> 1.76)
-      thor (~> 1.0)
-      tilt (~> 2.0)
-      yard (~> 0.9, >= 0.9.24)
-      yard-activesupport-concern (~> 0.0)
-      yard-solargraph (~> 0.1)
     stackprof (0.2.27)
     stringio (3.1.7)
-    thor (1.4.0)
-    tilt (2.6.1)
     timecop (0.9.10)
-    tryouts (3.6.0)
-      concurrent-ruby (~> 1.0)
+    tryouts (3.7.1)
+      concurrent-ruby (~> 1.0, < 2)
       irb
       minitest (~> 5.0)
       pastel (~> 0.8)
       prism (~> 1.0)
-      rspec (~> 3.0)
+      rspec (>= 3.0, < 5.0)
       tty-cursor (~> 0.7)
       tty-screen (~> 0.8)
+    tsort (0.2.0)
     tty-color (0.6.0)
     tty-cursor (0.7.1)
     tty-screen (0.8.2)
@@ -205,10 +174,6 @@ GEM
     unicode-emoji (4.1.0)
     uri-valkey (1.4.0)
     yard (0.9.37)
-    yard-activesupport-concern (0.0.1)
-      yard (>= 0.8)
-    yard-solargraph (0.1.0)
-      yard (~> 0.9)
     zeitwerk (2.7.3)
 
 PLATFORMS
@@ -223,15 +188,15 @@ DEPENDENCIES
   rbnacl (~> 7.1, >= 7.1.1)
   redcarpet
   reek
-  rubocop
+  rubocop (~> 1.81.1)
   rubocop-performance
   rubocop-thread_safety
+  ruby-lsp
   ruby-prof
-  solargraph
   stackprof
   timecop
-  tryouts (~> 3.6.0)
+  tryouts (~> 3.7.1)
   yard (~> 0.9)
 
 BUNDLED WITH
-   2.6.2
+   2.7.2

data/README.md

@@ -280,6 +280,7 @@ Flower.multiget("prose", "tulip", "daisy")
 
 ### Transactional Operations
 
+**Horreum Model Transactions:**
 ```ruby
 user.transaction do |conn|
   conn.set("user:#{user.id}:status", "active")
@@ -287,6 +288,44 @@ user.transaction do |conn|
 end
 ```
 
+**DataType Transactions** (standalone or parent-owned):
+```ruby
+# Recommended: Use DataType methods for clean, automatic key handling
+user.scores.transaction do
+  user.scores.add('level1', 100)
+  user.scores.add('level2', 200)
+end
+
+# Standalone DataType transaction (e.g., session storage)
+session_key = Familia::StringKey.new('session:abc123')
+session_key.transaction do
+  session_key.set(session_data)
+  session_key.expire(3600)  # Atomic: both succeed or both fail
+end
+
+# Advanced: Connection available for low-level Redis commands
+user.scores.transaction do |conn|
+  conn.zadd(user.scores.dbkey, 100, 'level1')
+  conn.hset(user.profile.dbkey, 'status', 'active')
+end
+```
+
+**Pipeline Operations** (batch commands for performance):
+```ruby
+# Recommended: Use DataType methods
+leaderboard.pipelined do
+  leaderboard.add('player1', 500)
+  leaderboard.add('player2', 600)
+  leaderboard.size
+end
+
+# Advanced: Raw Redis commands for fine-grained control
+leaderboard.pipelined do |conn|
+  conn.zadd(leaderboard.dbkey, 500, 'player1')
+  conn.zadd(leaderboard.dbkey, 600, 'player2')
+end
+```
+
 ### Advanced Patterns
 
 **Time-based Expiration:**

data/bin/try

@@ -0,0 +1,16 @@
+#!/usr/bin/env ruby
+# frozen_string_literal: true
+
+#
+# This file was generated by Bundler.
+#
+# The application 'try' is installed as part of a gem, and
+# this file is here to facilitate running it.
+#
+
+ENV["BUNDLE_GEMFILE"] ||= File.expand_path("../Gemfile", __dir__)
+
+require "rubygems"
+require "bundler/setup"
+
+load Gem.bin_path("tryouts", "try")

data/bin/tryouts

@@ -0,0 +1,16 @@
+#!/usr/bin/env ruby
+# frozen_string_literal: true
+
+#
+# This file was generated by Bundler.
+#
+# The application 'tryouts' is installed as part of a gem, and
+# this file is here to facilitate running it.
+#
+
+ENV["BUNDLE_GEMFILE"] ||= File.expand_path("../Gemfile", __dir__)
+
+require "rubygems"
+require "bundler/setup"
+
+load Gem.bin_path("tryouts", "tryouts")

data/changelog.d/20251105_flexible_external_identifier_format.rst

@@ -0,0 +1,66 @@
+.. Added
+.. -----
+
+.. Changed
+.. -------
+
+- **ExternalIdentifier Format Flexibility**: The `external_identifier` feature now supports customizable format templates via the `format` option. This allows you to control the entire format of generated external IDs, including the prefix, separator, and overall structure.
+
+  **Default format** (unchanged behavior):
+
+  .. code-block:: ruby
+
+     class User < Familia::Horreum
+       feature :external_identifier
+     end
+     user.extid  # => "ext_abc123def456ghi789"
+
+  **Custom format with different prefix**:
+
+  .. code-block:: ruby
+
+     class Customer < Familia::Horreum
+       feature :external_identifier, format: 'cust_%{id}'
+     end
+     customer.extid  # => "cust_abc123def456ghi789"
+
+  **Custom format with different separator**:
+
+  .. code-block:: ruby
+
+     class APIKey < Familia::Horreum
+       feature :external_identifier, format: 'api-%{id}'
+     end
+     key.extid  # => "api-abc123def456ghi789"
+
+  **Custom format without traditional prefix**:
+
+  .. code-block:: ruby
+
+     class Resource < Familia::Horreum
+       feature :external_identifier, format: 'v2/%{id}'
+     end
+     resource.extid  # => "v2/abc123def456ghi789"
+
+  The `format` option accepts a Ruby format string with the `%{id}` placeholder for the generated identifier. The default format is `'ext_%{id}'`. This provides complete flexibility for various ID formatting needs including different prefixes, separators (underscore, hyphen, slash), URL paths, or no prefix at all.
+
+.. Deprecated
+.. ----------
+
+.. Removed
+.. -------
+
+.. Fixed
+.. -----
+
+.. Security
+.. --------
+
+.. Documentation
+.. -------------
+
+.. AI Assistance
+.. -------------
+
+- **Design Review**: Claude Code provided analysis of the current implementation and recommended several idiomatic Ruby approaches for format flexibility, ultimately suggesting the format template pattern using Ruby's native string formatting.
+- **Implementation**: Claude Code implemented the format template feature including code changes, test cases, and documentation updates.

data/changelog.d/20251107_112554_delano_179_participation_asymmetry.rst

@@ -0,0 +1,44 @@
+.. A new scriv changelog fragment.
+..
+.. Uncomment the section that is right (remove the leading dots).
+.. For top level release notes, leave all the headers commented out.
+..
+Added
+-----
+
+- Bidirectional reverse collection methods for ``participates_in`` with ``_instances`` suffix (e.g., ``user.project_team_instances``, ``user.project_team_ids``). Supports union behavior for multiple collections and custom naming via ``as:`` parameter. Closes #179.
+
+.. Changed
+.. -------
+..
+.. - A bullet item for the Changed category.
+..
+.. Deprecated
+.. ----------
+..
+.. - A bullet item for the Deprecated category.
+..
+.. Removed
+.. -------
+..
+.. - A bullet item for the Removed category.
+..
+.. Fixed
+.. -----
+..
+.. - A bullet item for the Fixed category.
+..
+.. Security
+.. --------
+..
+.. - A bullet item for the Security category.
+..
+.. Documentation
+.. -------------
+..
+.. - A bullet item for the Documentation category.
+..
+AI Assistance
+-------------
+
+- Claude Opus 4 assisted with implementation of bidirectional participation relationships using ``_instances`` suffix pattern. Pivoted from initial dry-inflector pluralization approach based on feedback.

data/changelog.d/20251107_213121_delano_fix_thread_safety_races_011CUumCP492Twxm4NLt2FvL.rst

@@ -0,0 +1,20 @@
+.. Fixed mutex race conditions in thread safety implementation
+..
+
+Fixed
+-----
+
+- Fixed critical race condition in mutex initialization for connection chain lazy loading. The mutex itself was being lazily initialized with ``||=``, which is not atomic and could result in multiple threads creating different mutex instances, defeating synchronization. Changed to eager initialization via ``Connection.included`` hook. (`lib/familia/horreum/connection.rb`)
+
+- Fixed critical race condition in mutex initialization for logger lazy loading. Similar to connection chain issue, the logger mutex was lazily initialized with ``||=``. Changed to eager initialization at module definition time. (`lib/familia/logging.rb`)
+
+- Fixed logger assignment atomicity issue where ``Familia.logger=`` set ``DatabaseLogger.logger`` outside the mutex synchronization block, potentially causing ``Familia.logger`` and ``DatabaseLogger.logger`` to be temporarily out of sync during concurrent access. Moved ``DatabaseLogger.logger`` assignment inside the synchronization block. (`lib/familia/logging.rb`)
+
+- Added explicit return statement to ``Familia.logger`` method for robustness against future refactoring. (`lib/familia/logging.rb`)
+
+AI Assistance
+-------------
+
+- Code review analysis to identify critical race conditions in mutex initialization
+- Implementation of proper eager mutex initialization patterns
+- Test file updates to reflect new initialization approach

data/changelog.d/20251107_fix_participates_in_symbol_resolution.rst

@@ -0,0 +1,91 @@
+.. Added
+.. -----
+
+.. Changed
+.. -------
+
+.. Deprecated
+.. ----------
+
+.. Removed
+.. -------
+
+.. Fixed
+.. -----
+
+- **Participation Relationships with Symbol/String Target Classes**: Fixed four bugs that occurred when calling `participates_in` with a Symbol or String target class instead of a Class object.
+
+  **Bug 1 - NoMethodError during relationship definition**:
+
+  The error was: ``private method 'member_by_config_name' called for module Familia``.
+
+  **Background**: The `participates_in` method supports flexible target class specifications:
+
+  .. code-block:: ruby
+
+     class Domain < Familia::Horreum
+       # All three forms should work:
+       participates_in Customer, :domains           # Class object (always worked)
+       participates_in :Customer, :domains          # Symbol (was broken)
+       participates_in 'Customer', :domains         # String (was broken)
+     end
+
+  **Root Cause**: The method had redundant class resolution code that directly called the private `Familia.member_by_config_name` method instead of using the public `Familia.resolve_class` API.
+
+  **Solution**: Removed the redundant resolution code and now uses the already-resolved class from the public API, simplifying the implementation and fixing the visibility issue.
+
+  **Bug 2 - NoMethodError in current_participations**:
+
+  When calling `current_participations` on objects that used Symbol/String target classes, it would fail with ``undefined method 'familia_name' for Symbol``.
+
+  **Root Cause**: The `current_participations` method was calling `.familia_name` on `config.target_class`, which stores the original Symbol/String value passed to `participates_in`.
+
+  **Solution**: Use the resolved `target_class` variable instead of the stored config value. The resolved class is already available from the `Familia.resolve_class` call earlier in the method.
+
+  **Bug 3 - NoMethodError in target_class_config_name**:
+
+  When calling `current_participations`, the internal `target_class_config_name` method would fail with ``undefined method 'config_name' for Symbol``.
+
+  **Root Cause**: The `ParticipationRelationship.target_class_config_name` method was calling `.config_name` directly on the stored `target_class` value, which could be a Symbol or String.
+
+  **Solution**: Resolve the target class before calling `config_name` by using `Familia.resolve_class(target_class)`, which handles all input types (Class, Symbol, String) correctly.
+
+  **Bug 4 - Confusing error when target class not loaded**:
+
+  When the target class hasn't been loaded yet (load order issue), the error was: ``undefined method 'method_defined?' for nil``.
+
+  **Root Cause**: When `Familia.resolve_class` returns `nil` (because the target class isn't registered in `Familia.members` yet), the code would pass `nil` to `TargetMethods::Builder.build`, which then failed with a confusing error message that didn't explain the actual problem.
+
+  **Solution**: Added explicit nil check after `resolve_class` with a detailed ArgumentError that:
+
+  - Clearly states which target class couldn't be resolved
+  - Lists the three most common causes (load order, typo, not inheriting from Horreum)
+  - Shows all currently registered Familia classes for debugging
+  - Provides a clear solution for fixing the load order
+
+  **Impact**: Projects using Symbol or String target classes in `participates_in` declarations will now work correctly throughout the entire lifecycle, including relationship definition, method generation, and participation queries. When there's a load order issue or typo, developers get a clear, actionable error message instead of a confusing nil error. This pattern is common when avoiding circular dependencies or when target classes are defined in different files.
+
+.. Security
+.. --------
+
+.. Documentation
+.. -------------
+
+.. AI Assistance
+.. -------------
+
+- **Root Cause Analysis**: Claude Code analyzed the error stack trace from the implementing project and identified that a private method was being called as a public method from outside the Familia module.
+- **Fix Implementation**: Claude Code identified redundant class resolution code and simplified it to use the already-resolved class from the public API.
+- **Test Coverage**: Claude Code created comprehensive regression tests including:
+
+  - Feature-level tests for Symbol/String target class resolution in participation relationships
+  - Unit tests for the `Familia.resolve_class` public API
+  - Edge case coverage for case-insensitive resolution and modularized classes
+
+- **Second Bug Discovery**: During test execution, Claude Code discovered a related bug in `current_participations` that was also failing with Symbol/String target classes. The test coverage revealed that `.familia_name` was being called on the unresolved config value instead of the resolved class instance.
+
+- **Third Bug Discovery**: Further test execution revealed another Symbol/String bug in `target_class_config_name`, where `.config_name` was being called directly on Symbol/String values. This was fixed by resolving the class first using `Familia.resolve_class`.
+
+- **Test Coverage Refinement**: Claude Code identified and removed unrealistic test cases (all-uppercase, all-lowercase class names) that don't occur in real Ruby code and don't work with the `snake_case` method's design. Updated tests to focus on realistic naming conventions: PascalCase and snake_case, with clear documentation explaining why certain formats aren't supported.
+
+- **Fourth Bug Discovery**: After merging to main, the implementing project revealed a load order issue where `Familia.resolve_class` returned `nil`, causing a confusing "undefined method for nil" error. Claude Code added explicit error handling with a detailed, actionable error message that helps developers quickly identify and fix load order issues, typos, or inheritance problems.