@schilling.mark.a/atdd-guardian 1.0.0

package/CHANGELOG.md

@@ -0,0 +1,37 @@
+# Changelog
+
+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).
+
+## [1.0.0] - 2026-02-16
+
+### Added
+- Initial release of ATDD Guardian MCP Server
+- 14 MCP tools for ATDD workflow enforcement
+- Context tools: `start_feature`, `advance_phase`, `update_criterion`, `get_context`
+- Enforcement tools: `start_unit_cycle`, `advance_unit_cycle`, `run_tests`, `get_tdd_status`
+- Review tools: `review_code`, `review_file`
+- Rule tools: `list_rules`, `explain_rule`, `add_rule`
+- Feedback tools: `record_pr_feedback`
+- Phase gate enforcement for TDD discipline
+- Nested unit TDD cycle tracking
+- Team standards rule engine with customizable rules
+- PDCA cycle integration for continuous improvement
+- AC coverage validation
+- File completeness checking
+- Architecture decision compliance
+- Definition of Done validation
+- Test framework integration (Playwright, Jest, Vitest)
+- Persistent session state management
+- Markdown and JSON output formatting
+- Comprehensive README with examples
+
+### Documentation
+- Full README.md with architecture, workflow, and examples
+- MIT License
+- Contributing guidelines
+- Package configuration for npm distribution
+
+[1.0.0]: https://github.com/MarkSchilling/atdd-guardian/releases/tag/v1.0.0

package/CONTRIBUTING.md

@@ -0,0 +1,154 @@
+# Contributing to ATDD Guardian MCP Server
+
+Thank you for your interest in contributing! This document provides guidelines for contributing to the ATDD Guardian MCP Server.
+
+## Getting Started
+
+1. **Fork the repository** on GitHub
+2. **Clone your fork** locally:
+   ```bash
+   git clone https://github.com/YOUR-USERNAME/atdd-guardian.git
+   cd atdd-guardian
+   ```
+3. **Install dependencies**:
+   ```bash
+   npm install
+   ```
+4. **Build the project**:
+   ```bash
+   npm run build
+   ```
+
+## Development Workflow
+
+1. **Create a feature branch**:
+   ```bash
+   git checkout -b feature/your-feature-name
+   ```
+
+2. **Make your changes** following the code style
+   - Use TypeScript
+   - Follow existing code patterns
+   - Add JSDoc comments for public APIs
+
+3. **Build and test**:
+   ```bash
+   npm run build
+   npm start  # Test the server manually
+   ```
+
+4. **Commit your changes**:
+   ```bash
+   git add .
+   git commit -m "Description of your changes"
+   ```
+
+5. **Push to your fork**:
+   ```bash
+   git push origin feature/your-feature-name
+   ```
+
+6. **Open a Pull Request** on GitHub
+
+## Code Style
+
+- Use TypeScript for all code
+- Follow existing naming conventions
+- Use meaningful variable and function names
+- Add comments for complex logic
+- Keep functions focused and small
+
+## Adding New Rules
+
+To add a new team standard rule:
+
+1. Edit `src/rules/team-standards.json`
+2. Follow the existing rule structure:
+   ```json
+   {
+     "id": "unique-id",
+     "name": "Descriptive rule name",
+     "severity": "error" | "warning" | "info",
+     "pattern": "regex pattern",
+     "appliesTo": ["file globs"],
+     "applicablePhases": ["phases"],
+     "explanation": "Why this rule exists",
+     "fix": "How to fix violations",
+     "goodExample": "Code that follows the rule",
+     "badExample": "Code that violates the rule"
+   }
+   ```
+
+## Adding New Tools
+
+To add a new MCP tool:
+
+1. Define the tool schema in `src/schemas/tool-schemas.ts`
+2. Implement the tool handler in `src/tools/review-tools.ts`
+3. Update the README.md with tool documentation
+4. Test the tool manually with a real project
+
+## Project Structure
+
+```
+atdd-guardian-mcp-server/
+├── src/
+│   ├── index.ts              # MCP server entry point
+│   ├── types.ts              # Type definitions
+│   ├── constants.ts          # Shared constants
+│   ├── tools/                # MCP tool implementations
+│   ├── services/             # Core business logic
+│   ├── schemas/              # Zod validation schemas
+│   └── rules/                # Team standards rules
+├── package.json
+├── tsconfig.json
+└── README.md
+```
+
+## Testing
+
+Currently, testing is manual:
+
+1. Build the server: `npm run build`
+2. Configure it in your VS Code MCP settings
+3. Test with a real project that has the `.atdd-guardian/` directory
+
+We welcome contributions to add automated testing!
+
+## Documentation
+
+When adding features:
+
+- Update the README.md with new functionality
+- Add JSDoc comments to new functions
+- Update the tool documentation table if adding tools
+- Include examples in the README
+
+## Reporting Issues
+
+When reporting issues:
+
+1. Check existing issues first
+2. Provide a clear description
+3. Include steps to reproduce
+4. Share relevant configuration files
+5. Include error messages and logs
+
+## PDCA Cycle
+
+This project follows the PDCA (Plan-Do-Check-Act) cycle:
+
+- **Plan**: Define rules in team-standards.json
+- **Do**: Write code and run review_code
+- **Check**: Compare findings to actual PR feedback
+- **Act**: Add new rules based on feedback
+
+When contributing rules based on PR feedback, document the issue that led to the rule.
+
+## License
+
+By contributing, you agree that your contributions will be licensed under the MIT License.
+
+## Questions?
+
+Open an issue on GitHub for questions or clarifications.

package/DISTRIBUTION.md

@@ -0,0 +1,366 @@
+# Distribution Guide
+
+This guide explains how to share and distribute the ATDD Guardian MCP Server with others.
+
+## Table of Contents
+
+1. [Distribution Methods](#distribution-methods)
+2. [Publishing to npm](#publishing-to-npm)
+3. [Sharing via GitHub](#sharing-via-github)
+4. [Direct Distribution](#direct-distribution)
+5. [Installation Instructions for Users](#installation-instructions-for-users)
+6. [Versioning Strategy](#versioning-strategy)
+
+## Distribution Methods
+
+### 1. NPM Package (Recommended for Public Use)
+
+**Advantages:**
+- Easy installation with `npm install`
+- Automatic dependency management
+- Version control and updates
+- Discoverable in npm registry
+- Global installation option
+
+**When to use:**
+- Sharing with the broader community
+- Making the server easily accessible
+- Providing automatic updates
+
+### 2. GitHub Repository
+
+**Advantages:**
+- Open source collaboration
+- Issue tracking and discussions
+- Version control with git
+- Easy contribution workflow
+- Free hosting
+
+**When to use:**
+- Open source projects
+- Development and collaboration
+- Users who want latest features
+
+### 3. Direct Distribution (Tarball)
+
+**Advantages:**
+- No external dependencies (npm registry)
+- Works in air-gapped environments
+- Control over distribution
+- Simple file transfer
+
+**When to use:**
+- Internal/private distribution
+- Corporate environments without internet access
+- Quick sharing with specific users
+
+## Publishing to npm
+
+### Prerequisites
+
+1. Create an npm account at [npmjs.com](https://www.npmjs.com)
+2. Login via command line:
+   ```bash
+   npm login
+   ```
+
+### Publishing Process
+
+1. **Ensure package.json is correct:**
+   ```bash
+   # Check the package name is available
+   npm search atdd-guardian-mcp-server
+   
+   # View what will be published
+   npm pack --dry-run
+   ```
+
+2. **Build the project:**
+   ```bash
+   npm run build
+   ```
+
+3. **Test the package locally:**
+   ```bash
+   # Create a tarball
+   npm pack
+   
+   # Test install in another directory
+   cd /tmp/test-project
+   npm install /path/to/atdd-guardian-mcp-server-1.0.0.tgz
+   ```
+
+4. **Publish to npm:**
+   ```bash
+   # First release
+   npm publish
+   
+   # Or for scoped package (recommended for personal/org packages)
+   npm publish --access public
+   ```
+
+5. **Verify publication:**
+   ```bash
+   npm info atdd-guardian-mcp-server
+   ```
+
+### Updating Published Package
+
+1. **Update version in package.json:**
+   ```bash
+   # Patch version (bug fixes): 1.0.0 -> 1.0.1
+   npm version patch
+   
+   # Minor version (new features): 1.0.0 -> 1.1.0
+   npm version minor
+   
+   # Major version (breaking changes): 1.0.0 -> 2.0.0
+   npm version major
+   ```
+
+2. **Update CHANGELOG.md** with changes
+
+3. **Publish:**
+   ```bash
+   npm publish
+   ```
+
+### Unpublishing (if needed)
+
+```bash
+# Unpublish a specific version (within 72 hours)
+npm unpublish atdd-guardian-mcp-server@1.0.0
+
+# Deprecate a version (preferred over unpublish)
+npm deprecate atdd-guardian-mcp-server@1.0.0 "Use version 1.0.1 instead"
+```
+
+## Sharing via GitHub
+
+### Setting Up Repository
+
+1. **Push to GitHub** (already done):
+   ```bash
+   git push origin main
+   ```
+
+2. **Create releases:**
+   ```bash
+   # Tag the release
+   git tag -a v1.0.0 -m "Release version 1.0.0"
+   git push origin v1.0.0
+   ```
+
+3. **Create GitHub Release:**
+   - Go to https://github.com/MarkSchilling/atdd-guardian/releases
+   - Click "Create a new release"
+   - Select the tag (v1.0.0)
+   - Add release notes from CHANGELOG.md
+   - Attach the tarball (optional): `atdd-guardian-mcp-server-1.0.0.tgz`
+   - Publish release
+
+### Installation from GitHub
+
+Users can install with:
+
+```bash
+# Clone and build
+git clone https://github.com/MarkSchilling/atdd-guardian.git
+cd atdd-guardian
+npm install
+npm run build
+
+# Or install directly from GitHub (requires public repo)
+npm install github:MarkSchilling/atdd-guardian
+```
+
+## Direct Distribution
+
+### Creating a Distribution Package
+
+1. **Build the project:**
+   ```bash
+   npm run build
+   ```
+
+2. **Create tarball:**
+   ```bash
+   npm pack
+   # Creates: atdd-guardian-mcp-server-1.0.0.tgz
+   ```
+
+3. **Share the tarball:**
+   - Email attachment
+   - Internal file server
+   - Shared drive
+   - Cloud storage
+
+### Installation from Tarball
+
+Users install with:
+
+```bash
+npm install atdd-guardian-mcp-server-1.0.0.tgz
+```
+
+Or globally:
+
+```bash
+npm install -g atdd-guardian-mcp-server-1.0.0.tgz
+```
+
+## Installation Instructions for Users
+
+### From npm (after publishing)
+
+```bash
+# Global installation
+npm install -g atdd-guardian-mcp-server
+
+# Local installation
+npm install --save-dev atdd-guardian-mcp-server
+```
+
+**VS Code Configuration (global install):**
+```json
+{
+  "servers": {
+    "atdd-guardian": {
+      "type": "stdio",
+      "command": "atdd-guardian-mcp"
+    }
+  }
+}
+```
+
+### From GitHub
+
+```bash
+git clone https://github.com/MarkSchilling/atdd-guardian.git
+cd atdd-guardian
+npm install
+npm run build
+```
+
+**VS Code Configuration:**
+```json
+{
+  "servers": {
+    "atdd-guardian": {
+      "type": "stdio",
+      "command": "node",
+      "args": ["/absolute/path/to/atdd-guardian/dist/index.js"]
+    }
+  }
+}
+```
+
+### From Tarball
+
+```bash
+npm install /path/to/atdd-guardian-mcp-server-1.0.0.tgz
+```
+
+**VS Code Configuration:**
+```json
+{
+  "servers": {
+    "atdd-guardian": {
+      "type": "stdio",
+      "command": "node",
+      "args": ["./node_modules/atdd-guardian-mcp-server/dist/index.js"]
+    }
+  }
+}
+```
+
+## Versioning Strategy
+
+This project follows [Semantic Versioning](https://semver.org/):
+
+- **MAJOR** version (1.0.0 → 2.0.0): Incompatible API changes
+  - Breaking changes to tool schemas
+  - Removal of tools
+  - Changes to configuration file format
+  
+- **MINOR** version (1.0.0 → 1.1.0): New functionality, backwards compatible
+  - New MCP tools
+  - New team rules
+  - New configuration options (with defaults)
+  
+- **PATCH** version (1.0.0 → 1.0.1): Bug fixes, backwards compatible
+  - Bug fixes
+  - Documentation updates
+  - Minor rule improvements
+
+### Release Checklist
+
+Before each release:
+
+- [ ] Update version in `package.json`
+- [ ] Update `CHANGELOG.md` with changes
+- [ ] Run `npm run build` successfully
+- [ ] Test the build locally
+- [ ] Create git tag: `git tag -a v1.x.x -m "Release 1.x.x"`
+- [ ] Push tag: `git push origin v1.x.x`
+- [ ] Create GitHub Release with notes
+- [ ] Publish to npm: `npm publish`
+- [ ] Verify installation: `npm install -g atdd-guardian-mcp-server@latest`
+
+## Marketing and Community
+
+### Announce Your Release
+
+1. **GitHub:**
+   - Create a release with detailed notes
+   - Pin important issues or discussions
+
+2. **npm:**
+   - Ensure good README with examples
+   - Use relevant keywords in package.json
+   - Add badges (build status, version, downloads)
+
+3. **Social Media:**
+   - Dev.to article
+   - Twitter/X announcement
+   - Reddit (r/vscode, r/javascript)
+   - LinkedIn post
+
+4. **Documentation:**
+   - Create a website (GitHub Pages)
+   - Video tutorials
+   - Blog posts with examples
+
+### Community Building
+
+1. **Enable GitHub Discussions:**
+   - Q&A section
+   - Ideas and feature requests
+   - Show and tell
+
+2. **Documentation:**
+   - Keep README up to date
+   - Add more examples
+   - Create tutorials
+
+3. **Respond to Issues:**
+   - Be responsive to bug reports
+   - Welcome feature requests
+   - Help users with setup
+
+4. **Accept Contributions:**
+   - Review pull requests
+   - Provide feedback
+   - Merge and credit contributors
+
+## Support Resources
+
+- **Documentation:** [README.md](README.md)
+- **Quick Start:** [QUICKSTART.md](QUICKSTART.md)
+- **Contributing:** [CONTRIBUTING.md](CONTRIBUTING.md)
+- **Examples:** [examples/](examples/)
+- **Changelog:** [CHANGELOG.md](CHANGELOG.md)
+
+## License
+
+This project is licensed under the MIT License - see [LICENSE](LICENSE) for details.

package/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 Mark Schilling
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.