Deliver newly Matched rules at the earliest dispatch

[frap129]

Parent

#38

What to build

Use the pre-dispatch transform as the completeness gate so every newly Matched rule is available at the first provider dispatch where it can affect work, while preserving each Rule lifetime.

Acceptance criteria

• The pre-dispatch transform re-evaluates all Rule lifetimes against the freshest session context on every dispatch.
• Initial durable matches retain established user-message delivery.
• A durable Rule first matched mid-session is persisted through a synthetic no-reply message and equivalent guidance is available to the current in-memory dispatch.
• Transient Rule delivery remains dispatch-local and is consumed after one usable dispatch.
• Context producers record context without manipulating Rule-delivery state.
• Plugin-authored synthetic messages do not recursively trigger matching or delivery.
• Acceptance coverage proves next-dispatch visibility through the real server hook map and mocked OpenCode client interactions.

Blocked by

• Match Rules from successful Read observations #54