fix: Resolve codebase quality issues

.github/workflows/harmony-check.yml

@@ -34,7 +34,7 @@ jobs:
           # Exit codes: 0=harmonious, 1=medium, 2=high, 3=critical
           # Note: Currently informational as source code itself has some disharmony
           # (main.py functions do more than their names suggest - great meta example!)
-          find src -name "*.py" -type f | xargs harmonizer || {
+          find harmonizer -name "*.py" -type f | xargs harmonizer || {
             echo "━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━"
             echo "⚠️ Source code has disharmony (demonstrates tool working!)"
             echo "   This is a great example of semantic issues the tool catches."
@@ -76,7 +76,7 @@ jobs:
           echo "📋 Generating detailed JSON harmony report..."
 
           # Generate JSON report for all Python files
-          find src examples tests -name "*.py" -type f | xargs harmonizer --format json > harmony-report.json 2>/dev/null || true
+          find harmonizer examples tests -name "*.py" -type f | xargs harmonizer --format json > harmony-report.json 2>/dev/null || true
 
           # Display summary if report was generated
           if [ -f harmony-report.json ] && [ -s harmony-report.json ]; then
@@ -170,7 +170,7 @@ jobs:
 
           # Use stricter threshold (0.3 instead of default 0.5)
           # This catches even minor semantic drift
-          if find src -name "*.py" -type f | xargs harmonizer --threshold 0.3; then
+          if find harmonizer -name "*.py" -type f | xargs harmonizer --threshold 0.3; then
             echo "✅ Code meets excellent harmony standards!"
           else
             echo ""

CONTRIBUTING.md

@@ -55,15 +55,15 @@ We use `black` for code formatting and `flake8` for linting to ensure a consiste
 Before you commit your changes, please run `black` to automatically format your code:
 
 ```sh
-black src/ tests/
+black harmonizer/ tests/
 ```
 
 ### Linting
 
 You can check for any style issues or potential errors with `flake8`:
 
 ```sh
-flake8 src/ tests/
+flake8 harmonizer/ tests/
 ```
 
 Our Continuous Integration (CI) pipeline will automatically check for formatting and linting issues, so it's a good idea to run these tools locally before pushing your changes.

harmonizer/divine_invitation_engine_V2.py

@@ -451,7 +451,14 @@ def infer_unknown_meaning(
 
 
 class GeopoliticalAnalyzer:
-    """Optimized geopolitical analysis"""
+    """
+    Optimized geopolitical analysis
+
+    NOTE: This class is currently not integrated into the main analysis pipeline.
+    It provides experimental capabilities for analyzing entity postures and relationships
+    in a geopolitical context using the 4D semantic framework. Available for future
+    extensions or custom use cases.
+    """
 
     def __init__(self, vocab_manager: VocabularyManager, analyzer: SemanticAnalyzer):
         self.vocab = vocab_manager

pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "PythonCodeHarmonizer"
-version = "1.1.0"
+version = "1.4.0"
 description = "A semantic code debugger."
 readme = "README.md"
 license = { file="LICENSE" }
@@ -16,6 +16,9 @@ classifiers = [
 [project.scripts]
 harmonizer = "harmonizer.main:run_cli"
 
+[project.optional-dependencies]
+refactor = ["black>=24.4.2"]
+
 [tool.setuptools.packages.find]
 where = ["."]
 include = ["harmonizer"]

requirements.txt

@@ -1,7 +1,6 @@
 pytest
 black==24.4.2
 astunparse==1.6.3
-astunparse==1.6.3
 flake8
 isort
 pre-commit