JournalStepError class

Issue #1329: one failed step's diagnostic evidence, carried by the lane journal entry's optional error object — the spawned command, the exit code, and the truncated stderr/stdout tail, so a transient step failure is debuggable from the journal alone (the entry no longer reads only "violations": ["stopped_at=<id>:<step>"]). The object is schema-declared (see _entrySchema's error property) so writer and shipped schema cannot drift.

Constructors

JournalStepError({required String behavior, required String step, required String outcome, required int exitCode, required String command, required String output})

const

Properties

behavior → String

The failed step's behavior id.

final

command → String

The spawned command line, joined for display.

final

exitCode → int

The step process's exit code (-1 when nothing spawned).

final

hashCode → int

The hash code for this object.

no setter, inherited

outcome → String

The step's own failure outcome token (error, crashed, runner-error, ...).

final

output → String

The step's stderr/stdout tail (the same truncated tail the cycle-log error entry records).

final

runtimeType → Type

A representation of the runtime type of the object.

no setter, inherited

step → String

The step that failed (gen | verify-red | make | refactor).

final

Methods

noSuchMethod(Invocation invocation) → dynamic

Invoked when a nonexistent method or property is accessed.

inherited

toJson() → Map<String, dynamic>

toString() → String

A string representation of this object.

inherited

Operators

operator ==(Object other) → bool

The equality operator.

inherited

Static Methods

fromJson(Object? raw) → JournalStepError?

Tolerant decode: null for a missing or malformed object (a legacy journal never carries the field; a hand-edited one must not crash the reader).