downbeat 0.1.1__tar.gz

downbeat-0.1.1/.github/ISSUE_TEMPLATE/bug_report.yml

@@ -0,0 +1,69 @@
+name: Bug report
+description: Something isn't working as expected
+labels: ["bug"]
+body:
+  - type: dropdown
+    id: surface
+    attributes:
+      label: Which surface is affected?
+      options:
+        - TUI
+        - CLI
+        - Library (importing downbeat directly)
+        - Claude Code skill / hooks / slash-commands
+        - Packaging / install (init, uninstall)
+        - Other / not sure
+    validations:
+      required: true
+
+  - type: input
+    id: version
+    attributes:
+      label: Version
+      description: Output of `downbeat --version`
+      placeholder: "downbeat 0.1.0"
+    validations:
+      required: true
+
+  - type: textarea
+    id: what-happened
+    attributes:
+      label: What happened?
+      description: A clear description of the bug. Include exact commands/keystrokes if relevant.
+    validations:
+      required: true
+
+  - type: textarea
+    id: expected
+    attributes:
+      label: What did you expect to happen?
+    validations:
+      required: false
+
+  - type: textarea
+    id: repro
+    attributes:
+      label: Steps to reproduce
+      placeholder: |
+        1. `downbeat register foo --role parent`
+        2. `downbeat send bar hi hello`
+        3. ...
+    validations:
+      required: false
+
+  - type: textarea
+    id: logs
+    attributes:
+      label: Relevant logs / output
+      description: Run with `--debug` if possible. Paste terminal output; no need for backticks, it will be auto-formatted.
+      render: shell
+    validations:
+      required: false
+
+  - type: input
+    id: os
+    attributes:
+      label: OS + Python version
+      placeholder: "macOS 15, Python 3.12"
+    validations:
+      required: false

downbeat-0.1.1/.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,5 @@
+blank_issues_enabled: false
+contact_links:
+  - name: Feature request / idea
+    url: https://github.com/FreddieMcHeart/downbeat/discussions
+    about: Feature requests and ideas start as a Discussion, not an Issue — this lets us talk through scope before committing to it.

downbeat-0.1.1/.github/workflows/ci.yml

@@ -0,0 +1,18 @@
+name: ci
+on: [push, pull_request]
+jobs:
+  test:
+    runs-on: ${{ matrix.os }}
+    strategy:
+      fail-fast: false
+      matrix:
+        os: [ubuntu-latest, macos-latest]
+        python: ["3.11", "3.12", "3.13"]
+    steps:
+      - uses: actions/checkout@v4
+      - uses: astral-sh/setup-uv@v5
+        with:
+          python-version: ${{ matrix.python }}
+      - run: uv sync --locked --extra dev
+      - run: uv run ruff check .
+      - run: uv run pytest -q

downbeat-0.1.1/.github/workflows/release.yml

@@ -0,0 +1,71 @@
+name: release
+on:
+  push:
+    branches: [main]
+
+# NOTE: this workflow trusts that `main` only receives commits that already
+# passed ci.yml (via required-status-checks branch protection on GitHub —
+# configure that in repo Settings → Branches; cannot be set from a workflow
+# file). It does not re-run tests itself.
+
+permissions:
+  contents: read
+
+jobs:
+  release:
+    runs-on: ubuntu-latest
+    concurrency: release
+    permissions:
+      contents: write   # to push the version-bump commit, changelog, and tag
+    outputs:
+      released: ${{ steps.release.outputs.released }}
+      tag: ${{ steps.release.outputs.tag }}
+    steps:
+      - uses: actions/checkout@v4
+        with:
+          fetch-depth: 0
+          persist-credentials: true
+          # PAT, not the default GITHUB_TOKEN: main's branch ruleset requires
+          # all 6 ci.yml status checks and only bypasses RepositoryRole:Admin.
+          # The actual `git push` of the version-bump commit happens via the
+          # credentials persisted HERE (by actions/checkout), regardless of
+          # what token the semantic-release action below is given — the bot
+          # identity behind GITHUB_TOKEN isn't covered by the bypass and gets
+          # GH013-rejected. See docs/release-setup.md Step 4.
+          token: ${{ secrets.RELEASE_TOKEN }}
+      # NOTE: no setup-uv step here — this action runs build_command inside
+      # its OWN Docker container, isolated from the runner's PATH, so
+      # installing uv on the host has no effect. See build_command in
+      # pyproject.toml's [tool.semantic_release] for how uv gets installed
+      # where it's actually needed (inside the container).
+      - name: Python Semantic Release
+        id: release
+        uses: python-semantic-release/python-semantic-release@v9
+        with:
+          github_token: ${{ secrets.RELEASE_TOKEN }}
+
+  publish:
+    needs: release
+    if: needs.release.outputs.released == 'true'
+    runs-on: ubuntu-latest
+    # Requires a "pypi" environment configured in repo Settings → Environments,
+    # with a Trusted Publisher registered on pypi.org for this repo + workflow
+    # (org/repo, workflow filename "release.yml", environment "pypi"). Manual,
+    # one-time, PyPI-web-console setup — cannot be done from this workflow.
+    environment:
+      name: pypi
+      url: https://pypi.org/project/downbeat/
+    permissions:
+      contents: read   # needed for actions/checkout — a job-level `permissions:`
+      # block zeroes every unlisted scope (repo is private, so checkout without
+      # this 404s as "Repository not found" rather than 403 — GitHub hides
+      # private-repo existence from tokens that can't read it)
+      id-token: write   # OIDC token exchange for Trusted Publishing — no API token stored
+    steps:
+      - uses: actions/checkout@v4
+        with:
+          ref: main   # semantic-release already pushed the version-bump commit here
+      - uses: astral-sh/setup-uv@v5
+      - run: uv build
+      - name: Publish to PyPI (Trusted Publishing)
+        run: uv publish

downbeat-0.1.1/.gitignore

@@ -0,0 +1,11 @@
+__pycache__/
+*.py[cod]
+.venv/
+.pytest_cache/
+.ruff_cache/
+dist/
+build/
+*.egg-info/
+.coverage
+.textual_dev/
+.DS_Store

downbeat-0.1.1/.pre-commit-config.yaml

@@ -0,0 +1,12 @@
+# Enforces Conventional Commits on every commit message — required because
+# version bumps, CHANGELOG generation, and PyPI releases (semantic-release,
+# see pyproject.toml [tool.semantic_release]) are all derived from commit
+# history. See CONTRIBUTING.md.
+#
+# Install once per checkout: `uv run pre-commit install --hook-type commit-msg`
+repos:
+  - repo: https://github.com/compilerla/conventional-pre-commit
+    rev: v3.4.0
+    hooks:
+      - id: conventional-pre-commit
+        stages: [commit-msg]