merge: synchronize remote main

This commit is contained in:
Jesse_Chen
2026-07-21 22:57:50 +08:00
130 changed files with 10441 additions and 553 deletions
@@ -27,7 +27,7 @@
| 优先级 | 开源对象(仓内真实文件) | 当前状态 | 接哪里 | 用来干什么 | 许可证风险 | 预计几小时落地 |
|---|---|---|---|---|---|---|
| P0 | `references/open_source_sources/panchanga_api/README.md` `references/open_source_sources/panchanga_api/MCP.md` `references/open_source_sources/panchanga_api/SKILL.md` | 半接 | `scripts/prashna.py` `scripts/remedies.py` `scripts/jyotish_api_server.py` `scripts/unified_consultation_orchestrator.py` `jyotish-app/main.js` | 把“时间问事 / Muhurta / Panchanga / Remedies”压到统一入口,复用你刚接好的 `prashna` `audited_remedies` 主链 | 低。镜像内 README 指向 MIT;当前仓内有 `LICENSE` | 4-8h |
| 已接/参考 | `references/open_source_sources/panchanga_api/README.md` `references/open_source_sources/panchanga_api/MCP.md` `references/open_source_sources/panchanga_api/SKILL.md` | 已接入主链;外部镜像仅参考 | `scripts/prashna.py` `scripts/remedies.py` `scripts/jyotish_api_server.py` `scripts/unified_consultation_orchestrator.py` `jyotish-app/main.js` | 现有主链已覆盖 Prashna / Muhurta / Panchanga / Remedies;只保留镜像的方法学参考 | 不可直接复用。镜像 `LICENSE` `All rights reserved`,不得复制实现 | 不新增接线;仅做外部数值证据与显示合同 |
| P0 | `scripts/vedastro_service_adapter.py` `scripts/vedastro_official_mcp_bridge.py` `scripts/diagnose_vedastro_mode.py` | 半接 | `scripts/jyotish_api_server.py` `mcp_server.py` `scripts/unified_consultation_orchestrator.py` | 让 official layer 真正默认参与,而不是只做桥接存在证明;同时把 runtime truth 里的 `official/full/partial/fallback` 说清楚 | 低。这里主要是官方 API/桥接,不是复制外部 GPL 代码 | 3-6h |
| P0 | `references/oracle/artifacts/pyjhora_*` `references/oracle/artifacts/pending_packets/*pyjhora*.json` `scripts/generate_pyjhora_oracle_artifact_manifest.py` | 已接(黑盒证据层) | `scripts/external_oracle_sanity_closure.py` `scripts/oracle_benchmark_inventory.py` `scripts/historical_event_backtest.py` `README.md` | 保留 PyJHora 作为黑盒对照、历史事件回测、数值 sanity,不碰源码复制 | 中高。AGPL 风险不在“调用输出”,而在“复制代码/常量/实现” | 1-3h 做下一轮批量证据清点;8-16h 做更完整事件包 |
| P1 | `references/open_source_sources/jyotishganit/README.md` `references/open_source_sources/jyotishganit/LICENSE` `references/open_source_sources/jyotishganit/jyotishganit/*` | 已接(部分) | `scripts/bhava_bala.py` `scripts/shadbala.py` `scripts/shadbala_advanced.py` `scripts/trimshamsa_d30.py` `scripts/constants/mit_imported_constants.py` `scripts/jyotish_engine.py` | 继续把 MIT 安全算法/常量吸收到本地精度层,尤其是 `Bhava Bala``Sputa Drishti`、部分 divisional / constants 对齐 | 低。MIT,且本仓已有显式标注“基于 jyotishganit” | 2-6h 做一轮定点补强;10-20h 做系统 sweep |
@@ -0,0 +1,29 @@
# Panchanga local ↔ jyotishganit comparison — TEMCQ-061
Date: 2026-07-21
This packet closes the first local comparison step for the Panchanga schema ticket without writing a new Panchanga algorithm.
## Result
- Local method: `scripts/muhurta.py::calc_panchanga`
- Case: Steve Jobs
- Compared fields: `vaara`, `tithi`, `nakshatra`, `yoga`, `karana`
- Result: 4 exact matches + 1 naming alias
- Truth upgrade: 0
## Field comparison
| Field | Local | jyotishganit | Status |
|---|---|---|---|
| vaara | Thursday | Thursday | within_tolerance |
| tithi | Shukla Tritiya | Shukla Tritiya | within_tolerance |
| nakshatra | Uttara Bhadrapada | Uttara Bhadrapada | within_tolerance |
| yoga | Shubha | Shubha | within_tolerance |
| karana | Garija | Gara | alias_match |
`Gara` and `Garija` are recorded as a naming alias, not a formula mismatch.
## Boundary
This is still `research_observation_only`. It does not upgrade Panchanga to global truth because VedAstro and PyJHora/JHora five-field normalized packets are not pinned for this same comparison, and sunrise-relative semantics still need multi-case closure.
@@ -0,0 +1,26 @@
# Panchanga TEMCQ-061 schema packet — 2026-07-21
## Result
- Status: `schema_mapping_required`
- Normalized fields ready: `0`
- Truth upgrades: `0`
## Observed jyotishganit raw
- Vaara: Thursday
- Tithi: Shukla Tritiya
- Nakshatra: Uttara Bhadrapada
- Yoga: Shubha
- Karana: Gara
## Blockers
- Local archived high-rigor raw lacks a normalized Panchanga field.
- PyJHora/JHora normalized Panchanga raw is not archived.
- VedAstro shared Panchanga endpoint/method is not pinned.
- Naming and calculation conventions must be fixed before field comparison.
## Boundary
This is schema mapping only. It does not prove Panchanga parity or production timing readiness.
@@ -0,0 +1,20 @@
# Three-engine BAV/SAV field closure packet — 2026-07-21
## Result
- Rows: `8`
- Local / PyJHora-JHora / jyotishganit agreement: `5/8`
- Multi-engine variants: `3/8`
- Truth upgrades: `0`
## Required evidence before upgrade
- Public worked BAV/SAV table
- Contributor set
- Lagna inclusion policy
- Shodhana state
- Rashi order / orientation
## Boundary
This packet reuses existing arbitration/probe output. It does not implement or copy a new Ashtakavarga algorithm and does not upgrade formula truth.
@@ -0,0 +1,26 @@
# Three-engine D2 field closure packet — 2026-07-21
## Result
- Rows: `7`
- Local / PyJHora-JHora / jyotishganit agreement: `7/7`
- VedAstro differing endpoint result: `7/7`
- Truth upgrades: `0`
## Interpretation
For the Steve Jobs public same-case D2 rows, local, PyJHora/JHora and
jyotishganit agree on seven planet signs. VedAstro differs on all seven rows.
This is therefore classified as:
`partial_consensus_vedastro_endpoint_blocked`
The remaining blocker is not local formula evidence. It is VedAstro hosted
endpoint/method semantics: same ayanamsa, node mode, varga and timezone contract
must be pinned before these rows can become global truth.
## Boundary
This packet supports local/PyJHora/jyotishganit D2 confidence only. It does not
upgrade global oracle truth or commercial production tuning.
@@ -0,0 +1,18 @@
# Three-engine D4/D9/D10 field closure packet — 2026-07-21
## Result
- Rows: `3`
- Local / PyJHora-JHora / jyotishganit agreement: `3/3`
- VedAstro differing endpoint result: `3/3`
- Truth upgrades: `0`
## Classification
D4, D9 and D10 each have one Moon.sign mismatch row. In all three rows, local, PyJHora/JHora and jyotishganit agree; VedAstro differs.
Status: `partial_consensus_vedastro_endpoint_blocked`
## Boundary
This packet supports partial same-case confidence for these three varga rows only. It does not upgrade global oracle truth or commercial production tuning.
@@ -0,0 +1,18 @@
# Three-engine field status batch — 2026-07-21
## Result
- Existing TEMCQ rows classified: `18`
- New Panchanga ticket placeholder: `TEMCQ-061`
- Truth upgrades: `0`
## Classification
- `10` D2/D4/D9/D10 rows are ready for endpoint/method semantics checks.
- `8` BAV/SAV rows are ready for public worked-example comparison.
- Panchanga has jyotishganit raw but no existing mismatch ticket, so it is queued separately.
## Boundary
This is a closure-status packet only. It does not mark any field as numeric
truth, formula parity, or production timing evidence.
@@ -0,0 +1,27 @@
# Three-engine jyotishganit bridge applied — 2026-07-21
## Status
- Claim status: `observation_only`
- Truth upgrades: `0`
- Source selected hash: `4709b8ade84efdea4d0a67c15f3e32cea516a5aa2e8abe3885578feda20cb3f4`
## Applied rows
- Existing TEMCQ tickets mapped: `18`
- No existing ticket: `1`
Mapped groups:
- D2/D4/D9/D10 sign rows → existing `endpoint_or_varga_semantics` tickets.
- BAV/SAV rows → existing `ashtakavarga_table_or_contributor_variant` tickets.
- Panchanga → no old mismatch ticket; create a separate closure row before comparison.
## Boundary
This packet only proves that jyotishganit selected raw can be routed into the
existing closure queue. It does not prove formula truth, timing readiness, or
commercial production tuning.
Shadbala remains an explicit gap because the current jyotishganit probe does not
expose `shadbala` or `strengths` in selected raw.