Module task 

TaskStore — persistence for Task records.

Part of the issue #13 ID-hierarchy reconciliation: Blueprint -> Task -> Run -> Step -> Attempt. A Task is the work-item identity: one row per unit of work (“resolve issue #10” + a Blueprint ref snapshot + an input ctx), created once when the work is submitted (e.g. POST /v1/tasks). A single Task can be kicked N times; each kick mints a RunId and is tracked by the sibling crate::store::run store — this module owns only the 1-row-per-Task identity and its coarse lifecycle status.

Current scope:

• InMemoryTaskStore — process-volatile default.
• SqliteTaskStore — file-backed persistence via rusqlite-isle (thread-isolated Connection, single-writer FIFO discipline; same shape as crate::store::issue::sqlite::SqliteIssueStore).
• Other persistent backends (Git / mini-app / …) are future carries.

Re-exports

pub use inmemory::InMemoryTaskStore;

pub use sqlite::SqliteTaskStore;

Modules

inmemory

InMemoryTaskStore — a process-volatile TaskStore used by the current default.

sqlite

SqliteTaskStore — SQLite-backed TaskStore using [rusqlite-isle].

Structs

TaskRecord

One persisted Task row — the work-item identity.

Enums

TaskRecordStatus

Lifecycle status of a TaskRecord.

TaskStoreError

Errors surfaced by a TaskStore implementation.

Traits

TaskStore

Persistence interface for Task records — the work-item identity layer of the issue #13 ID hierarchy.