You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Deliver newly Matched rules at the earliest dispatch #59
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.
The pre-dispatch transform re-evaluates all Rule lifetimes against freshest context on every dispatch: src/runtime.ts onMessagesTransform -> evaluateSessionRules per dispatch
A durable rule first matched mid-session (any file-observation-family condition: globs, fileContains, or both) is persisted through a synthetic no-reply message via awaited session.prompt({ noReply: true }) and equivalent guidance reaches the current dispatch: src/observation-admission.test.ts:122,340 (incl. globs-only admission at observation time)
Transient delivery remains dispatch-local and consumed after one usable dispatch: src/rule-delivery.test.ts:784,900,947
Context producers record context without touching delivery state; the runtime owns all transitions
Plugin-authored synthetic messages do not recursively trigger matching: src/observation-admission.test.ts:179
Next-dispatch visibility proven through the real server hook map with mocked client interactions, including the fallback/retry path: src/observation-admission.test.ts:221 (transient fallback + persistence retry through transform).
Activity
frap129 commentedon Aug 30, 2026
Implemented in 1d4504d.
src/runtime.tsonMessagesTransform -> evaluateSessionRules per dispatchsrc/chat-message-persistence.test.ts:66session.prompt({ noReply: true })and equivalent guidance reaches the current dispatch:src/observation-admission.test.ts:122,340(incl. globs-only admission at observation time)src/rule-delivery.test.ts:784,900,947src/observation-admission.test.ts:179src/observation-admission.test.ts:221(transient fallback + persistence retry through transform).