Struct IssueLikeHook 

pub struct IssueLikeHook {
    pub kind: &'static str,
}

KindHook shared by issue and pull_request — both require properties.number (integer) and properties.project_id (UUID), and, when present, validate properties.state_reason (governed to a fixed set for issue per ADR-088 §3; only checked for non-emptiness for pull_request). See crates/khive-pack-git/docs/api/hooks.md#issuelikehook for why project_id is required here rather than left to caller discipline.

Fields

kind: &'static str

The note kind this instance validates: "issue" or "pull_request".

Trait Implementations

impl Debug for IssueLikeHook

fn fmt(&self, f: &mut Formatter<'_>) -> Result

Formats the value using the given formatter.

impl KindHook for IssueLikeHook

fn prepare_create<'life0, 'life1, 'life2, 'async_trait>( &'life0 self, _runtime: &'life1 KhiveRuntime, args: &'life2 mut Value, ) -> Pin<Box<dyn Future<Output = Result<(), RuntimeError>> + Send + 'async_trait>>

where Self: 'async_trait, 'life0: 'async_trait, 'life1: 'async_trait, 'life2: 'async_trait,

Mutate args before the storage write. Fill defaults, normalize values, rearrange user-facing fields into the storage shape expected by the shared CRUD handler.

fn after_create<'life0, 'life1, 'life2, 'async_trait>( &'life0 self, _runtime: &'life1 KhiveRuntime, _id: Uuid, _args: &'life2 Value, ) -> Pin<Box<dyn Future<Output = Result<(), RuntimeError>> + Send + 'async_trait>>

where Self: 'async_trait, 'life0: 'async_trait, 'life1: 'async_trait, 'life2: 'async_trait,

Fire side effects after a successful storage write — graph edges, derived observations, etc. The newly created record’s UUID is passed so the hook can attach metadata referencing it.