### expert_build/prompts.py
VERDICT: PASS
CORRECTNESS: VALID
SPEC_COMPLIANCE: N/A
ISSUE_COMPLIANCE: N/A
BELIEF_COMPLIANCE: CONSISTENT
TEST_COVERAGE: UNTESTED
INTEGRATION: WIRED
REASONING: The addition of `SUMMARIZE_CODE` provides a well-structured template for source code analysis. It covers essential sections like Title, Usage Patterns, API/Configuration, Key Behaviors, and Relationships, which are highly relevant for building expert knowledge from codebases. It follows the same structural pattern as the existing `SUMMARIZE` prompt.
---

### expert_build/summarize.py
VERDICT: CONCERN
CORRECTNESS: QUESTIONABLE
SPEC_COMPLIANCE: N/A
ISSUE_COMPLIANCE: N/A
BELIEF_COMPLIANCE: N/A
TEST_COVERAGE: UNTESTED
INTEGRATION: WIRED
REASONING: 
1. **Unreachable Code**: The truncation logic at line 76 includes a check for `source_path.suffix == ".pdf"`. However, the glob pattern on lines 27-30 only includes `*.md` and `*.py`. Thus, this warning is currently unreachable.
2. **PDF Handling Logic Error**: Even if `.pdf` files were included in the glob, the `source_path.read_text()` call on line 44 would likely fail with a `UnicodeDecodeError` or read corrupted data, as PDFs are binary. Summarization of PDFs should likely be handled by a specialized tool (like the `chunk-pdf` command mentioned in the warning) rather than `read_text()`.
3. **Implicit Encoding**: `read_text()` is called without an explicit encoding. It is best practice to use `encoding="utf-8"` to ensure consistent behavior across different environments.
4. **Title Extraction**: For non-code documents using the `SUMMARIZE` template, the first header is almost always "Overview". The title extraction logic at line 84 will therefore name most entries "Overview", which leads to poor discoverability. `SUMMARIZE_CODE` correctly addresses this by requesting a descriptive title, but the generic template could be improved.
5. **Test Coverage**: No automated tests were provided or found for the `summarize` command or the new template-switching logic.
---

### SELF_REVIEW
LIMITATIONS: I was unable to run the `entry` CLI to verify its behavior or check for the existence of tests that might be located outside standard paths (though none were found in the root or `expert_build`). I also lack the full context of how `SUMMARIZE` is currently performing in the wild regarding the "Overview" title issue.
---

### FEATURE_REQUESTS
- Include the `run_shell_command` tool in the reviewer's toolset to allow for verification of CLI integrations and environment state.
- Automatically include existing test files in the context when they relate to the modified source files.
---
