Completes the two existing participation-mode event criteria through registered administrator creation/mode updates and native Quest Giver acceptance → acknowledged authority → US-092 JSONL.
Original Quest Giver identity/location now accompanies camp acceptance.
Meaningful RED: missing camp Giver, three dungeon pool variants, seven created/changed future-application cases. Earlier exact-menu, close-stage and console-port setup failures retained and corrected without weakening assertions/bounds, changing production authority or global mocks/harness.
Initial separate full gate passed 2,294 tests on the previous base; US-079 advanced main while it ran. This unpublished ticket was cleanly rebased and verification renewed:
Separate fresh ./gradlew clean check jar: 2,309 tests = 441 JVM + 1,816 native + 52 tools, zero failures/errors/skips; all 26 new native cases clean.
All 644 frozen source hashes, Node v26.9.0 executable and unchanged declared Java 25/native 1 GiB exact. Full 688 legacy SEVERE header/exception/cause-chain/normalized-first-frame signatures match the verified baseline, not blanket native/security clearance.
Ordinary scoped diff review passes: four production paths and four new native suites only; git diff --check clean.
Evidence: /private/tmp/us081-evidence/rebased-{inputs,summary,diagnostics}.json, rebased-affected*, rebased-full*; prior failing and passing generations retained.
Integration and exclusions
This conversation owns US-081-only source integration through required PR gates, Gitea merge and fetched identical-tree verification, then immediate completion/wiki publication and stop. Recheck exact head/base and repository protections/reviews/checks before merge; if base advances, rebase and rerun affected plus full verification again. No direct source main push or protection bypass.
Branch/PR/merge publication may trigger CI/release. Ordinary exact-merge release/assets remain asynchronous/unverified. Existing final-plugin security/scanner/FS-SEC-10 holds are intact; this is not security, artifact or deployment clearance. No other-owner source work, runner/tooling/secret/workflow repair, live settings/server changes, GitOps preparation/push or deployment.
## Approved US-081 scope
Completes the two existing participation-mode event criteria through registered administrator creation/mode updates and native Quest Giver acceptance → acknowledged authority → US-092 JSONL.
- Original Quest Giver identity/location now accompanies camp acceptance.
- Existing dungeon quest outcome owner retains captured XP/coin pools as decimal strings.
- Existing camp/champion/dungeon created/changed payloads explicitly declare `application: future_acceptances`, preserving previous fields and event suffixes. No duplicate success owner/type or gameplay/persistence authority change.
- Four strict native suites prove all modes × partyless/member/leader choices; circle/rectangle/default definitions; correlated admin actions; denied/console/invalid/no-op/failed/concurrent/stale updates; failed acceptance and post-save party rollback; captured mode/roster/Giver/session/rewards across future policy changes and genuine rejected-writer owner-intent replay after restart.
Canonical story: https://git.garvis.dev/dmg/somc-okf/src/branch/main/user-stories/purpur-fantasy-stick/us-081-configure-adventure-participation-modes.md
## Verification
Meaningful RED: missing camp Giver, three dungeon pool variants, seven created/changed future-application cases. Earlier exact-menu, close-stage and console-port setup failures retained and corrected without weakening assertions/bounds, changing production authority or global mocks/harness.
Initial separate full gate passed 2,294 tests on the previous base; US-079 advanced main while it ran. This unpublished ticket was cleanly rebased and verification renewed:
- Tested head: `18769f40038b5c344eee577fb46557f7bb87d822`
- Tested Git tree: `179a4509fa8297ec3820199d629273373cc18699`
- Current target base: `d2090bd35a77975c3bdf3f09730e0260570a20ee`
- Affected: **595 tests = 441 JVM + 102 native + 52 tools**, zero failures/errors/skips/SEVERE.
- Separate fresh `./gradlew clean check jar`: **2,309 tests = 441 JVM + 1,816 native + 52 tools**, zero failures/errors/skips; all **26 new native cases clean**.
- All **644 frozen source hashes**, Node v26.9.0 executable and unchanged declared Java 25/native 1 GiB exact. Full 688 legacy SEVERE header/exception/cause-chain/normalized-first-frame signatures match the verified baseline, not blanket native/security clearance.
- Ordinary scoped diff review passes: four production paths and four new native suites only; `git diff --check` clean.
Evidence: `/private/tmp/us081-evidence/rebased-{inputs,summary,diagnostics}.json`, `rebased-affected*`, `rebased-full*`; prior failing and passing generations retained.
## Integration and exclusions
This conversation owns US-081-only source integration through required PR gates, Gitea merge and fetched identical-tree verification, then immediate completion/wiki publication and stop. Recheck exact head/base and repository protections/reviews/checks before merge; if base advances, rebase and rerun affected plus full verification again. No direct source main push or protection bypass.
Branch/PR/merge publication may trigger CI/release. Ordinary exact-merge release/assets remain asynchronous/unverified. Existing final-plugin security/scanner/FS-SEC-10 holds are intact; this is not security, artifact or deployment clearance. No other-owner source work, runner/tooling/secret/workflow repair, live settings/server changes, GitOps preparation/push or deployment.
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.
Approved US-081 scope
Completes the two existing participation-mode event criteria through registered administrator creation/mode updates and native Quest Giver acceptance → acknowledged authority → US-092 JSONL.
application: future_acceptances, preserving previous fields and event suffixes. No duplicate success owner/type or gameplay/persistence authority change.Canonical story: https://git.garvis.dev/dmg/somc-okf/src/branch/main/user-stories/purpur-fantasy-stick/us-081-configure-adventure-participation-modes.md
Verification
Meaningful RED: missing camp Giver, three dungeon pool variants, seven created/changed future-application cases. Earlier exact-menu, close-stage and console-port setup failures retained and corrected without weakening assertions/bounds, changing production authority or global mocks/harness.
Initial separate full gate passed 2,294 tests on the previous base; US-079 advanced main while it ran. This unpublished ticket was cleanly rebased and verification renewed:
18769f40038b5c344eee577fb46557f7bb87d822179a4509fa8297ec3820199d629273373cc18699d2090bd35a77975c3bdf3f09730e0260570a20ee./gradlew clean check jar: 2,309 tests = 441 JVM + 1,816 native + 52 tools, zero failures/errors/skips; all 26 new native cases clean.git diff --checkclean.Evidence:
/private/tmp/us081-evidence/rebased-{inputs,summary,diagnostics}.json,rebased-affected*,rebased-full*; prior failing and passing generations retained.Integration and exclusions
This conversation owns US-081-only source integration through required PR gates, Gitea merge and fetched identical-tree verification, then immediate completion/wiki publication and stop. Recheck exact head/base and repository protections/reviews/checks before merge; if base advances, rebase and rerun affected plus full verification again. No direct source main push or protection bypass.
Branch/PR/merge publication may trigger CI/release. Ordinary exact-merge release/assets remain asynchronous/unverified. Existing final-plugin security/scanner/FS-SEC-10 holds are intact; this is not security, artifact or deployment clearance. No other-owner source work, runner/tooling/secret/workflow repair, live settings/server changes, GitOps preparation/push or deployment.