chore: release v0.1.4 with comprehensive test coverage and enhanced error messages (#19)

* chore: release v0.1.4 with comprehensive test coverage and enhanced error messages

* Added 26 new tests, increasing overall code coverage from ~78% to ~86%, with a focus on cache cleanup, parameter validation, and error handling.
* Improved error messages across all MCP tools to provide actionable guidance and context for users.
* Fixed version inconsistencies in documentation and codebase to ensure alignment with package.json version 0.1.4.
* Introduced a Code of Conduct to promote a respectful and inclusive community environment.
* Added a roadmap for future enhancements and features to guide project development.

Author: AmiteK23

CHANGELOG.md

@@ -5,6 +5,58 @@ All notable changes to this project will be documented in this file.
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [0.1.4] - 2026-01-14
+
+### Added
+
+- **Comprehensive Test Coverage** - Added 26 new tests significantly improving code coverage
+  - **Coverage Improvements**: Overall coverage increased from ~78% to ~86% (statements, branches, lines)
+  - **Cache Cleanup Tests** (10 tests) - Added tests for cache corruption detection, stale path detection, and cleanup logic
+    - Tests for corrupted cache detection (invalid JSON in `context_main.json`)
+    - Tests for stale cache detection (mismatched project paths in config files)
+    - Tests for valid cache preservation and explicit cleanup
+  - **Parameter Validation Tests** (7 tests) - Added comprehensive validation tests for `depth` parameter
+    - Invalid depth values (non-integer, zero, negative)
+    - Valid depth values (1, 3, default 2)
+    - String-to-number conversion handling
+  - **Error Code Preservation Tests** (4 tests) - Added tests ensuring error information is properly preserved
+    - Error code preservation from exec errors
+    - stdout/stderr preservation in error objects
+    - ENOENT error handling for missing files
+  - **Server Error Handling Tests** (4 tests) - Added tests for server-level error handling
+    - Tool execution error wrapping in MCP format
+    - Non-Error exception handling
+    - Graceful error handling for all tools
+  - **Documentation Error Handling Tests** (2 tests) - Added tests for error message structure and consistency
+  - **File Coverage Improvements**:
+    - `compare-modes.ts`: 60% → ~95% statements (+35%)
+    - `refresh-snapshot.ts`: ~67% → ~96% statements (+29%)
+  - Total test count: 163 → 189 tests (+26 tests)
+  - All tests passing with improved confidence in error handling and edge cases
+
+- **Enhanced Error Messages** - Improved error messages throughout all MCP tools to be more actionable and helpful
+  - All error messages now include context about what was attempted and why it failed
+  - Added suggestions for common errors (e.g., "Run logicstamp_refresh_snapshot first" when snapshot is missing)
+  - Included relevant file paths and next steps in error messages
+  - Error messages now guide users toward solutions instead of just reporting failures
+  - Enhanced messages in: `logicstamp_refresh_snapshot`, `logicstamp_list_bundles`, `logicstamp_read_bundle`, `logicstamp_compare_snapshot`, `logicstamp_compare_modes`, `logicstamp_read_logicstamp_docs`
+  - Example improvement: "context_main.json not found" → "context_main.json not found in /path/to/project. This file is required for comparison but hasn't been generated yet. Options: (1) Run logicstamp_refresh_snapshot first to generate context files, (2) Use forceRegenerate: true in this call to regenerate automatically before comparing, (3) Run 'stamp context' manually from the project directory."
+
+- **Code of Conduct** - Added Contributor Covenant Code of Conduct to establish community standards and promote a respectful, inclusive environment
+  - Available at [`CODE_OF_CONDUCT.md`](CODE_OF_CONDUCT.md)
+
+- **Roadmap** - Added roadmap document outlining planned enhancements and future features to guide project development
+  - Available at [`ROADMAP.md`](ROADMAP.md)
+
+### Fixed
+
+- **Version Consistency** - Fixed version mismatches across codebase to ensure all version references match `package.json`
+  - **README.md** - Updated version badge from `0.1.2` to `0.1.4`
+  - **src/mcp/server.ts** - Updated server version from `0.1.2` to `0.1.4` (was incorrectly `0.1.2` for version `0.1.3`)
+  - **docs/mcp_integration.md** - Updated example config version from `0.1.2` to `0.1.4`
+  - All version references now consistently match `package.json` version `0.1.4`
+  - Prevents confusion when users check version information across different sources
+
 ## [0.1.3] - 2026-01-13
 
 ### Changed
@@ -170,6 +222,8 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 - Requires `logicstamp-context` CLI to be installed globally (`npm install -g logicstamp-context`)
 - All tools are read-only - they analyze but never modify your codebase
 
+[0.1.4]: https://github.com/LogicStamp/logicstamp-mcp/releases/tag/v0.1.4
+
 [0.1.3]: https://github.com/LogicStamp/logicstamp-mcp/releases/tag/v0.1.3
 
 [0.1.2]: https://github.com/LogicStamp/logicstamp-mcp/releases/tag/v0.1.2

CODE_OF_CONDUCT.md

@@ -0,0 +1,45 @@
+# Code of Conduct
+
+## Our Pledge
+
+We pledge to make participation in our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, caste, color, religion, or sexual identity and orientation.
+
+We commit to acting in ways that contribute to an open, welcoming, diverse, inclusive, and healthy community.
+
+## Scope
+
+This Code of Conduct applies to all official community spaces (GitHub issues, pull requests, discussions) and when officially representing the community in public spaces.
+
+## Enforcement
+
+The project maintainer(s) are responsible for enforcing these standards, and additional moderators may be designated as the project grows.
+They may remove, edit, or reject contributions that violate this Code of Conduct and will communicate moderation decisions when appropriate.
+
+**Reporting:** Report violations to logicstamp.dev@gmail.com. All complaints will be reviewed promptly and fairly. Reporter privacy will be respected.
+
+**Enforcement Guidelines:**
+
+1. **Correction** - Inappropriate language or unprofessional behavior
+   - Private written warning with explanation; public apology may be requested
+
+2. **Warning** - Single incident or series of violations
+   - Warning with consequences; no interaction with involved parties for a specified period; violation may lead to ban
+
+3. **Temporary Ban** - Serious or sustained violations
+   - Temporary ban from all community interaction; no contact with involved parties; violation may lead to permanent ban
+
+4. **Permanent Ban** - Pattern of violations, harassment, or aggression toward individuals or groups
+   - Permanent ban from all community interaction
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 2.1, available at [https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1].
+
+Enforcement guidelines were inspired by [Mozilla's code of conduct enforcement ladder][Mozilla CoC].
+
+For answers to common questions, see [https://www.contributor-covenant.org/faq][FAQ].
+
+[homepage]: https://www.contributor-covenant.org
+[v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html
+[Mozilla CoC]: https://github.com/mozilla/diversity
+[FAQ]: https://www.contributor-covenant.org/faq

CONTRIBUTING.md

@@ -2,6 +2,10 @@
 
 Thank you for your interest in contributing! This guide will help you get started.
 
+## Code of Conduct
+
+This project adheres to a [Code of Conduct](CODE_OF_CONDUCT.md). By participating, you are expected to uphold this code. Please report unacceptable behavior to logicstamp.dev@gmail.com.
+
 ## Development Setup
 
 ### Prerequisites
@@ -199,7 +203,7 @@ If you already ran `npm link` during installation (see [Installation](#installat
 2. **Verify it's linked:**
    ```bash
    npm list -g logicstamp-mcp
-   # Should show: logicstamp-mcp@0.1.2 -> /path/to/logicstamp-mcp
+   # Should show: logicstamp-mcp@0.1.4 -> /path/to/logicstamp-mcp
    ```
 
 3. **Your MCP clients will automatically use the local version** if they're configured with `npx logicstamp-mcp` (which is the standard configuration). No additional configuration needed!
@@ -415,9 +419,6 @@ When adding features, update:
 - Configuration file support
 - Multiple project support
 
-## Code of Conduct
-
-Be respectful, inclusive, and constructive in all interactions.
 
 ## License
 

README.md

@@ -6,7 +6,7 @@
 
   <br/>
 
-  ![Version](https://img.shields.io/badge/version-0.1.2-blue.svg) ![Beta](https://img.shields.io/badge/status-beta-orange.svg) ![License](https://img.shields.io/badge/license-MIT-green.svg) ![Node](https://img.shields.io/badge/node-%3E%3D18.18.0-brightgreen.svg) [![CI](https://github.com/LogicStamp/logicstamp-mcp/workflows/CI/badge.svg)](https://github.com/LogicStamp/logicstamp-mcp/actions)
+  ![Version](https://img.shields.io/badge/version-0.1.4-blue.svg) ![Beta](https://img.shields.io/badge/status-beta-orange.svg) ![License](https://img.shields.io/badge/license-MIT-green.svg) ![Node](https://img.shields.io/badge/node-%3E%3D18.18.0-brightgreen.svg) [![CI](https://github.com/LogicStamp/logicstamp-mcp/workflows/CI/badge.svg)](https://github.com/LogicStamp/logicstamp-mcp/actions)
 
   <br/>
 
@@ -300,10 +300,18 @@ These assets may not be used for third-party branding, logos, or commercial iden
 
 Contributions welcome! Please see [CONTRIBUTING.md](CONTRIBUTING.md) for guidelines.
 
+## Community
+
+This project follows a [Code of Conduct](CODE_OF_CONDUCT.md). By participating, you agree to uphold it.
+
 ## Changelog
 
 See [CHANGELOG.md](CHANGELOG.md) for a detailed list of changes and version history.
 
+## Roadmap
+
+See [ROADMAP.md](ROADMAP.md) for planned enhancements and future features.
+
 ## Links
 
 - [LogicStamp](https://logicstamp.dev) - Official website and documentation