coding-agent-telegram 2026.3.26__tar.gz → 2026.3.27__tar.gz

coding_agent_telegram-2026.3.27/.github/workflows/pull-request-checks.yml

@@ -0,0 +1,45 @@
+name: Pull Request Checks
+
+on:
+  pull_request:
+
+permissions:
+  contents: read
+
+jobs:
+  test-and-build:
+    runs-on: ubuntu-latest
+    env:
+      SETUPTOOLS_SCM_PRETEND_VERSION_FOR_CODING_AGENT_TELEGRAM: 0.0.dev0
+
+    steps:
+      - uses: actions/checkout@v4
+        with:
+          fetch-depth: 0
+
+      - uses: actions/setup-python@v5
+        with:
+          python-version: "3.x"
+
+      - name: Install test and build dependencies
+        run: |
+          python -m pip install --upgrade pip
+          python -m pip install pytest build twine setuptools-scm
+          python -m pip install -e .
+
+      - name: Run tests
+        run: pytest
+
+      - name: Build release distributions
+        run: python -m build
+
+      - name: Validate package metadata
+        run: python -m twine check dist/*
+
+      - name: Smoke test built wheel
+        run: |
+          python -m venv .smoke-test-venv
+          source .smoke-test-venv/bin/activate
+          python -m pip install --upgrade pip
+          python -m pip install --no-deps dist/*.whl
+          python -c "import coding_agent_telegram"

coding_agent_telegram-2026.3.27/.github/workflows/python-publish.yml

@@ -0,0 +1,95 @@
+# This workflow will upload a Python Package to PyPI when a release is created
+# For more information see: https://docs.github.com/en/actions/automating-builds-and-tests/building-and-testing-python#publishing-to-package-registries
+
+# This workflow uses actions that are not certified by GitHub.
+# They are provided by a third-party and are governed by
+# separate terms of service, privacy policy, and support
+# documentation.
+
+name: Upload Python Package
+
+on:
+  release:
+    types: [published]
+
+permissions:
+  contents: read
+
+jobs:
+  release-build:
+    runs-on: ubuntu-latest
+
+    steps:
+      - uses: actions/checkout@v4
+        with:
+          fetch-depth: 0
+
+      - uses: actions/setup-python@v5
+        with:
+          python-version: "3.x"
+
+      - name: Verify PyPI version
+        run: |
+          python -m pip install setuptools-scm
+          VERSION="$(python -m setuptools_scm)"
+          echo "Derived version: $VERSION"
+          if [[ "$VERSION" == *".dev"* ]]; then
+            echo "PyPI publishing does not allow .dev versions." >&2
+            exit 1
+          fi
+
+      - name: Run tests
+        run: |
+          python -m pip install pytest
+          python -m pip install -e .
+          pytest
+
+      - name: Build release distributions
+        run: |
+          python -m pip install build
+          python -m build
+
+      - name: Smoke test built wheel
+        run: |
+          python -m venv .smoke-test-venv
+          source .smoke-test-venv/bin/activate
+          python -m pip install --upgrade pip
+          python -m pip install --no-deps dist/*.whl
+          python -c "import coding_agent_telegram"
+
+      - name: Upload distributions
+        uses: actions/upload-artifact@v4
+        with:
+          name: release-dists
+          path: dist/
+
+  pypi-publish:
+    runs-on: ubuntu-latest
+    needs:
+      - release-build
+    permissions:
+      # IMPORTANT: this permission is mandatory for trusted publishing
+      id-token: write
+
+    # Dedicated environments with protections for publishing are strongly recommended.
+    # For more information, see: https://docs.github.com/en/actions/deployment/targeting-different-environments/using-environments-for-deployment#deployment-protection-rules
+    environment:
+      name: pypi
+      # OPTIONAL: uncomment and update to include your PyPI project URL in the deployment status:
+      # url: https://pypi.org/p/YOURPROJECT
+      #
+      # ALTERNATIVE: if your GitHub Release name is the PyPI project version string
+      # ALTERNATIVE: exactly, uncomment the following line instead:
+      # url: https://pypi.org/project/YOURPROJECT/${{ github.event.release.name }}
+
+    steps:
+      - name: Retrieve release distributions
+        uses: actions/download-artifact@v4
+        with:
+          name: release-dists
+          path: dist/
+
+      - name: Publish release distributions to PyPI
+        uses: pypa/gh-action-pypi-publish@release/v1
+        with:
+          packages-dir: dist/

coding_agent_telegram-2026.3.27/.github/workflows/testpypi-publish.yml

@@ -0,0 +1,84 @@
+# This workflow will upload a Python package to TestPyPI for dev tags.
+
+name: Upload Python Package to TestPyPI
+
+on:
+  workflow_dispatch:
+  push:
+    tags:
+      - "v*.dev*"
+
+permissions:
+  contents: read
+
+jobs:
+  release-build:
+    runs-on: ubuntu-latest
+
+    steps:
+      - uses: actions/checkout@v4
+        with:
+          fetch-depth: 0
+
+      - uses: actions/setup-python@v5
+        with:
+          python-version: "3.x"
+
+      - name: Verify TestPyPI version
+        run: |
+          python -m pip install setuptools-scm
+          VERSION="$(python -m setuptools_scm)"
+          echo "Derived version: $VERSION"
+          if [[ "$VERSION" != *".dev"* ]]; then
+            echo "TestPyPI publishing requires a .dev version." >&2
+            exit 1
+          fi
+
+      - name: Run tests
+        run: |
+          python -m pip install pytest
+          python -m pip install -e .
+          pytest
+
+      - name: Build release distributions
+        run: |
+          python -m pip install build
+          python -m build
+
+      - name: Smoke test built wheel
+        run: |
+          python -m venv .smoke-test-venv
+          source .smoke-test-venv/bin/activate
+          python -m pip install --upgrade pip
+          python -m pip install --no-deps dist/*.whl
+          python -c "import coding_agent_telegram"
+
+      - name: Upload distributions
+        uses: actions/upload-artifact@v4
+        with:
+          name: release-dists
+          path: dist/
+
+  testpypi-publish:
+    runs-on: ubuntu-latest
+    needs:
+      - release-build
+    permissions:
+      id-token: write
+    environment:
+      name: testpypi
+      # OPTIONAL: uncomment and update to include your TestPyPI project URL in the deployment status:
+      # url: https://test.pypi.org/project/coding-agent-telegram/
+
+    steps:
+      - name: Retrieve release distributions
+        uses: actions/download-artifact@v4
+        with:
+          name: release-dists
+          path: dist/
+
+      - name: Publish release distributions to TestPyPI
+        uses: pypa/gh-action-pypi-publish@release/v1
+        with:
+          repository-url: https://test.pypi.org/legacy/
+          packages-dir: dist/

coding_agent_telegram-2026.3.27/.gitignore

@@ -0,0 +1,14 @@
+__pycache__/
+*.pyc
+.pytest_cache/
+.venv*/
+.env_*
+.env.*
+state.json
+state.json.lock
+state.json.tmp
+state.json.bak
+*.egg-info/
+logs/
+.codex
+.copilot

