Module issues_http 

Derived issue/project state (#949 phase 3). pub so lex-hub can wrap the handlers with owner-session auth for the console, as it does for review_http. Derived issue/project state over HTTP (#949 phase 3).

A board is a view: GET /v1/issues returns every issue with its state computed from the op-log (open / in progress / verified / blocked), GET /v1/issues/<id> adds the recorded verdicts, and GET /v1/projects groups issues by project with per-state counts. Nothing here is stored or moved by hand — see lex_store::issues for the derivation rules — so the board cannot drift from the code. The hub delegates these per tenant; the browser console’s owner-auth wrapping is lex-hub’s concern.

Functions

issue_detail_handler

GET /v1/issues/<id> — one issue, its derived state, and every recorded IssueVerified verdict. 404 for an unknown id.

issues_state_handler

GET /v1/issues — every issue with its derived state.

projects_handler

GET /v1/projects — issues grouped by project (a project is a subgraph with a goal), each with per-state counts. Issues with no project appear in /v1/issues only.