ArcForge iOS - Native Application

This project is a native Swift/SwiftUI implementation of ArcForge: The Unified Creation Engine.

Given the massive scope of ArcForge (IDE, local LLMs, Agent Swarms, Git orchestration), this application is structured using a production-ready SwiftUI Architecture featuring Dependency Injection, State Management, and a modular feature-based folder structure.

Project Structure (The Five Pillars)

The codebase is organized exactly according to the ArcForge specifications:

• App: Core entry point, Dependency Container, and main routing.
• Core: App State, Theme definitions, and Service Protocols (Mocked for now; ready for real backend bindings like llama.cpp-swift and SwiftGit2).
• Features:
  • Forge: The IDE Editor interface with split views and file explorers.
  • Nexus: Git repository tracking, CI/CD, and deployment hub.
  • Mind: Local LLM management, prompt handling, and chat interface.
  • Swarm: Visual agent orchestration system and workflow visualizer.
  • Mirror: The live-preview engine layout and device frame simulators.
• UI: Shared components, Vibe Coding overlays, and App-wide layout controls.

How to Open & Run (Native iOS/macOS)

This project was built as a modern .swiftpm (Swift Package App). It contains no proprietary .xcodeproj cruft and is universally compatible with Apple's ecosystem.

1. On macOS: Simply double-click the ArcForge.swiftpm folder. It will instantly open in Xcode as a native app package. You can build and run it on any iOS Simulator, Mac Catalyst, or a plugged-in physical device.
2. On iPad: Airdrop the ArcForge.swiftpm folder to your iPad and open it in Swift Playgrounds. It will compile and run natively on the device.

Next Steps for Production

To realize the full "local execution" scope on iOS devices:

1. The Mind: Replace MockLLMService by linking llama.cpp for Swift to run GGUF models via Apple's Metal framework directly on-device.
2. The Nexus: Replace MockGitService with SwiftGit2 to manage true local repository orchestration.
3. The Forge: iOS strictly forbids spawning arbitrary bash terminals or sub-processes natively. For a true iOS App Store release, the "Terminal" pillar must either be emulated (e.g., via SSH to a remote worker) or the app must be distributed via macOS (where arbitrary processes are allowed).