Compound Refresh

Maintain the quality of the project's tunan:solution learnings over time. This workflow reviews existing learning comments against the current codebase, then refreshes any related learnings that depend on them.

Storage: tunan:solution comments on feature issues

Learnings live on GitHub, never local files. Each learning is a comment on a feature issue — first line <!-- tunan:solution -->, then a fenced ```yaml block (the frontmatter from references/schema.yaml) followed by markdown sections. The host feature issue carries the tunan:solution label so gh issue list --label tunan:solution still indexes every feature that has a learning. This skill reads, PATCHes, and deletes those comments (and adjusts the host issue's label when its last solution comment goes away) — it never reads or writes any local learning file. Read references/comment-chain-storage.md for the comment-chain model and the exact gh recipes.

GH preflight — run before any issue read or write. If any check fails, abort and surface the guidance; never fall back to a local file.

1. gh is installed. If not, install from https://cli.github.com or run /tunan:setup.
2. gh auth status exits 0. If not, run gh auth login (in Claude Code, suggest typing ! gh auth login).
3. gh repo view --json nameWithOwner resolves. If not, a GitHub repo is required.
4. Setup reminder (non-blocking). If the repo has no tunan:config issue, this repo hasn't been through tunan setup — tell the user once, "This repo isn't set up for tunan yet; run /tunan:setup to configure it," then continue. A missing config is non-blocking and never aborts the run.

Core gh operations (the feature issue #N carries the label; its solution lives in a comment):