Module enhance 

The POST /v1/issues dispatcher — see enhance::EnhanceApplication. EnhanceApplication — the dispatcher for the POST /v1/issues path.

The entry point (POST /v1/issues) only does IssueStore.create — a synchronous enqueue. The actual dispatch is drained by a consumer loop calling tick():

POST /v1/issues ──→ IssueStore (queue)
                           ↓
    consumer loop (tokio::spawn) ── tick() ──┐
                                             ↓
                 IssueStore.pop_pending + EnhanceSettingStore.get
                                             ↓
                 BPStore.read_head(setting.blueprint.id)      (fetched on use)
                                             ↓
                 TaskLaunchService.launch(...)                (engine bind + attach + start_task)

Current scope:

• Engine task-completion → Issue.update_status is a carry.
• Setting VersionSelector (Fixed / Latest / SemverReq) is a carry — today we always use BPStore.read_head.
• The agent-selection convention is setting.blueprint.agents.first().name.

Structs

EnhanceApplication

The POST /v1/issues dispatcher — enqueues via Application::handle, drains via EnhanceApplication::tick / EnhanceApplication::run_forever.

EnhanceApplicationConfig

Configuration parameters for EnhanceApplication.

EnhanceApplicationInput

Input to EnhanceApplication::handle — the POST /v1/issues request body once decoded.

TickOutcome

Result of a single tick. task_id is gone — the flow-eval path runs many steps to completion instead of being tied to a single task id, so the entire final_ctx is the result. Outcomes are checked through status.

Enums

EnhanceApplicationError

Failure modes of EnhanceApplication::tick and the internal dispatch_one step it wraps.