Canonical US-011, approved in the operator conversation as the blocker enabler for US-077. Four native test/fixture files only. No production, CI, Gradle, heap, numerical-bound, scanner/security, live, GitOps or deployment change. Historical failures remain failures; controlled delay proves missing observation barriers, not the exact original full-run causes.
Switch native logout retains the persisted original session and awaits its actual character.switch_delay_started JSONL before teardown; all original default/zero/37-second and admission/custody assertions remain.
Real registered fishing giver/Paper journey awaits matching catalog/site/solo-character/snapshot plus native acceptance acknowledgment before reading its active quest. Original catch/Inventory/submission/reset/claim assertions remain.
Local strict native ports supply actual VILLAGER type/no fishing hook, not global mocks or suppression.
Controlled actual-worker RED: two failures, no errors/skips/SEVERE; connected GREEN: eight pass, no SEVERE.
Verified candidate
Head: a630490f5bafffc70f68502cfab7a3649f183079
Tree: 8aaefe3201ffc46f95b5532eb95a61d403f9914d
Base: 441037f5ff6e60f73fda47da8406ee0c9e8e34e6
All 632 frozen inputs unchanged through verification/commit.
Affected: 440 API + 74 native + 52 tools = 566, zero failures/errors/skips.
Own ./gradlew clean check jar --stacktrace: 2,185 (440 API + 1,693 native + 52 tools), zero failures/errors/skips; Java 25/native 1 GiB, existing bounds unchanged.
Full native legacy diagnostic signatures 688 versus baseline 694; only six local typed-port errors removed, no new header/exception/normalized-first-frame signature. No blanket native/security clearance.
Coordinator: this explicitly approved operator conversation. Before Gitea merge, recheck exact head/base, mergeability and current required checks/reviews. Any advancing base requires rebase plus affected and full branch verification; no direct main push. Verify actual merged/closed PR and fetched merged tree equality, immediately mark US-011 done and selectively publish wiki, then resume only approved US-077 for its own separately rebased verification/merge/closed PR; pause after US-077.
Branch/merge publication may trigger normal CI/release jobs. Those are tracked for the actual merged SHA; this is not security/artifact/live/deployment clearance or permission to change GitOps.
## Approved test-only verification enabler
[Canonical US-011](https://git.garvis.dev/dmg/somc-okf/src/branch/main/user-stories/purpur-fantasy-stick/us-011-verify-and-publish-plugin.md), approved in the operator conversation as the blocker enabler for US-077. Four native test/fixture files only. No production, CI, Gradle, heap, numerical-bound, scanner/security, live, GitOps or deployment change. Historical failures remain failures; controlled delay proves missing observation barriers, not the exact original full-run causes.
- Switch native logout retains the persisted original session and awaits its actual `character.switch_delay_started` JSONL before teardown; all original default/zero/37-second and admission/custody assertions remain.
- Real registered fishing giver/Paper journey awaits matching catalog/site/solo-character/snapshot plus native acceptance acknowledgment before reading its active quest. Original catch/Inventory/submission/reset/claim assertions remain.
- Local strict native ports supply actual VILLAGER type/no fishing hook, not global mocks or suppression.
- Controlled actual-worker RED: two failures, no errors/skips/SEVERE; connected GREEN: eight pass, no SEVERE.
## Verified candidate
- Head: `a630490f5bafffc70f68502cfab7a3649f183079`
- Tree: `8aaefe3201ffc46f95b5532eb95a61d403f9914d`
- Base: `441037f5ff6e60f73fda47da8406ee0c9e8e34e6`
- All 632 frozen inputs unchanged through verification/commit.
- Affected: 440 API + 74 native + 52 tools = **566**, zero failures/errors/skips.
- Own `./gradlew clean check jar --stacktrace`: **2,185** (440 API + 1,693 native + 52 tools), zero failures/errors/skips; Java 25/native 1 GiB, existing bounds unchanged.
- Full native legacy diagnostic signatures 688 versus baseline 694; only six local typed-port errors removed, no new header/exception/normalized-first-frame signature. No blanket native/security clearance.
- Operator-local retained artifacts: `/tmp/us011-switch-fishing-controlled-red.log`/results, `-connected-green.log`/results, `-affected.log`/results, `-full.log`, `-full-reports/test-results`, `-full-summary.json`, `-inputs.json`.
Coordinator: this explicitly approved operator conversation. Before Gitea merge, recheck exact head/base, mergeability and current required checks/reviews. Any advancing base requires rebase plus affected and full branch verification; no direct main push. Verify actual merged/closed PR and fetched merged tree equality, immediately mark US-011 done and selectively publish wiki, then resume only approved US-077 for its own separately rebased verification/merge/closed PR; pause after US-077.
Branch/merge publication may trigger normal CI/release jobs. Those are tracked for the actual merged SHA; this is not security/artifact/live/deployment clearance or permission to change GitOps.
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 test-only verification enabler
Canonical US-011, approved in the operator conversation as the blocker enabler for US-077. Four native test/fixture files only. No production, CI, Gradle, heap, numerical-bound, scanner/security, live, GitOps or deployment change. Historical failures remain failures; controlled delay proves missing observation barriers, not the exact original full-run causes.
character.switch_delay_startedJSONL before teardown; all original default/zero/37-second and admission/custody assertions remain.Verified candidate
a630490f5bafffc70f68502cfab7a3649f1830798aaefe3201ffc46f95b5532eb95a61d403f9914d441037f5ff6e60f73fda47da8406ee0c9e8e34e6./gradlew clean check jar --stacktrace: 2,185 (440 API + 1,693 native + 52 tools), zero failures/errors/skips; Java 25/native 1 GiB, existing bounds unchanged./tmp/us011-switch-fishing-controlled-red.log/results,-connected-green.log/results,-affected.log/results,-full.log,-full-reports/test-results,-full-summary.json,-inputs.json.Coordinator: this explicitly approved operator conversation. Before Gitea merge, recheck exact head/base, mergeability and current required checks/reviews. Any advancing base requires rebase plus affected and full branch verification; no direct main push. Verify actual merged/closed PR and fetched merged tree equality, immediately mark US-011 done and selectively publish wiki, then resume only approved US-077 for its own separately rebased verification/merge/closed PR; pause after US-077.
Branch/merge publication may trigger normal CI/release jobs. Those are tracked for the actual merged SHA; this is not security/artifact/live/deployment clearance or permission to change GitOps.