chore: rename markitect_project to markitect-main across project

Finishes the in-progress rename so docs, configs, tests, and capability
manifests all reference the current repo name consistently. Fixes two
tests (test_roundtrip_consolidated.py, test_issue_140_roundtrip_simplified.py)
whose hardcoded cwd paths would have broken under the renamed directory.

Archival content under history/, reports/, and roadmap/eat-the-frog/, plus
derived artifacts (.venv_old/, node_modules/, asset_registry.json) are
intentionally left untouched.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

.clinerules

@@ -10,7 +10,7 @@ principles with strict separation of concerns.
 
 ## Directory Structure & Clean Architecture
 ```
-markitect_project/
+markitect-main/
 ├── domain/          # Business logic (innermost layer)
 ├── application/     # Use cases and workflows
 ├── infrastructure/ # External interfaces (database, file system)

.gitmodules

@@ -1,6 +1,6 @@
 [submodule "wiki"]
 	path = wiki
-	url = http://92.205.130.254:32166/coulomb/markitect_project.wiki.git
+	url = http://92.205.130.254:32166/coulomb/markitect-main.wiki.git
 	branch = main
 [submodule "capabilities/kaizen-agentic"]
 	path = capabilities/kaizen-agentic

DEPENDENCIES.md

@@ -457,7 +457,7 @@ Sister projects can reuse these capabilities directly:
 Install capabilities via local file references:
 ```toml
 [project.dependencies]
-release-management = {path = "../markitect_project/capabilities/release-management"}
+release-management = {path = "../markitect-main/capabilities/release-management"}
 ```
 
 ### Shared Infrastructure

agents/agent-capability-manager.md

@@ -15,7 +15,7 @@ You are responsible for:
 
 ### Directory Structure
 ```
-markitect_project/
+markitect-main/
 ├── Makefile                           # Main project Makefile
 ├── scripts/
 │   └── capability_discovery.mk       # Auto-discovery and delegation system

capabilities/DETACHED-issue-facade.yaml

@@ -7,7 +7,7 @@ detachment:
   capability_name: issue-facade
   capability_family: issue-tracking
   integration_pattern: capabilities-directory
-  original_location: /home/worsch/markitect_project/capabilities/issue-facade
+  original_location: /home/worsch/markitect-main/capabilities/issue-facade
 
 capability_metadata:
   spec_file: CAPABILITY-issue-tracking.yaml
@@ -17,23 +17,23 @@ capability_metadata:
 
 integration_details:
   parent_project: capabilities
-  parent_path: /home/worsch/markitect_project/capabilities
+  parent_path: /home/worsch/markitect-main/capabilities
 
 re_integration_guide: |
   To re-integrate this capability using the new architecture:
 
   # Option 1: Git submodule (recommended)
-  cd /home/worsch/markitect_project/capabilities
+  cd /home/worsch/markitect-main/capabilities
   git submodule add <repo-url> _issue-facade
   pip install -e _issue-facade/
 
   # Option 2: Clone directly
-  cd /home/worsch/markitect_project/capabilities
+  cd /home/worsch/markitect-main/capabilities
   git clone <repo-url> _issue-facade
   pip install -e _issue-facade/
 
   # Option 3: Copy into project
-  cd /home/worsch/markitect_project/capabilities
+  cd /home/worsch/markitect-main/capabilities
   cp -r /path/to/issue-facade _issue-facade
   pip install -e _issue-facade/
 

capabilities/markitect-content/tests/test_issue_46_schema_generation_outline.py

@@ -8,7 +8,7 @@ This test module validates outline mode schema generation improvements including
 - Content instruction integration
 - End-to-end workflow from example document to generated drafts
 
