feat: leakage verification harness + v4 observability docs (#52)#87
Merged
itscooleric merged 3 commits intodevfrom Mar 17, 2026
Merged
feat: leakage verification harness + v4 observability docs (#52)#87itscooleric merged 3 commits intodevfrom
itscooleric merged 3 commits intodevfrom
Conversation
Test harness to verify AI agents don't leak gitignored secrets: - setup-fixture.sh: creates synthetic repo with unique markers in .env, credentials.json, *.pem, secrets/, node_modules/ - check-leakage.py: scans intercept/egress/conversation logs for marker strings — exits 0 (clean) or 1 (leaked) - run-test.sh: full end-to-end test runner Also adds docs/observability.md documenting the full v4 stack: session logging, token tracking, egress audit, intercept proxy, leakage testing, firewall, MITM cert trust, secret redaction. Closes #52 Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
- Start intercept proxy in entrypoint.sh (not just claude-entrypoint) so web terminal sessions also route through the proxy - Install mitmproxy CA cert system-wide + set NODE_EXTRA_CA_CERTS so Node.js (Claude Code) trusts the MITM HTTPS interception - Wait 2s for mitmproxy to generate its CA before proceeding Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
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
1 participant
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
Leakage test harness
Verifies AI agents don't send gitignored secrets to their API endpoints:
tests/leakage/setup-fixture.sh— synthetic repo with unique markers in .env, credentials.json, *.pem, secrets/, node_modules/tests/leakage/check-leakage.py— scans intercept/egress/conversation logs for marker stringstests/leakage/run-test.sh— end-to-end: create fixture → run Claude → check logsObservability docs
docs/observability.md— comprehensive documentation of the full v4 stack:Closes #52 — this closes out all v4: Agent Observability tickets!
v4 final status
Test plan
🤖 Generated with Claude Code