[codex] Add Telegram manifest contract tests#2
Draft
mimeding wants to merge 1 commit into
Draft
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds Telegram manifest contract tests and updates stale test fixtures to match the current task event and stream state models.
Business Rationale
Telegram is a public-facing interaction surface, so regressions in route, tool, or payload contracts can directly break user conversations. Executable contract coverage keeps the integration stable as host and plugin schemas evolve.
Coding Rationale
The existing runtime behavior already expects the current model shapes. Updating tests and adding manifest assertions makes the supported contract explicit without adding new host behavior.
Expected LLM Performance Improvement
A stable tool and route contract reduces malformed tool usage, improves message handoff reliability, and keeps model-driven Telegram interactions from drifting across schema changes.
Changes
Test Plan
swift testswift build -c releaseswift-format lint --strict Tests/osaurus_telegram_tests/ManifestContractTests.swift Tests/osaurus_telegram_tests/ModelsTests.swift Tests/osaurus_telegram_tests/StreamingTests.swiftgit diff --check