test: add LiveKit Agents drift proof - #48
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
MaazAhmed47
marked this pull request as ready for review
August 15, 2026 15:02
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 a fixed-scope, synthetic LiveKit Agents proof for this exact path:
The proof records an explicitly approved read-only/internal boundary, performs one allowed call, explicitly refreshes discovery after a same-identity read-plus-export/external mutation, observes Interlock quarantine only the changed tool, and proves the later wrapper call is held with zero upstream execution delta. It also retains review evidence and verifies all currently supported Security Receipt checks.
No Interlock core behavior is changed.
Exact provenance
a78d5a0a4557a63f0db71e41a70d451c03bb13bb3c24b45a614f1c2f4e201b7a4152d6aee30aeb6ctrue06c71f9c718e24a151630447755a9fa86851b3891.6.101.28.13.12.9SHA-bound local verification
At
3c24b45a614f1c2f4e201b7a4152d6aee30aeb6c:proof.jsonrecords the pinned base SHA, exact integration SHA, and successful ancestry verification.MCPToolset.setup().adapter_enforced_explicit_approvalisfalse.1.0.record_found,chain,receipt_match,evidence_digest, andbindingalltrue.22 passed.125 passed.1977 passed, 134 skipped, 6 xfailed, 4 warnings.5 integration Python files unchanged.3 source files, no issues.git diff --check: passed.Limitations
AgentSessionis started and no LLM selects or invokes the tool./mcp/toolsexposes no distinct explicit-approval marker.POST /mcp/discoverobservation refresh.requirements-pinned.txtcontains direct dependency pins and is not a resolved transitive lock.CI repair
Two focused follow-up commits repair the old-SHA Backend CI failures without changing Interlock runtime behavior:
c93092ed76b506b0cfead88505ab3cc8df6ed2a9-ci: run LiveKit proof in backend checksfetch-depth: 0, allowing the proof's pinned-base ancestry check to run against the pull-request merge checkout.requirements.txtandexamples/livekit_agents/requirements-pinned.txtwhile retaining the whole-directorypython -m pytest tests/ -q -ragate.3c24b45a614f1c2f4e201b7a4152d6aee30aeb6c-test: remove stochastic payment evidence assertion4242substring scan and the timestamp-stripping helper made unused by that removal.cus_secret,pm_secret,ch_secret, andacct_secretsanitization assertions and the hash-evidence assertion.New-SHA verification
Clean full-history verification at
3c24b45a614f1c2f4e201b7a4152d6aee30aeb6cused the revised CI install:pip check: no broken requirements.pip-audit 2.10.1: no known vulnerabilities.22 passed.25/25consecutive passes; complete payment proof file3 passed.125 passed.1977 passed, 134 skipped, 6 xfailed, 4 warnings.68 Python files unchanged.61 source files, no issues.3 source files, no issues.git diff --check, workflow YAML validation, and secret/artifact scans: passed.Exact-SHA GitHub checks
GitHub Actions run 31884920835 and all external statuses are bound to
3c24b45a614f1c2f4e201b7a4152d6aee30aeb6c:1974 passed, 137 skipped, 6 xfailed, 4 warnings.