Summary

• add broadcast: :invalidation for observable dependencies that must refresh components without storing or broadcasting their projected value
• include the originally staged arguments: in effect success and failure callbacks
• accept identifier-style rejection codes and make malformed codes terminal through InvalidRejectionCode
• add run_due_reminders(now:) for deterministic database-clock reminder tests
• document the security boundary and prepare version 0.12.1

Root cause

Normal observables did not express whether their value was safe to persist and place in the Action Cable broadcast payload. The renderer therefore built a scalar replacement for every changed observable, even when the application used it only as a component invalidation signal.

Effect result messages also omitted the staged arguments, malformed rejection codes raised a retryable ArgumentError, and Rails time travel could not move the database clock used by reminder claims.

API, security, and compatibility

• Existing observables keep broadcast: :value behavior by default.
• broadcast: :invalidation stores {}, renders metadata only, refreshes dependent components, and cannot be used as a scalar target.
• Effect callbacks now require arguments:; this is a deliberate breaking callback change.
• Ruby reject(code, message, details:) continues to accept strings and symbols. Codes now follow identifier grammar, including camelCase.
• No database migration is required.
• The roadmap, security guide, realtime guide, example actor, generated RBS, changelog, version, and lockfile are updated together.

Red/green evidence

The focused tests failed before implementation with the expected contract gaps:

• ArgumentError: wrong number of arguments (given 2, expected 1) for observable ..., broadcast: :invalidation
• KeyError: key not found: "arguments" for an effect result message
• NoMethodError: undefined method 'run_due_reminders' for the public test helper
• a retry-driven SolidObjects::SyncTimeout for an accepted camelCase rejection code
• no error when rendering an invalidation-only observable as a scalar target

All focused regression suites pass after the implementation.

Validation

• bundle exec rake — 436 tests, 1,467 assertions, 0 failures, 0 errors, 14 optional-adapter skips; Standard Ruby, RuboCop, RBS validation, Steep, and Brakeman all pass
• SOLID_OBJECTS_DATABASE_URL=postgresql://... bundle exec rake test — 436 tests, 1,444 assertions, 0 failures, 0 errors, 15 optional-service skips
• gem build solid_objects.gemspec --output /tmp/solid_objects-0.12.1.gem — built version 0.12.1 successfully

MySQL and Trilogy were not rerun locally because the available unrelated service rejected the dedicated test credentials; the repository CI matrix remains the validation path for those clients.