Fix ActiveRecord dependency check for Zeitwerk eager loading

[trevorturk]

Summary

• Fixes Zeitwerk::NameError when eager loading without ActiveRecord present
• Wraps all lib/ruby_llm/active_record/*.rb files with if defined?(ActiveRecord::Base) check
• Adds active_record directory to Zeitwerk ignore list
• Updates railtie to load method modules before acts_as modules

Details

This PR ensures all ActiveRecord integration files only define their modules when ActiveRecord is available, following the pattern for conditional module loading.

Changes:

• Wrapped acts_as.rb, acts_as_legacy.rb, chat_methods.rb, message_methods.rb, and model_methods.rb with if defined?(ActiveRecord::Base)
• Added loader.ignore("#{__dir__}/ruby_llm/active_record") to prevent Zeitwerk from auto-loading these conditional files
• Updated railtie initializer to explicitly require method modules before acts_as modules
• Removed duplicate require from lib/ruby_llm.rb (now only in railtie)

Testing:

• ✅ Zeitwerk eager load works without ActiveRecord
• ✅ Zeitwerk eager load works with ActiveRecord
• ✅ All specs pass

🤖 Generated with Claude Code

[trevorturk]

This one is much easier to view with Hide Whitespace enabled: https://github.com/crmne/ruby_llm/pull/504/files?w=1

[crmne]

Thanks for the work here. I closed #505 so we can fold it into #504 and keep this as one complete fix.

Could you please update #504 with the following?

1. Add the CI eager-load check from #505 into this PR.

• We do want that guard in CI, just bundled with the code changes it depends on.

2. Keep the Railtie ActiveSupport.on_load(:active_record) integration.

• This is the right Rails hook: AR-related code only runs when ActiveRecord is actually loaded.

3. Remove the top-level if defined?(ActiveRecord::Base) wrappers in AR files (acts_as.rb, acts_as_legacy.rb, chat_methods.rb, message_methods.rb, model_methods.rb).

• Those wrappers can make a file load as a no-op if AR isn’t ready yet.
• Later requires won’t re-run the file, so constants/modules may stay undefined.
• Better pattern: define modules normally, and control when they are included via Railtie hooks.

4. Add explicit requires for direct dependencies in those files (for example require "active_support/concern" where ActiveSupport::Concern is used).

• This avoids relying on incidental load order and makes eager loading more reliable.

5. Run the eager-load check in appraisal/matrix context (same Rails version under test).

• That makes sure the check validates the actual gem set for each matrix target, not just the base bundle.

Reason for all of this: we keep the Rails eager-loading fix, avoid subtle load-order traps, and keep a clean path for possible non-Rails ActiveRecord support later (CLI/Sinatra).

[trevorturk]

Apologies for the delay. I made the updates as requested but please let me know if I misunderstood something or if there's anything else to change. Thanks!

[trevorturk]

Rebased this branch onto current main (ac4d5d7) and fixed the RuboCop style offense in lib/ruby_llm.rb. CI is now passing on head b808b6d: RuboCop (Fast) pass, gitleaks pass. Could you take another look when you have a moment?

[seuros]

This is not really needed. you can do it in the test helper

[seuros]

every require should in line 4 of railtie , after if defined?(Rails::Railtie)

Then you dont have dups.