Design 47 H: H-A-166, a view reader hears an event on its bare subject too

This commit is contained in:
2026-11-20 17:37:45 +01:00
parent 541defcd78
commit ad2ecbcc84
@@ -853,3 +853,11 @@ Where two preparers disagreed, the chosen one is named.
released version". The indexer: a version-released of a package starts the re-pin of every module whose
`packages` hold it (the pass of H-A-161 for those modules alone), so pins move on the event and never wait for a
merge or a hand act. P3, P1, P11.
- **H-A-166 (a view reader hears an event on its bare subject too, 17:37)** Met at main.20 and main.22 after
the registration of mesh-delivery-contracts (17:34): the seat mesh-catalog says registration-changed on the bare
subject (its contract), while the SDK's view reader adopts a handler on `<subject>.>` alone, so the runner's event
hub took the event "by no handler, acknowledged" and A-327's placing never ran; the same kind as this morning's
consumer filters (vault, assigner) in another place. The contract is the seat's word: the SDK's view reader listens
on the bare subject and on `<subject>.>` alike (one handler, both forms), for events and for views, with the test
that a bare-subject event reaches the handler; an event a module declares it consumes and nobody handles is said
loud in the journal with the subject, as today, and counted in the module's health as a finding. P3, P9, P7.