docs: retire the honesty debt; state the goal; update the pipeline reality table

- README: 'Production Ready' and 'Idris-inside' badges removed/replaced with
  the true statement (Idris2 contract spec + Elixir runtime boundary); new
  Goal section (fluid for the sender, shaped for the receiver, intent-
  preserving, research mode, foundational sorting); the three tools and the
  interactive loop documented.
- TOPOLOGY.md / STATE.a2ml: honest per-component statuses (no universal 100%).
- ROADMAP.adoc: real history and forward path.
- EXPLAINME.adoc: the engine is wrapped by bug-filing-mcp; it is not itself
  a cartridge, and feedback-mcp is unrelated.
- AUTONOMOUS-BUG-PIPELINE.adoc: C1 redrawn engine-side (decision recorded);
  reality table updated — C1/C2 BUILT, C3 built as contract-spec + runtime
  boundary, Deduplicator wired, NetworkVerifier optionally wired; D0 RESOLVED;
  honesty-debt items marked retired.

Part of hyperpolymath/boj-server#274.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017LDhR8gtnittEWSafunnrq

Author: claude

.machine_readable/6a2/STATE.a2ml

@@ -1,32 +1,34 @@
 # SPDX-License-Identifier: MPL-2.0
 # STATE.a2ml — Project state checkpoint
 # Converted from STATE.scm on 2026-03-15
-# Updated 2026-04-09
+# Updated 2026-07-09
 
 [metadata]
 project = "feedback-o-tron"
-version = "1.0.0"
-last-updated = "2026-04-09"
-status = "production"
+version = "1.2.0-dev"
+last-updated = "2026-07-09"
+status = "active-development"
 
 [project-context]
 name = "feedback-o-tron"
-completion-percentage = 95
-phase = "Production"
+completion-percentage = 75
+phase = "Synthesis Engine + honest reconciliation"
 
 [components]
 cli = "100%"
-mcp-server = "100%"
+mcp-server = "100% (research_feedback, synthesize_feedback, submit_feedback, migration_observe)"
+http-intake = "done (Bandit :7722, localhost-only, off by default; boj bug-filing-mcp wire)"
+synthesis-engine = "done (this PR: TemplateFetcher, TemplateCache, IntentClassifier, Hydrator, Research, Synthesizer, FormValidator, FormRenderer, TextSimilarity)"
 channels-github = "100%"
-channels-gitlab = "100%"
-channels-bitbucket = "100%"
-channels-codeberg = "100%"
+channels-gitlab = "90%"
+channels-bitbucket = "90%"
+channels-codeberg = "90%"
 channels-bugzilla = "100%"
 channels-email = "80%"
-deduplication = "100%"
+deduplication = "wired (record/3 called on successful submission; check/1 consulted pre-dispatch and by Research)"
 audit-logging = "100%"
-network-verifier = "90%"
+network-verifier = "70% (real probing; opt-in via Hydrator network_probe; BGP/RPKI partial)"
 rate-limiter = "100%"
 retry-backoff = "100%"
-zig-ffi = "95%"
-idris2-proofs = "80%"
+zig-ffi = "stub"
+idris2 = "contract spec only (Contract.idr), no FFI enforcement"

EXPLAINME.adoc

@@ -11,31 +11,31 @@ ____
 Autonomous multi-platform bug reporting for AI agents. Successfully validated on 2026-02-07 with 2 real bugs filed to Fedora Bugzilla: Bug #2437503 (maliit-keyboard crash) and Bug #2437504 (xwaylandvideobridge error).
 ____
 
-This is achieved through six submitters (GitHub, GitLab, Bitbucket, Codeberg, Bugzilla, Email), fuzzy deduplication (Levenshtein distance), and formal verification of ABI boundaries via Idris2.
+This is achieved through six submitters (GitHub, GitLab, Bitbucket, Codeberg, Bugzilla, Email), fuzzy deduplication (Levenshtein distance), and an Idris2-verified contract spec (`src/abi/FeedbackOTron/Contract.idr`) mirrored at runtime by the Elixir validation boundary (`FormValidator`). Full FFI enforcement (the Zig bridge) is not built — the contract is a proof-carrying spec, not a boundary the payload physically crosses.
 
 == Two Verifiable Claims from How-It-Works
 
 === Claim 1: Bugzilla REST API Supports Product/Component/Version Targeting
 
