Document the Fail2BanBlocked and Allow2BanBlocked events

[sascha-egerer]

No description provided.

[Copilot]

Pull request overview

Documents the newly added Fail2BanBlocked and Allow2BanBlocked PSR-14 events across the Phirewall documentation, clarifying what fires when a request is blocked due to an already-banned key.

Changes:

• Update Fail2Ban/Allow2Ban feature docs to describe and link the new “blocked-by-existing-ban” events.
• Extend observability and notification docs to include the new event classes and properties.
• Update architecture documentation to reflect the additional event dispatch points.

Reviewed changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated 1 comment.

File	Description
docs/features/fail2ban.md	Adds/links Fail2BanBlocked and Allow2BanBlocked event documentation and updates flow descriptions.
docs/advanced/track-notifications.md	Adds the new events to the consolidated event reference table.
docs/advanced/observability.md	Adds the new events to the event summary and documents their semantics; updates diagnostics category examples.
docs/advanced/architecture.md	Notes event dispatch behavior when requests are blocked due to existing bans.

Comments suppressed due to low confidence (1)

docs/features/fail2ban.md:312

• Same formatting issue as the Fail2Ban diagram above: this first line no longer has the leading |/indent used by the rest of the ASCII diagram, so the flowchart alignment is off.

Request --> Is key already banned? --> Yes --> 403 (Allow2BanBlocked event)

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.