peneo 0.4.0__tar.gz

peneo-0.4.0/.github/workflows/python-ci.yml

@@ -0,0 +1,31 @@
+name: Python CI
+
+on:
+  push:
+  pull_request:
+
+jobs:
+  lint-and-test:
+    runs-on: ubuntu-latest
+
+    steps:
+      - uses: actions/checkout@v4
+
+      - uses: astral-sh/setup-uv@v4
+        with:
+          python-version: "3.12"
+
+      - name: Install system dependencies
+        run: sudo apt-get install -y ripgrep
+
+      - name: Install dependencies
+        run: uv sync --dev
+
+      - name: Prepare temp directory
+        run: mkdir -p "$RUNNER_TEMP/peneo-tmp"
+
+      - name: Lint
+        run: uv run ruff check .
+
+      - name: Test
+        run: TMPDIR="$RUNNER_TEMP/peneo-tmp" uv run pytest

peneo-0.4.0/.github/workflows/release.yml

@@ -0,0 +1,171 @@
+name: Release
+
+on:
+  push:
+    tags:
+      - 'v*.*.*'
+
+permissions:
+  contents: read
+
+jobs:
+  build-distributions:
+    runs-on: ubuntu-latest
+    outputs:
+      version: ${{ steps.version.outputs.version }}
+
+    steps:
+      - name: Checkout code
+        uses: actions/checkout@v4
+        with:
+          fetch-depth: 0
+
+      - name: Set up Python with uv
+        uses: astral-sh/setup-uv@v4
+        with:
+          python-version: "3.12"
+
+      - name: Install dependencies
+        run: uv sync --dev
+
+      - name: Prepare temp directory
+        run: mkdir -p "$RUNNER_TEMP/peneo-tmp"
+
+      - name: Extract version from tag
+        id: version
+        run: |
+          VERSION=${GITHUB_REF#refs/tags/v}
+          echo "version=$VERSION" >> $GITHUB_OUTPUT
+          echo "Version: $VERSION"
+
+      - name: Verify version consistency
+        run: |
+          TAG_VERSION=${{ steps.version.outputs.version }}
+          PY_VERSION=$(python3 - <<'PY'
+          import tomllib
+
+          with open("pyproject.toml", "rb") as f:
+              print(tomllib.load(f)["project"]["version"])
+          PY
+          )
+          if [ "$TAG_VERSION" != "$PY_VERSION" ]; then
+            echo "Error: Tag version ($TAG_VERSION) does not match pyproject.toml version ($PY_VERSION)"
+            exit 1
+          fi
+
+      - name: Run tests
+        run: TMPDIR="$RUNNER_TEMP/peneo-tmp" uv run pytest
+
+      - name: Build source distribution
+        run: |
+          uv build --sdist --out-dir dist
+
+      - name: Build wheel
+        run: |
+          uv build --wheel --out-dir dist
+
+      - name: Upload distribution artifacts
+        uses: actions/upload-artifact@v4
+        with:
+          name: python-package-distributions
+          path: dist/*
+
+  publish-testpypi:
+    runs-on: ubuntu-latest
+    needs: build-distributions
+
+    steps:
+      - name: Download distribution artifacts
+        uses: actions/download-artifact@v4
+        with:
+          name: python-package-distributions
+          path: dist
+
+      - name: Publish package distributions to TestPyPI
+        uses: pypa/gh-action-pypi-publish@release/v1
+        with:
+          packages-dir: dist/
+          password: ${{ secrets.TEST_PYPI_API_TOKEN }}
+          repository-url: https://test.pypi.org/legacy/
+
+  verify-testpypi:
+    runs-on: ubuntu-latest
+    needs:
+      - build-distributions
+      - publish-testpypi
+
+    steps:
+      - name: Set up Python with uv
+        uses: astral-sh/setup-uv@v4
+        with:
+          python-version: "3.12"
+
+      - name: Wait for package availability on TestPyPI
+        env:
+          VERSION: ${{ needs.build-distributions.outputs.version }}
+        run: |
+          uv venv .testpypi-venv
+          for attempt in $(seq 1 10); do
+            if uv pip install \
+              --python .testpypi-venv/bin/python \
+              --refresh \
+              --index-url https://test.pypi.org/simple/ \
+              --extra-index-url https://pypi.org/simple/ \
+              "peneo==${VERSION}"; then
+              exit 0
+            fi
+            echo "Package not available yet on TestPyPI, retrying..."
+            sleep 15
+          done
+          echo "Failed to install peneo==${VERSION} from TestPyPI"
+          exit 1
+
+      - name: Verify installed package import
+        run: .testpypi-venv/bin/python -c "import peneo; import peneo.__main__"
+
+  publish-pypi:
+    runs-on: ubuntu-latest
+    needs: verify-testpypi
+    environment:
+      name: pypi
+      url: https://pypi.org/p/peneo
+
+    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
+        with:
+          packages-dir: dist/
+          password: ${{ secrets.PYPI_API_TOKEN }}
+
+  create-github-release:
+    runs-on: ubuntu-latest
+    needs:
+      - build-distributions
+      - publish-pypi
+    permissions:
+      contents: write
+
+    steps:
+      - name: Download distribution artifacts
+        uses: actions/download-artifact@v4
+        with:
+          name: python-package-distributions
+          path: dist
+
+      - name: Create GitHub Release
+        uses: softprops/action-gh-release@v2
+        with:
+          tag_name: ${{ github.ref_name }}
+          name: Peneo ${{ needs.build-distributions.outputs.version }}
+          generate_release_notes: true
+          files: |
+            dist/*
+          draft: false
+          prerelease: false
+          fail_on_unmatched_files: true

peneo-0.4.0/.gitignore

@@ -0,0 +1,9 @@
+.venv/
+__pycache__/
+.pytest_cache/
+.ruff_cache/
+.mypy_cache/
+*.pyc
+.vscode/
+.serena/
+

peneo-0.4.0/.python-version

@@ -0,0 +1 @@
+3.12

peneo-0.4.0/AGENTS.md

@@ -0,0 +1,35 @@
+# Repository Guidelines
+
+## Project Structure & Module Organization
+
+Core application code lives under `src/peneo/`. Keep UI concerns in `src/peneo/ui/`, state and reducers in `src/peneo/state/`, side-effect orchestration in `src/peneo/services/`, external integrations in `src/peneo/adapters/`, and shared data models in `src/peneo/models/`. Tests live in `tests/`. Product and MVP notes belong in `docs/`. CI is defined in `.github/workflows/python-ci.yml`.
+
+Current input handling is centralized in `src/peneo/state/input.py`. Keep key interpretation in the dispatcher and reducer-facing actions rather than embedding per-widget branching in `src/peneo/ui/`.
+
+## Build, Test, and Development Commands
+
+- `uv sync --python 3.12 --dev`: create or refresh the local environment with dev dependencies.
+- `uv run peneo`: start the Textual app through the console script.
+- `uv run python -m peneo`: alternate module-based entrypoint.
+- `uv run ruff check .`: run lint checks.
+- `uv run pytest`: execute the test suite.
+
+Run commands from the repository root so paths and config resolution stay consistent.
+
+## Coding Style & Naming Conventions
+
+Target Python 3.12 and follow PEP 8 with 4-space indentation. Use `snake_case` for modules, functions, and variables; `PascalCase` for classes; and short imperative names for actions or commands. Keep UI code presentation-focused and move filesystem or OS-specific logic into `adapters/` and `services/`. Use `ruff` for import sorting and lint enforcement before opening a PR.
+
+## Testing Guidelines
+
+Use `pytest` for all tests and `pytest-asyncio` for async or Textual headless cases. Name test files `test_*.py` and test functions `test_*`. Add or update tests with every behavior change. New UI bootstrap or state transitions should have at least one smoke-level test proving the app can start or the reducer path works.
+
+The current app renders a live three-pane filesystem browser and routes keyboard input through the centralized dispatcher/reducer flow. Covered interactions include directory navigation, reload, filtering, sort changes, directories-first toggle, selection, copy/cut/paste, delete-to-trash with configurable confirmation, single-target rename, create file/directory flows, recursive file search from the command palette, read-only attribute inspection, startup-config editing and saving, opening files with the OS default app, opening files in a terminal editor with `e`, copying paths to the system clipboard, opening a terminal in the current directory with optional `config.toml` overrides, toggling hidden-file visibility from the command palette, and using the embedded split terminal. `HistoryState` exists in state but back/forward navigation is not yet wired to the UI; keep AGENTS/README in sync when that changes.
+
+## Commit & Pull Request Guidelines
+
+Recent history uses short imperative commit subjects such as `Add MVP specification document`. Follow that style and keep commits focused. Create feature branches per issue from the latest `develop` branch, for example `feat/issue-7-textual-bootstrap`. Treat `develop` as the next release candidate and keep it in a state that is ready for functional verification. Merge feature work by opening PRs from the feature branch into `develop`. Except for hotfixes, do not merge work branches directly into `main`; release by merging `develop` into `main`. PR titles should include the related issue ID, and PR descriptions should summarize scope, test results, and follow-up work. Link the issue, and include terminal output or screenshots when a UI change is easier to review visually.
+
+## Configuration & Workflow Notes
+
+Use `gh` for GitHub operations. Sync the latest `develop` branch before creating a feature branch, and keep the hotfix exception explicit when a direct `main` update is required. Keep `.venv/`, cache directories, and editor-specific files out of commits. Update `README.md` when setup steps, commands, repository layout, or developer workflow change.

peneo-0.4.0/CLAUDE.md

@@ -0,0 +1,35 @@
+# Repository Guidelines
+
+## Project Structure & Module Organization
+
+Core application code lives under `src/peneo/`. Keep UI concerns in `src/peneo/ui/`, state and reducers in `src/peneo/state/`, side-effect orchestration in `src/peneo/services/`, external integrations in `src/peneo/adapters/`, and shared data models in `src/peneo/models/`. Tests live in `tests/`. Product and MVP notes belong in `docs/`. CI is defined in `.github/workflows/python-ci.yml`.
+
+Current input handling is centralized in `src/peneo/state/input.py`. Keep key interpretation in the dispatcher and reducer-facing actions rather than embedding per-widget branching in `src/peneo/ui/`.
+
+## Build, Test, and Development Commands
+
+- `uv sync --python 3.12 --dev`: create or refresh the local environment with dev dependencies.
+- `uv run peneo`: start the Textual app through the console script.
+- `uv run python -m peneo`: alternate module-based entrypoint.
+- `uv run ruff check .`: run lint checks.
+- `uv run pytest`: execute the test suite.
+
+Run commands from the repository root so paths and config resolution stay consistent.
+
+## Coding Style & Naming Conventions
+
+Target Python 3.12 and follow PEP 8 with 4-space indentation. Use `snake_case` for modules, functions, and variables; `PascalCase` for classes; and short imperative names for actions or commands. Keep UI code presentation-focused and move filesystem or OS-specific logic into `adapters/` and `services/`. Use `ruff` for import sorting and lint enforcement before opening a PR.
+
+## Testing Guidelines
+
+Use `pytest` for all tests and `pytest-asyncio` for async or Textual headless cases. Name test files `test_*.py` and test functions `test_*`. Add or update tests with every behavior change. New UI bootstrap or state transitions should have at least one smoke-level test proving the app can start or the reducer path works.
+
+The current app renders a live three-pane filesystem browser and routes keyboard input through the centralized dispatcher/reducer flow. Covered interactions include directory navigation, reload, filtering, sort changes, directories-first toggle, selection, copy/cut/paste, delete-to-trash with configurable confirmation, single-target rename, create file/directory flows, recursive file search from the command palette, read-only attribute inspection, startup-config editing and saving, opening files with the OS default app, opening files in a terminal editor with `e`, copying paths to the system clipboard, opening a terminal in the current directory with optional `config.toml` overrides, toggling hidden-file visibility from the command palette, and using the embedded split terminal. `HistoryState` exists in state but back/forward navigation is not yet wired to the UI; keep AGENTS/README in sync when that changes.
+
+## Commit & Pull Request Guidelines
+
+Recent history uses short imperative commit subjects such as `Add MVP specification document`. Follow that style and keep commits focused. Create feature branches per issue from the latest `develop` branch, for example `feat/issue-7-textual-bootstrap`. Treat `develop` as the next release candidate and keep it in a state that is ready for functional verification. Merge feature work by opening PRs from the feature branch into `develop`. Except for hotfixes, do not merge work branches directly into `main`; release by merging `develop` into `main`. PR titles should include the related issue ID, and PR descriptions should summarize scope, test results, and follow-up work. Link the issue, and include terminal output or screenshots when a UI change is easier to review visually.
+
+## Configuration & Workflow Notes
+
+Use `gh` for GitHub operations. Sync the latest `develop` branch before creating a feature branch, and keep the hotfix exception explicit when a direct `main` update is required. Keep `.venv/`, cache directories, and editor-specific files out of commits. Update `README.md` when setup steps, commands, repository layout, or developer workflow change.

peneo-0.4.0/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 devgamesan
+
+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.