com_r35157_nenjim-hubd-impl_ref/openspec/changes/archive/2026-10-07-94-gate-buybacks-on-evelyn-reference-price/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 8s. Normal Gradle-integrated Detag and both source compilations executed. The initial sandbox attempt could not create the existing Gradle cache lock outside the workspace; the same compilation passed with approved cache access.
• Temporary sources in /tmp/evelyn-issue94 compiled with javac --enable-preview --release 25 -cp 'build/classes/java/main:build/libs/*' -d /tmp/evelyn-issue94.
• java --enable-preview -cp '/tmp/evelyn-issue94:build/classes/java/main:build/libs/*' Issue94Verification → PASS: 459 focused issue #94 assertions.
• The copied Issue93Verification → PASS: 246 burn-policy regression assertions.
• The copied Issue92Verification → PASS: 115 input-minimum regression assertions.
• The copied Issue91Verification, restricted to burner checks → PASS: 80 pending-swap/recovery regression assertions. Unchanged Solana/Jupiter library checks were not rerun.
• Production composition source check verifies the corresponding Production status dependency and preserved input reserves/minima/maxima, EVE burn minimum/reserve, hourly interval, slippage, freshness and finalization arguments.
• An INFO/WARN-enabled controlled run verifies purchase-skip reasons for at/above reference, unavailable/invalid reference and unusable market price, without arbitrary reference/Ticker exception messages.

The 900 controlled assertions invoke the actual burner iteration with offline wallet, chain, swap, Ticker, reference and notification collaborators. No RPC, signing, live financial operation, application/Hub startup or deployment configuration read occurs. The Hub dependency guard is invoked directly without constructing a Hub. No permanent automated tests were added. Prior harness copies only add an always-below reference stub to constructor calls and update #92's expected canonical EVE/USDT lookup count for eligible purchases; original temporary files remain intact.

The #94 harness covers 14.99/15.00/15.01 against reference 15, numeric equality across scales, a close below-reference decimal, the current reference decision instant instead of observation/history time, complete independent burns and reserve preservation, missing/unavailable/non-positive/null-amount/wrong-pair market and reference data, stale market observations, fresh independent burn valuation after a purchase-price failure, stale burn valuation postponement, next-iteration recovery from every rejection category, input priority and amount limits, below-minimum input fallback, no-eligible-input/direct-EVE-only paths, manual swap suspension and null status validation. It verifies original-signature read-only reconciliation while price is above reference, unresolved retention, definitive success/failure/proven expiry followed by a newly rejected purchase, later below-reference recovery, and simultaneous pending burn/swap priority with no reference lookup or new transaction. PriceObservation itself rejects null observation timestamp/price before they can reach the burner.

An initial temporary harness compilation used the wrong fully qualified component-ID type; it was corrected to the repository's existing com.r35157.nenjim.service.registry.valuetypes.NenjimComponentId. Final compiled checks pass. Concurrent initial Java invocations reported harmless performance-data lock warnings; the controlled diagnostic run disabled performance data. No production fix was needed for either verification-only issue.

Review and workflow

Parent independent review of the proposal/specs/design, implementation, operating documentation and controlled harness found no actionable findings. The existing malformed burn JavaDoc line was corrected while updating that same list item. Scope is limited to the required reference dependency, new-purchase condition, Hub composition, related documentation and two OpenSpec capability deltas. Transaction execution, reconciliation, burn valuation/policy, ValueTags, scheduling and private deployment files retain their existing behavior.

Strict validation of the active change and git diff --check pass. All four planning artifact types and all five implementation tasks are complete. The active change is ready for review; main specifications have not been synchronized and the change has not been archived.

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

Follow-up: clearer purchase-skip logs

The owner's requested logging refinement keeps price eligibility unchanged. INFO price skips now show a direct labelled comparison, for example Skipping buyback as EVE price is at or above reference (market=15.01 >= reference=15 USDT/EVE), followed by the trading pair, decision instant and next action. Prices use plain decimals without redundant trailing zeros. WARN skips retain their reason; unavailable or invalid reference-price diagnostics also include the known market price.

JAVA_HOME=/usr/local/software/java/jfx-25 ./gradlew compileJava --offline --no-daemon passed. The existing temporary #94 harness passed its 459 assertions again with INFO/WARN enabled. Its captured output in /tmp/evelyn-issue94/issue94-logging-refinement.log confirms the numeric comparison for both equality and higher prices, reference failure details, missing/stale market diagnostics and exclusion of arbitrary exception messages. No new tests were added.