Skip to content

Windows rig: check active ship and cargo against the live client #52

Open

Description

@Fazorath

Why

#51 builds the Windows test rig but leaves out the active ship and cargo, because the app can't read them from EVE until #47 (Fetch from EVE for the cargo before / cargo after fields) lands.

What

Once #47 is merged, extend the Windows rig and its run-windows skill to check, with the live character docked:

  • The active ship the app reads matches the ship in the client.
  • The cargo value from Fetch from EVE matches the client's estimated value of the cargo hold. Only the cargo hold counts, not drones or loaded ammo (see CONTEXT.md).
  • The check allows for ESI's asset cache of up to an hour (ADR 0001): note when the reading was taken, and if it doesn't match, compare again after the cache expires before calling it a failure.

All of #51's hard rules apply unchanged. Above all: no input to the EVE client, no undocking, a throwaway ABYSS_TRACKER_DB, live screenshots kept local, and announce any Gmail access.

Blocked by #47. Part of #51.

Metadata

Metadata

Assignees

No one assigned

    Labels

    buildPackaging and CIesiEVE Online ESI integrationready-for-agentSpec'd and safe for the night shift to build

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions