What changed in Lumin

• Save a chart per person. Ask by name. Your existing chart stays the default.
• Every reading names the chart it used in its first line, with the birth moment and coordinates.
• With several charts saved, a question that names nobody gets asked which one. No default, no guessing.

A chart cannot live in a project folder. Plugin settings come from your user settings only, by design. Saved profiles work from any folder.

Significators are stricter, so readings shift. An occupant or owner delivers a house only while no other planet sits in its own star. Older readings may differ.

get_significators returns a demoted block. Every occupant or owner that no longer signifies its house is listed with the planets that took over.

Long results are paged, not capped. A 3 month transit scan finds 1,072 crossings. You used to get 50 of them and no way to ask for the rest. Every paged result names the exact call that fetches the next page.

Two tools were too large to return and failed on every single call. Both work now. get_dasha_periods went from 116,603 characters to 12,631 once its documented default was applied, and get_horary_chart_v2 from 140,395 to 30,559.

Pratyantardasha is its own tool. The 3-lock rule needs the mahadasha, antardasha and pratyantardasha lords to agree, so the third lock is where timing actually resolves.

A catalog for picking the right tool. Ask for the map, then filter by family, phase or system. 41 of the 198 tools are Parashari, 6 Jaimini and 2 Tajik, so you can see which method is answering before you quote it.

Install into Claude Code with two commands. You get the reading methodology, agents that take one phase at a time, and a guard that holds a reading to its call floor.

Choghadiya and hora were a day out everywhere east of Greenwich. Both divide the day sunrise to sunrise, so before local sunrise they read the previous day's table. Send utc_offset_minutes and they land on the right day.

Nine tools named for the thing you are timing, so you no longer describe the event and hope. Each one knows its own house group.

Four tools for anything else. Search a date range, rank dates you can actually make, list every event you can time, or time one moment across two charts.

Tell it the hours you can use and the answer gets sharper. Office hours on a wedding search cut one field from 195 candidates to 72.

You get one moment, or three when nothing separates them, each with the reason it won. Not a list of ten to choose between.

A second KP school can cross-check the same moment, off by default. The two schools agree on 26% of windows and partly agree on 68%. A disagreement is a second opinion, not a fault.

Timing questions route now. 'Best date for our wedding' and 'when should we hold the board meeting' both returned nothing before. 8 of 40 phrasings found no timing tool, now none do.

find_auspicious_time never searched for a time. It had no date input, read only birth data, and returned the same answer on every call. It also silently dropped 76 of its own 78 event names.

Transit analysis was comparing your chart against your own birth positions. It runs on every full reading, so every reading was affected. Moon transit had the same fault and returned one answer for all dates.

Rahu Kaal is correct now. Sunrise was estimated from latitude alone, with no longitude and no date, so every window built on it was wrong. Yamaganda, Gulikai and Abhijit are added.

Every panchang layer now says where KP stands on it. Rahu Kaal is endorsed when Rahu rules the dasha or bhukti. Yamaganda, Gulikai and Choghadiya appear nowhere in the KP texts and are labelled classical reference.

The rules come from KP Readers 3, 5 and 6, cited to the page. Reader 5 carries a 20 recipe electional chapter that was unreadable in every text copy in circulation.

Electional results carry no score. The KP texts never rank a moment by a number, so scoring one would be our invention, not the method. Selection is rejection, then your constraint, then ordered tests.

Surgery timing now aims at recovery. The old profile ruled out houses 5 and 11, which the texts call cure and cessation of suffering.

get_panchang returns the local civil date in `date`, where it used to return the UTC date. Sunrise and sunset keep their HH:MM strings and gain ISO instants.

Documentation pages were missing for 6 tools and 13 more were documented with no parameters, including 4 with none at all. The generator dropped them silently and now fails loudly.

Five foundation and verdict tools: a career cusp panel, job against your own concern, a blockage diagnosis, earned income, and business viability.

Five timing and horary tools: promotion, job change windows, termination risk, working abroad, and a career horary with 14 question types.

178 modern occupations the KP texts never carried, from data scientist to wind turbine technician. Every match shows where its signature came from.

12 new career events for event timing: unemployment, resignation, interview, suspension, reinstatement, salary increment, pension, and foreign job.

Career questions route properly now. 'When will I get promoted' returned nothing before. The full career reading was returning empty values.

Rahu no longer hardcodes the software signature. Nodes resolve to their star lord and sign lord, which moves IT scores. No schema changed.

Every career tool is a supplementary lens, never a screening tool. Termination risk returns a risk band, never a firing verdict.

Six foundation tools: an overall health read, a vitality score, disease nature, which treatment fits, dated recovery windows, and a right-now health snapshot.

Nine timing and verdict tools: medical horary, hospitalization windows, misdiagnosis risk, surgery date grading (GO/DEFER/RESCHEDULE), mental health patterns, epidemic susceptibility, a day-level health alert calendar, habit patterns, and transplant timing.

Every health tool is a supplementary lens, not a diagnosis. The mental health panel always includes a crisis support note.

MCP clients: point at mcp.lumin.guru/mcp and sign in when prompted. Direct API: create a key at app.lumin.guru/developer and send it as Authorization: Bearer mcp_...

14 new tools, grouped by theme.

The headline: pass a chart and an event, get four independent verdicts and a consensus level (UNANIMOUS, STRONG, MIXED, or SPLIT).

Four astrometeorology tools. Every response carries a plain-language disclaimer: this is the astrological tradition's seasonal read, not a meteorological forecast.

62 new tools, grouped by lineage and domain.

8 composite workflows bundle 5-15 sub-calls into one round-trip: marriage, career, kundli match, today, year outlook, triple-dasha consensus, Karakamsa lens, and a pre-verdict audit.

New questions you can ask, grouped by domain.

Per-tool reference pages now auto-generate at /build/reference/tools/<slug>.

v2 tools active by default, plus two new methodology helpers.

14 advanced technique tools: CSL convergence, retrograde, dasha, transit, ruling planets, horary, medical, financial, foreign settlement, marriage, career, legal, muhurta, and rectification.

Breaking: the deprecated v1 finders are removed. Callers receive a clear error pointing to the v2 replacements.

Connect from Claude or any MCP-compatible client and ask your first KP question.