Legacy V2 (registry/treasury) DAOs no longer appear anywhere; re-indexing path documented

**Status: parked. This becomes actionable only if members of a V2 DAO ask for it.**

## Background

The indexer deployment that served legacy V2 DAOs (`v2-homebase-indexer.w3api.dev`) is gone (NXDOMAIN), and its database with it. #966 removed the app's dead client for it. The legacy app at v2.tezos-homebase.io still serves its bundle but points at the same dead host, so V2 DAO data is currently unreachable everywhere. The DAOs themselves are intact on-chain: 31 V2 DAOs on mainnet (20 registry, 11 treasury), enumerable via TzKT (`/v1/contracts?typeHash=-1969785317`), including Crunchy.Network, Bean DAO, Matter DAO and Sebuh.net. An earlier 2021 generation (33 contracts, typeHash -1585634750) went unindexed even before that.

## Observed activity

Checked via TzKT (2026-08-16): the most recent governance action found across the V2 set is an `unfreeze` on the Sebuh.net DAO in March 2024; most of the 31 have had no governance operations since 2022. Later account activity is passive deposits only (NFT and XTZ transfers into treasury addresses, most recently July 2026), which requires no frontend. In short: no evidence of anyone currently trying to govern these DAOs, hence parked.

## Why they vanished

The active indexer (dOrgTech/homebase-indexer) discovers DAOs via DipDup `similar_to` code-hash matching against a seed contract, and the current seed matches only lambda-generation code. The V2 configuration still exists on the `v2-master` branch, the handler code retains its registry/treasury branches, and the Hasura schema still has the V2 tables, so this is a config-and-plumbing gap, not a rebuild.

## Restoration tiers

1. **List-only (small config change):** add a V2 seed contract and factory index to the active DipDup config, reusing existing handlers. V2 DAOs reappear in the explorer list (the V2 card branch still renders). Requires a full re-sync per the project's reindex settings; storage typing differs between generations and needs care. Card links need a decision: TzKT vs nothing (the legacy app they used to link to is a dead shell).
2. **Read-only detail views (moderate frontend port):** restore the proposal/extras mappers removed in 808dfd1f and add non-lambda handling to `useDAO`, as a forward-port (the removed code predates the MUI/React/query-layer refactors). Write actions suppressed.
3. **Full interaction (larger restore, real unknowns):** restore the old contract classes and Michelson encoders against current Taquito. No working test environment exists for originating fresh V2 DAOs.

Recommendation if interest materializes: tier 1 with cards linking to TzKT, then gauge whether anyone actually needs more.

If V2 interest materializes, review the active DipDup configuration, the retained registry/treasury handler branches, the V2 tables in the Hasura schema, and the V2 card branch. Start by validating tier 1 with a V2 seed and factory index; done means a full re-sync restores V2 DAOs to the explorer list and the card-link destination is decided.

Written by the indexing model from the issue text.