{coding_agent_telegram-2026.3.26/src/coding_agent_telegram.egg-info → coding_agent_telegram-2026.3.27}/PKG-INFO

@@ -1,8 +1,8 @@
 Metadata-Version: 2.4
 Name: coding-agent-telegram
-Version: 2026.3.26
+Version: 2026.3.27
 Summary: Telegram bot bridge for local coding agents (Codex/Copilot CLI)
-Author: Codex
+Author: DCHA
 License: MIT
 Requires-Python: >=3.9
 Description-Content-Type: text/markdown
@@ -89,15 +89,16 @@ cd coding-agent-telegram
 
 What `startup.sh` does:
 
-- creates `.env` from `src/coding_agent_telegram/resources/.env.example` if missing
+- creates `.env_coding_agent_telegram` from `src/coding_agent_telegram/resources/.env.example` if missing
+- falls back to legacy `.env` if it already exists
 - creates the state files if missing
 - creates `.venv` if missing
 - installs the package into the virtual environment
 - starts the Telegram bot server
 
-#### 3. Update `.env`
+#### 3. Update The Env File
 
-On first run, update the required fields in `.env`:
+On first run, update the required fields in `.env_coding_agent_telegram`:
 
 - `WORKSPACE_ROOT`
 - `TELEGRAM_BOT_TOKENS`
@@ -118,9 +119,10 @@ coding-agent-telegram
 
 What happens on first run:
 
-- the command creates `.env` in your current working directory if missing
+- the command creates `.env_coding_agent_telegram` in your current working directory if missing
+- if legacy `.env` already exists, it reuses that instead
 - it tells you which required fields to update
