Summary
Verify that all config.load_defaults behavioral flags introduced in Rails 7.0 and 7.1 have been accounted for in Workarea's test suite and migration notes.
Objective
The load-defaults-behavioral-flags pattern doc documents known risky flag behaviors (BigDecimal serialization, QueryCache middleware position). This task audits the actual coverage — are the risky behaviors tested? Are there gaps?
Approach
# Check current load_defaults setting across engine config files
grep -r 'load_defaults' workarea-*/config/ --include='*.rb'
# Check for BigDecimal/Money cache round-trip tests
grep -rn 'BigDecimal\|to_money\|Money.new' workarea-*/test/ --include='*.rb' | grep -i cache
For each behavioral flag in the pattern doc:
- Confirm it's been addressed (test exists, or documented as N/A for Workarea)
- Note any gaps where behavior change could affect downstream apps silently
Acceptance Criteria
Verification Plan
Read the notes file output. Each behavioral flag should have a clear PASS/N/A/NEEDS-FOLLOW-UP status.
Client Impact
None (verification/documentation only).
Summary
Verify that all
config.load_defaultsbehavioral flags introduced in Rails 7.0 and 7.1 have been accounted for in Workarea's test suite and migration notes.Objective
The
load-defaults-behavioral-flagspattern doc documents known risky flag behaviors (BigDecimal serialization, QueryCache middleware position). This task audits the actual coverage — are the risky behaviors tested? Are there gaps?Approach
For each behavioral flag in the pattern doc:
Acceptance Criteria
load_defaultsversion confirmed in all engine config filesnotes/WA-VERIFY-107-load-defaults-audit.mdVerification Plan
Read the notes file output. Each behavioral flag should have a clear PASS/N/A/NEEDS-FOLLOW-UP status.
Client Impact
None (verification/documentation only).