feat: audit log every successful chunk claim

[tastybento]

Summary

• Logs a detailed audit line on every successful chunk claim: player name, UUID, exact position, look direction, action type (LEFT_CLICK_AIR vs LEFT_CLICK_BLOCK etc.), whether a block was clicked (vs air ray-trace), sneaking state, target chunk coords, distance from nearest border of the claimed chunk, confirmation setting, chunk count, and credit before/after
• Changes attemptClaim return type from void to ClaimResult so the caller can react to the outcome

Context

A player reported two chunks being claimed while they were mining a cobble generator "nowhere near the chunk border" with no other island members online. With require-confirmation: true, an accidental claim requires four separate LEFT_CLICK_AIR events with sneaking on the 2nd and 4th — extremely unlikely but not impossible if the player was closer to a border than they realized.

The audit trail will capture the exact trigger conditions if this happens again. Key fields for investigation:

• borderDist — was the player actually within 5 blocks of a locked chunk?
• action — was it LEFT_CLICK_AIR (cobble-generator gap)?
• sneaking — was the confirmation path involved?
• clickedBlock — was there a block under the crosshair?

Example log output

CHUNK CLAIM: player=AiboPals uuid=abc-123 at=[108.5, 65.0, 200.3] yaw=90 pitch=15 action=LEFT_CLICK_AIR clickedBlock=false sneaking=true chunk=(7,13) offset=(1,0) borderDist=3.5 confirm=true count=8 credit=147->131

Test plan

• All 727 existing tests pass (including 22 ChunkClaimListenerTest tests)
• Deploy to test server, claim a chunk, verify audit line appears in console/log

🤖 Generated with Claude Code

https://claude.ai/code/session_01B94CWZDoiM9VevWtXb4RxF

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
100.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[tastybento]

Summary

• Logs a detailed audit line on every successful chunk claim: player name, UUID, exact position, look direction, action type (LEFT_CLICK_AIR vs LEFT_CLICK_BLOCK etc.), whether a block was clicked (vs air ray-trace), sneaking state, target chunk coords, distance from nearest border of the claimed chunk, confirmation setting, chunk count, and credit before/after
• Changes attemptClaim return type from void to ClaimResult so the caller can react to the outcome

Context

A player reported two chunks being claimed while they were mining a cobble generator "nowhere near the chunk border" with no other island members online. With require-confirmation: true, an accidental claim requires four separate LEFT_CLICK_AIR events with sneaking on the 2nd and 4th — extremely unlikely but not impossible if the player was closer to a border than they realized.

The audit trail will capture the exact trigger conditions if this happens again. Key fields for investigation:

• borderDist — was the player actually within 5 blocks of a locked chunk?
• action — was it LEFT_CLICK_AIR (cobble-generator gap)?
• sneaking — was the confirmation path involved?
• clickedBlock — was there a block under the crosshair?

Example log output

CHUNK CLAIM: player=AiboPals uuid=abc-123 at=[108.5, 65.0, 200.3] yaw=90 pitch=15 action=LEFT_CLICK_AIR clickedBlock=false sneaking=true chunk=(7,13) offset=(1,0) borderDist=3.5 confirm=true count=8 credit=147->131

Test plan

• All 727 existing tests pass (including 22 ChunkClaimListenerTest tests)
• Deploy to test server, claim a chunk, verify audit line appears in console/log

🤖 Generated with Claude Code

https://claude.ai/code/session_01B94CWZDoiM9VevWtXb4RxF

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
100.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[tastybento]

Summary

• Logs a detailed audit line on every successful chunk claim: player name, UUID, exact position, look direction, action type (LEFT_CLICK_AIR vs LEFT_CLICK_BLOCK etc.), whether a block was clicked (vs air ray-trace), sneaking state, target chunk coords, distance from nearest border of the claimed chunk, confirmation setting, chunk count, and credit before/after
• Changes attemptClaim return type from void to ClaimResult so the caller can react to the outcome

Context

A player reported two chunks being claimed while they were mining a cobble generator "nowhere near the chunk border" with no other island members online. With require-confirmation: true, an accidental claim requires four separate LEFT_CLICK_AIR events with sneaking on the 2nd and 4th — extremely unlikely but not impossible if the player was closer to a border than they realized.

The audit trail will capture the exact trigger conditions if this happens again. Key fields for investigation:

• borderDist — was the player actually within 5 blocks of a locked chunk?
• action — was it LEFT_CLICK_AIR (cobble-generator gap)?
• sneaking — was the confirmation path involved?
• clickedBlock — was there a block under the crosshair?

Example log output

