Problem: An opt-in hosted discovery-index plane is fully documented but 0% implemented — none of its configuration is referenced anywhere in the actual codebase. It's also a narrower concept than this milestone's cross-tenant execution work (sharing a discovery corpus, not each miner's own claims/queue/plans), and it's unclear whether it should be built as originally documented, folded into this milestone's broader hosted architecture, or retired.
Area: AMS / Product decision
Proposal: Make an explicit decision — build as documented, redesign as part of this milestone's broader architecture, or retire the concept and remove the dead documentation and config references (including the extension's own dead config field tracked in the Miner Wave 4 milestone).
Deliverables:
- A documented decision and, if retiring, removal of the dead references it leaves behind.
Problem: An opt-in hosted discovery-index plane is fully documented but 0% implemented — none of its configuration is referenced anywhere in the actual codebase. It's also a narrower concept than this milestone's cross-tenant execution work (sharing a discovery corpus, not each miner's own claims/queue/plans), and it's unclear whether it should be built as originally documented, folded into this milestone's broader hosted architecture, or retired.
Area: AMS / Product decision
Proposal: Make an explicit decision — build as documented, redesign as part of this milestone's broader architecture, or retire the concept and remove the dead documentation and config references (including the extension's own dead config field tracked in the Miner Wave 4 milestone).
Deliverables: