call-copilot 0.2.0__tar.gz

call_copilot-0.2.0/.github/workflows/ci.yml

@@ -0,0 +1,45 @@
+name: CI
+
+on:
+  push:
+    branches: [main]
+  pull_request:
+    branches: [main]
+
+# Cancel in-flight runs for the same ref when a new commit is pushed.
+concurrency:
+  group: ${{ github.workflow }}-${{ github.ref }}
+  cancel-in-progress: true
+
+jobs:
+  test:
+    name: Test (Python ${{ matrix.python-version }})
+    # audiotap is macOS-only (Core Audio process taps), so the editable install
+    # would fail on Linux before a single test runs. The test suite itself is
+    # offline and mocks audiotap / faster-whisper, so no audio device or model
+    # download is needed.
+    runs-on: macos-latest
+    strategy:
+      fail-fast: false
+      matrix:
+        python-version: ["3.11", "3.12", "3.13"]
+
+    steps:
+      - uses: actions/checkout@v4
+
+      - name: Set up Python ${{ matrix.python-version }}
+        uses: actions/setup-python@v5
+        with:
+          python-version: ${{ matrix.python-version }}
+          cache: pip
+
+      - name: Install package and dev dependencies
+        run: |
+          python -m pip install --upgrade pip
+          pip install -e ".[dev]"
+
+      - name: Lint with ruff
+        run: ruff check .
+
+      - name: Run tests
+        run: python -m pytest tests -v

call_copilot-0.2.0/.github/workflows/release.yml

