Implement ProjectionReadModel query layer

freemo commented

2026-03-15 23:08:39 +00:00

Owner

Metadata

Commit Message: feat(event-sourcing): implement ProjectionReadModel query layer
Branch: feature/m3-projection-read-model

Background and Context

ES projections maintain denormalized read-model tables (:game_objects, :players, :rooms). A query layer must expose these as a read API compatible with how Gary/CacheGary currently load objects from GDBM via StorageMachine.

Acceptance Criteria

ProjectionReadModel provides load_object(goid), load_player(name), load_all, check_password
Returns reconstructed game objects from projection data
API compatible with StorageMachine's read interface

Subtasks

Create ProjectionReadModel class in lib/aethyr/core/event_sourcing/
Implement load_object(goid) from game_objects projection
Implement load_player(name) from players projection
Implement load_all from projections
Implement check_password from players projection
Tests (Cucumber): Scenarios for each read method
Run bundle exec rake unit, fix any failures
Docs: Update YARD comments on affected classes and methods. Update relevant Docusaurus documentation pages if applicable.
Tests (Cucumber Integration): Add integration feature in tests/integration/ verifying ProjectionReadModel returns correct game state from event projections.
Tests (Profiling): Run bundle exec rake unit_profile and verify no performance regressions.
Quality: Verify coverage >=97% via bundle exec rake unit. If coverage is <97% then review the current unit test coverage report at build/tests/unit/coverage/ and use it to write new Cucumber based unit tests to improve code coverage. Specifically, write Cucumber/Gherkin style unit tests that are descriptively named and specifically improve coverage on whichever file has the most uncovered lines by writing tests that will target the uncovered lines in the report. Once that is done rerun bundle exec rake unit to verify all tests pass and coverage is above >=97%. Only mark this as complete once coverage is >=97%, if not repeat this task as many times as is needed until coverage reaches >=97%.
Quality: Run bundle exec rake (default task: unit tests with coverage) and bundle exec rake integration, fix any errors if needed ensuring both pass across entire code base, do not ignore any failure even if it seems unrelated to this commit, fix it.

Definition of Done

This issue is complete when:

All subtasks above are completed and checked off.
A Git commit is created where the first line of the commit message matches the Commit Message in Metadata exactly, followed by a blank line, then additional lines providing relevant details about the implementation.
The commit is pushed to the remote on the branch matching the Branch in Metadata exactly.
The commit is submitted as a pull request to master, reviewed, and merged before this issue is marked done.

## Metadata - **Commit Message:** `feat(event-sourcing): implement ProjectionReadModel query layer` - **Branch:** `feature/m3-projection-read-model` ## Background and Context ES projections maintain denormalized read-model tables (`:game_objects`, `:players`, `:rooms`). A query layer must expose these as a read API compatible with how `Gary`/`CacheGary` currently load objects from GDBM via `StorageMachine`. ## Acceptance Criteria - `ProjectionReadModel` provides `load_object(goid)`, `load_player(name)`, `load_all`, `check_password` - Returns reconstructed game objects from projection data - API compatible with `StorageMachine`'s read interface ## Subtasks - [ ] Create `ProjectionReadModel` class in `lib/aethyr/core/event_sourcing/` - [ ] Implement `load_object(goid)` from game_objects projection - [ ] Implement `load_player(name)` from players projection - [ ] Implement `load_all` from projections - [ ] Implement `check_password` from players projection - [ ] Tests (Cucumber): Scenarios for each read method - [ ] Run `bundle exec rake unit`, fix any failures - [ ] Docs: Update YARD comments on affected classes and methods. Update relevant Docusaurus documentation pages if applicable. - [ ] Tests (Cucumber Integration): Add integration feature in `tests/integration/` verifying ProjectionReadModel returns correct game state from event projections. - [ ] Tests (Profiling): Run `bundle exec rake unit_profile` and verify no performance regressions. - [ ] Quality: Verify coverage >=97% via `bundle exec rake unit`. If coverage is <97% then review the current unit test coverage report at `build/tests/unit/coverage/` and use it to write new Cucumber based unit tests to improve code coverage. Specifically, write Cucumber/Gherkin style unit tests that are descriptively named and specifically improve coverage on whichever file has the most uncovered lines by writing tests that will target the uncovered lines in the report. Once that is done rerun `bundle exec rake unit` to verify all tests pass and coverage is above >=97%. Only mark this as complete once coverage is >=97%, if not repeat this task as many times as is needed until coverage reaches >=97%. - [ ] Quality: Run `bundle exec rake` (default task: unit tests with coverage) and `bundle exec rake integration`, fix any errors if needed ensuring both pass across **entire** code base, do not ignore any failure even if it seems unrelated to this commit, fix it. ## Definition of Done This issue is complete when: - All subtasks above are completed and checked off. - A Git commit is created where the **first line** of the commit message matches the Commit Message in Metadata exactly, followed by a blank line, then additional lines providing relevant details about the implementation. - The commit is pushed to the remote on the branch matching the **Branch** in Metadata exactly. - The commit is submitted as a **pull request** to `master`, reviewed, and **merged** before this issue is marked done.