fix(filter): exclude_entity_globs now overrides include_entity_globs (#33)

[SAY-5]

Closes #33.

Reproduction (from the issue)

include_entity_globs: [\"sensor.*_temperature\"]
exclude_entity_globs: [\"sensor.processor_*\"]

Expected: sensor.processor_temperature is excluded.
Actual: sensor.processor_temperature is still recorded.

Root cause

Home Assistant's generate_filter (homeassistant.helpers.entityfilter._generate_filter_from_sets_and_pattern_lists, case 4a) lets include_entity_globs short-circuit over exclude_entity_globs:

return entity_id in include_e or (
    entity_id not in exclude_e
    and (
        bool(include_eg and include_eg.match(entity_id))   # <-- include glob wins, exclude never checked
        or (
            split_entity_id(entity_id)[0] in include_d
            and not (exclude_eg and exclude_eg.match(entity_id))
        )
    )
)

So when both globs match, the include glob short-circuits to True and the exclude glob is never consulted. Scribe users — and the issue reporter — expect the opposite.

Fix

Wrap the result of generate_filter with a small _build_exclude_priority_filter that:

1. checks exclude_entities and exclude_entity_globs first; on any match the entity is rejected,
2. otherwise defers to the upstream filter.

The wrapper preserves HA semantics for everything else (domain include/exclude, entity-level include, no-filter pass-through), and is a no-op when no excludes are configured (common-case fast path).

entity_filter = generate_filter(...)
entity_filter = _build_exclude_priority_filter(entity_filter, exclude_entities, exclude_entity_globs)

Test plan

Added test_exclude_entity_globs_overrides_include_entity_globs in tests/test_filter.py — the exact reproduction from the issue (include: sensor.*_temperature, exclude: sensor.processor_*):

• sensor.living_room_temperature (include only) → recorded.
• sensor.processor_temperature (matches both) → excluded (was: incorrectly recorded).
• sensor.processor_use (exclude only) → excluded.

Local results:

• python3 -m ast parses both modified files cleanly.
• Standalone Python repro confirms the wrapper produces the documented behavior on simulated generate_filter output.
• Full pytest suite requires the home-assistant test harness which the repo bootstraps via requirements_test.txt; CI will run it.

[jonathan-gtd]

Thanks :)