---
title: Remove the wager-record leaks feature until the feature is clarified
type: task
status: in_progress
description: >-
  Remove the unclear wager-record leaks display from the wagers page end to end (UI, API, lib,
  script flag, tests, docs); land scope for a clearer re-introduction.
base_uri: user:task/league/remove-wager-record-leaks-feature.md
created_at: '2026-10-12T00:46:09.373Z'
entity_id: 727e1b83-6d1e-4201-ba2e-d84dd3ca3568
owner_identity_uri: █████████████████████████
public_read: true
tags:
  - user:tag/league-xo-football.md
updated_at: '2026-10-12T00:46:09.373Z'
visibility_analyzed_at: '2026-11-05T23:50:01.468Z'
---

## What

Remove the wager-record "leaks" feature from the wagers page end to end, because the "N leaks" display (seen as "3 leaks" on /m/trashman/wagers) was unclear and the feature's use case is unsettled. Reopen only when the operator has clarity on what the feature is for and what it should communicate.

## Plan

- [x] Remove the leaks feature end to end: GET /wager-record/:owner_user_id/leaks, libs-server/wager-record/find-wager-record-leaks.mjs, the --leaks flag on scripts/run-wager-record.mjs, the SPA wiring (action types, saga call, reducer slice, API client binding, describe_wager_record_leak), and the RecordLeaks component and styles on /wagers and /m/:username/wagers.
- [x] Trim the leak specs and the docs/guides/{data,api}.md references, and update the db/gates/check-spa-stale-column-reads value adjudication to keep only wagers-view.js.
- [x] Verify locally: the three wager-record specs (27 passing), the action-type-registration spec, eslint on every changed file, and the stale-column-read gate. Committed as 9b296f1a6 (19 files, +29 / -611); the record headline and POST /api/wager-record/search stay.
- [x] Confirm the local verify chain on the commit: the pre-push guard's own run passed for 9b296f1a6 (memoized at pass, 169s in the guard's submodule-free worktree) — the same oracle a real push would have used.
- [ ] See the commit's CI once its push lands: the push is held by a live sibling's uncommitted tree (share-wagers-link.mjs and the private pointer), so it converges when that tree clears; check-red-main.sh already watches the branch for a red.
- [ ] Record the operator's decision on whether and how to re-introduce the feature (the reopen trigger is clarity on what a leak should mean and say).

## Notes

The private submodule showed M during the work from a concurrent session's pointer change, not mine; I left it untouched. Sibling session ██████████████████████████████ is also live in the league repo on the wagers-page domain; its uncommitted share-wagers-link.mjs edit is what holds the league push of 9b296f1a6.