bc-cli 0.1.0__tar.gz

bc_cli-0.1.0/.claude/settings.local.json

@@ -0,0 +1,12 @@
+{
+  "enableAllProjectMcpServers": true,
+  "enabledMcpjsonServers": [
+    "bc-proxy"
+  ],
+  "permissions": {
+    "allow": [
+      "Bash(~/.claude/skills/gstack/bin/gstack-config set *)",
+      "Bash(touch ~/.claude/skills/gstack/.feature-prompted-continuous-checkpoint)"
+    ]
+  }
+}

bc_cli-0.1.0/.env.example

@@ -0,0 +1,5 @@
+# Business Central API credentials
+# Referenced by client_secret_env in ~/.config/bcapi/config.toml
+BCAPI_SECRET=your-client-secret-here
+BCAPI_PROD_SECRET=your-production-secret-here
+BCAPI_SANDBOX_SECRET=your-sandbox-secret-here

bc_cli-0.1.0/.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,39 @@
+---
+name: Bug report
+about: Report a problem with bcli
+title: "[bug] "
+labels: bug
+---
+
+## Description
+
+What's the unexpected behavior?
+
+## Reproduction
+
+Minimal steps to reproduce:
+
+1.
+2.
+3.
+
+## Expected vs. Actual
+
+**Expected:**
+
+**Actual:**
+
+## Environment
+
+- bcli version: `bcli --version`
+- Python version: `python --version`
+- OS:
+- BC environment: (Production / Sandbox / ...)
+
+## Logs / Stack trace
+
+```
+paste relevant output here
+```
+
+## Additional context

bc_cli-0.1.0/.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,20 @@
+---
+name: Feature request
+about: Suggest a new capability for bcli
+title: "[feat] "
+labels: enhancement
+---
+
+## Problem
+
+What are you trying to do, and why is it hard today?
+
+## Proposed solution
+
+What would make this easier? CLI command, SDK method, config option, etc.
+
+## Alternatives considered
+
+Any workarounds you've tried.
+
+## Additional context

bc_cli-0.1.0/.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,23 @@
+## Summary
+
+What does this PR do, in one or two sentences?
+
+## Changes
+
+- 
+- 
+
+## Test plan
+
+- [ ] `uv run pytest tests/ -v` passes
+- [ ] `uv run ruff check src/ tests/` is clean
+- [ ] Added / updated tests for new behavior
+- [ ] Manual testing notes:
+
+## Breaking changes
+
+Any? If so, what's the migration path?
+
+## Related issues
+
+Closes #

bc_cli-0.1.0/.github/workflows/tests.yml

@@ -0,0 +1,50 @@
+name: Tests
+
+on:
+  push:
+    branches: [main]
+  pull_request:
+    branches: [main]
+
+# Default to read-only — every job must opt in to anything writeable.
+# Without this, GITHUB_TOKEN inherits the repo-wide default (often
+# write-all on older repos), which gives anyone who can land a PR an
+# overly permissive token if they trick a workflow step.
+permissions:
+  contents: read
+
+jobs:
+  test:
+    runs-on: ubuntu-latest
+    permissions:
+      contents: read
+    strategy:
+      fail-fast: false
+      matrix:
+        python-version: ["3.11", "3.12", "3.13"]
+
+    steps:
+      # Third-party actions are pinned by full commit SHA, not a moving
+      # tag like @v4. The trailing comment names the human-readable tag
+      # so a maintainer can audit the version without resolving SHAs.
+      # Bumping requires checking the new SHA against the upstream
+      # release notes and updating both fields together.
+      - uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683  # v4.2.2
+
+      - name: Install uv
+        uses: astral-sh/setup-uv@d4b2f3b6ecc6e67c4457f6d3e41ec42d3d0fcb86  # v5
+        with:
+          enable-cache: true
+          python-version: ${{ matrix.python-version }}
+
+      - name: Install dependencies (locked)
+        # `--locked` requires uv.lock to be committed and exactly match the
+        # current pyproject.toml, so CI is reproducible from the lockfile
+        # under code review rather than re-resolving versions on every run.
+        run: uv sync --locked --extra dev --extra etl
+
+      - name: Lint with ruff
+        run: uv run ruff check src/ tests/
+
+      - name: Run tests
+        run: uv run pytest tests/ -v

bc_cli-0.1.0/.gitignore

@@ -0,0 +1,34 @@
+__pycache__/
+*.py[cod]
+*$py.class
+*.egg-info/
+dist/
+build/
+.eggs/
+*.egg
+.venv/
+venv/
+.env
+.env.local
+# Note: uv.lock IS committed (used by `uv sync --locked` in CI for
+# reproducible builds). Other ad-hoc *.lock files (e.g. .dotnet) are
+# still ignored.
+.pytest_cache/
+.ruff_cache/
+.mypy_cache/
+htmlcov/
+.coverage
+*.log
+.DS_Store
+
+# dlt pipeline state and secrets
+.dlt/
+*.duckdb
+*.duckdb.wal
+TRASH/
+TRASH-FILES.md
+
+# Internal planning docs (not part of OSS release)
+PRD-*.md
+TODOS.md
+bcapi_cli_prd.md