-- after updating `.env`, run `coding-agent-telegram` again
+- after updating the env file, run `coding-agent-telegram` again
 
 Recommended flow:
 
@@ -131,7 +133,7 @@ pip install coding-agent-telegram
 coding-agent-telegram
 ```
 
-Then update `.env` and run:
+Then update `.env_coding_agent_telegram` and run:
 
 ```bash
 coding-agent-telegram
@@ -157,7 +159,7 @@ If an unsupported message type is sent, the bot replies with a short error inste
 
 ## ⚙️ Environment Variables
 
-These are the main fields in `.env`.
+These are the main fields in the resolved env file, which defaults to `.env_coding_agent_telegram` and falls back to legacy `.env`.
 
 ### Required
 
@@ -282,7 +284,7 @@ GitHub documents these Copilot CLI approval controls here:
 - `ENABLE_SENSITIVE_DIFF_FILTER`
   Hide diffs for sensitive paths.
 
-### Example `.env` Snippet
+### Example Env Snippet
 
 ```env
 WORKSPACE_ROOT=~/git
@@ -376,7 +378,6 @@ _During each agent run, the bot also takes a lightweight before/after project sn
 
 - the app walks the project directory before and after the run
 - for normal text files, the app prefers the per-run snapshot diff rather than a git-head diff
-- `hidden files` and `hidden directories` are skipped by the snapshot walker by default, git-head diff will be used instead
 - common dependency, cache, and runtime directories are also skipped
 - binary files and files larger than `SNAPSHOT_TEXT_FILE_MAX_BYTES` are not loaded as text
 - for huge projects, this extra scan can add noticeable I/O and memory overhead
@@ -389,7 +390,18 @@ Snapshot exclusion rules live in package resource files:
 - `src/coding_agent_telegram/resources/snapshot_excluded_dir_globs.txt`
 - `src/coding_agent_telegram/resources/snapshot_excluded_file_globs.txt`
 
-If you want the snapshot diff to include hidden files or hidden directories, remove the `.*` rule from the relevant snapshot exclusion file and restart the bot.
+You can override those defaults in the env file without editing the installed package:
+
+- `SNAPSHOT_INCLUDE_PATH_GLOBS`
+  Force-include matching paths in diffs.
+  Example: `.github/*,.profile.test,.profile.prod`
+
+- `SNAPSHOT_EXCLUDE_PATH_GLOBS`
+  Add extra diff exclusions on top of the packaged defaults.
+  Example: `.*,personal/*,sensitive*.txt`
+  Note: `.*` matches hidden paths, including files inside hidden directories.
+
+If both include and exclude rules match, the include rule wins.
 
 ## 🌿 Branch Workflow
 
@@ -454,6 +466,14 @@ Typical logged events:
 - `pyproject.toml`
   Packaging and dependency configuration
 
+## 📦 Release Versioning
+
+Package versions are derived from Git tags.
+
+- TestPyPI/testing: `v2026.3.26.dev1`
+- PyPI prerelease: `v2026.3.26rc1`
+- PyPI stable: `v2026.3.26`
+
 ## 🛠️ Typical Local Flow
 
 ```bash

{coding_agent_telegram-2026.3.26 → coding_agent_telegram-2026.3.27}/README.md

@@ -75,15 +75,16 @@ cd coding-agent-telegram
 
 What `startup.sh` does:
 
-- creates `.env` from `src/coding_agent_telegram/resources/.env.example` if missing
+- creates `.env_coding_agent_telegram` from `src/coding_agent_telegram/resources/.env.example` if missing
+- falls back to legacy `.env` if it already exists
 - creates the state files if missing
 - creates `.venv` if missing
 - installs the package into the virtual environment
 - starts the Telegram bot server
 
-#### 3. Update `.env`
+#### 3. Update The Env File
 
-On first run, update the required fields in `.env`:
+On first run, update the required fields in `.env_coding_agent_telegram`:
 
 - `WORKSPACE_ROOT`
 - `TELEGRAM_BOT_TOKENS`
@@ -104,9 +105,10 @@ coding-agent-telegram
 
 What happens on first run:
 
-- the command creates `.env` in your current working directory if missing
+- the command creates `.env_coding_agent_telegram` in your current working directory if missing
+- if legacy `.env` already exists, it reuses that instead
 - it tells you which required fields to update
-- after updating `.env`, run `coding-agent-telegram` again
+- after updating the env file, run `coding-agent-telegram` again
 
 Recommended flow:
 
@@ -117,7 +119,7 @@ pip install coding-agent-telegram
 coding-agent-telegram
 ```
 
-Then update `.env` and run:
+Then update `.env_coding_agent_telegram` and run:
 
 ```bash
 coding-agent-telegram
@@ -143,7 +145,7 @@ If an unsupported message type is sent, the bot replies with a short error inste
 
 ## ⚙️ Environment Variables
 
-These are the main fields in `.env`.
+These are the main fields in the resolved env file, which defaults to `.env_coding_agent_telegram` and falls back to legacy `.env`.
 
 ### Required
 
@@ -268,7 +270,7 @@ GitHub documents these Copilot CLI approval controls here:
 - `ENABLE_SENSITIVE_DIFF_FILTER`
   Hide diffs for sensitive paths.
 
-### Example `.env` Snippet
+### Example Env Snippet
 
 ```env
 WORKSPACE_ROOT=~/git
@@ -362,7 +364,6 @@ _During each agent run, the bot also takes a lightweight before/after project sn
 
 - the app walks the project directory before and after the run
 - for normal text files, the app prefers the per-run snapshot diff rather than a git-head diff
-- `hidden files` and `hidden directories` are skipped by the snapshot walker by default, git-head diff will be used instead
 - common dependency, cache, and runtime directories are also skipped
 - binary files and files larger than `SNAPSHOT_TEXT_FILE_MAX_BYTES` are not loaded as text
 - for huge projects, this extra scan can add noticeable I/O and memory overhead
@@ -375,7 +376,18 @@ Snapshot exclusion rules live in package resource files:
 - `src/coding_agent_telegram/resources/snapshot_excluded_dir_globs.txt`
 - `src/coding_agent_telegram/resources/snapshot_excluded_file_globs.txt`
 
-If you want the snapshot diff to include hidden files or hidden directories, remove the `.*` rule from the relevant snapshot exclusion file and restart the bot.
+You can override those defaults in the env file without editing the installed package:
+
+- `SNAPSHOT_INCLUDE_PATH_GLOBS`
+  Force-include matching paths in diffs.
+  Example: `.github/*,.profile.test,.profile.prod`
+
+- `SNAPSHOT_EXCLUDE_PATH_GLOBS`
+  Add extra diff exclusions on top of the packaged defaults.
+  Example: `.*,personal/*,sensitive*.txt`
+  Note: `.*` matches hidden paths, including files inside hidden directories.
+
+If both include and exclude rules match, the include rule wins.
 
 ## 🌿 Branch Workflow
 
@@ -440,6 +452,14 @@ Typical logged events:
 - `pyproject.toml`
   Packaging and dependency configuration
 
+## 📦 Release Versioning
+
+Package versions are derived from Git tags.
+
+- TestPyPI/testing: `v2026.3.26.dev1`
+- PyPI prerelease: `v2026.3.26rc1`
+- PyPI stable: `v2026.3.26`
+
 ## 🛠️ Typical Local Flow
 
 ```bash

{coding_agent_telegram-2026.3.26 → coding_agent_telegram-2026.3.27}/pyproject.toml

@@ -1,15 +1,15 @@
 [build-system]
-requires = ["setuptools>=68", "wheel"]
+requires = ["setuptools>=68", "setuptools-scm>=8", "wheel"]
 build-backend = "setuptools.build_meta"
 
 [project]
 name = "coding-agent-telegram"
-version = "2026.03.26"
+dynamic = ["version"]
 description = "Telegram bot bridge for local coding agents (Codex/Copilot CLI)"
 readme = "README.md"
 requires-python = ">=3.9"
 license = { text = "MIT" }
-authors = [{ name = "Codex" }]
+authors = [{ name = "DCHA" }]
 dependencies = [
   "python-telegram-bot>=21.0,<22.0",
   "python-dotenv>=1.0.0,<2.0.0",
@@ -34,6 +34,11 @@ coding_agent_telegram = [
 [tool.setuptools.packages.find]
 where = ["src"]
 
+[tool.setuptools_scm]
+version_scheme = "no-guess-dev"
+local_scheme = "no-local-version"
+tag_regex = "^v(?P<version>.*)$"
+
 [tool.pytest.ini_options]
 testpaths = ["tests"]
 addopts = "-q"

coding_agent_telegram-2026.3.27/src/coding_agent_telegram/__init__.py

@@ -0,0 +1 @@
+"""coding_agent_telegram package."""