Retained evidence: the initial baseline and first changed-tree full runs each exposed a different unrelated timing-sensitive event-export failure; each exact failing test passed immediately in isolation. No source changed before the bounded renewed full clean gate passed.
Delivery effects
Merging to main triggers the existing semantic-release workflow and is expected to publish a patch release. No GitOps, deployment, live-server, configuration, dependency, CI, or tooling change is included.
## Summary
- suppress the false recovery warning only when a well-formed `RESTORED` marker exactly matches the completed last-exit receipt
- preserve marker, receipt history, inventory, cursor, character data, and inactive session state
- retain recovery warnings and nonmutation for malformed, mismatched, non-restored markers and genuine Fantasy Stick remnants
OpenProject: https://project.dmg.games/work_packages/402
## Verification
- meaningful RED: registered `PlayerJoinEvent` clean-exit test expected zero notices and observed one `NATIVE_RECOVERY_REQUIRED`
- focused GREEN: 2/2 clean/unsafe login-path tests
- affected GREEN: 158/158 `EquipmentSessionsNativeTest` and `EquipmentSessionEventsNativeTest` checks
- full branch gate: `./gradlew clean check jar` — 2,539 checks passed (489 ordinary Java, 1,995 native, 55 release-tool)
- tested commit: `a2140bd8d7ce9f9036032e137f047cb8321936df`
- tested tree: `553d2047ec718c22b1d654575a50a7a7d7d58873`
- target base: `7ea6e254eb5a77ab91633a5d1bfa8047ea9e28f5`
- frozen inputs: 666 tracked files; manifest SHA-256 `1750349e9595f860a5894ec5b9fd42e69652fd684528f7192fea5a23422f3bcc`
Retained evidence: the initial baseline and first changed-tree full runs each exposed a different unrelated timing-sensitive event-export failure; each exact failing test passed immediately in isolation. No source changed before the bounded renewed full clean gate passed.
## Delivery effects
Merging to `main` triggers the existing semantic-release workflow and is expected to publish a patch release. No GitOps, deployment, live-server, configuration, dependency, CI, or tooling change is included.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Summary
RESTOREDmarker exactly matches the completed last-exit receiptOpenProject: https://project.dmg.games/work_packages/402
Verification
PlayerJoinEventclean-exit test expected zero notices and observed oneNATIVE_RECOVERY_REQUIREDEquipmentSessionsNativeTestandEquipmentSessionEventsNativeTestchecks./gradlew clean check jar— 2,539 checks passed (489 ordinary Java, 1,995 native, 55 release-tool)a2140bd8d7ce9f9036032e137f047cb8321936df553d2047ec718c22b1d654575a50a7a7d7d588737ea6e254eb5a77ab91633a5d1bfa8047ea9e28f51750349e9595f860a5894ec5b9fd42e69652fd684528f7192fea5a23422f3bccRetained evidence: the initial baseline and first changed-tree full runs each exposed a different unrelated timing-sensitive event-export failure; each exact failing test passed immediately in isolation. No source changed before the bounded renewed full clean gate passed.
Delivery effects
Merging to
maintriggers the existing semantic-release workflow and is expected to publish a patch release. No GitOps, deployment, live-server, configuration, dependency, CI, or tooling change is included.