[bug] effect semantics not distinct — Exclusion, AdapterCapabilities ignored

[nkanf-dev]

Problem

Several defined effects and capabilities have no real behavioral distinction in the engine. This tracks the overall issue of effect semantics being cosmetic rather than functional.

Sub-issues

• [bug] Exclusion effect has identical semantics to Deny #7 Exclusion effect has identical semantics to Deny
• [bug] AdapterCapabilities checked at registration but ignored at decide time #9 AdapterCapabilities checked at registration but ignored at decide time

Expected

Each defined effect should have distinct, observable behavior. Registered capabilities should be enforced at decision time.

[nkanf-dev]

Resolved by engine refactoring: implemented explicit capability checks in Decide and distinct handling for Exclusion effects.