foga 0.1.0__tar.gz

foga-0.1.0/.devcontainer/devcontainer.json

@@ -0,0 +1,32 @@
+{
+  "name": "devkit",
+  "image": "mcr.microsoft.com/devcontainers/base:ubuntu",
+  "remoteUser": "vscode",
+  "features": {
+    "ghcr.io/devcontainers/features/python:1": {
+      "version": "3.11"
+    },
+    "ghcr.io/devcontainers/features/node:1": {
+      "version": "22"
+    }
+  },
+  "postCreateCommand": "bash .devcontainer/post-create.sh",
+  "runArgs": [
+    "--security-opt=seccomp=unconfined",
+    "--security-opt=apparmor=unconfined"
+  ],
+  "mounts": [
+    "type=bind,source=${localEnv:HOME}/.codex,target=/home/vscode/.codex"
+  ],
+  "customizations": {
+    "vscode": {
+      "extensions": [
+        "ms-python.python",
+        "ms-python.vscode-pylance",
+        "ms-vscode.cmake-tools",
+        "charliermarsh.ruff",
+        "openai.chatgpt"
+      ]
+    }
+  }
+}

foga-0.1.0/.devcontainer/post-create.sh

@@ -0,0 +1,33 @@
+#!/usr/bin/env bash
+
+set -euo pipefail
+
+export DEBIAN_FRONTEND=noninteractive
+
+# Install the native development toolchain that `devkit` users commonly need
+# when building and testing Python packages with C/C++ bindings.
+sudo apt-get update
+sudo apt-get install -y --no-install-recommends \
+    build-essential \
+    bubblewrap \
+    clang \
+    cmake \
+    gdb \
+    git \
+    gh \
+    ninja-build \
+    pkg-config
+sudo apt-get clean
+sudo rm -rf /var/lib/apt/lists/*
+
+# Upgrade pip first so editable installs and modern packaging tools behave
+# consistently inside the fresh container image.
+python3 -m pip install --upgrade pip
+
+# Install this repository in editable mode together with the development
+# dependencies used to build, test, and publish `devkit` itself.
+python3 -m pip install -e ".[dev]"
+
+# Install Codex in the container so the development environment matches the
+# local workflow expected for this repository.
+npm install -g @openai/codex

foga-0.1.0/.github/workflows/ci.yml

@@ -0,0 +1,36 @@
+name: CI
+
+on:
+  push:
+    branches:
+      - main
+  pull_request:
+
+jobs:
+  verify:
+    name: Verify
+    runs-on: ubuntu-latest
+
+    steps:
+      - name: Check out repository
+        uses: actions/checkout@v4
+
+      - name: Set up Python 3.11
+        uses: actions/setup-python@v5
+        with:
+          python-version: "3.11"
+
+      - name: Install project and development dependencies
+        run: python -m pip install -e ".[dev]"
+
+      - name: Lint with Ruff
+        run: ruff check .
+
+      - name: Run test suite
+        run: pytest
+
+      - name: Build package
+        run: python -m build
+
+      - name: Validate example configuration
+        run: foga --config examples/qupled/foga.yml validate

foga-0.1.0/.github/workflows/publish.yml

@@ -0,0 +1,59 @@
+name: Publish
+
+on:
+  push:
+    tags:
+      - "v*"
+  workflow_dispatch:
+
+jobs:
+  build:
+    name: Build Release Artifacts
+    runs-on: ubuntu-latest
+
+    steps:
+      - name: Check out repository
+        uses: actions/checkout@v4
+
+      - name: Set up Python 3.11
+        uses: actions/setup-python@v5
+        with:
+          python-version: "3.11"
+
+      - name: Install project and development dependencies
+        run: python -m pip install -e ".[dev]"
+
+      - name: Run lint checks
+        run: ruff check .
+
+      - name: Run test suite
+        run: pytest
+
+      - name: Build package
+        run: python -m build
+
+      - name: Upload distribution artifacts
+        uses: actions/upload-artifact@v4
+        with:
+          name: python-package-distributions
+          path: dist/
+
+  publish-pypi:
+    name: Publish To PyPI
+    runs-on: ubuntu-latest
+    needs: build
+    environment:
+      name: pypi
+      url: https://pypi.org/p/foga
+    permissions:
+      id-token: write
+
+    steps:
+      - name: Download distribution artifacts
+        uses: actions/download-artifact@v4
+        with:
+          name: python-package-distributions
+          path: dist/
+
+      - name: Publish package distributions to PyPI
+        uses: pypa/gh-action-pypi-publish@release/v1

foga-0.1.0/.gitignore

@@ -0,0 +1,47 @@
+# Python bytecode and caches
+__pycache__/
+**/__pycache__/
+*.py[cod]
+*$py.class
+
+# Build and packaging artifacts
+.Python
+build/
+dist/
+site/
+*.egg
+*.egg-info/
+.eggs/
+pip-wheel-metadata/
+
+# Virtual environments
+.venv/
+venv/
+env/
+ENV/
+
+# Test and coverage output
+.coverage
+.coverage.*
+.pytest_cache/
+htmlcov/
+.tox/
+.nox/
+
+# Type checker and linter caches
+.mypy_cache/
+.ruff_cache/
+.pyre/
+
+# Jupyter
+.ipynb_checkpoints/
+
+# Local tool state
+.codex
+
+# Editors and OS files
+.vscode/
+.idea/
+*.swp
+*.swo
+.DS_Store

foga-0.1.0/AGENTS.md

@@ -0,0 +1,69 @@
+# Repository Guidelines
+
+## Project Structure & Module Organization
+
+Application code lives under `src/foga/`. Keep CLI entrypoints in `src/foga/cli.py`, shared config handling in `src/foga/config.py`, execution helpers in `src/foga/executor.py`, and backend-specific command builders in `src/foga/adapters/`. Tests live in `tests/` and currently cover config loading, adapter behavior, and CLI routing. Example user configuration lives in `examples/qupled/foga.yml`. Use `README.md` for end-user setup. Track unfinished product work in GitHub issues and milestones.
+
+## Build, Test, and Development Commands
+
+Set up a local environment with:
+
+```bash
+pip install -e .[dev]
+```
+
+Format the code with:
+
+```bash
+ruff format .
+```
+
+Run the test suite with:
+
+```bash
+pytest
+```
+
+Lint the code with:
+
+```bash
+ruff check .
+```
+
+Validate packaging metadata with:
+
+```bash
+python -m build
+```
+
+Exercise the CLI during development with commands such as `foga validate`, `foga build --profile mpi`, and `foga deploy --dry-run`. When using the devcontainer, `.devcontainer/post-create.sh` installs the same editable development environment automatically.
+
+Shared Python implementation guidance lives in `skills/python-development/`. Use that skill when editing Python code, tests, packaging metadata, or developer-tooling configuration in this repository.
+Shared GitHub execution guidance lives in `skills/github-issue-workflow/`. Use that skill when starting work from GitHub issues or when the task should end with an opened pull request.
+Shared PR review coordination guidance lives in `skills/pr-review-loop/`. Use that skill when one agent should review a PR on GitHub and another agent should implement the published comments without relaying them manually in chat.
+
+## Coding Style & Naming Conventions
+
+Target Python 3.10+ and use 4-space indentation. Follow existing module boundaries instead of adding large multi-purpose files. Prefer descriptive snake_case for functions, variables, and test names; keep class names in PascalCase. Match the repository’s current style: small focused functions, straightforward control flow, and minimal comments unless behavior is non-obvious. Run `ruff format .` and `ruff check .` for formatting and linting, and keep diffs consistent with surrounding code.
+
+## Testing Guidelines
+
+Use `pytest` for all tests. Add new tests in `tests/` with filenames named `test_<area>.py` and test functions named `test_<behavior>()`. Cover both happy paths and invalid configuration or command-generation cases. Run `ruff format .`, `ruff check .`, and `pytest` before merging. Run `python -m build` when packaging metadata or install behavior changes. If you change CLI behavior, add or update CLI-facing tests before merging.
+
+## Commit & Pull Request Guidelines
+
+Recent commits use short, imperative subjects such as `Add devcontainer bootstrap and development docs`. Keep commit titles concise and specific.
+
+Before creating commits or changing git settings, check `.codex/` for repository-local git configuration instructions or other custom workflow notes.
+
+Codex identity: use the repository's configured bot account for repository-local commits, branch pushes, pull request creation, and PR comments or reviews unless the user explicitly asks otherwise.
+
+Development flow: work locally on a dedicated branch. One subprocess implements the change, and a separate subprocess reviews the local diff before any GitHub interaction. Address review findings locally before pushing or opening a pull request.
+
+Pull request flow: after the PR is open, the human user is the reviewer. The human reviews on GitHub, leaves comments, and Codex resumes local development to address that feedback. Repeat the local edit plus internal review loop until the human is satisfied, then the human approves and merges.
+
+When picking up work from GitHub issues, always create a dedicated branch before making changes and open a pull request when the work is complete. Pull requests should explain the user-facing change, note any config or CLI behavior differences, and list the verification performed, for example `ruff format .`, `ruff check .`, `pytest`, `python -m build`, or a representative `foga ... --dry-run` command. Include sample output only when it clarifies behavior. After opening the PR, stop and wait for user feedback instead of continuing automatically.
+
+## Configuration Notes
+
+`foga` expects a root-level `foga.yml`. When adding new configuration fields or adapter behavior, update `README.md` and the example in `examples/qupled/foga.yml` so the documented workflow stays accurate.

foga-0.1.0/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 Federico Lucco Castello
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.