What it requires. A custom context definition was cloned rather than extended and lacks mappings the standard definition has since gained.
Why it matters. [doc] Extending a standard definition carries automatic upgrades and a Sync Now option, so mappings added by later releases arrive on their own; a clone of a standard definition gets "no automatic upgrades" (Salesforce Help, Clone a Context Definition). The exception is the thing this check keys on: a clone of an already-extended definition keeps its upgrades only when Preserve Inheritance was enabled, which is exactly the ClonedFrom-populated-with-InheritedFrom-empty state. A mapping that never arrived means the attribute is silently null in context, so every element referencing it no-ops: wrong price, no error. Separately, a definition carrying BOTH lineages "can result in unexpected pricing errors and should be recreated" (KB 004259656) - that is RC-006.
How to fix it. Recreate as an extension, or diff against the current standard and add the missing mappings deliberately.
Is this rule worth checking?
Votes and comments are published here. We read them, and we publish what we change with the reasoning — a vote does not move a rule on its own.