align exclude_events default with hooks-logging: drop llm:stream_block_delta by default

[bkrabach]

Aligns the hook-context-intelligence exclude_events default with amplifier-module-hooks-logging — both now default to ['llm:stream_block_delta'], keeping the high-frequency per-token streaming delta out of the local events.jsonl AND the graph-server dispatch by default (opt back in with exclude_events: []). The two hooks share no code; they are aligned by value and by the common streaming contract. Backwards-compatible: the excluded event ships with the new streaming providers, so existing logs/dispatch are unchanged. This removes the need for users to set exclude_events manually.

What

• Added _DEFAULT_EXCLUDE_EVENTS: list[str] = ["llm:stream_block_delta"] module-level constant to config_resolver.py with a comment explaining the intentional value-alignment with hooks-logging (not shared code — deliberately decoupled).
• Updated ConfigResolver.exclude_events property to use _DEFAULT_EXCLUDE_EVENTS as the default (previously []).
• Updated module docstring to document the default and opt-out pattern.
• Updated tests/test_config_resolver.py: renamed test_defaults_to_empty_set → test_defaults_to_block_delta and added 6 new tests covering the complete semantics.

Why

Before this change, hook-context-intelligence defaulted to exclude_events: [], meaning llm:stream_block_delta (the per-token streaming event, firing hundreds-to-thousands of times per turn) would flood both the local events.jsonl and the graph-server dispatch unless users manually configured the exclusion. amplifier-module-hooks-logging already excluded it by default on its feat/exclude-events branch. This change brings the two hooks into alignment.

Semantics

Config	Behaviour
exclude_events unset	frozenset({"llm:stream_block_delta"}) — delta suppressed
exclude_events: []	frozenset() — filter disabled, every event logged/dispatched
exclude_events: ["llm:stream_*"]	all four streaming events suppressed

The existing if exclude else events gate in __init__.py ensures excluded events are never registered → suppressed from BOTH the local write and graph dispatch. No logic changes needed there.

No shared code

The two hooks are deliberately decoupled. _DEFAULT_EXCLUDE_EVENTS in config_resolver.py is an independent constant — no import, no shared module, no cross-repo dependency. If the value needs to change in future, both hooks are updated independently.

Tests

uv run pytest tests/test_config_resolver.py -v
# 75 passed in 0.16s

uv run pytest
# 310 passed in 1.28s