Skip to content

docs: point the hook/event plan at the follow-up issues it split out - #1204

Merged
mastacontrola merged 1 commit into
working-1.6from
docs-hook-event-followups
Aug 19, 2026
Merged

docs: point the hook/event plan at the follow-up issues it split out#1204
mastacontrola merged 1 commit into
working-1.6from
docs-hook-event-followups

Conversation

@mastacontrola

Copy link
Copy Markdown
Member

Closes the loop between docs/hook-event-plan.md and the tracker now that #1202 and #1203 exist. Documentation only — no code, no test, no route change.

The rejected one-dispatcher alternative is deliberately not filed as an issue; the plan now says why.

🤖 Generated with Claude Code

https://claude.ai/code/session_013mJVe4CpK3rRbi9H5GubXd

The plan named two things as belonging in their own issue and one as
rejected. Now that #1202 (the two notification events that have never fired)
and #1203 (Hook extends Event) exist, say so, so the reasoning and the
tracker are not two separate records of the same decisions.

The rejected one-dispatcher alternative is explicitly not filed: an open
issue for something nobody is arguing for reads as agreed work.

Co-Authored-By: Claude <noreply@anthropic.com>
@mastacontrola
mastacontrola merged commit 29d7e42 into working-1.6 Aug 19, 2026
3 checks passed
@mastacontrola
mastacontrola deleted the docs-hook-event-followups branch August 19, 2026 10:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants