菜单
Reload the mycelium-tero memory API's served index from disk after the committed docs/tero-index/index.json has been regenerated — the freshness operation of the transparent memory API (DN-87 / E39-1). Requires the broader `refresh` token scope (not read-only).
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Generate the validated "read" (prose) that accompanies extracted code facts — language-book chapters, reference-manual entries, and learning-corpus lessons — from the committed index JSON, with a mandatory faithfulness gate so nothing is hallucinated. Wraps tools/llm-harness/narrate/ (Generator -> FaithfulnessChecker -> Loop): only validated, cited prose is committed; the rest is dropped and reported (never silently). Deterministic Mock backends by default (offline/CI).
Classify a Rust construct's Mycelium native-translation strategy using the ratified DN-111 native-equivalence taxonomy — Native Equivalent · Idiomatic Remapping · Approximation · Interop Bridge (DN-110's Adaptation/Solution/Approximation/Bridge handles are permanent aliases). Runs DN-110 §9's six-step decision procedure: verify-first against the corpus, identify the underlying PROBLEM (not Rust's mechanism), classify by the {exact?}×{native?} generator, apply the DN-109 §3.2 auto-fire ratchet, and emit a register-style record with an honest, never-upgraded guarantee tag (VR-5).
Reconcile the repo's GitHub issues to the committed source of truth (tools/github/issues.yaml + idmap.tsv) the rate-limit-frugal, diff-based way: one bulk snapshot, only-the-deltas writes, dry-run by default. Hits the API only for issues that are missing (create) or drifted (update), skipping everything already in sync. A periodic DESKTOP operation (real API) — not for the cloud/web session.
Maintain Mycelium's changelogs. Keeps the top-level CHANGELOG.md (Keep a Changelog 1.1.0, ISO dates, design-phase framing) and each doc's changelog footer in sync with a change, and enforces the append-only status discipline (Draft→Accepted→Superseded, Resolved for notes). Use when finishing a change, moving a doc's status, or cutting a release.
Develop a change forward (up the tiers) the spec-first, staged, context-windowed way: spec/DN (requirements, DoD, user stories) -> public API -> private API -> component seam-map -> code, each stage a bounded working set that persists a compact artifact and drops from context once consumed (DN-96). Owns the staged design pipeline, the change-sizing check (soft ~1-2k / hard 4,000 LOC), and the precursor doc/index-branch mechanic; delegates isolation, review+merge-up, index regen, and the main landing to /worktree-guard, /pr-land, /doc-index + /tero-refresh, and /land, following DN-97's ratified Rank-1 batch-engine command sequences for the actual landing.
Propagate a squashed landing on `main` back down to the persistent lower trunks -- main -> integration -> dev -- via a plain, no-force merge per tier (DN-97 Rank 1, maintainer-ratified: same-content trunks make this trivially conflict-free -- no merge-driver, no veto, no keep-list). Landed through the same PR-merge mechanism /pr-land and /land already use for these protected branches, never a raw git push. Run once per batch after 1-6 disjoint work-set squashes land on main. Also covers the in-flight-adapt one-liner for a still-open work-set branch.
| name | tero-refresh |
| description | Reload the mycelium-tero memory API's served index from disk after the committed docs/tero-index/index.json has been regenerated — the freshness operation of the transparent memory API (DN-87 / E39-1). Requires the broader `refresh` token scope (not read-only). |
| when_to_use | Use when the corpus index has been regenerated (just tero-index) and you want a running tero-http / tero-mcp server to pick up the new rows without a restart. Requires a token with the `refresh` scope. |
| allowed-tools | Bash(curl:*), Bash(just:*), Read |
The fronts serve a snapshot of docs/tero-index/index.json loaded at startup. refresh reloads it
from disk in place — for use after the drift-gated index is regenerated:
just tero-index # regenerate docs/tero-index/{INDEX.md,index.json} (deterministic)
refresh is the one operation that is not read-only, so it requires a token with the refresh
scope (read-only tokens get a 403 / JSON-RPC -32002). Read-only stays the default (DN-87 §6.4).
curl -s -X POST -H 'Authorization: Bearer admin' http://127.0.0.1:8787/v1/refresh
Success: {"kind":"refreshed","ok":true,"items":<count>}. If the on-disk index is missing/unreadable
the server returns a 500 with a JSON error envelope — never a silent stale-serve (G2).
tools/call with { "name": "refresh", "arguments": { "token": "admin" } } (a refresh-scoped
token).
Freshness is drift-gated like the indices tero generalizes: the encoding regenerates
deterministically from the corpus (scripts/checks/tero-index.sh fails on drift). refresh never
fabricates or partially-applies — it swaps in a fully-loaded new snapshot or fails loudly, leaving
the previous snapshot intact.