Skip to main content

Module issue

Module issue 

Source
Expand description

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

Same layer as BPStore. Dedicated to CRUD and status lookup on Issues. The old enhance::issue::IssueSource’s acquire/release queue semantics are gone — the shape now has EnhancePP fetch directly.

Current scope:

  • InMemoryIssueStore — process-volatile default.
  • SqliteIssueStore — file-backed persistence via rusqlite-isle (thread-isolated Connection, single-writer FIFO discipline).
  • Other persistent backends (Git / mini-app / …) are future carries.

Re-exports§

pub use inmemory::InMemoryIssueStore;
pub use sqlite::SqliteIssueStore;

Modules§

inmemory
InMemoryIssueStore — a process-volatile IssueStore used by the current default.
sqlite
SqliteIssueStore — SQLite-backed IssueStore using [rusqlite-isle].

Structs§

IssueId
Issue identifier — the human-facing id for an enhance request.
IssuePayload
The unit of work the Enhance loop processes — a request that says “please modify Blueprint X”.

Enums§

IssueStatus
Lifecycle state of an Issue.
IssueStoreError
Errors surfaced by an IssueStore implementation.

Traits§

IssueStore
Persistence interface for Issues — same layer as BPStore.