Files
Ayaan Zaidi 10e0e690df feat(mantis): programmable proof boundaries with recipe library (#127782)
Makes the Mantis Telegram Desktop proof agent programmable at its trust boundaries: declarative Bot API fault rules (drop/status per method), per-request scripted mock-provider responses, observe-until predicates (post-cursor events/text, cumulative provider count), and bounded proxy-side recording of outbound Bot API requests as trusted lane facts. Adds a reusable recipe library under .github/codex/prompts/mantis-recipes/ and raises the proof agent's reasoning effort to high.

Security: the SUT container shadows proxy-control with an inaccessible tmpfs so candidate PR code sharing the mantis-sut uid cannot read or rewrite the proxy's recorded evidence; unmount is blocked by cap-drop/no-new-privileges. Proof doctrine now treats proxy-recorded Bot API facts as trusted comparison evidence and provider request logs as diagnostics.

Follow-up named in PR: move the mock OpenAI server out of the SUT container so provider request facts also become candidate-tamper-proof.
2026-08-22 11:06:06 +05:30
..

Mantis proof recipes

Use the closest recipe, keep baseline and candidate inputs identical, and adapt only identifiers returned by the lane. Trusted request facts can prove a change even when Telegram Desktop pixels match.

  • send-failure-injection.md: outbound Bot API failures and retry behavior
  • busy-queue-scripted-provider.md: ordered slow/fast multi-turn responses
  • callback-data-payload-proof.md: byte-level callback payload differences

Return to mantis-telegram-desktop-proof.md for limits, cleanup, and publishing.