-**Location**: `/var/mnt/eclipse/repos/feedback-o-tron/elixir-mcp/lib/feedback_a_tron/submitter.ex` (Elixir submitter module)
+**Location**: `elixir-mcp/lib/feedback_a_tron/submitter.ex` and `elixir-mcp/lib/feedback_a_tron/channels/bugzilla.ex`
 
 **How verified**: The Bugzilla submitter (in the above file) uses the Bugzilla REST API endpoint (`/rest/bug`) to create bugs. README (§Production Status) claims "Bugzilla REST API: Full product/component/version support" and provides a real-world example: `--repo "Fedora" --component "maliit-keyboard" --version "43"` successfully filed Bug #2437503. The submitter validates that component exists before submitting (via GET `/rest/product/{product}/valid_field_values?field=component`), rejects invalid versions, and includes full stack traces in the body.
 
 **Caveat**: Component validation is API-based (not local); if the Bugzilla instance changes its components, validation may fail silently.
 
 === Claim 2: Deduplicator Prevents Duplicate Submissions Using Fuzzy Matching
 
-**Location**: `/var/mnt/eclipse/repos/feedback-o-tron/elixir-mcp/lib/feedback_a_tron/deduplicator.ex` (Elixir deduplication)
+**Location**: `elixir-mcp/lib/feedback_a_tron/deduplicator.ex` (Elixir deduplication)
 
-**How verified**: The deduplicator implements three strategies: SHA-256 hash (exact match), Levenshtein distance (typos/minor rewording), and fuzzy match (substring matching). README (§Key Features) claims "Prevents duplicate submissions using fuzzy matching (Levenshtein distance)." The module is tested in `tests/deduplication_test.exs` which verifies: identical reports are caught, reports differing by <10% edit distance are flagged as similar, and unrelated reports pass through.
+**How verified**: The deduplicator implements three strategies: SHA-256 hash (exact match), Levenshtein distance (typos/minor rewording), and fuzzy match (substring matching). README (§Key Features) claims "Prevents duplicate submissions using fuzzy matching (Levenshtein distance)." The module is tested in `elixir-mcp/test/deduplicator_test.exs` which verifies: identical reports are caught, reports differing by <10% edit distance are flagged as similar, and unrelated reports pass through. As of the Synthesis Engine branch the dedup is *wired end-to-end*: `Submitter` calls `Deduplicator.record/3` after each successful submission and `check/1` before dispatch, and `Synthesis.Research` consults `check/1` during research mode.
 
 **Caveat**: Fuzzy matching threshold (10%) is empirical, not formally justified. May have false positives/negatives.
 
 == Dogfooded Across The Account
 
-Uses the hyperpolymath ABI/FFI standard (Idris2 + Zig) for formally verified credential handling. The Submitter module calls formally specified Idris2 ABI types (from the `proven` repo) to guarantee memory safety at FFI boundaries. This is reused in gossamer (window management credentials) and echidna (proof solver credentials).
+Follows the hyperpolymath ABI/FFI repo layout (Idris2 spec + Zig bridge). To be precise about what that means here: the Idris2 side is a real, proof-carrying contract spec (`Contract.idr`), the Elixir `FormValidator` enforces the same rules at runtime, and the Zig FFI bridge is a stub — the Submitter does **not** call Idris2-compiled code or `proven` types at any FFI boundary.
 
-Also integrates with boj-server (cartridge system) — feedback-o-tron is a cartridge itself.
+Also integrates with boj-server (cartridge system) — but feedback-o-tron is **not** a cartridge itself. The engine is wrapped by the `bug-filing-mcp` cartridge in `boj-server-cartridges`, which forwards requests over the engine's localhost HTTP intake (`127.0.0.1:7722`). The similarly named `feedback-mcp` cartridge is an unrelated sentiment counter that merely shares the name (see `docs/AUTONOMOUS-BUG-PIPELINE.adoc` §5).
 
 == File Map
 
@@ -44,28 +44,31 @@ Also integrates with boj-server (cartridge system) — feedback-o-tron is a cart
 | Path | What's There
 
 | `elixir-mcp/lib/feedback_a_tron/cli.ex` | CLI entry point: escript with submit, --mcp-server, --version, --help commands
-| `elixir-mcp/lib/feedback_a_tron/submitter.ex` | Submitter module: six platform adapters (GitHub, GitLab, Bitbucket, Codeberg, Bugzilla, Email)
+| `elixir-mcp/lib/feedback_a_tron/submitter.ex` | Submitter module: dispatch to platform channels; validates `template_data` against the fetched form before rendering/dispatch
+| `elixir-mcp/lib/feedback_a_tron/channels/` | Platform channel adapters (GitHub, GitLab, Bitbucket, Codeberg, Bugzilla, Email, and more)
 | `elixir-mcp/lib/feedback_a_tron/deduplicator.ex` | Fuzzy deduplication: SHA-256, Levenshtein distance, substring matching
