Skip to content

Radar blocking-score order and copy do not match #58

Description

@RainMona

Observed

Play 2026-08-20 evening, look-only /?view=radar (http://127.0.0.1:4220/). Pair blocking score on screen:

  • Pair 01 59.21%
  • Pair 02 30.95%
  • Pair 03–05 100.00%
  • Pair 06 56.27%
  • Pair 07 55.39%

The three 100% pairs sit in the middle. There is no grouping. The method strip still says positive bigint gross hints ranked first. bigint is a leaked type name (App.tsx radar-method-strip). Look-only; Refresh live radar / triage were not clicked.

Not #8 (Refresh live radar reads as a live feed). Not #9 (positive gross hints read as profit). Not #11 (pair spend CTA).

Why it matters

“Blocking score” plus “ranked first” promises an order the list does not keep. The strongest pairs are buried. bigint is an implementation leak in operator copy.

Proposed direction (not a spec)

Either sort (or group) by the score the heading names, or stop saying they are ranked that way. Drop the leaked type name. Do not start triage or spend from this strip.

Out of scope

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions