Skip to content

fix(http): treat watchdog interruption as deadline timeout - #319

Open
Coding-Dev-Tools wants to merge 11 commits into
mainfrom
feat/file-guard-protection
Open

Coding-Dev-Tools wants to merge 11 commits into
mainfrom
feat/file-guard-protection

Conversation

@Coding-Dev-Tools

Copy link
Copy Markdown
Owner

Summary

Re-submits the remaining unique work from closed #309. The file-guard, desktop-memory, stdio-bridge, and history-integrity changes are already in main; this PR carries the HTTP deadline fix and its evidence rebind:

  • Treat a watchdog shutdown interruption during chunk read as a deadline timeout instead of letting socket/transport errors bubble up.
  • Rebind the offline benchmark artifact and rendered provenance to the merged tree.

Verification

  • pytest tests/test_cloud_session_deadline.py tests/test_jev_deadlines.py -q — passed.
  • python scripts/check_commercial_manifest.py — OK.
  • Branch is reconciled with current main.

Agent: commandcode

Coding-Dev-Tools and others added 11 commits October 14, 2026 07:33
…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
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.

Co-authored-by: coding-dev-tools <coding-dev-tools@users.noreply.github.com>
Co-authored-by: CommandCodeBot <noreply@commandcode.ai>
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.

Co-authored-by: CommandCodeBot <noreply@commandcode.ai>
@chatgpt-codex-connector

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ⚠️ Failed 2026-11-04T06:02:18.228145Z
We couldn’t complete this review. Comment @codex review to try again.
5e38189 PR opened
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@chatgpt-codex-connector

Copy link
Copy Markdown

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.

@Coding-Dev-Tools
Coding-Dev-Tools force-pushed the main branch 2 times, most recently from 3d330e8 to 8ef46b6 Compare November 4, 2026 06:12

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant