Nine native test/support files only; no gameplay, workflow, dependency, heap or timeout changes.
Wait for fresh menus, native acceptance, command responses, persisted dungeon-run initialization and merchant tagging instead of quiet callback queues.
Share strict audit snapshots executed on the owning serial writer; preserve malformed completed-record failures.
Await pending-intent retirement separately from export visibility.
Replace repeated per-key idle waits with terminal configuration-action export acknowledgments; retain exact counts/content and a final duplicate/extra-row check.
Verification
Small meaningful RED: delayed callback and held partial append fail with unrepaired observations; completed malformed JSON retains its strict error contract. Reused existing audit regression cases.
Connected 72 native cases pass; final affected 12 native + 447 API + 52 tools pass before the original full gate.
Original full clean gate: 2,360 pass on tree 8e1a990c020a6c9c903491d32ece7eb5abafd909.
Local retained logs/XML/input manifest: /tmp/fs-test-01-evidence/ (rebased-affected.log, rebased-full-clean.log, rebased-full-clean-results, rebased-inputs.json).
Configuration catalog: 56.268s baseline; 25.739s connected; 26.474s original full; 16.826s rebased full. These samples are not a controlled suite-wide benchmark. The connected cohort overall was slower, so no blanket performance claim.
Existing native SEVERE first-cause signatures are preserved rather than suppressed; no global listener/security clearance is claimed.
Integration boundary
Source coordinator assignment/explicit operator-mediated merge handoff is pending. Do not merge automatically. Before merge, verify current head/base, required PR checks/reviews, and that the proposed merged tree matches this verified candidate. If main changes, reconcile and rerun affected/full verification under the workspace process.
Current Gitea CI proves packaging only (FS-BUILD-02); local full-suite proof above remains mandatory. A main merge can trigger release processing, not deployment. No GitOps, server changes, security clearance or next story is authorized.
## Scope
[FS-TEST-01: deterministic native test synchronization](https://git.garvis.dev/dmg/somc-okf/src/branch/main/user-stories/purpur-fantasy-stick/fs-test-01-deterministic-native-test-synchronization.md)
Nine native test/support files only; no gameplay, workflow, dependency, heap or timeout changes.
- Wait for fresh menus, native acceptance, command responses, persisted dungeon-run initialization and merchant tagging instead of quiet callback queues.
- Share strict audit snapshots executed on the owning serial writer; preserve malformed completed-record failures.
- Await pending-intent retirement separately from export visibility.
- Replace repeated per-key idle waits with terminal configuration-action export acknowledgments; retain exact counts/content and a final duplicate/extra-row check.
## Verification
- Small meaningful RED: delayed callback and held partial append fail with unrepaired observations; completed malformed JSON retains its strict error contract. Reused existing audit regression cases.
- Connected 72 native cases pass; final affected 12 native + 447 API + 52 tools pass before the original full gate.
- Original full clean gate: 2,360 pass on tree `8e1a990c020a6c9c903491d32ece7eb5abafd909`.
- Rebased onto merged packaging change `6563f61f192778beecbd5e8acf7795129753ae20`; affected 55 workflow/release-tool tests pass.
- **Fresh final `./gradlew clean check jar`: 2,363 pass (1,861 native + 447 API + 55 tools), zero failures/errors/skips, 15m45s.** All 649 frozen source inputs unchanged.
- Verified head: `cd4d5a1360fe1f6d466d7e5920886729b913fd2d`; tree: `33de3f59c6af540fc1420f08e26bb4e03ac20558`.
- Local retained logs/XML/input manifest: `/tmp/fs-test-01-evidence/` (`rebased-affected.log`, `rebased-full-clean.log`, `rebased-full-clean-results`, `rebased-inputs.json`).
- Configuration catalog: 56.268s baseline; 25.739s connected; 26.474s original full; 16.826s rebased full. These samples are not a controlled suite-wide benchmark. The connected cohort overall was slower, so no blanket performance claim.
- Existing native SEVERE first-cause signatures are preserved rather than suppressed; no global listener/security clearance is claimed.
## Integration boundary
Source coordinator assignment/explicit operator-mediated merge handoff is pending. **Do not merge automatically.** Before merge, verify current head/base, required PR checks/reviews, and that the proposed merged tree matches this verified candidate. If main changes, reconcile and rerun affected/full verification under the workspace process.
Current Gitea CI proves packaging only (FS-BUILD-02); local full-suite proof above remains mandatory. A main merge can trigger release processing, not deployment. No GitOps, server changes, security clearance or next story is authorized.
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.
Scope
FS-TEST-01: deterministic native test synchronization
Nine native test/support files only; no gameplay, workflow, dependency, heap or timeout changes.
Verification
8e1a990c020a6c9c903491d32ece7eb5abafd909.6563f61f192778beecbd5e8acf7795129753ae20; affected 55 workflow/release-tool tests pass../gradlew clean check jar: 2,363 pass (1,861 native + 447 API + 55 tools), zero failures/errors/skips, 15m45s. All 649 frozen source inputs unchanged.cd4d5a1360fe1f6d466d7e5920886729b913fd2d; tree:33de3f59c6af540fc1420f08e26bb4e03ac20558./tmp/fs-test-01-evidence/(rebased-affected.log,rebased-full-clean.log,rebased-full-clean-results,rebased-inputs.json).Integration boundary
Source coordinator assignment/explicit operator-mediated merge handoff is pending. Do not merge automatically. Before merge, verify current head/base, required PR checks/reviews, and that the proposed merged tree matches this verified candidate. If main changes, reconcile and rerun affected/full verification under the workspace process.
Current Gitea CI proves packaging only (FS-BUILD-02); local full-suite proof above remains mandatory. A main merge can trigger release processing, not deployment. No GitOps, server changes, security clearance or next story is authorized.