Support REP Yes/No universes with shared fork navigation

[KillariDev]

REP Yes and REP No are the two canonical Zoltar roots, descended from the Augur v2 universe. Each deployment supplies its selected REP token through Zoltar's existing constructor argument. The UI names the roots Augur v2 › Yes and Augur v2 › No; each is local universe 0 in its own deployment.

• Deploy both roots with shared infrastructure, separate manifests and per-address verification retaining each root's constructor arguments. Mainnet remains disabled; Sepolia remains the default.
• Require an explicit genesis=yes|no choice in all three apps. A missing or invalid choice shows the verified historical fork question before starting the backend.
• Share UniverseBrowserView, the route-heading pattern, universe summary/status badge, fork-question section and outcome controls between the historical entry and future forks. Historical facts are supplied directly; live universes retain their loader, actual ID/supply/timestamp, actions and child state. No historical Zoltar metrics are invented.
• Preserve ordinary parent/child navigation, scalar outcomes, pagination, retry and REP migration. Either canonical root's parent returns to Augur v2 universe to choose a deployment.
• Use the selected-root formatter for lineage, identifiers, portfolio empty states, recovery and saved-state warnings. Scope favorites, downloads and pending deployment actions by canonical REP identity; retain account/network-wide wallet history and captured scopes for in-flight operations.
• Reject saved states from another root with a recoverable warning. Preserve error/retry behavior and explicit pending/duplicate-selection guards.
• Merge current main's automatic discovery, loading contrast and glanceable UI changes. Resolve generated screenshot conflicts by recapturing the combined checkout and rebuilding the documentation search index. The deployment guide explicitly includes the initial truthful-universe choice.

Protocol execution and ABI are unchanged. Solidity edits from main are comments. Bots and augurScan keep explicit Yes deployments; dual scanner ingestion is outside this change.

Current validation

• Full bun run tsc, all shared/app/worker builds and all three production bundles pass with pinned Bun 1.4.2.
• 4,202 UI cases across 363 files pass, with eleven expected external-network/archive skips. New helper exports from main required refreshing ignored test builds; all ten initially import-blocked files then passed 132 cases. After the final pending fix, the six owning/current-consumer files pass 99 cases, and all three production chooser tests pass again.
• bun run format:check, full bun run check, bun run knip, bun run check:generated-clean and git diff --check pass.
• Browser QA: 51 post-merge product captures, 51 baseline pairs, native keyboard checks, then 18 final pending captures / 12 exact bounds comparisons across all three apps at 1440×900 and 390×844, Chromium 155.0.8059.39. Both buttons retain exactly the same x/y/width/height during either selection. No browser errors or horizontal overflow. The visual review's pending-row movement finding is fixed; no findings are deferred.
• Canonical docs: all 22 figures / 23 embeds recaptured and strictly checked after the main merge; every image and all eight embedding pages reviewed. Sixteen rendered page captures pass both widths. The final pending-only fix is absent from every documented scenario (genesis=yes bypasses the chooser and live callers omit pendingLabel), so those images remain visually current. Broad source-fingerprint warnings are recorded for this last change; hashes are not falsely marked fresh and strict freshness is not claimed on the final head.
• Fresh text review: 96/100, no issues. Fresh visual review after the fix: 95/100, no issues. Final review: 95/100, no issues, no deferred findings.
• Full root, separate bot/scanner, contract/security/fuzz/invariant/deployment and long wallet-browser workflow suites are excluded from this presentation follow-up: their execution paths are unchanged. Current UI interfaces and merged-main integration are covered above. Unchanged original owners previously passed 130 deployment/manifest cases, 86 contract/scanner/dashboard cases and 944 affected UI cases; the earlier naming/merge follow-up passed 305 cases. The earlier feature CI passed all 40 jobs, predating these merges. Mutable-mainnet/archive tests remain explicitly gated; current-head CI is reported separately.
• Final local head 4c9a609389cfd995b39a1674010258d62742f4c5. Fetched origin/main after the final fix: zero commits behind d144ad301; worktree clean. The PR remains unmerged.

Resulting UI

The historical Augur v2 universe and future forks share the same browser presentation:

Desktop and mobile across all three apps

The 14 resulting-UI images include the final stable pending states; unchanged live views retain their verified post-merge captures. All were uploaded through the permanent Catbox endpoint and download-SHA256 verified; QA images are not committed. Registered documentation figures use the canonical capture command.

Augur question/identity source: final fork record.