fix(consult): run the local skill's full technique spectrum on the web path

Web answers were thinner than a local Agent calling yinduzhanxing-skill:
theme-subset vargas, no visible audit table, and a prompt that dropped the
invocation contract. Bind the commercial method, compute D1–D60 plus Western
layers, and deliver the same Full-Spectrum checklist.

Co-authored-by: Cursor <cursoragent@cursor.com>

references/strict-workflow-router.md

@@ -58,7 +58,19 @@ Every Level 2+ chart reading must include `MEVG / Global Web Evidence` and
 
 ---
 
-## 0.7 User-Led Reading Calibration Gate
+## 0.7 Full-Spectrum Invocation Contract
+
+For career, wealth, annual forecast, event timing, rectification, or a comprehensive reading, the system must **actually execute every available, question-relevant Indian and Western technique** before interpretation. A module merely existing in the repository, registry, or UI does not count as used.
+
+1. Preserve every produced raw payload, varga, dasha, strength table, transit window, and cross-system difference. Information density must never be reduced because an oracle, formula variant, or holdout is incomplete.
+2. Invoke the Indian core relevant to the route: D1 plus all relevant vargas; Vimshottari, Narayana, Chara Dasha, Yogini, Ashtottari, Kalachakra and Bhrigu Pada where implemented; Jaimini/Arudha; KP; Double Transit PAC; transit LL/7L; Bhava Chalit; Sudarshana; Tajika/Varshaphala/Muntha; Nakshatra overlay; strengths, AV, yoga, argala, and relevant sahams.
+3. Invoke the Western core for the same birth data: tropical natal chart, transit-to-natal duration scan, Solar Return, secondary progressions, solar arc, converse progressions/arcs, midpoints, Lunar Return, and parans where implemented.
+4. A technique requiring unavailable inputs (for example partner data, Prashna question time, or an electional target) must still appear in the Technique Audit Table as `blocked` with its required input. It must not be silently skipped.
+5. Keep raw information and conditional interpretations visible. The only restricted content is an unsupported certainty claim: no inevitable event, no unsupported exact day, and no claim of cross-system verification when only one system ran.
+6. The report must state per technique: `executed`, `blocked`, or `not_applicable`, its settings, raw-output path, and its effect on assertion strength. `not_executed` is a workflow failure for a relevant technique.
+
+---
+## 0.8 User-Led Reading Calibration Gate
 
 This gate turns the user's follow-up interrogation into workflow control. It is
 not a personality preference; it prevents vague readings, memory-based
@@ -116,6 +128,7 @@ declared.
 | "When will career opportunities appear?" / job / project / public status / profession | `career-timing-strict` | Level 3 |
 | Marriage / partner / relationship timing | `relationship-timing-strict` | Level 3 |
 | Money / income / gains / assets | `wealth-timing-strict` | Level 2 or 3 |
+| Health / illness / hospitalization / injury / recovery pressure | `health-timing-strict` | Level 2 or 3 |
 | "Will this event happen?" / concrete yes-no / project landing | `event-timing-strict` | Level 3 |
 | "Why did this past event happen?" / technique reliability | `event-verification-strict` | Level 3 |
 | General natal reading | `full-reading-strict` | Level 2 |
@@ -131,7 +144,7 @@ For every Level 2+ reading, complete or explicitly mark unavailable:
 
 - D1 Rashi: houses, lords, dignity, exact degrees, Nakshatra, dispositor chain.
 - D9 Navamsa: dignity confirmation, Vargottama, major dignity reversals.
-- Relevant divisional chart: D10 for career, D7 for children, D12 for family/ancestral themes, D2 for wealth, D24 for education.
+- Relevant divisional chart: D10 for career, D7 for children, D12 for family/ancestral themes, D2 for wealth, D24 for education, D6/D8/D30 for health pressure and vulnerability review.
 - Vimshottari Dasha: MD/AD/PD when timing is requested.
 - Transit: Saturn/Jupiter/Rahu-Ketu, plus Moon trigger for month/day-level timing.
 - Functional benefic/malefic status by Lagna.
@@ -227,7 +240,37 @@ Use when the user asks for concrete timing, yes/no, project approval, launch, mo
 
 ---
 
-## 7. `event-verification-strict`
+## 7. `health-timing-strict`
+
+Use when the user asks about health pressure, vitality risks, hospitalization, injury, surgery periods, recovery windows, or whether a difficult health phase is being activated.
+
+### Mandatory modules
+
+- D1: Lagna, Lagna lord, Moon, Sun, Saturn, Mars, 6H, 8H, 12H, and their lords.
+- D6: core health-difficulty divisional review.
+- D8: obstacle / vulnerability review when the question involves crisis, chronicity, or sharp disruption.
+- D30: pressure, misfortune, or acute-friction layer; do not silently omit it when the route is health.
+- Vimshottari: MD/AD/PD activation of 1L/6L/8L/12L, Lagna, Moon, Sun, Saturn, Mars.
+- Narayana Dasha cross-check before making timing emphasis.
+- Functional benefic/malefic: explicit Lagna-based classification and conflict note if natural and functional roles diverge.
+- Strength: Shadbala for Lagna lord, Moon, Sun, Saturn, Mars, and the main activated lords.
+- Transit: Saturn/Jupiter/Rahu-Ketu to Lagna, Moon, 6H, 8H, 12H, and their lords.
+- Boundary layer: keep a visible non-medical boundary; no diagnosis, no treatment claim, and no certainty language about bodily outcomes.
+- Historical verification if the user provides past health-pressure dates or crisis windows.
+
+### Health timing output
+
+Always separate:
+
+1. **Pressure window**: strain, exhaustion, anxiety, or destabilizing background.
+2. **Event-risk window**: injury / hospitalization / disruption activation candidates.
+3. **Recovery-support window**: easing, stabilization, or reduced pressure after the peak.
+
+Do not present this route as medical advice, diagnosis, or treatment guidance.
+
+---
+
+## 8. `event-verification-strict`
 
 Use when the user provides past events and asks whether the technique is reliable.