CHUNK CLAIM: player=AiboPals uuid=abc-123 at=[108.5, 65.0, 200.3] yaw=90 pitch=15 action=LEFT_CLICK_AIR clickedBlock=false sneaking=true chunk=(7,13) offset=(1,0) borderDist=3.5 confirm=true count=8 credit=147->131

Test plan

• All 727 existing tests pass (including 22 ChunkClaimListenerTest tests)
• Deploy to test server, claim a chunk, verify audit line appears in console/log

🤖 Generated with Claude Code

https://claude.ai/code/session_01B94CWZDoiM9VevWtXb4RxF

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
100.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[tastybento]

Summary

• Logs a detailed audit line on every successful chunk claim: player name, UUID, exact position, look direction, action type (LEFT_CLICK_AIR vs LEFT_CLICK_BLOCK etc.), whether a block was clicked (vs air ray-trace), sneaking state, target chunk coords, distance from nearest border of the claimed chunk, confirmation setting, chunk count, and credit before/after
• Changes attemptClaim return type from void to ClaimResult so the caller can react to the outcome

Context

A player reported two chunks being claimed while they were mining a cobble generator "nowhere near the chunk border" with no other island members online. With require-confirmation: true, an accidental claim requires four separate LEFT_CLICK_AIR events with sneaking on the 2nd and 4th — extremely unlikely but not impossible if the player was closer to a border than they realized.

The audit trail will capture the exact trigger conditions if this happens again. Key fields for investigation:

• borderDist — was the player actually within 5 blocks of a locked chunk?
• action — was it LEFT_CLICK_AIR (cobble-generator gap)?
• sneaking — was the confirmation path involved?
• clickedBlock — was there a block under the crosshair?

Example log output

CHUNK CLAIM: player=AiboPals uuid=abc-123 at=[108.5, 65.0, 200.3] yaw=90 pitch=15 action=LEFT_CLICK_AIR clickedBlock=false sneaking=true chunk=(7,13) offset=(1,0) borderDist=3.5 confirm=true count=8 credit=147->131

Test plan

• All 727 existing tests pass (including 22 ChunkClaimListenerTest tests)
• Deploy to test server, claim a chunk, verify audit line appears in console/log

🤖 Generated with Claude Code

https://claude.ai/code/session_01B94CWZDoiM9VevWtXb4RxF

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
100.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[tastybento]

Summary

• Logs a detailed audit line on every successful chunk claim: player name, UUID, exact position, look direction, action type (LEFT_CLICK_AIR vs LEFT_CLICK_BLOCK etc.), whether a block was clicked (vs air ray-trace), sneaking state, target chunk coords, distance from nearest border of the claimed chunk, confirmation setting, chunk count, and credit before/after
• Changes attemptClaim return type from void to ClaimResult so the caller can react to the outcome

Context

A player reported two chunks being claimed while they were mining a cobble generator "nowhere near the chunk border" with no other island members online. With require-confirmation: true, an accidental claim requires four separate LEFT_CLICK_AIR events with sneaking on the 2nd and 4th — extremely unlikely but not impossible if the player was closer to a border than they realized.

The audit trail will capture the exact trigger conditions if this happens again. Key fields for investigation:

• borderDist — was the player actually within 5 blocks of a locked chunk?
• action — was it LEFT_CLICK_AIR (cobble-generator gap)?
• sneaking — was the confirmation path involved?
• clickedBlock — was there a block under the crosshair?

Example log output

CHUNK CLAIM: player=AiboPals uuid=abc-123 at=[108.5, 65.0, 200.3] yaw=90 pitch=15 action=LEFT_CLICK_AIR clickedBlock=false sneaking=true chunk=(7,13) offset=(1,0) borderDist=3.5 confirm=true count=8 credit=147->131

Test plan

• All 727 existing tests pass (including 22 ChunkClaimListenerTest tests)
• Deploy to test server, claim a chunk, verify audit line appears in console/log

🤖 Generated with Claude Code

https://claude.ai/code/session_01B94CWZDoiM9VevWtXb4RxF

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
100.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[tastybento]

Summary

• Logs a detailed audit line on every successful chunk claim: player name, UUID, exact position, look direction, action type (LEFT_CLICK_AIR vs LEFT_CLICK_BLOCK etc.), whether a block was clicked (vs air ray-trace), sneaking state, target chunk coords, distance from nearest border of the claimed chunk, confirmation setting, chunk count, and credit before/after
• Changes attemptClaim return type from void to ClaimResult so the caller can react to the outcome

Context

A player reported two chunks being claimed while they were mining a cobble generator "nowhere near the chunk border" with no other island members online. With require-confirmation: true, an accidental claim requires four separate LEFT_CLICK_AIR events with sneaking on the 2nd and 4th — extremely unlikely but not impossible if the player was closer to a border than they realized.

The audit trail will capture the exact trigger conditions if this happens again. Key fields for investigation:

• borderDist — was the player actually within 5 blocks of a locked chunk?
• action — was it LEFT_CLICK_AIR (cobble-generator gap)?
• sneaking — was the confirmation path involved?
• clickedBlock — was there a block under the crosshair?

Example log output

CHUNK CLAIM: player=AiboPals uuid=abc-123 at=[108.5, 65.0, 200.3] yaw=90 pitch=15 action=LEFT_CLICK_AIR clickedBlock=false sneaking=true chunk=(7,13) offset=(1,0) borderDist=3.5 confirm=true count=8 credit=147->131

Test plan

• All 727 existing tests pass (including 22 ChunkClaimListenerTest tests)
• Deploy to test server, claim a chunk, verify audit line appears in console/log

🤖 Generated with Claude Code

https://claude.ai/code/session_01B94CWZDoiM9VevWtXb4RxF

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
100.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[tastybento]

Summary

• Logs a detailed audit line on every successful chunk claim: player name, UUID, exact position, look direction, action type (LEFT_CLICK_AIR vs LEFT_CLICK_BLOCK etc.), whether a block was clicked (vs air ray-trace), sneaking state, target chunk coords, distance from nearest border of the claimed chunk, confirmation setting, chunk count, and credit before/after
• Changes attemptClaim return type from void to ClaimResult so the caller can react to the outcome

Context

A player reported two chunks being claimed while they were mining a cobble generator "nowhere near the chunk border" with no other island members online. With require-confirmation: true, an accidental claim requires four separate LEFT_CLICK_AIR events with sneaking on the 2nd and 4th — extremely unlikely but not impossible if the player was closer to a border than they realized.

The audit trail will capture the exact trigger conditions if this happens again. Key fields for investigation:

• borderDist — was the player actually within 5 blocks of a locked chunk?
• action — was it LEFT_CLICK_AIR (cobble-generator gap)?
• sneaking — was the confirmation path involved?
• clickedBlock — was there a block under the crosshair?

Example log output

CHUNK CLAIM: player=AiboPals uuid=abc-123 at=[108.5, 65.0, 200.3] yaw=90 pitch=15 action=LEFT_CLICK_AIR clickedBlock=false sneaking=true chunk=(7,13) offset=(1,0) borderDist=3.5 confirm=true count=8 credit=147->131

Test plan

• All 727 existing tests pass (including 22 ChunkClaimListenerTest tests)
• Deploy to test server, claim a chunk, verify audit line appears in console/log

🤖 Generated with Claude Code

https://claude.ai/code/session_01B94CWZDoiM9VevWtXb4RxF

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
100.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[tastybento]

Summary

• Logs a detailed audit line on every successful chunk claim: player name, UUID, exact position, look direction, action type (LEFT_CLICK_AIR vs LEFT_CLICK_BLOCK etc.), whether a block was clicked (vs air ray-trace), sneaking state, target chunk coords, distance from nearest border of the claimed chunk, confirmation setting, chunk count, and credit before/after
• Changes attemptClaim return type from void to ClaimResult so the caller can react to the outcome

Context

A player reported two chunks being claimed while they were mining a cobble generator "nowhere near the chunk border" with no other island members online. With require-confirmation: true, an accidental claim requires four separate LEFT_CLICK_AIR events with sneaking on the 2nd and 4th — extremely unlikely but not impossible if the player was closer to a border than they realized.

The audit trail will capture the exact trigger conditions if this happens again. Key fields for investigation:

• borderDist — was the player actually within 5 blocks of a locked chunk?
• action — was it LEFT_CLICK_AIR (cobble-generator gap)?
• sneaking — was the confirmation path involved?
• clickedBlock — was there a block under the crosshair?

Example log output

CHUNK CLAIM: player=AiboPals uuid=abc-123 at=[108.5, 65.0, 200.3] yaw=90 pitch=15 action=LEFT_CLICK_AIR clickedBlock=false sneaking=true chunk=(7,13) offset=(1,0) borderDist=3.5 confirm=true count=8 credit=147->131

Test plan

• All 727 existing tests pass (including 22 ChunkClaimListenerTest tests)
• Deploy to test server, claim a chunk, verify audit line appears in console/log

🤖 Generated with Claude Code

https://claude.ai/code/session_01B94CWZDoiM9VevWtXb4RxF

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
100.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud