# DGR-004 verification blocker — 2026-07-14

## Verified state

The pre-existing DGR-004 boundary is present and its lock data is internally
consistent:

- `scripts/llama_cpp_dependency.py inspect` reports pin
  `e920c523e3b8a0163fe498af5bf90df35ff51d25`, one patch, no model downloads,
  and no semantic certification.
- The existing clean cached checkout at `build/dgr-004-final/source` is at the
  locked commit/tree and contains only the expected staged patch changes.
- The existing `llama-gguf-hash --help` smoke binary runs successfully.
- `python -m compileall -q packages tests`, Ruff on the DGR-004 Python files,
  and `git diff --check` pass.

## Blocker

The verification environment no longer contains the `.venv` recorded in
`commands.txt`, nor a `cmake` executable on `PATH`. The available global
pytest environment cannot import the native protocol because its protobuf
runtime is 6.33.6 while the checked-in generated code requires 7.35.0. This
causes both `tests/test_llama_cpp_dependency.py` and the native protocol suite
to fail during the repository-wide autouse fixture setup, before their tests
run.

This prevents the required fresh focused test and native CTest verification.
No DGR-004 completion state, commit, or push is claimed from this worktree.

## Continuation

1. Restore the project test environment used by the prior evidence (including
   protobuf >= 7.35.0 and CMake), without changing DGR-004 source files.
2. Run the exact focused test command from `commands.txt` and the clean
   `reproduce` command using the local llama.cpp object cache.
3. Re-run compileall, Ruff, diff check, and the deterministic full suite.
4. Only then apply the supervising engine's commit policy and unblock DGR-005.

## Dependency graph

`DGR-004 verification -> DGR-005 range-aware GGUF ownership -> DGR-003 live
ShardIdentity emission`. DGR-005 and DGR-003-emission were not modified.