[Epic]: Autonomous bug-reporting pipeline — boj Gateway → feedback-o-tron Synthesis → verified dispatch

[hyperpolymath]

What this tracks

The end-to-end autonomous bug-reporting pipeline (2026-06-28 diagram). Full architecture +
honest built-vs-proposed status: feedback-o-tron/docs/AUTONOMOUS-BUG-PIPELINE.adoc.

Crash → boj Gateway ─①fetch template schema→ bug.yml ─②schema+state→ feedback-o-tron Synthesis
(hydrate + environment · LLM trajectory/logs · NetworkVerifier/OS · Deduplicator) ─③clean
validated payload→ Idris2 Verified ABI ─④dispatch→ GitHub/GitLab/Bugzilla.

Why

On 2026-06-28, #262/#263/#264 captured pieces of the runtime this pipeline runs in
(containerisation, caching, tracing) but not the pipeline itself. This is the fan-in.

Current reality (updated 2026-07-17)

Core pipeline delivered and merged. C1 (engine-side template fetch), C2 (Synthesis
Engine, agent-in-the-loop), C3 (Idris2 contract spec + strict Elixir runtime boundary),
Deduplicator wired, bug.yml forms in all three repos. Merged via
hyperpolymath/feedback-o-tron#51, hyperpolymath/boj-server-cartridges#85 (cartridge v0.2,
Teranga), #285 (bundling + offline menu). Only the runtime triplet remains.

Sub-issues

• D0 Resolve feedback-o-tron vs feedback-mcp identity — RESOLVED 2026-07-09: new wrapping cartridge bug-filing-mcp (see comment below)
• HTTP intake POST 127.0.0.1:7722/api/v1/submit_feedback — [Feature]: feedback-o-tron HTTP intake — POST /api/v1/submit_feedback on 127.0.0.1:7722 #278
• bug-filing-mcp cartridge wrapping the engine — [Feature]: new bug-filing-mcp cartridge wrapping the real feedback-o-tron engine #279 (now v0.2 Teranga via boj-server-cartridges#85)
• C1 Template-schema fetch (redrawn engine-side) + C2 Synthesis Engine — [Feature]: C1+C2 — Synthesis Engine in feedback-o-tron (engine-side template fetch, intent classification, hydration, research mode) #282 (merged: feedback-o-tron#51)
• C3 Verified payload boundary: real Idris2 contract spec + Elixir runtime enforcement — [Feature]: C3 — real Idris2 contract spec + strict Elixir runtime validation boundary (drop the fictional ABI claims) #283 (merged: feedback-o-tron#51; full FFI enforcement deferred to Follow-up: full FFI enforcement — Idris-derived validator on the dispatch path (Zig NIF) feedback-o-tron#49)
• Wire the Deduplicator (record/3) — merged in feedback-o-tron#51
• Author bug.yml issue forms — merged across all three repos (chore(deps): bump nixpkgs from ebc0854 to 73c703c #51/docs: OpenSSF Scorecard + Software Heritage badges + CITATION.cff #85/feat(cartridges): bundle bug-filing-mcp v0.2 — core (Teranga) discoverability #285)
• (runtime) OCI containerisation — [Feature]: OCI containerisation & immutable runtime isolation for boj-server #275 (re-file of [Deps]: containerise and guix the thing fully #262)
• (runtime) SWR cartridge caching — [Feature]: Offline pre-fetch & stale-while-revalidate cartridge caching #276 (re-file of [Perf]: speed up cache staleness #263)
• (runtime) OpenTelemetry tracing — [Feature]: OpenTelemetry distributed tracing across the boj ↔ ABI ↔ cartridge boundary #277 (re-file of [Feature]: #264)

[hyperpolymath]

D0 RESOLVED (owner, 2026-07-09): New wrapping cartridge (converge without collision).

• The existing feedback-mcp sentiment-counter cartridge is left untouched (no rename, no rewrite).
• A new first-class cartridge (bug-filing-mcp) will wrap the real feedback-o-tron engine.
• feedback-o-tron gains a real HTTP intake on 127.0.0.1:7722 (POST /api/v1/submit_feedback) so the gateway → cartridge → engine chain is live.

This is decision-safe/reversible and ends the name ambiguity by making the real engine first-class rather than mutating a published artifact. See feedback-o-tron/docs/AUTONOMOUS-BUG-PIPELINE.adoc §5. Build issues below close the intake (C2-intake) and the new cartridge.