JournalReader class

The ONE canonical read API (issue #1113 requirement 2): any tool — theater, status, prove, simulate — reads the journal stream through here, not N file-format parsers.

Constructors

JournalReader()

const

Properties

hashCode → int

The hash code for this object.

no setter, inherited

runtimeType → Type

A representation of the runtime type of the object.

no setter, inherited

Methods

noSuchMethod(Invocation invocation) → dynamic

Invoked when a nonexistent method or property is accessed.

inherited

read({required String feature, required String projectRoot, String? featureDir}) → Future<FeatureJournal>

Load feature's whole journal stream under projectRoot.

toString() → String

A string representation of this object.

inherited

Operators

operator ==(Object other) → bool

The equality operator.

inherited

Static Methods

lastResetTombstone(String featureDir) → Future<({DateTime? at, Set<String> behaviors})>

Issue #1331: the feature's LAST reset tombstone — the invalidated behavior ids WITH the reset's timestamp. Consumers (make's re-drive adoption probe) compare the timestamp against the surviving evidence's - at: to separate the re-drive class (the surviving certification predates the tombstone — stale by decree) from a live drift (the evidence postdates the reset — authoritative again).

tombstonedBehaviors(String featureDir) → Future<Set<String>>

Issue #1264: the behavior ids the feature's LAST reset tombstone invalidated — the empty set when no tombstone exists. The run driver's reconciliation subtracts these from the cycle-log evidence sets, so a reset's dropped behaviors re-drive instead of skipping as "already done" off surviving green evidence.