chore(apps): consolidate accessor implementation to runtime (2/4)
Merged
D-
3mo ago+2433+2433+0123456789012345678901234567890123456789-320-320-012345678901234567890123456789
- refactor(apps): Phase 1 - port Reader family, Persistence and server Environment into base-runtime
- refactor(apps): Phase 2 - port Modify family into base-runtime
- refactor(apps): Phase 3 - registration + app-settings surface via AppResourceBridge
Proposed changes (including videos or screenshots)
Issue(s)
Related Jira task: ARCH-2185: reunite duplicated accessor implementations into a shared location
Steps to test or reproduce
Further comments
Summary by CodeRabbit
- New Features
- Added concrete base-runtime accessors for environment, persistence, server settings, and expanded reader/modify coverage (rooms/messages/livechat/uploads/OAuth/scheduling/moderation/video conferencing), eliminating proxy-based delegation.
- Introduced an app resource bridge for configuration registration and setting updates, with special handling during subprocess restarts.
- Bug Fixes
- Improved settings βnot foundβ behavior by treating
null/undefinedresults as missing across the RPC boundary. - Updated scheduler job-id suffix check to avoid namespace collisions.
- Improved settings βnot foundβ behavior by treating
- Tests
- Expanded runtime reader/modify/persistence/configuration tests to validate outgoing bridge calls and parameters.
- Documentation
- Updated the phased migration plan and added follow-up notes.