update: installing foliant from PyPi and updating dependencies

[TOsmanov]

---

EntelligenceAI PR Summary

Standardizes Foliant installation and version detection to use stable master branch and PyPI releases instead of development branch.

• Updated version retrieval in all build scripts (build_full.sh, build_latest.sh, build_pandoc.sh, build_slim.sh) to fetch from 'master' branch
• Removed TODO comments across all build scripts
• Modified Dockerfile-slim to install Foliant from PyPI with version constraint instead of building from 'add-partial-copy' branch source
• Commented out previous GitHub clone and Poetry-based build process in Dockerfile-slim

---

Confidence Score: 5/5 - Safe to Merge

• No review comments were generated, indicating the PR passed all automated checks cleanly
• Heuristic analysis shows zero critical, significant, or high-risk issues across all severity levels
• No existing unresolved comments that would block merging
• The PR appears to be safe to merge as-is based on available information

[entelligence-ai-pr-reviews]

Walkthrough

This PR transitions the Foliant Docker build process from using a development branch to the stable master branch. The changes standardize version detection across all build scripts (full, latest, pandoc, and slim) to fetch from the 'master' branch instead of 'add-partial-copy'. The Dockerfile-slim has been updated to install Foliant directly from PyPI rather than building from source via a GitHub branch clone. This simplifies the build process, removes technical debt indicated by TODO comments, and aligns the project with using official releases instead of development branches.

Changes

File(s)	Summary
build_full.sh build_latest.sh build_pandoc.sh build_slim.sh	Updated Foliant version retrieval logic to fetch from 'master' branch instead of 'add-partial-copy' branch and removed TODO comments indicating this planned change.
Dockerfile-slim	Replaced custom Foliant installation from GitHub branch (cloning, building with Poetry, installing wheel) with standard PyPI installation using version constraint foliant>=$VERSION. Commented out the previous source-based installation approach.

Sequence Diagram

This diagram shows the interactions between components:

sequenceDiagram
    participant Docker as Docker Build
    participant Pip as pip3
    participant PyPI as PyPI Registry
    participant Foliant as Foliant Package

    Note over Docker,Foliant: New Installation Flow (Simplified)
    
    Docker->>Pip: pip3 install foliant>=$VERSION
    activate Pip
    Pip->>PyPI: Request foliant package (version >= $VERSION)
    activate PyPI
    PyPI-->>Pip: Return package metadata and wheel
    deactivate PyPI
    Pip->>Foliant: Install package from wheel
    activate Foliant
    Foliant-->>Pip: Installation complete
    deactivate Foliant
    Pip-->>Docker: Package installed successfully
    deactivate Pip

    Note over Docker,Foliant: Old Installation Flow (Commented Out)
    
    rect rgb(240, 240, 240)
        Note right of Docker: Previous approach:<br/>1. Clone from GitHub branch<br/>2. Build with Poetry<br/>3. Install local wheel
    end

Loading

---

🔗 Cross-Repository Impact Analysis

Enable automatic detection of breaking changes across your dependent repositories. → Set up now

Learn more about Cross-Repository Analysis

What It Does

• Automatically identifies repositories that depend on this code
• Analyzes potential breaking changes across your entire codebase
• Provides risk assessment before merging to prevent cross-repo issues

How to Enable

1. Visit Settings → Code Management
2. Configure repository dependencies
3. Future PRs will automatically include cross-repo impact analysis!

Benefits

• 🛡️ Prevent breaking changes across repositories
• 🔍 Catch integration issues before they reach production
• 📊 Better visibility into your multi-repo architecture

---