[Engine] runtime-owned reset contract 확장#132
Merged
Merged
Conversation
6ea1a52 to
40ffe02
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
DeterministicRng를 추가하고EngineRuntime이initialize()/stop()경계에서 base seed 기준으로 다시 reseed하도록 정리했습니다.EngineStepContext.derivedSeed를 실제 run/fixed-step 조합에서 파생한 값으로 채워 restart 이후에도 같은 입력이면 같은 seed stream이 재구성되도록 했습니다.Related Issue
Area
Architecture Check
application -> domain -> engine.src/domain.domainorapplicationdependencies tosrc/engine.src/as the include root.Verification
cmake --preset windows-debugcmake --build --preset build-debugctest --preset test-debugQt app 전체 preset 대신, CI와 같은 engine/domain/test 경로를 no-app preset으로 검증했습니다.
cmake --build --preset build-no-app-debugctest --preset test-no-app-debugRisks / Follow-up
DeterministicRng의 system별 stream 분리나 추가 파생 규칙은 Task-Implement DeterministicRng and run seed contract #22 범위에서 이어서 확장할 수 있습니다.TriggerPolicy::Intervalcadence 판정 자체는 이미main에 반영된 [Engine] TriggerPolicy cadence execution and interval reset #128 구현을 그대로 따릅니다.