-Created for Issue #46: https://gitea.coulomb.social/coulomb/markitect_project/issues/46
+Created for Issue #46: https://gitea.coulomb.social/coulomb/markitect-main/issues/46
 """
 
 import pytest

capabilities/release-management/MIGRATION_PLAN.md

@@ -209,7 +209,7 @@ tests/
 ## 🎯 Detailed File Structure After Migration
 
 ```
-markitect_project/
+markitect-main/
 ├── capabilities/
 │   └── release-management/
 │       ├── README.md                              ✅ CREATED

capabilities/release-management/README.md

@@ -162,7 +162,7 @@ clean_before_build = true
 [tool.release-management.registries.gitea]
 url = "http://92.205.130.254:32166"
 owner = "coulomb"
-repo = "markitect_project"
+repo = "markitect-main"
 auth_token_env = "GITEA_API_TOKEN"
 
 [tool.release-management.registries.pypi]

capabilities/release-management/docs/package_publishing.md

@@ -141,7 +141,7 @@ make release-publish VERSION=0.8.0
 ## Registry Information
 
 - **Gitea URL**: http://92.205.130.254:32166
-- **Repository**: coulomb/markitect_project
+- **Repository**: coulomb/markitect-main
 - **PyPI Registry URL**: http://92.205.130.254:32166/api/packages/coulomb/pypi
 - **Package List URL**: http://92.205.130.254:32166/api/v1/packages/coulomb
 

docs/CAPABILITIES_QUICK_REFERENCE.md

@@ -8,7 +8,7 @@
 
 ```bash
 # ❌ WRONG - Don't edit capability files from main repo
-cd /home/worsch/markitect_project/capabilities/testdrive-jsui
+cd /home/worsch/markitect-main/capabilities/testdrive-jsui
 vim src/testdrive_jsui/core.py  # DON'T DO THIS!
 
 # ✅ CORRECT - Use separate Claude instance/session
@@ -29,7 +29,7 @@ cd /path/to/work/testdrive-jsui
 
 | Session | Purpose | Location |
 |---------|---------|----------|
-| **Main Repo** | Integration, configuration | `/home/worsch/markitect_project` |
+| **Main Repo** | Integration, configuration | `/home/worsch/markitect-main` |
 | **Capability** | Feature development, bugs | Separate clone or `capabilities/capability-name` |
 
 **Why?** Prevents accidental cross-contamination and respects repository boundaries.
@@ -40,7 +40,7 @@ cd /path/to/work/testdrive-jsui
 
 ```bash
 # After pushing changes to capability repo
-cd /home/worsch/markitect_project
+cd /home/worsch/markitect-main
 git submodule update --remote capabilities/testdrive-jsui
 git add capabilities/testdrive-jsui
 git commit -m "chore: update testdrive-jsui to latest"
@@ -50,7 +50,7 @@ git push
 ### Add New Capability
 
 ```bash
-cd /home/worsch/markitect_project
+cd /home/worsch/markitect-main
 
 # Add as submodule
 git submodule add http://gitea/coulomb/new-capability.git capabilities/new-capability
@@ -67,7 +67,7 @@ git commit -m "feat: add new-capability submodule"
 
 ```bash
 # Option 1: In submodule directory (careful!)
-cd /home/worsch/markitect_project/capabilities/testdrive-jsui
+cd /home/worsch/markitect-main/capabilities/testdrive-jsui
 git checkout -b feature-branch
 # make changes
 git commit -m "feat: new feature"
@@ -86,7 +86,7 @@ git push origin feature-branch
 ### Check Capability Status
 
 ```bash
-cd /home/worsch/markitect_project
+cd /home/worsch/markitect-main
 
 # List all capabilities
 make capabilities-list

docs/PROJECT_STRUCTURE.md

@@ -9,7 +9,7 @@ MarkiTect is a markdown processing toolkit with transclusion, schema validation,
 ## Current Directory Structure
 
 ```
-markitect_project/
+markitect-main/
 ├── markitect/                    # Main package
 │   ├── [34 root-level .py files] # Core functionality (see below)
 │   ├── assets/                   # Asset discovery, management, caching (21 files)

docs/architecture/CAPABILITIES_ARCHITECTURE.md

@@ -8,7 +8,7 @@ MarkiTect uses a **capabilities-based architecture** where functionality is orga
 
 ### 1. **Separation of Concerns**
 
-**Critical Rule:** The main repository (`markitect_project`) **MUST NOT** directly modify capability code.
+**Critical Rule:** The main repository (`markitect-main`) **MUST NOT** directly modify capability code.
 
 - ✅ **DO**: Use capabilities as dependencies
 - ✅ **DO**: Configure capabilities through documented interfaces
@@ -28,7 +28,7 @@ MarkiTect uses a **capabilities-based architecture** where functionality is orga
 Capabilities are integrated as **git submodules**, not regular directories:
 
 ```
-markitect_project/
+markitect-main/
 ├── .gitmodules                    # Submodule configuration
 ├── capabilities/
 │   ├── testdrive-jsui/           # Git submodule → separate repo
@@ -80,8 +80,8 @@ engine.render_document(content, mode='edit', config=config)
 
 #### Main Repository Session
 ```bash
-# In markitect_project/
-cd /home/worsch/markitect_project
+# In markitect-main/
+cd /home/worsch/markitect-main
 
 # Main repo tasks:
 # - Integrate capabilities
@@ -93,7 +93,7 @@ cd /home/worsch/markitect_project
 #### Capability Session
 ```bash
 # In capability repository
-cd /home/worsch/markitect_project/capabilities/testdrive-jsui
+cd /home/worsch/markitect-main/capabilities/testdrive-jsui
 
 # OR clone separately
 git clone http://gitea/coulomb/testdrive-jsui.git
@@ -122,7 +122,7 @@ cd testdrive-jsui
 
 2. **Update main project** (different Claude instance)
    ```bash
-   cd /home/worsch/markitect_project
+   cd /home/worsch/markitect-main
    git submodule update --remote capabilities/testdrive-jsui
    git commit -m "chore: update testdrive-jsui submodule"
    ```
@@ -139,7 +139,7 @@ When a capability releases a new version:
 
 ```bash
 # In main repo
-cd /home/worsch/markitect_project
+cd /home/worsch/markitect-main
 
 # Update specific capability
 cd capabilities/testdrive-jsui
@@ -160,7 +160,7 @@ git commit -am "chore: update all capabilities"
 # http://gitea/coulomb/new-capability
 
 # 2. Add as submodule to main repo
-cd /home/worsch/markitect_project
+cd /home/worsch/markitect-main
 git submodule add http://gitea/coulomb/new-capability.git capabilities/new-capability
 
 # 3. Add dependency to pyproject.toml
@@ -324,7 +324,7 @@ def test_testdrive_jsui_integration():
 1. **Create separate git repo**
    ```bash
    cd /tmp
-   cp -r markitect_project/capabilities/capability-name capability-name
+   cp -r markitect-main/capabilities/capability-name capability-name
    cd capability-name
    git init
    git add .
@@ -335,7 +335,7 @@ def test_testdrive_jsui_integration():
 
 2. **Remove from main repo**
    ```bash
-   cd markitect_project
+   cd markitect-main
    git rm -rf capabilities/capability-name
    git commit -m "chore: remove capability-name for submodule conversion"
    ```

examples/content-generator/TUTORIAL.md

@@ -117,7 +117,7 @@ This graph enables:
 
 ```bash
 # Ensure MarkiTect is installed
-cd /path/to/markitect_project
+cd /path/to/markitect-main
 pip install -e .
 ```
 

package-lock.json

@@ -1,11 +1,11 @@
 {
-  "name": "markitect_project",
+  "name": "markitect-main",
   "version": "1.0.0",
   "lockfileVersion": 3,
   "requires": true,
   "packages": {
     "": {
-      "name": "markitect_project",
+      "name": "markitect-main",
       "version": "1.0.0",
       "license": "ISC",
       "dependencies": {

package.json

@@ -1,5 +1,5 @@
 {
-  "name": "markitect_project",
+  "name": "markitect-main",
   "version": "1.0.0",
   "description": "",
   "main": "index.js",
@@ -14,7 +14,7 @@
   },
   "repository": {
     "type": "git",
-    "url": "http://92.205.130.254:32166/coulomb/markitect_project"
+    "url": "http://92.205.130.254:32166/coulomb/markitect-main"
   },
   "keywords": [],
   "author": "",

roadmap/testdrive-jsui-publication/PLAN.md

@@ -39,7 +39,7 @@ Confirm the main Markitect application still works correctly with the current
 capability code before publishing.
 
 ```bash
-cd /home/worsch/markitect_project
+cd /home/worsch/markitect-main
 make testdrive-jsui-test-all   # 84 tests must pass
 # Manually verify view and edit modes in the running Markitect app
 ```

tests/test_issue_140_roundtrip_simplified.py

@@ -30,7 +30,7 @@ class TestActualRoundtripBehavior:
         cmd = ["python", "-m", "markitect.cli"] + args
         result = subprocess.run(
             cmd,
-            cwd="/home/worsch/markitect_project",
+            cwd="/home/worsch/markitect-main",
             capture_output=True,
             text=True
         )

tests/test_l7_foundation_database_core.py

@@ -5,7 +5,7 @@ This test implements the requirements for initializing a SQLite database
 and storing markdown files with front matter parsing.
 
 Issue #1: Initialize Database and Store Example Markdown File
-https://gitea.coulomb.social/coulomb/markitect_project/issues/1
+https://gitea.coulomb.social/coulomb/markitect-main/issues/1
 """
 
 import pytest

tests/test_roundtrip_consolidated.py

@@ -33,7 +33,7 @@ class TestRoundtripBase:
             cmd,
             capture_output=True,
             text=True,
-            cwd="/home/worsch/markitect_project"
+            cwd="/home/worsch/markitect-main"
         )
 
     def validate_basic_structure_preservation(self, original: str, reconstructed: str) -> Dict[str, Any]: