[BUG] Model approves a PR that adds a new build/runtime dependency despite a loaded rule banning new dependencies

In a long PR-review session the project memory (loaded every session) states that new runtime dependencies are not allowed. Reviewing a PR that linked a native plugin against an extra library (new build-stage package, new runtime shared-library requirement, new CI install step), the model returned an unconditional approve. It checked functional correctness only and never applied the loaded dependency rule. The verdict changed only after the user objected.

Expected: rules loaded into context are applied to the review before a verdict is issued.