@@ -0,0 +1,103 @@
+name: Release
+
+# Publishes to PyPI when a `v*` tag is pushed. Uses PyPI Trusted Publishing
+# (OIDC) — no API token stored in repo secrets. Configure the trusted publisher
+# once on PyPI (see docs/HOMEBREW.md / repo settings):
+#   PyPI project → Publishing → Add a publisher
+#     Environment: release
+#     Workflow:    .github/workflows/release.yml
+#     GitHub repo: AnisurRahmann/call-copilot
+
+on:
+  push:
+    tags:
+      - "v*"
+
+# One release at a time per tag; never cancel a publish mid-flight.
+concurrency:
+  group: release-${{ github.ref }}
+  cancel-in-progress: false
+
+# The OIDC token needs these permissions to be issued by GitHub.
+permissions:
+  id-token: write
+  contents: read
+
+jobs:
+  build:
+    name: Build sdist + wheel
+    runs-on: macos-latest
+    # Trusted Publishing scopes the publish to this environment name; it must
+    # match the environment configured on the PyPI project.
+    environment: release
+    steps:
+      - uses: actions/checkout@v4
+
+      - name: Set up Python 3.12
+        uses: actions/setup-python@v5
+        with:
+          python-version: "3.12"
+          cache: pip
+
+      # Run the test suite on the exact tag we're publishing, so a broken
+      # release can never reach PyPI. Install with dev extras for pytest/ruff.
+      - name: Install package + dev dependencies
+        run: |
+          python -m pip install --upgrade pip
+          pip install -e ".[dev]"
+          pip install build
+
+      - name: Lint
+        run: ruff check .
+
+      - name: Run tests
+        run: python -m pytest tests -v
+
+      - name: Build sdist + wheel
+        run: python -m build
+
+      # A quick sanity check that the just-built wheel installs cleanly and the
+      # console script is present — catches packaging regressions before upload.
+      - name: Verify the wheel installs and exposes `rec`
+        run: |
+          pip install --force-reinstall dist/*.whl
+          rec --version
+
+      - name: Upload build artifacts
+        uses: actions/upload-artifact@v4
+        with:
+          name: dist
+          path: dist/
+          if-no-files-found: error
+          retention-days: 7
+
+  publish:
+    name: Publish to PyPI
+    needs: build
+    runs-on: ubuntu-latest
+    environment: release
+    steps:
+      - name: Download build artifacts
+        uses: actions/download-artifact@v4
+        with:
+          name: dist
+          path: dist/
+
+      # Trusted Publishing: no password/token. pypa/gh-action-pypi-publish
+      # exchanges the OIDC token issued by GitHub for a short-lived PyPI upload
+      # credential scoped to this exact workflow + environment.
+      - name: Publish to PyPI
+        uses: pypa/gh-action-pypi-publish@release/v1
+        with:
+          # `skip-existing` avoids a hard failure if the same version is
+          # re-pushed (e.g. re-running a partially-failed release). PyPI never
+          # overwrites a file — it just skips the duplicate.
+          skip-existing: true
+
+      - name: Create GitHub Release
+        uses: softprops/action-gh-release@v2
+        with:
+          generate_release_notes: true
+          files: |
+            dist/*.whl
+            dist/*.tar.gz

call_copilot-0.2.0/CODE_OF_CONDUCT.md

@@ -0,0 +1,133 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our
+community a harassment-free experience for everyone, regardless of age, body
+size, visible or invisible disability, ethnicity, sex characteristics, gender
+identity and expression, level of experience, education, socio-economic status,
+nationality, personal appearance, race, caste, color, religion, or sexual identity
+and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming,
+diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our
+community include:
+
+* Demonstrating empathy and kindness toward other people
+* Being respectful of differing opinions, viewpoints, and experiences
+* Giving and gracefully accepting constructive feedback
+* Accepting responsibility and apologizing to those affected by our mistakes,
+  and learning from the experience
+* Focusing on what is best not just for us as individuals, but for the
+  overall community
+
+Examples of unacceptable behavior include:
+
+* The use of sexualized language or imagery, and sexual attention or
+  advances of any kind
+* Trolling, insulting or derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or email
+  address, without their explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of
+acceptable behavior and will take appropriate and fair corrective action in
+response to any behavior that they deem inappropriate, threatening, offensive,
+or harmful.
+
+Community leaders have the right and responsibility to remove, edit, or reject
+comments, commits, code, wiki edits, issues, and other contributions that are
+not aligned to this Code of Conduct, and will communicate reasons for moderation
+decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when
+an individual is officially representing the community in public spaces.
+Examples of representing our community include using an official email address,
+posting via an official social media account, or acting as an appointed
+representative at an online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported to the community maintainer responsible for enforcement at
+**pshakilwizard@gmail.com**.
+
+All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the
+reporter of any incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining
+the consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed
+unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders, providing
+clarity around the nature of the violation and an explanation of why the
+behavior was inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series
+of actions.
+
+**Consequence**: A warning with consequences for continued behavior. No
+interaction with the people involved, including unsolicited interaction with
+those enforcing the Code of Conduct, for a specified period of time. This
+includes avoiding interactions in community spaces as well as external channels
+like social media. Violating these terms may lead to a temporary or
+permanent ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including
+sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public
+communication with the community for a specified period of time. No public or
+private interaction with the people involved, including unsolicited interaction
+with those enforcing the Code of Conduct, is allowed during this period.
+Violating these terms may lead to a permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community
+standards, including sustained inappropriate behavior, harassment of an
+individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within
+the community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage],
+version 2.1, available at
+[https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1].
+
+Community Impact Guidelines were inspired by
+[Mozilla's code of conduct enforcement ladder][Mozilla CoC].
+
+For answers to common questions about this code of conduct, see the FAQ at
+[https://www.contributor-covenant.org/faq][FAQ]. Translations are available at
+[https://www.contributor-covenant.org/translations][translations].
+
+[homepage]: https://www.contributor-covenant.org
+[v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html
+[Mozilla CoC]: https://github.com/mozilla/diversity
+[FAQ]: https://www.contributor-covenant.org/faq
+[translations]: https://www.contributor-covenant.org/translations

call_copilot-0.2.0/CONTRIBUTING.md

@@ -0,0 +1,84 @@
+# Contributing to Call Copilot
+
+Thanks for your interest in Call Copilot! This project is small and focused — a
+terminal meeting recorder for macOS that transcribes locally. The easiest way to
+help is one of these:
+
+1. **File an issue** for a bug, a missing feature, or a doc gap.
+2. **Open a pull request** for a concrete fix. Small, focused PRs land fastest.
+
+## Project scope
+
+Call Copilot deliberately does one thing: record meeting audio and produce a clean
+local transcript. It is **not** aiming to become a meeting summarizer, a calendar
+integrator, or a cloud product. If your change broadens the scope, open an issue to
+discuss it before investing in a PR — it may be a better fit as a separate tool.
+
+## Development setup
+
+You need **macOS 14.2+** (the `audiotap` dependency uses Core Audio process taps,
+which is macOS-only) and **Python 3.11+**.
+
+```bash
+git clone https://github.com/AnisurRahmann/call-copilot.git
+cd call-copilot
+make install          # creates .venv and installs the package + dev deps (editable)
+```
+
+## Running the tests
+
+```bash
+make test             # == .venv/bin/python -m pytest tests -v
+```
+
+The suite is **fully offline**: no audio device, no microphone permission, and no
+Whisper model download is required. It mocks `audiotap`, `faster-whisper`, and the
+filesystem, so it runs on any macOS box (including CI) without setup. Expect **89
+passing** on a clean tree.
+
+> The tests pass anywhere, but running the actual `rec` commands still requires
+> macOS 14.2+ with capture permissions granted.
+
+## Code style
+
+- **Lint:** [ruff](https://docs.astral.sh/ruff/) is configured in `pyproject.toml`
+  (`target-version = "py311"`, `line-length = 100`). Run `ruff check .` before
+  pushing; CI enforces it.
+- **Python:** 3.11+. New code may use modern syntax (`X | None`, `match`, etc.).
+- Match the surrounding style — module docstrings, `from __future__ import
+  annotations`, type hints, and `log.debug/info/warning` via the `log.py` helper.
+
+## Pull requests
+
+1. **Branch** off `main`. Use a descriptive name: `feat/...`, `fix/...`, `docs/...`.
+2. **Keep it focused.** One logical change per PR; put unrelated work in separate PRs.
+3. **Add or update tests** for any behavior change. The test suite is the contract.
+4. **Run the gate locally** before pushing:
+   ```bash
+   make test
+   .venv/bin/ruff check .
+   ```
+5. **Reference the issue** your PR addresses in the description (e.g. `Closes #12`).
+6. Be patient and kind. This is a small project; review may take a few days.
+
+If a change touches audio capture, transcription output, or the session file format,
+call that out explicitly in the PR description — those are the load-bearing parts.
+
+## Reporting bugs
+
+Open an [issue](https://github.com/AnisurRahmann/call-copilot/issues) and include:
+
+- macOS version and chip (Intel / Apple Silicon).
+- Python version (`python3 --version`).
+- The exact `rec` command(s) you ran and the flags used.
+- The output of `rec diagnose <session-id> --stdout` (it bundles logs + metadata
+  without including the audio itself).
+
+## Security issues
+
+Do **not** open a public issue for security problems. See [SECURITY.md](SECURITY.md)
+for private reporting.
+
+## Code of conduct
+
+By participating you agree to uphold the [Code of Conduct](CODE_OF_CONDUCT.md).

call_copilot-0.2.0/LICENSE

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

call_copilot-0.2.0/MANIFEST.in

@@ -0,0 +1,11 @@
+# Include docs + metadata in the source distribution (sdist). The wheel only
+# needs the Python package under src/; the sdist also carries README, LICENSE,
+# the Homebrew formula, and the release docs so the package is self-describing.
+include README.md
+include LICENSE
+include CONTRIBUTING.md
+include SECURITY.md
+include CODE_OF_CONDUCT.md
+include Makefile
+recursive-include docs *.md
+recursive-include .github *.yml

call_copilot-0.2.0/Makefile

@@ -0,0 +1,60 @@
+.PHONY: install test build run run-verbose list status logs diagnose clean help
+
+PYTHON := .venv/bin/python
+PIP    := .venv/bin/pip
+REC    := .venv/bin/rec
+
+help:
+	@echo "rec — meeting recorder"
+	@echo "  make install       create venv + install dev deps"
+	@echo "  make test          run unit tests"
+	@echo "  make build         build sdist + wheel into dist/ (for release)"
+	@echo "  make run           rec start"
+	@echo "  make run-verbose   rec -v start (INFO logs on stderr)"
+	@echo "  make list          rec list"
+	@echo "  make status        rec status"
+	@echo "  make logs          tail -f the global log"
+	@echo "  make diagnose      rec diagnose <latest> --stdout (bundle for AI debugging)"
+	@echo "  make clean         remove build artifacts"
+
+install: .venv
+	$(PIP) install -e ".[dev]"
+
+.venv:
+	python3.11 -m venv .venv
+	$(PIP) install --upgrade pip
+
+test:
+	$(PYTHON) -m pytest tests -v
+
+# Build the publishable sdist + wheel. `build` is a dev-only tool (not a
+# runtime dependency), so install it here if the editable env lacks it.
+build:
+	$(PIP) install --quiet build >/dev/null
+	$(PYTHON) -m build
+
+run:
+	$(REC) start
+
+run-verbose:
+	$(REC) -v start
+
+list:
+	$(REC) list
+
+status:
+	$(REC) status
+
+logs:
+	@echo "Tailing ~/.local/share/rec/logs/rec.log (Ctrl+C to stop)"
+	@tail -f ~/.local/share/rec/logs/rec.log
+
+diagnose:
+	@echo "Bundling debug info for the most recent session..."
+	@latest=$$(ls -1 ~/.local/share/rec/sessions/ 2>/dev/null | tail -1); \
+	if [ -z "$$latest" ]; then echo "No sessions found."; exit 1; fi; \
+	$(REC) diagnose "$$latest" --stdout
+
+clean:
+	rm -rf build dist *.egg-info .pytest_cache .mypy_cache
+	find . -type d -name __pycache__ -exec rm -rf {} +