* Refactor CLAUDE.md and related files for December 2025 updates - Updated CLAUDE.md in src/services/worker with new entries for December 2025, including changes to Search.ts, GeminiAgent.ts, SDKAgent.ts, and SessionManager.ts. - Revised CLAUDE.md in src/shared to reflect updates and new entries for December 2025, including paths.ts and worker-utils.ts. - Modified hook-constants.ts to clarify exit codes and their behaviors. - Added comprehensive hooks reference documentation for Claude Code, detailing usage, events, and examples. - Created initial CLAUDE.md files in various directories to track recent activity. * fix: Merge user-message-hook output into context-hook hookSpecificOutput - Add footer message to additionalContext in context-hook.ts - Remove user-message-hook from SessionStart hooks array - Fixes issue where stderr+exit(1) approach was silently discarded Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com> * Update logs and documentation for recent plugin and worker service changes - Added detailed logs for worker service activities from Dec 10, 2025 to Jan 7, 2026, including initialization patterns, cleanup confirmations, and diagnostic logging. - Updated plugin documentation with recent activities, including plugin synchronization and configuration changes from Dec 3, 2025 to Jan 7, 2026. - Enhanced the context hook and worker service logs to reflect improvements and fixes in the plugin architecture. - Documented the migration and verification processes for the Claude memory system and its integration with the marketplace. * Refactor hooks architecture and remove deprecated user-message-hook - Updated hook configurations in CLAUDE.md and hooks.json to reflect changes in session start behavior. - Removed user-message-hook functionality as it is no longer utilized in Claude Code 2.1.0; context is now injected silently. - Enhanced context-hook to handle session context injection without user-visible messages. - Cleaned up documentation across multiple files to align with the new hook structure and removed references to obsolete hooks. - Adjusted timing and command execution for hooks to improve performance and reliability. * fix: Address PR #610 review issues - Replace USER_MESSAGE_ONLY test with BLOCKING_ERROR test in hook-constants.test.ts - Standardize Claude Code 2.1.0 note wording across all three documentation files - Exclude deprecated user-message-hook.ts from logger-usage-standards test Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com> * fix: Remove hardcoded fake token counts from context injection Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com> * Address PR #610 review issues by fixing test files, standardizing documentation notes, and verifying code quality improvements. * fix: Add path validation to CLAUDE.md distribution to prevent invalid directory creation - Add isValidPathForClaudeMd() function to reject invalid paths: - Tilde paths (~) that Node.js doesn't expand - URLs (http://, https://) - Paths with spaces (likely command text or PR references) - Paths with # (GitHub issue/PR references) - Relative paths that escape project boundary - Integrate validation in updateFolderClaudeMdFiles loop - Add 6 unit tests for path validation - Update .gitignore to prevent accidental commit of malformed directories - Clean up existing invalid directories (~/, PR #610..., git diff..., https:) Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com> * fix: Implement path validation in CLAUDE.md generation to prevent invalid directory creation - Added `isValidPathForClaudeMd()` function to validate file paths in `src/utils/claude-md-utils.ts`. - Integrated path validation in `updateFolderClaudeMdFiles` to skip invalid paths. - Added 6 new unit tests in `tests/utils/claude-md-utils.test.ts` to cover various rejection cases. - Updated `.gitignore` to prevent tracking of invalid directories. - Cleaned up existing invalid directories in the repository. * feat: Promote critical WARN logs to ERROR level across codebase Comprehensive log-level audit promoting 38+ WARN messages to ERROR for improved debugging and incident response: - Parser: observation type errors, data contamination - SDK/Agents: empty init responses (Gemini, OpenRouter) - Worker/Queue: session recovery, auto-recovery failures - Chroma: sync failures, search failures (now treated as critical) - SQLite: search failures (primary data store) - Session/Generator: failures, missing context - Infrastructure: shutdown, process management failures - File Operations: CLAUDE.md updates, config reads - Branch Management: recovery checkout failures Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com> * fix: Address PR #614 review issues - Remove incorrectly tracked tilde-prefixed files from git - Fix absolute path validation to check projectRoot boundaries - Add test coverage for absolute path validation edge cases Closes review issues: - Issue 1: ~/ prefixed files removed from tracking - Issue 3: Absolute paths now validated against projectRoot - Issue 4: Added 3 new test cases for absolute path scenarios Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com> * build assets and context --------- Co-authored-by: Claude Opus 4.5 <noreply@anthropic.com>
4.9 KiB
Plan: Address PR #610 Review Issues
Overview
This plan addresses the issues identified in the PR review for PR #610 "fix: Update hooks for Claude Code 2.1.0/1 - SessionStart no longer shows user messages".
Phase 0: Verification and Discovery
0.1 Verify Test Failure
- File:
tests/hook-constants.test.ts - Issue: Lines 61-63 test for
HOOK_EXIT_CODES.USER_MESSAGE_ONLYwhich was removed - Verification: Run
bun test tests/hook-constants.test.tsto confirm failure
0.2 Verify No Code References USER_MESSAGE_ONLY
- Finding: Grep found references only in:
tests/hook-constants.test.ts(test file - needs fix)src/services/CLAUDE.md(memory context - auto-generated, not code)plugin/scripts/CLAUDE.md(memory context - auto-generated, not code)
- Conclusion: Only the test file needs updating; CLAUDE.md files are memory records
0.3 Verify CLAUDE.md Files Are Legitimate
- Clarification: The PR reviewer mentioned "user-specific CLAUDE.md files starting with ~/"
- Finding: All CLAUDE.md files in the commit are within the repository (
docs/,src/,plugin/) - Conclusion: These are legitimate in-repo context files, not user-specific paths
Phase 1: Fix Test File (REQUIRED)
Task 1.1: Remove USER_MESSAGE_ONLY Test
File: tests/hook-constants.test.ts
Action: Delete lines 61-63 that test for the removed constant
// DELETE THESE LINES:
it('should define USER_MESSAGE_ONLY exit code', () => {
expect(HOOK_EXIT_CODES.USER_MESSAGE_ONLY).toBe(3);
});
Task 1.2: Add Test for BLOCKING_ERROR
File: tests/hook-constants.test.ts
Action: Add test for the new BLOCKING_ERROR constant (exit code 2) that replaced it
// ADD THIS TEST:
it('should define BLOCKING_ERROR exit code', () => {
expect(HOOK_EXIT_CODES.BLOCKING_ERROR).toBe(2);
});
Verification
- Run
bun test tests/hook-constants.test.ts - Expect: All tests pass
Phase 2: Documentation Consistency (NICE TO HAVE)
Issue
Three similar notes about Claude Code 2.1.0 have slightly different wording:
-
docs/public/architecture/hooks.mdx:254:"SessionStart hooks no longer display any user-visible messages. Context is still injected via
hookSpecificOutput.additionalContextbut users don't see startup output in the UI." -
docs/public/hooks-architecture.mdx:31:"SessionStart hooks no longer display any user-visible messages. Context is silently injected via
hookSpecificOutput.additionalContext." -
docs/public/hooks-architecture.mdx:441:"SessionStart hooks output is never displayed to users. Context is injected silently via
hookSpecificOutput.additionalContext."
Task 2.1: Standardize Note Wording
Action: Use consistent wording across all three locations
Standard text:
As of Claude Code 2.1.0 (ultrathink update), SessionStart hooks no longer display user-visible messages. Context is silently injected via `hookSpecificOutput.additionalContext`.
Files to Update
docs/public/architecture/hooks.mdx:253-255- Update Note blockdocs/public/hooks-architecture.mdx:30-32- Update Note blockdocs/public/hooks-architecture.mdx:440-442- Update Note block
Verification
- Grep for the standard text in all three files
- Visual review of documentation
Phase 3: Code Quality Improvements (OPTIONAL)
Issue 3.1: Hardcoded Promotional Message
File: src/hooks/context-hook.ts:66-68
Current code:
const enhancedContext = `${text}
Access 300k tokens of past research & decisions for just 19,008t. Use MCP search tools to access memories by ID.`;
Options
- Leave as-is: The token count is a rough estimate and doesn't need to be exact
- Make configurable: Add to settings (over-engineering for this use case)
- Remove hardcoded numbers: Use relative language instead
Recommendation
Leave as-is for now. The token counts are marketing copy, not critical functionality. Creating a PR just for this adds unnecessary complexity.
Phase 4: Final Verification
4.1 Run Full Test Suite
bun test
4.2 Build Verification
npm run build
4.3 Grep Verification
grep -r "USER_MESSAGE_ONLY" src/ --include="*.ts" --include="*.js"
Expected: No results (CLAUDE.md files excluded as they're memory records)
Summary
| Phase | Priority | Effort | Description |
|---|---|---|---|
| 1 | REQUIRED | 5 min | Fix test file - remove USER_MESSAGE_ONLY test, add BLOCKING_ERROR test |
| 2 | Nice to have | 10 min | Standardize documentation note wording |
| 3 | Skip | - | Hardcoded token counts are fine as-is |
| 4 | REQUIRED | 5 min | Run tests and build to verify |
Expected Outcome
- All tests pass
- Build succeeds
- No code references to removed USER_MESSAGE_ONLY constant
- Documentation uses consistent wording (if Phase 2 is done)