fix(accounts): declare unpriceable positions instead of dropping them silently

[JSONbored]

/api/v1/accounts/{ss58}/positions published position_count: 0,
total_stake_alpha: 0 and no degraded block for coldkeys that demonstrably hold positions in
the ledger it reads.

Coldkey 5Df7xwEP… is the first row of chain.nominator_positions — hotkey 5FyVinYp…,
netuid 18, share_fraction: 1 — and the route answered zero. Indistinguishable from "this account
delegates nothing."

The skip is correct; the silence was not

buildAccountPositions prices each position off the live neurons table and skips any it cannot
price. That skip stays: #9066 removed the unpriced_* escape hatches, so a position with no
known stake must not be published with a fabricated stake_tao: 0. What was missing is any signal
that it happened.

neurons carries only currently-registered neurons while the position ledger is a snapshot, so
the overlap is far worse than it looks — sampling eight distinct hotkeys from the live ledger, only
1 of 8 was present in neurons. And neurons itself is healthy (129 netuids, 30,085 rows,
captured minutes ago), so this does not heal on its own.

Fix

POSITIONS_DEGRADED_UNPRICEABLE, set whenever any row was dropped for want of a price.

Any, not all: a partially-priced total understates the account just as silently and is harder
to notice, because the payload looks healthy for carrying positions.

A malformed row is deliberately not counted — that is bad data, not an unpriced holding, and
conflating them would report a pricing problem that is not happening.

The existing snapshot_predates_stake_activity still wins when both apply: both mean "do not trust
this total", and that one says why more usefully and carries the two provenance stamps this pure
builder cannot see. When the annotator does not contradict the zero, this marker survives its pass
— both directions are tested.

No schema change. degraded.reason is a free-form string, and the block is absent on every
trustworthy answer, so a consumer that ignores it reads exactly what it read before.
validate:contract-drift passes and npm run build produces no diff.

Verification

Four mutations, each caught:

mutation	tests failed
revert to the silent skip	4
mark only all-zero results	1
mark when nothing was dropped	3
count malformed rows as unpriceable	1

Patch coverage 9/9 = 100% with every branch taken, measured by intersecting the diff's line
ranges with v8's uncovered set. 457 tests pass across the positions suites plus
request-handlers-entities; tsc --noEmit, prettier and eslint clean.

Two things this does NOT fix, both filed in #9305

• nominator_positions does not exist as a table in production D1 (only account_position_daily
  does), so fix(accounts): nominator_positions has no live refresh — /positions is frozen at the export and drifts forever #9273's hot leg can never fire and the route is pinned to a frozen 2026-08-02 export.
  Whether to create it or abandon the lane is a call I did not make unilaterally — it is a
  production schema change.
• Whether callers should additionally get a dropped_position_count is a contract question left
  open there.

Refs #9305

[superagent-security]

Superagent didn't find any vulnerabilities or security issues in this PR.

[cloudflare-workers-and-pages]

Deploying with    Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status	Name	Latest Commit	Updated (UTC)
✅ Deployment successful! View logs	metagraphed-data-api	3ace7f3	Aug 03 2026, 08:40 PM

[cloudflare-workers-and-pages]

Deploying with    Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status	Name	Latest Commit	Updated (UTC)
✅ Deployment successful! View logs	metagraphed-registry-sync-api	3ace7f3	Aug 03 2026, 08:40 PM