Fix non-interactive (rake / rails runner) audit on Evergreen

[grantcox]

Problem

On Evergreen, rails runner and rake commands produce no noninteractive_command record. Interactive consoles and the same commands on datadog-proxy-staging work. Both failures below are swallowed by the gem's fail-open rescues, so the only symptom is a warning on the one-off dyno's stderr.

1. Rake is only partially loaded

[console-audit] noninteractive audit failed (ignored): undefined method 'application' for module Rake

NoninteractiveAudit.detect checked defined?(Rake) before calling Rake.application. Evergreen requires rails/test_unit/railtie, and in Rails 8.1 that chain ends in require "rake/file_list". That defines Rake without Rake.application.

Fix: check defined?(Rake.application) instead.

2. The enqueue runs before rails_semantic_logger has patched ActiveJob

[console-audit] failed to queue noninteractive_command (ignored): undefined method 'current_tags' for nil

The Railtie's after_initialize is registered when Bundler requires the gem, so it runs before the hooks of gems listed later in the Gemfile. rails_semantic_logger swaps Rails.logger for a SemanticLogger during initializers, but only patches ActiveJob's logging in its own after_initialize. Until that patch runs, ActiveJob's logger_tagged_by_active_job? calls logger.formatter.current_tags, and a SemanticLogger has no formatter. In Evergreen, rails_semantic_logger sits in the production group below console_audit. In datadog-proxy it comes first, which is why datadog-proxy worked. Interactive consoles enqueue long after boot, so they're unaffected.

Fix: the non-interactive audit's after_initialize is now registered from an initializer. Initializers run after Bundler.require, so the hook runs after every gem's after_initialize, whatever the Gemfile order.

Tests

• noninteractive_audit_spec: a bare Rake module still detects rails runner.
• railtie_spec: boots a forked app with an after_initialize hook registered after console_audit loads, standing in for a later gem. The spec checks that the audit runs after that hook, and not at all when auditing is disabled.

Both new specs fail without their fix. The full suite (72 examples) and standardrb pass.

Manual testing

I have tested these changes on Evergreen PR https://github.com/ynab/evergreen/pull/30446 , working through our full console auditing test script.

Release

This bumps VERSION to 1.0.1 and moves the changelog entries under 1.0.1. Tag v1.0.1 on main after merge. Evergreen then needs to pin console_audit to that tag.

🤖 Generated with Claude Code

[becky-ynab]

Looks great