-| `elixir-mcp/lib/feedback_a_tron/credential_loader.ex` | Environment variables + CLI config auto-detection (gh, glab)
+| `elixir-mcp/lib/feedback_a_tron/credentials.ex` | Environment variables + CLI config auto-detection (gh, glab)
 | `elixir-mcp/lib/feedback_a_tron/audit_log.ex` | JSON-lines audit trail; records all submissions (success, failure, dry-run)
-| `elixir-mcp/lib/feedback_a_tron/network_verifier.ex` | Pre/post-submission checks: latency, DNS, TLS, DNSSEC, BGP/RPKI
-| `elixir-mcp/src/abi/` | Idris2 ABI definitions for Submitter interface (formal spec, generates C headers)
-| `elixir-mcp/src/abi/Types.idr` | Idris2 type definitions with dependent type proofs for memory layout
-| `elixir-mcp/src/abi/Foreign.idr` | Idris2 FFI declarations for C ABI boundary
-| `tests/deduplication_test.exs` | Deduplicator tests: exact, fuzzy, substring matching
-| `tests/submitter_test.exs` | Submitter tests for each platform (mocked HTTP)
-| `tests/network_verification_test.exs` | Network verifier tests (DNS, TLS, DNSSEC)
-| `tests/integration_test.exs` | End-to-end tests with real Bugzilla (dry-run mode, Bug #2437503/#2437504 validated)
+| `elixir-mcp/lib/feedback_a_tron/network_verifier.ex` | Network checks: latency, DNS, TLS, DNSSEC, BGP/RPKI (opt-in via Hydrator `network_probe`)
+| `elixir-mcp/lib/feedback_a_tron/synthesis/` | Synthesis Engine: TemplateFetcher/Cache, IntentClassifier, Hydrator, Research, Synthesizer, FormValidator, FormRenderer
+| `elixir-mcp/lib/feedback_a_tron/http_intake/router.ex` | Optional localhost HTTP intake (`:7722`) — the boj `bug-filing-mcp` cartridge wire
+| `src/abi/FeedbackOTron/Contract.idr` | Idris2-verified contract spec for form validation (total, proof-carrying; mirrored by FormValidator)
+| `ffi/zig/src/main.zig` | Zig FFI bridge — currently a stub; no FFI enforcement
+| `elixir-mcp/test/deduplicator_test.exs` | Deduplicator tests: exact, fuzzy, substring matching
+| `elixir-mcp/test/submitter_test.exs` | Submitter tests for each platform (mocked HTTP)
+| `elixir-mcp/test/network_verifier_test.exs` | Network verifier tests (DNS, TLS, DNSSEC)
+| `elixir-mcp/test/synthesis/` | Synthesis Engine tests (classifier, hydrator, research, synthesizer, validator, renderer, fetcher)
 |===
 
 == Testing Critical Paths
 
-* **Bugzilla REST API**: `tests/submitter_test.exs` — mock Bugzilla API, verify product/component/version handling
-* **Deduplication**: `tests/deduplication_test.exs` — test hash, Levenshtein, and fuzzy matching with edge cases
-* **Credential loading**: `tests/credential_loader_test.exs` — verify env vars, gh, glab configs are loaded in priority order
-* **Audit logging**: `tests/audit_log_test.exs` — verify all submissions recorded, JSON-lines format valid
-* **Integration**: `tests/integration_test.exs` — real Bugzilla instance (dry-run), verify Bug #2437503/#2437504 creation flow
-* **Network verification**: `tests/network_verification_test.exs` — mock DNS/TLS, verify latency, DNSSEC, route checks
+* **Bugzilla REST API**: `elixir-mcp/test/submitter_test.exs` — mock Bugzilla API, verify product/component/version handling
+* **Deduplication**: `elixir-mcp/test/deduplicator_test.exs` — test hash, Levenshtein, and fuzzy matching with edge cases
+* **Credential loading**: `elixir-mcp/test/credentials_test.exs` — verify env vars, gh, glab configs are loaded in priority order
+* **Audit logging**: `elixir-mcp/test/audit_log_test.exs` — verify all submissions recorded, JSON-lines format valid
+* **Integration**: `elixir-mcp/test/integration/` and `elixir-mcp/test/e2e_test.exs` — end-to-end flows in dry-run mode
+* **Network verification**: `elixir-mcp/test/network_verifier_test.exs` — mock DNS/TLS, verify latency, DNSSEC, route checks
+* **Synthesis Engine**: `elixir-mcp/test/synthesis/` — classifier gate (salvage/reject/open-questions), hydration, research, form validation/rendering
 
 == Questions?