katgpt-rs: Skill for Claude Code

feature-gate-audit — Verify feature-gate claims against production code

This skill exists because of a caught error chain: session f92a7ffe in riir-ai (2026-07-18) framed npc_sleep_time's engine-DEFAULT-ON / civ-OPT-IN state as a "promotion discrepancy" and claimed the catalog was "wired but not yet exercised in production civ tick". Session f865913e (same day) verified both claims against production code and found them factually wrong:

• The split is a deliberate layer split (engine = generic runtime; civ = IP-bearing catalog + graceful-degradation hook into SleepConsolidateNode::tick Gate 3).
• The catalog IS exercised in production via crates/riir-games-civ/src/civ/daily_loop/mod.rs:1071-1078, which calls ctx.sleep_runtime.sleep_cycle_tick(&hla, &self.dirs).

The three defenses below would have caught both errors before they landed. Apply them to every feature-gate claim you encounter.

When to use

• A doc, plan, issue, commit message, or session summary claims a "promotion discrepancy" between two crates' feature-gate status
• A doc claims a feature is "wired but not yet exercised in production"
• You encounter a // Default-off until G1–GN GOAT gate passes comment in source code
• Before promoting a feature flag to default-on (or demoting to opt-in) in any product-set repo (8; canonical list in katgpt-rs/AGENTS.md §"Repo count" — this said 7 and silently excluded riir-dapps)
• Quarterly as a feature-gate-hygiene gate (alongside doc-sync and goat-audit)

The four defenses

Defense 1 — Verify every "discrepancy" / "not yet wired" claim against production code

NEVER propagate a doc/plan/session-summary's framing of feature-gate state without first grepping the actual production wiring. Plausible-but- wrong framings are the canonical failure mode — they read as reasoned verdicts, get propagated through summaries, and solidify into "facts" that downstream sessions trust.

Protocol:

1. Identify the production host(s) — the function that would invoke the gated code path on the hot tick. Common hosts in this stack:
   • tick_proactive_salience (salience gate)
   • tick_cgsp_curiosity (CGSP runtime)
   • tick_motivation (motivation system)
   • SleepConsolidateNode::tick (sleep-time, daily loop)
   • evolve_feeling_brain (emotion systems)
2. grep for the feature name across all .rs files in the crate tree, not just the file the doc cited:

   grep -rn "FEATURE_NAME" crates/ --include="*.rs"
   

3. Read the body of every host function whose signature imports a type from the gated module.
4. If a #[cfg(feature = "FEATURE_NAME")] block is reached along the tick path, the feature IS exercised in production — regardless of what the doc says.
5. If no host reaches the gated block, then the "not yet wired" claim may be accurate — but verify with a call-graph grep, not just a single-file read.