Cross-protocol double-count: both Y10k Capital vaults already tracked under rockawayx

[BhariGowda]

Both addresses added in the new "y10k-capital" registry entry
(registries/erc4626.js, PR #20059) are already live and counted under
projects/rockawayx/index.js right now:

1. Ethereum - 0x953972ea0C1703c58F09FB6fD2477Fdcf0FEe074

   • New: 'y10k-capital': { ethereum: ['0x953972ea0C1703c58F09FB6fD2477Fdcf0FEe074'] }
   • Already live: EMBER_VAULTS.ethereum, explicitly commented
     // eY10K, summed via sumERC4626Vaults.

2. Sei - 0x6137dcfdd3c83fe2922b1cba4105d2e92b327a06

   • New: 'y10k-capital': { sei: ['0x6137dcfdd3c83fe2922b1cba4105d2e92b327a06'] }
   • Already live: configs.blockchains.sei.morpho, commented
     // PYUSD0.

Both are wired into module.exports in the rockawayx file (confirmed,
not dead config) - so this isn't a coincidental address collision.
RockawayX's own // eY10K comment shows the connection was already
known when that file was written.

Also confirmed this is a real partnership, not an assumption: Y10k
Capital's own bio states "Risk operations by @RockawayX," and their
launch post describes RockawayX providing "institutional-grade risk
operations to every Y10k Capital deployment." Y10k Capital appears to
be the capital-sourcing/branding layer; RockawayX operates the actual
risk management on the same underlying vaults.

Since DefiLlama sums each project file independently with no
cross-project dedup, both vaults' real TVL is currently being counted
twice - once under RockawayX's protocol page, once under Y10k
Capital's.

Flagging rather than fixing unilaterally, since the right resolution
depends on how you want partnership-structured vaults attributed
(same category of call as the Sommelier/Veda BoringVault case) -
whether this belongs under one protocol, both with an explicit
"doublecounted" exclusion on one side, or a shared attribution model.

cc @RohanNero since you authored the y10k-capital commit that
introduced this overlap