Own catalogue: sales map, demand model and market advisor (plan)

New docs/catalogue-intelligence.md for Alexander's idea of a catalogue
the plant presses for itself. Why (idle Classic hours ~60k to 160k
records a year at 60 % specials on the doc basis; two-week represses
from the metal archive; Thai catalogue sells in Japan, EM Records,
ZudRangMa), scope (Poy Records as seed; customers' data and press dates
protected), data sources with access terms (Bandcamp ship-to fields,
distributor sell-through clauses, opt-in record passport registrations,
Spotify for Artists, Discogs CC0 dumps; Discogs API marketplace and
want data restricted), ERPNext touchpoints (Licence, Channel Sales
Report, Catalogue Recommendation, geocoded addresses, CRM), PDPA rules
for the map, dashboard views on an open-source map stack, a staged
demand model with a stocking rule for run size, a propose-only advisor
on an open-weights model, phasing, cost estimates, risks and open
decisions.

Backlinks: README (planning documents, layout), roadmap item 28,
digital-factory tool rule, artist-platform repress pre-orders,
production-timeline repress, revenue-model ResurRec Japan.

docs/production-timeline.md

@@ -195,7 +195,8 @@ Two commercial consequences worth acting on:
   to go back to, so a repress restarts at lacquer cutting and costs the
   customer six weeks and a new cutting fee. 3-step buys the two-week
   repress, and that repress is the highest-margin order the plant will
-  ever take. Decided (October 2026): the plant keeps the **father as well
+  ever take. For a catalogue of the plant's own it is also what makes
+  small, demand-led runs possible ([own catalogue](catalogue-intelligence.md)). Decided (October 2026): the plant keeps the **father as well
   as the mother** of every side.
 - **How many represses a mother carries.** The common rule of thumb is
   about **10 stamper sets per mother** before it degrades (Third Man