Fix GitHub Actions build failures for asmoses & moses components

[Copilot]

The GitHub Actions CI workflows were failing when building asmoses and moses components with the error:

CMake Error: The source directory "/__w/opencog-central/asmoses" does not appear to contain CMakeLists.txt.
Specify --help for usage, or press the help button on the CMake GUI.
Error: Process completed with exit code 1.

Root Cause

The CI workflows (ci-org-generalized.yml, ci-org-v7.yml, ci-org-v8.yml) were attempting to clone external repositories for asmoses and moses components, but these components already exist as local directories in the opencog-central monorepo. The complex git repository detection logic was:

1. Finding existing local asmoses/moses directories
2. Detecting they weren't git repositories
3. Backing up and removing the local directories
4. Cloning external repositories
5. Failing during the cmake build step due to path issues

Solution

Refactored all affected workflows to build the local asmoses and moses components directly instead of cloning external repositories:

• ci-org-generalized.yml: Simplified both asmoses and moses build steps (removed 130+ lines of complex git logic per component)
• ci-org-v7.yml: Fixed asmoses build to use local component
• ci-org-v8.yml: Fixed both asmoses and moses builds to use local components

The new build logic:

- name: Build and Install asmoses
  run: |
    COMPONENT="asmoses"
    if [ -d "$COMPONENT" ]; then
      mkdir -p "$COMPONENT/build"
      cd "$COMPONENT/build"
      cmake -DCMAKE_BUILD_TYPE=Release ..
      make -j2
      sudo make install
      sudo ldconfig
      cd ../..
    else
      echo "ERROR: Local $COMPONENT directory not found!"
      exit 1
    fi

Benefits

• Eliminates the CMakeLists.txt not found errors
• Reduces workflow complexity and maintenance burden
• Ensures consistent behavior across all CI workflows
• Builds from the actual monorepo components rather than external dependencies
• Maintains proper build order and dependency structure

All modified workflows have been validated for YAML syntax and no external clone references remain for asmoses/moses components.

Fixes #7.

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[drzo]

good times