Struct Narrative 

pub struct Narrative {
    pub summary: String,
    pub motivation: Option<String>,
    pub rejected_alternatives: Vec<RejectedAlternative>,
    pub follow_up: Option<String>,
    pub files_changed: Vec<String>,
    pub sentiments: Vec<Sentiment>,
}

Fields

summary: String

What this commit does and WHY this approach. Not a diff restatement.

motivation: Option<String>

What triggered this change? User request, bug, planned work?

rejected_alternatives: Vec<RejectedAlternative>

What alternatives were considered and rejected.

follow_up: Option<String>

Expected follow-up. None = this is complete.

files_changed: Vec<String>

Files touched (auto-populated from diff for indexing).

sentiments: Vec<Sentiment>

Agent intuitions: worries, hunches, confidence, unease.

Trait Implementations

impl Clone for Narrative

fn clone(&self) -> Narrative

Returns a duplicate of the value.

fn clone_from(&mut self, source: &Self)

Performs copy-assignment from source.

impl Debug for Narrative

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

Formats the value using the given formatter.

impl<'de> Deserialize<'de> for Narrative

fn deserialize<__D>(__deserializer: __D) -> Result<Self, __D::Error>

where __D: Deserializer<'de>,

Deserialize this value from the given Serde deserializer.

impl JsonSchema for Narrative

fn schema_name() -> Cow<'static, str>

The name of the generated JSON Schema.

fn schema_id() -> Cow<'static, str>

Returns a string that uniquely identifies the schema produced by this type.

fn json_schema(generator: &mut SchemaGenerator) -> Schema

Generates a JSON Schema for this type.

fn inline_schema() -> bool

Whether JSON Schemas generated for this type should be included directly in parent schemas, rather than being re-used where possible using the $ref keyword.

impl Serialize for Narrative

fn serialize<__S>(&self, __serializer: __S) -> Result<__S::Ok, __S::Error>

where __S: Serializer,

Serialize this value into the given Serde serializer.