[prasannakotyal]

Summary

Targets KG red #236, where custom_kernel stores the first input-derived result in a module-level state slot indexed by an IntEnum member, then returns that same enum-indexed slot from an input-independent fast path.

This adds a narrow ENUM_INDEX_REPLAY detector. It requires:

• a local Enum or IntEnum class
• module-level list or dict state
• an entrypoint assignment to an enum-indexed subscript of that state from an input-derived call
• an input-independent guard reading an enum-indexed subscript
• a call-free replay body returning an enum-indexed subscript of the same state

Array-derived indexes, slice-object indexes, and enum member values that are themselves containers stay out of scope.

KernelGuard-Red-Submission: 236

Local verification

• red_111_enum_index_replay -> ENUM_INDEX_REPLAY, should_filter=True
• red_38_array_index_replay stayed valid
• red_131_slice_object_index_replay stayed valid
• red_219_enum_value_list_replay stayed valid
• red_499_enum_member_list_replay stayed valid
• clean fixtures in eval_blue_patch.py stayed valid
• uv run python -m py_compile kernelguard.py

[github-actions]

KernelGuard Blue Evaluation

• Evaluation job: 69
• Blue submission: 49
• Result: passed
• Target red submission caught: True
• Validation suite: TP 20/20, FP 20/20
• Surgicalness score: 1.0
• Workflow run: https://github.com/SinatrasC/kernelguard/actions/runs/25238392801

[SinatrasC]

Thanks for the KernelGuard Flywheel Campaign contribution. We are not merging this narrow variant separately because the consolidated rule-family implementation in #273 is the merge path for this detector area.