Repository navigation
fix(benchmark): rebind offline evidence artifact to refreshed source hashes - #328
Merged
Merged
Conversation
…nd Code hook - Implement file_guard.py for host-mediated protection of sensitive files - Add Command Code PreToolUse hook integration in integrations/commandcode/file_guard_hook.py - Support --file-guard flag in scripts/install_cc_hook.py with idempotent hook registration - Add documentation in docs/FILE_PROTECTION.md and update SECURITY.md and README.md - Add comprehensive unit tests in tests/test_file_guard.py and tests/test_install_cc_hook.py
…work - Add the dependency-free stdio MCP bridge so desktop clients share one warm engine - Add desktop-memory evaluation and closure/session-lineage test coverage - Update recall, store, sync, dashboard, and MCP internals for governed temporal history, session lineage, and deterministic measurements - Refresh documentation, benchmark evidence, and local browser-auth behavior - Record the 1.7.10 candidate changelog and version markers
- Bump package, plugin, and commercial-manifest versions to 1.7.12 - Record the 1.7.12 changelog entry for the stdio bridge, desktop-memory evaluation, and history-integrity work - Refresh Claude plugin asset checksums
- Promote the local RAM tester into tools/ram_probe.py with argparse entry points, a Windows guard, and a docstring - Verify constant patterns in bounded windows so checking never doubles the resident allocation, and cap walking/random windows explicitly - Report worker, pass, offset, expected value, and XOR diff on a mismatch
Agent: antigravity
IncompleteRead and other http.client.HTTPException instances raised when the watchdog interrupts socket reads now map to TimeoutError rather than failing into generic transport errors. Agent: antigravity
engraphis/http_deadline.py changed in this branch but the registered artifact still bound its previous digest, so test_benchmark_evidence.py failed on Python 3.10 through 3.14, the numpy-only 3.9 core floor, and the coverage gate. Re-record the producer digest, recompute the suite digest, and re-pin the artifact SHA in the sidecar, README, BENCHMARKS, both SVGs, both PNG provenance chunks, and the test constant.
Take main's 1.7.12 release evidence artifact for the conflicted benchmark surfaces, then rebind it to this branch's http_deadline.py change: re-record the producer digest, recompute the suite digest, and re-pin the artifact SHA across the sidecar, README, BENCHMARKS, both SVGs, both PNG provenance chunks, and the test constant.
CVE-2026-115557 in the Python 3.11.17 runtime is fixed in 3.11.18. Pin the new multi-arch digest so the release grype gate can pass.
Main was replayed onto the release lineage; the trees differ only by the Python base-image update. Merge the new lineage so the PR has a valid merge base without rewriting the branch.
## Why upgrade to Pro or Team in the README - Adds a prominent upgrade section after the local feature list. - Explains memory health analytics, scheduled upkeep, encrypted sync, team roles/audit, and the included Jev allowance. - Shows how Jev helps agentic memory: safe vs risky actions, contradictory vs reinforcing memories, supported vs unsupported answers, and complete vs unfinished work. - Adds pricing, no-card trial details, comparison link, and Pro/Team signup links. Tests: documentation contracts, Pro CTA, plugin distribution, and skill package pass; ruff clean.
Bring the branch current with main.
Resolve the evidence conflicts to the newer receipt-diagnostics artifact published on main; the http watchdog deadline fix and its memory-timeout evidence remain the branch contribution.
Codex Review Summary: ❌ FailedThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
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.
Refreshed the public offline benchmark-evidence artifact and re-pinned every published surface to the new artifact SHA d13497f0a36fe53ca7871597d8acfbc878348a1f6985ebae4714b4e0bee4985e after source drift made the full pytest suite red. Full suite now green (exit 0).