Original mission marker frames

Source image SHA256: 6891f70a021fa9f3a0e00458c284f48d1226e68ae7fc02ad48081aed47857e93. The bounded offline script Trace-GalaxyMissionMarkerIcons.py validates this hash and resolves the actual jump-table entries of original 3A4E940, without accessing or changing a running client.

Actual marker type	Table entry	Leaf	Original frame string
4	`3A4EB38`	`3A4E97F`	`5521BB8: GM_DisplayOptions_Missions`
45	`3A4EBDC`	`3A4E987`	`5524278: GM_Marker_MissionComplete`

Both exact frames are already extracted from the original current mapui icon resource. The provider's actual4/45 value is retained separately from MissionID and system address. Normal marker4 is not changed to45 by interpreting a mission name, public information, or Journal history. Producer/source details are separately documented in galaxy-original-fleet-mission-evidence.md.

GalaxyMissionMarkerStyles.BySystem uses every actual published SystemAddresses entry, not only the selected last target. Repeated identical types are deduplicated, while4 and45 at the same system both remain. An absent address set does not gain a marker at the selected address, and an unknown marker type does not silently select a known frame.

The view model attaches these styles to the existing process/FID-bound NativeAccountMarkers runtime source, which is excluded from JSON persistence. Explicit replacement, lost process, lost source or account switch removes old native styles. Journal positive mission history remains a separate source. Main map uses the exact frames and offsets simultaneous icons so a completed and ordinary mission do not overlap each other. Both remain subject to the same mission query target and independent mission display switch.

Core tests verify shared systems, full address sets, duplicate removal, unknown types, explicit replacement, object reuse, disk exclusion and account/process isolation. Final screenshot and current-version live acceptance are separate checks; fixture/source evidence does not establish cache freshness or whole-account completeness.

# Original mission marker frames Source image SHA256: `6891f70a021fa9f3a0e00458c284f48d1226e68ae7fc02ad48081aed47857e93`. The bounded offline script `Trace-GalaxyMissionMarkerIcons.py` validates this hash and resolves the actual jump-table entries of original `3A4E940`, without accessing or changing a running client. | Actual marker type | Table entry | Leaf | Original frame string | | --- | --- | --- | --- | | 4 | `3A4EB38` | `3A4E97F` | `5521BB8: GM_DisplayOptions_Missions` | | 45 | `3A4EBDC` | `3A4E987` | `5524278: GM_Marker_MissionComplete` | Both exact frames are already extracted from the original current mapui icon resource. The provider's actual4/45 value is retained separately from MissionID and system address. Normal marker4 is not changed to45 by interpreting a mission name, public information, or Journal history. Producer/source details are separately documented in `galaxy-original-fleet-mission-evidence.md`. `GalaxyMissionMarkerStyles.BySystem` uses every actual published `SystemAddresses` entry, not only the selected last target. Repeated identical types are deduplicated, while4 and45 at the same system both remain. An absent address set does not gain a marker at the selected address, and an unknown marker type does not silently select a known frame. The view model attaches these styles to the existing process/FID-bound `NativeAccountMarkers` runtime source, which is excluded from JSON persistence. Explicit replacement, lost process, lost source or account switch removes old native styles. Journal positive mission history remains a separate source. Main map uses the exact frames and offsets simultaneous icons so a completed and ordinary mission do not overlap each other. Both remain subject to the same `mission` query target and independent mission display switch. Core tests verify shared systems, full address sets, duplicate removal, unknown types, explicit replacement, object reuse, disk exclusion and account/process isolation. Final screenshot and current-version live acceptance are separate checks; fixture/source evidence does not establish cache freshness or whole-account completeness.