com_r35157_nenjim-hubd-impl_ref/openspec/changes/archive/2026-10-06-93-add-minimum-eve-burn-and-reserve/verification.md

Verification

Verified on 2026-10-06 with /usr/local/software/java/jfx-25.

Compilation and controlled acceptance checks

• JAVA_HOME=/usr/local/software/java/jfx-25 ./gradlew compileJava compileTestJava --offline --no-daemon → BUILD SUCCESSFUL in 6s; normal Detag and both source compilations executed. The initial sandbox attempt could not create Gradle's existing cache lock outside the workspace; the same compilation passed with approved cache access.
• Temporary harness sources in /tmp/evelyn-issue93 compiled with javac --enable-preview --release 25 -cp 'build/classes/java/main:build/libs/*' -d /tmp/evelyn-issue93.
• java --enable-preview -cp '/tmp/evelyn-issue93:build/classes/java/main:build/libs/*' Issue93Verification → PASS: 235 focused burn-policy assertions.
• Same invocation for the copied Issue92Verification → PASS: 89 buyback-minimum regression assertions.
• Same invocation for the copied Issue91Verification, restricted to its burner checks → PASS: 63 pending-swap/recovery regression assertions. Unchanged RPC/Jupiter library checks were not rerun.
• Production source check confirms canonical EVE minimum 0.1 and reserve 0.01 in the correct constructor order and preserved input bounds, hourly interval, freshness and finalization arguments.

All wallet, transaction, chain, pricing and notification dependencies are controlled. No real RPC, signing or live financial operation occurs. No permanent automated tests were added. The older temporary harness copies add only a positive EVE burn minimum of 0.000001 and zero reserve to their constructor calls, retaining their original buyback/recovery expectations; original temporary files are preserved.

The #93 checks cover every issue #93 1/0.1 example and production 0.1/0.01 boundaries, numerical equality across decimal scales, zero reserve, fractional minimum above the rounded candidate, fractional reserve preservation, zero after rounding, both SPL Token and Token-2022 precision, missing/unsupported mint data, supply/mint/program mismatch, invalid decimals, I/O and interruption, missing/negative balance, stale price, repeated small buyback accumulation and subsequent reserve-based accumulation, direct deposits with absent/below-minimum inputs, no burn maximum, failed/unknown buybacks, original pending signature and amount/value across timeout/I/O/interruption, failed finalization without notification, once-only notification after delayed finalization, delivery failure and signature-less burn suspension with continued buybacks. Null/invalid numeric configuration, wrong/unknown UUIDs and stale EVE metadata are checked before worker/transaction activity; CurrencyType itself rejects null UUIDs before burner configuration.

An initial temporary harness compile failed because its notification-error fixture used Throwable rather than the transport's IOException contract; the fixture was corrected. Its default successful swap output was also corrected from zero to a positive amount, preventing fixture-only result validation failures. The final checks above pass against the unchanged production implementation.

Review and workflow

Parent independent source/design/documentation and harness review found no material findings. Two delta scenario wording fixes were applied to state the actual eligible amount and grammatically separate the new production burn settings. Scope is limited to constructor burn policy, EVE eligibility/actual amount use, JavaDoc, production arguments, Evelyn docs and their specification. Buyback limits, priority, pending recovery, lifecycle, Jupiter, Ticker, ValueTags and private deployment files are preserved.

Strict active-change validation and git diff --check passed before synchronization. Final strict validation of the active change and synchronized main specification passed. Six delta requirement blocks match the main specification exactly; 12 untouched requirements remain byte-for-byte intact. The purpose now describes accumulated, threshold-qualified burns above reserve. Existing long-requirement informational hints remain because modified requirement blocks stay whole.

An initial temporary synchronization matcher allowed a requirement title to span lines and copied an invalid delta header into the main specification. Strict validation caught this before archive. The matcher was corrected and the main-spec edit rebuilt from the clean starting version plus the six intended blocks, then compared for exact delta matching and untouched-content preservation. Final strict validation passes.

All four planning artifacts and all five tasks are complete. The completed change is archived at openspec/changes/archive/2026-10-06-93-add-minimum-eve-burn-and-reserve. After archival, openspec list --json reports no active changes, and openspec validate --archived --json --report findings passed for all 31 archived changes with 0 failures. Final whitespace validation also passes.

No deployment, push, Gitea write or live integration was performed.