docs(plans): add Milliquas quasar catalog implementation plan

[rulkens]

Summary

Adds the TDD implementation plan for Milliquas v8 (Flesch 2023, ~880k spec-z quasars + AGN) as a new top-level survey alongside SDSS, 2MRS, GLADE, and Famous.

No code changes — just the plan document. Execution would happen in a follow-up PR via subagent-driven-development against this plan.

Design decisions locked in (from the grill session earlier today)

• Subset: spec-z only (~880k of 1.02M Milliquas entries). Excludes the ~66k pQSO≥99% photometric candidates whose redshifts are 0.1-rounded — they'd produce visible concentric shells in the renderer otherwise.
• Binary format: reuse existing 64-byte GalaxyCatalog v4, with morphology-specific slots zeroed (axisRatio, PA, diameter, vMaxWeight, schechterRatio, angularDensityWeight). The plan's parser-task docstring carries the rationale: point-source AGN don't have galaxy morphology, and the wasted bytes gzip away on R2 anyway.
• Tiering: small / medium / large by apparent magnitude. Plan proposes target counts modelled on GLADE's tiering shape.
• Default visibility: OFF in SettingsPanel. Matches the recent CF-4 / MCPM default-off pattern.
• Source code: append-only assignment in sources.ts per its documented convention (left for the implementer to pick at task time so they read the current state of the file).
• Cross-matching: none for v1. Milliquas's AGN cores and their host galaxies in GLADE/2MRS are physically distinct entities; deduping would discard real data.
• Citation: Flesch 2023, OJAp 6, 49 (also cited as Milliquas v8).

Plan shape

• 7 phases: Parser → Source enum → Encoder integration → Fetcher → Runtime+UI → Deploy → End-to-end verification
• 11 tasks, each bite-sized with explicit "tests first" guidance and acceptance criteria
• Tier targets and source code assignment intentionally left as implementer-time decisions (avoid baking stale assumptions into the plan)

Reviewer notes

Take a particular look at:

• Task 3 (encoder integration with N/A field zeroing) — gets to the heart of the format-reuse trade-off
• Task 5 (tier definitions) — proposed numbers are by analogy to GLADE; sanity-check makes sense
• Task 10 (deploy + R2 ALLOW filter) — make sure the filter update matches your sync conventions

Test plan

• Review the plan end-to-end for any decisions you'd push back on before execution starts
• Confirm the tier-target proposals are roughly right (small/medium/large counts)
• Sanity-check the parser approach (fixed-width text release rather than FITS)

[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	Preview URL	Updated (UTC)
✅ Deployment successful! View logs	skymap	0ee87b4	Commit Preview URL Branch Preview URL	May 20 2026, 12:04 AM