Repository navigation
feat: host file protection, stdio bridge, and history integrity (1.7.12 candidate) - #289
Coding-Dev-Tools wants to merge 4 commits into
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 Co-authored-by: CommandCodeBot <noreply@commandcode.ai>
- 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 Co-authored-by: CommandCodeBot <noreply@commandcode.ai>
- 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 Co-authored-by: CommandCodeBot <noreply@commandcode.ai>
Codex Review SummaryThis 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. |
|
Closing as stale. This branch was cut before #270 and re-imported a local snapshot in c828bbc, so it conflicts with main across 75 files while reverting newer work (Spec Studio, newer Ledger, release evidence). Its headline file-protection engine already shipped on main via #270, and main's copies are newer and larger. Its only unique remaining pieces were salvaged into #297: the desktop/MCP concurrency regressions, the Windows RAM integrity probe, and the local pre-flight script (with the Fast/full branch bug fixed). Ageing static//classic_assets/ trees and the graph compatibility shim were deliberately not restored. If there is intent here that #297 does not capture, reopen with a rebase onto current main so we can review it as a real diff. |
Summary
Brings the local
feat/file-guard-protectionline up to a 1.7.12 launch candidate:PreToolUseguard hook (fail-closed).Verification
ruff check .— all checks passedpyright(repo config, Python 3.9 target) — 0 errors, 0 warningspython -m build— sdist + wheel built;twine checkPASSED for bothengraphis 1.7.12Merge note
The branch is based on
619f4986;mainhas moved 8 commits ahead (1.7.10/1.7.11 release content), so GitHub reports merge conflicts in overlapping release files. Resolving them is an owner decision: prefermain's 1.7.10/1.7.11 content and re-apply this branch's new surface (bridge, file guard, closure/lineage work, tests, 1.7.12 bump).Before release
scripts/check_release_readiness.pyneeds the private candidate ledger; final release authority stays outside it.release.ymlrequires the tag commit onmainwith tag ==pyprojectversion.