Notemd v1.9.2

Highlights

This release covers the effective remote-main delta after 1.9.1: the notes below are derived from the shipped 3c90553..1cb58cb range, which is the remote-history path from the 1.9.1 release cut to the latest main.
Sidebar observability regains its usable layout: the footer scroll container and API activity styling are restored so activity details no longer push log output out of view.
Local knowledge inspection is more diagnostic without widening runtime behavior: maintainer inspection now reports bounded query diagnostics and low-signal navigation-note cautions instead of silently hiding why a derived query may be weak.

Added dedicated Chapter Split + TOC spotlight docs in both English and Simplified Chinese, plus a checked-in showcase SVG and docs-hub entry points so the feature is now part of the visible shipped documentation surface.
Expanded local-knowledge.inspect explainability with structured queryDiagnostics, including the derived basename, the bounded stripped-source character count used for diagram-source queries, and cautions for navigation-like note names such as index.*.
Re-aligned repo-local maintainer CLI help, examples, and capability-matrix docs to the actual vault-relative contract required by --vault docs, reducing drift between examples and real invocations.
Kept release-maintenance truth tighter by preserving maintainer authorship in the chronicle refresh helper instead of letting release-driven doc refreshes fall back to a bot identity.

Fixed the sidebar footer region so Log output and API activity can scroll within the shipped panel again instead of fighting for the same fixed vertical space.
Fixed the docs-vault local knowledge inspection examples that previously used repo-relative docs/... paths instead of vault-relative index.zh-CN.md / maintainer inputs.
Fixed maintainer CLI help output so the minimal examples now reinforce the same vault-relative path rule that runtime expects.
Fixed local knowledge inspect coverage for low-signal navigation notes by surfacing explicit cautions in tests and runtime output, instead of leaving those retrieval misses under-explained.

Before: sidebar request activity styling had regressed enough to make the combined API/log surface harder to inspect during real tasks.
After: the footer region is explicitly scrollable again, and API activity styling fits inside the sidebar without hiding the log stream.
Before: local-knowledge.inspect showed the derived query, but not enough bounded evidence about why a basename- or diagram-derived query might be weak.
After: the inspect surface stays maintainer-only, but now returns bounded query diagnostics and navigation-note cautions that make low-signal retrieval chains easier to debug.
Before: maintainer CLI docs implied repo-relative paths in --vault docs examples, which drifted from actual runtime expectations.
After: examples and tests now converge on the real vault-relative contract, reducing operator error in local verification.

本次发布覆盖远端 1.9.1 之后的有效主线增量：以下内容基于已发货的 3c90553..1cb58cb 区间生成，也就是远端历史中从 1.9.1 release cut 到当前 main 的真实差异。
Sidebar 可观测性布局恢复可用：底部滚动区与 API activity 样式已经恢复，活动信息不再把 Log output 挤出视野。
本地知识库 inspect 更可诊断，但不扩大运行时行为面：维护者 inspect 现在会返回有界 query diagnostics，并对低信号导航笔记给出 caution，而不是只暴露一个弱 query 结果。

新增“章节拆分 + TOC”中英文独立聚焦文档、效果图 SVG 与文档入口，使该功能正式进入仓库可见的发货文档面，而不再只存在于维护者语境。
扩展 local-knowledge.inspect 的 explainability，新增结构化 queryDiagnostics：包括派生 basename、diagram-source 查询实际使用的有界 stripped-source 字符数，以及 index.* 这类导航型笔记名的 caution。
将仓库内维护者 CLI 帮助、示例与 capability matrix 重新对齐到 --vault docs 所要求的真实 vault-relative 路径契约，减少文档示例与实际调用之间的漂移。
收紧 release 维护链路真值：chronicle refresh helper 现在会保留维护者身份，不再把发布驱动的文档刷新提交写成 bot 身份。

修复了 sidebar 底部区域的滚动行为，使 Log output 与 API activity 可以在同一个发货面板内正常纵向滚动，而不是争夺固定高度。
修复了 docs vault 中本地知识库 inspect 示例此前错误使用 docs/... repo-relative 路径的问题，现统一为 index.zh-CN.md / maintainer 这类 vault-relative 输入。
修复了维护者 CLI help 的最小示例输出，使其与运行时一致地强调 vault-relative 路径规则。
修复了低信号导航笔记场景下本地知识库 inspect 的可解释性不足问题：现在测试与运行时输出都会显式给出 caution，而不是让这类检索弱命中继续处于“结果为空但原因不明”的状态。

改动前：sidebar 中的 request activity 样式回退后，API 与日志的联合观察面变得更难用。
改动后：底部区域重新具备明确的滚动边界，API activity 不会再遮挡日志流。
改动前：local-knowledge.inspect 虽然暴露了派生 query，但没有足够有界的证据说明 basename / diagram-source query 为什么会偏弱。
改动后：inspect 仍保持 maintainer-only，但现在会返回有界 query diagnostics 与 navigation-note caution，便于定位低信号检索链路。
改动前：维护者 CLI 文档在 --vault docs 示例中暗示了 repo-relative 路径，这与真实运行时预期不一致。
改动后：示例、帮助输出与测试全部收敛到真实的 vault-relative 契约，降低本地验证时的操作性错误。