Module store 

Persistence layer — the sibling of application / service in the Layered decomposition.

Every entry in this module is either a Store trait or one of its backend implementations. Domain entities themselves (Blueprint, EnhanceSetting, EnhanceLogEntry, …) live in their originating domain modules; the traits here describe the persistence contract and nothing else.

Blueprint is the one exception: its store lives at crate::blueprint::store because the Git-backed backend is deeply tied to BlueprintVersion / ContentHash / commit-graph semantics and does not fit the flat-CRUD shape used here.

Modules

enhance_log

EnhanceLogStore — append-only log of one LogEntry per Enhance-flow invocation.

enhance_setting

EnhanceSettingStore — a key-value store for EnhanceSetting.

issue

IssueStore — the persistence abstraction for enhance requests (Issues).

output

output_store — Data-plane support layer

replay

ReplayStore — per-run log of completed step outputs plus the whole Ctx snapshot captured at the moment each step passed.

run

RunStore — persistence for Run records (one kick of a Task).

task

TaskStore — persistence for Task records.

trace

RunTraceStore — the persisted per-Run trace rail (TraceEvent stream) plus the normalized worker-stats types (TokenUsage / WorkerStats) shared by the trace rail and the crate::store::run::StepEntry step-stats extension.