[zheng-weihao]

Problem

The cruise hint's skip condition — "skip only if its content is already in your context" — is unreliable after a compaction. A compaction summarizes the head of the conversation, and the summary typically preserves paraphrases of the skill (goal / workflow / rules). Asked whether the skill content is "in context", the model sees those paraphrases and misjudges presence — so it skips the reload and keeps working without the actual rules. A presence check cannot distinguish content from a summary's paraphrase of content.

Change

The skip condition becomes an enumeration-recall test:

skip only if you can fully recall its "Safety rules" section, count included, from the loaded skill text — not from a summary; on any doubt, invoke

Design points:

• Named section. "Safety rules" is a titled section of the skill, so "the full set, and how many" has a definite referent. A summary typically preserves at most a single-rule paraphrase, not the full enumeration with its count.
• Source exclusion. "from the loaded skill text — not from a summary" names the remaining failure mode (a summarizer diligent enough to keep the full enumeration) as an explicit exclusion instead of leaving provenance implicit.
• Doubt default. Uncertainty collapses toward one cheap tool call, never toward skipping.

To make the count a first-class anchor, the Safety rules in SKILL.md are now numbered 1–6 (content unchanged).

No interface or mechanism change — hint wording, docs, and tests only.

Surfaces

• hooks/session-resume.sh — hint + header comment (shared by Claude / Qoder / Codex)
• .opencode-plugin/plugin.ts — CRUISE_HINT
• .opencode-plugin/plugin.test.ts — assertions pin the four design points (named section / count / source exclusion / doubt default), plus a negative assertion against the old condition
• skills/orbit/evals/evals.json — cruise-tier expectation updated to the new semantics
• docs/spec-hooks.md — hint contract section quotes the new hint verbatim; auto-approve section gains a boundary bullet (auto-approve cuts confirmation friction; it is not a security boundary — allow-only, never deny)
• USAGE.md — same one-line boundary note
• skills/orbit/SKILL.md — Safety rules numbered 1–6 (content unchanged)

Plugin tests: 16/16 green.