Shift the README narrative so that non-developer users — the 99% of the
actual audience — find the browser entry point first and the CLI install
second. The old structure buried fojin.app/chat at line 48 under a wall
of developer badges.
Changes:
- README.md / README_EN.md: new "立即体验 / Try It Now" hero section
right after the title block, with a big call-to-action linking to
fojin.app/chat, a "which master should I ask" recommendation table,
and an explicit redirect for CLI users to the developer section.
- Rename "快速开始 / Quick Start" → "开发者安装 / Developer Installation"
with a clear "if you just want to try it, use the browser instead"
callout at the top.
- Update TOC anchors in both languages to match.
- prebuilt/<master>/meta.json × 8: new `starter_questions` field with
4 Q&A entries per master. Each entry has `q` (the question) and `why`
(why this question is suited for this specific master's voice and
source corpus). Intended consumer: fojin.app/chat can fetch the raw
meta.json on master selection and render these as cold-start prompts
— solving the empty-input-box problem for first-time users.
Rationale: the biggest onboarding gap for non-CLI users is "I don't
know what to ask this master." A curated 4-question starter per master
provides both a safe entry point and a teaching signal about what this
particular master is actually good at answering.
Validated: scripts/validate.py --strict passes (9/9 masters).
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Each teacher's meta.json now includes search_scope with tradition-specific
CBETA/SuttaCentral IDs, dictionary sources, and keywords for focused RAG
retrieval. New tools/cross_reference.py enables lineage queries and
cross-tradition concept comparison via FoJin KG.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
xianren