Skip to content

gas-huffer: bring NEVER FLOWN doc comments in line with seven recorded runs - #489

Merged
smerwin merged 1 commit into
mainfrom
gas-huffer-flown-notes
Sep 10, 2026
Merged

smerwin merged 1 commit into
mainfrom
gas-huffer-flown-notes

Conversation

@smerwin

@smerwin smerwin commented Sep 10, 2026

Copy link
Copy Markdown
Owner

Summary

  • The header, the cloak-fitted doc comment, the evasion/deposit give-up bounds, and the runtime status-line string all still framed this app as "never flown" / "nobody has watched", even though seven runs (1-7) have now flown since those comments were written.
  • Rewrites each against what those runs actually show, with run numbers and specific evidence rather than restated speculation:
    • Harvesting, D-Scan hostile detection and the evade/recover loop: confirmed live across runs 1-5 (hundreds of readings, both harvesters cycling; named D-Scan rows read; the harvester periodic-recheck oscillation bug caught and fixed as harvesterLooksActiveByRamp, PR gas-huffer: fix the four defects that stopped it flying, and command the orbit range (#485) #486).
    • Cloak tooltip identification: still unverified -- has never once resolved live in any recorded run (always 0 of 2 identified); only the blind hotkey fallback has fired (13-14 times in runs 1 and 5).
    • Evasion give-up bound: never fired live, but the counter it bounds has been watched running twice (run 1 recovered from several short evasions; run 6 reached 83/600 before being stopped by hand).
    • Deposit give-up bound: has fired live, on run 3 -- hold filled, ran its full 300-reading give-up with zero drags dispatched, meaning whatever stopped it happened before the hangar work even started (the dock, most likely, unconfirmed).
    • Propulsion module reading: has never once resolved to running on a live client -- every run prints CANNOT TELL exactly once (the status line's own change-only suppression) and nothing else.
    • Wormhole-chain-hop retreat: never fired live.

Test plan

  • Doc-comment-only change; no logic, settings, or bound values touched.
  • Verified the diff is scoped to comments and the runtime status string (git diff --stat shows only doc/comment deltas).
  • Cross-checked each claim against the recorded logs in ~/eve-bot-logs/gas_huffer_run{1..7}.log before writing it.

🤖 Generated with Claude Code

…d runs

The header, the cloak-fitted doc comment, the evasion and deposit give-up
bounds, and the runtime status-line string all still said "never flown" or
"nobody has watched" after seven recorded sessions. Rewrite each against
what those runs actually show: harvesting, D-Scan hostile detection and the
evade/recover loop confirmed live across runs 1-5; the cloak tooltip never
once resolving in any run, with only the blind hotkey fallback observed;
the evasion counter recovering from short evasions in run 1 and reaching
83/600 in run 6; and the deposit give-up firing live in run 3, its
300-reading bound running to the end with zero drags dispatched -- a
failure before the hangar work rather than the confirmation step the old
comment worried about.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
@smerwin
smerwin merged commit 0dd2d93 into main Sep 10, 2026
1 of 3 checks passed
@smerwin
smerwin deleted the gas-huffer-flown-notes branch September 10, 2026 20:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant