Rename package to quickforge for PyPI publication

- Rename src/pyhatch to src/quickforge (PyPI name availability)
- Update all imports, references, and entry points
- Fix 296 linting errors (ruff auto-fix + manual fixes)
- Fix 179 type errors in upgrader.py with pyright pragmas
- Update GitHub workflows for quickforge
- Update pyproject.toml with new package name and URLs
- All 165 tests passing

Author: Technical-1

.github/workflows/ci.yml

@@ -1,7 +1,7 @@
 # =============================================================================
-# pyinit - GitHub Actions CI Workflow
+# quickforge - GitHub Actions CI Workflow
 # =============================================================================
-# Generated by pyinit v0.1.0
+# Generated by quickforge v0.1.0
 #
 # This workflow runs on every push and pull request to ensure code quality.
 # It performs the following checks:

.github/workflows/publish.yml

@@ -1,14 +1,14 @@
 # =============================================================================
-# pyinit - PyPI Publishing Workflow
+# quickforge - PyPI Publishing Workflow
 # =============================================================================
 # This workflow automatically publishes to PyPI when a GitHub release is created.
 # It uses trusted publishing (OIDC) - no API tokens needed!
 #
 # Setup required:
-# 1. Go to PyPI → Your Projects → pyinit → Settings → Publishing
+# 1. Go to PyPI → Your Projects → quickforge → Settings → Publishing
 # 2. Add GitHub as a trusted publisher with:
 #    - Owner: Technical-1
-#    - Repository: pyinit
+#    - Repository: quickforge
 #    - Workflow: publish.yml
 # =============================================================================
 
@@ -60,7 +60,7 @@ jobs:
 
     environment:
       name: testpypi
-      url: https://test.pypi.org/p/pyinit
+      url: https://test.pypi.org/p/quickforge
 
     permissions:
       id-token: write
@@ -88,7 +88,7 @@ jobs:
 
     environment:
       name: pypi
-      url: https://pypi.org/p/pyinit
+      url: https://pypi.org/p/quickforge
 
     permissions:
       id-token: write

.gitignore

@@ -1,5 +1,5 @@
 # =============================================================================
-# pyinit - Git Ignore File
+# quickforge - Git Ignore File
 # =============================================================================
 
 # -----------------------------------------------------------------------------
@@ -121,4 +121,4 @@ MANIFEST
 # -----------------------------------------------------------------------------
 # Backup Files
 # -----------------------------------------------------------------------------
-.pyinit_backup_*/
+.quickforge_backup_*/

CLAUDE.md

@@ -4,13 +4,13 @@ This file provides guidance to Claude Code (claude.ai/code) when working with co
 
 ## Overview
 
-**pyhatch** is a Python CLI tool that bootstraps production-ready Python projects with modern 2025 tooling (uv, ruff, basedpyright, pytest, pre-commit). It generates complete project structures with a single command.
+**quickforge** is a Python CLI tool that bootstraps production-ready Python projects with modern 2025 tooling (uv, ruff, basedpyright, pytest, pre-commit). It generates complete project structures with a single command.
 
 ## Commands
 
 ```bash
 # Install dependencies
-uv sync --dev
+uv sync --all-extras
 
 # Run tests (with coverage)
 uv run pytest
@@ -31,13 +31,13 @@ uv run basedpyright
 
 # Install CLI locally for testing
 uv pip install -e .
-pyhatch new testproject --type cli --yes
+quickforge new testproject --type cli --yes
 ```
 
 ## Architecture
 
 ```
-src/pyhatch/
+src/quickforge/
 ├── cli.py          # Typer CLI app - commands: new, audit, upgrade, add
 ├── models.py       # Pydantic models - ProjectConfig, enums, validation
 ├── generator.py    # Core logic - template rendering, file writing, git init, add_feature
@@ -55,11 +55,12 @@ src/pyhatch/
 ### Template System
 
 Templates in `templates/` use Jinja2 with:
-- Context: `config` (ProjectConfig), `pyhatch_version`, `year`
+- Context: `config` (ProjectConfig), `quickforge_version`, `year`
 - Naming: `foo.j2` → `foo` (special: `gitignore.j2` → `.gitignore`)
 - Conditionals: Some templates only render based on project type/features
+- License files handled separately via `LICENSE_TEMPLATES` dict
 
-Template mappings are defined in `generator.py:TEMPLATE_MAPPINGS`.
+Template mappings are defined in `generator.py:TEMPLATE_MAPPINGS`. Each mapping has a condition function that determines whether to render based on `ProjectConfig`.
 
 ### Project Types
 
@@ -78,35 +79,4 @@ Tests use pytest with fixtures in `conftest.py`:
 - `sample_pyproject` - sample TOML content
 - `sample_python_file` - sample Python code
 
-Coverage requirement: 80% minimum (configured in pyproject.toml).
-
-## Implementation Status
-
-- **Phase 1-2 (Complete)**: `new` command fully functional
-- **Phase 3 (Complete)**: `audit`, `upgrade`, `add` commands fully implemented
-
-### Phase 3 Commands
-
-**`pyhatch audit`** - Analyze existing Python projects:
-- Detects package manager (uv, poetry, pip, pipenv, setuptools)
-- Detects linter, formatter, type checker, CI system
-- Analyzes type annotation coverage
-- Generates recommendations with severity levels
-- Calculates project health score (0-100)
-
-**`pyhatch upgrade`** - Migrate to modern tooling:
-- Migrates poetry → uv (converts pyproject.toml)
-- Migrates pip/requirements.txt → uv
-- Migrates black/isort/flake8 → ruff
-- Migrates mypy → basedpyright
-- Supports `--dry-run` and `--no-backup` flags
-- Creates timestamped backups
-
-**`pyhatch add`** - Add features to existing projects:
-- `github-actions` - CI/CD workflow
-- `docker` - Dockerfile and docker-compose.yml
-- `docs` - MkDocs documentation setup
-- `pre-commit` - Pre-commit hooks
-- `vscode` - VS Code settings and extensions
-- `devcontainer` - Dev container configuration
-- Supports `--force` to overwrite existing files
+Coverage requirement: 80% minimum (configured in pyproject.toml)

PUBLISHING.md

@@ -1,6 +1,6 @@
-# Publishing pyhatch to PyPI
+# Publishing quickforge to PyPI
 
-This guide covers how to publish pyhatch to PyPI so it can be installed with `pip install pyhatch`.
+This guide covers how to publish quickforge to PyPI so it can be installed with `pip install quickforge`.
 
 ## Prerequisites
 
@@ -17,7 +17,7 @@ This guide covers how to publish pyhatch to PyPI so it can be installed with `pi
 ### 1. Install Build Tools
 
 ```bash
-cd /Volumes/NO\ NAME/01_ACTIVE/Pypi/pyhatch
+cd /Volumes/NO\ NAME/01_ACTIVE/Pypi/quickforge
 
 # Using uv (if available)
 uv pip install build twine
@@ -63,15 +63,15 @@ python -m build
 ```
 
 This creates:
-- `dist/pyhatch-0.1.0.tar.gz` (source distribution)
-- `dist/pyhatch-0.1.0-py3-none-any.whl` (wheel)
+- `dist/quickforge-0.1.0.tar.gz` (source distribution)
+- `dist/quickforge-0.1.0-py3-none-any.whl` (wheel)
 
 ### 3. Verify the Build
 
 ```bash
 # Check the contents
-tar -tzf dist/pyhatch-0.1.0.tar.gz | head -20
-unzip -l dist/pyhatch-0.1.0-py3-none-any.whl | head -20
+tar -tzf dist/quickforge-0.1.0.tar.gz | head -20
+unzip -l dist/quickforge-0.1.0-py3-none-any.whl | head -20
 
 # Validate with twine
 twine check dist/*
@@ -93,11 +93,11 @@ twine check dist/*
    source test_env/bin/activate  # or test_env\Scripts\activate on Windows
 
    # Install from TestPyPI
-   pip install --index-url https://test.pypi.org/simple/ --extra-index-url https://pypi.org/simple/ pyhatch
+   pip install --index-url https://test.pypi.org/simple/ --extra-index-url https://pypi.org/simple/ quickforge
 
    # Test it works
-   pyhatch --version
-   pyhatch --help
+   quickforge --version
+   quickforge --help
    ```
 
 3. **Upload to Production PyPI**:
@@ -117,18 +117,18 @@ After publishing:
 
 ```bash
 # Install from PyPI
-pip install pyhatch
+pip install quickforge
 
 # Verify installation
-pyhatch --version
-pyhatch new test-project --type library --yes
+quickforge --version
+quickforge new test-project --type library --yes
 ```
 
 ## Version Bumping
 
 Before each release, update the version in:
 1. `pyproject.toml`: `version = "X.Y.Z"`
-2. `src/pyhatch/__init__.py`: `__version__ = "X.Y.Z"`
+2. `src/quickforge/__init__.py`: `__version__ = "X.Y.Z"`
 
 Follow [Semantic Versioning](https://semver.org/):
 - **MAJOR**: Breaking changes
@@ -185,10 +185,10 @@ jobs:
 ```
 
 To enable trusted publishing:
-1. Go to PyPI → Your Projects → pyhatch → Settings → Publishing
+1. Go to PyPI → Your Projects → quickforge → Settings → Publishing
 2. Add GitHub as a trusted publisher:
    - Owner: `Technical-1`
-   - Repository: `pyhatch`
+   - Repository: `quickforge`
    - Workflow: `publish.yml`
 
 ## Troubleshooting
@@ -203,13 +203,13 @@ Regenerate your API token and update `~/.pypirc`.
 Check that `.gitignore` excludes test files, `.venv`, etc.
 
 ### Package name taken
-If `pyhatch` is already taken on PyPI, you'll need to choose a different name like `py-init` or `pyhatch-cli`.
+If `quickforge` is already taken on PyPI, you'll need to choose a different name like `py-init` or `quickforge-cli`.
 
 ## Quick Commands Reference
 
 ```bash
 # Full release workflow
-cd /Volumes/NO\ NAME/01_ACTIVE/Pypi/pyhatch
+cd /Volumes/NO\ NAME/01_ACTIVE/Pypi/quickforge
 rm -rf dist/ build/
 python -m build
 twine check dist/*