freelancer-payment-protection-cli 0.1.0__tar.gz

freelancer_payment_protection_cli-0.1.0/.gitignore

@@ -0,0 +1,50 @@
+# Dependencies
+node_modules/
+.pnp
+.pnp.js
+
+# Build outputs
+.next/
+.turbo/
+dist/
+build/
+out/
+
+# Environment files — NEVER commit real secrets
+.env
+.env.local
+.env.*.local
+*.env
+
+# Python
+__pycache__/
+*.pyc
+*.pyo
+.venv/
+venv/
+*.egg-info/
+.pytest_cache/
+htmlcov/
+.coverage
+coverage.xml
+
+# Local dev databases — no credentials in these
+*.db
+*.sqlite
+*.sqlite3
+
+# OS
+.DS_Store
+Thumbs.db
+
+# IDE
+.idea/
+.vscode/settings.json
+*.swp
+
+# Reference docs (local strategy docs — not for public repo)
+reference-docs-context/
+
+# Generated PDFs / docs (created at runtime)
+generated-docs/
+tmp/

freelancer_payment_protection_cli-0.1.0/LICENSE

@@ -0,0 +1,35 @@
+Copyright (c) 2026 Rudrendu Paul and Sourav Nandy. All rights reserved.
+
+PROPRIETARY LICENSE
+
+This software and associated documentation files (the "Software") are the
+exclusive intellectual property of Rudrendu Paul and Sourav Nandy
+("the Owners").
+
+RESTRICTIONS
+
+1. No use, copying, modification, merging, publishing, distribution,
+   sublicensing, or selling of this Software — in whole or in part — is
+   permitted without prior written approval from both Owners.
+
+2. Any personal, academic, commercial, or scheduled use of this Software
+   requires explicit written permission obtained directly from:
+
+       Rudrendu Paul   — https://github.com/RudrenduPaul
+       Sourav Nandy    — (contact via Rudrendu Paul)
+
+3. Unauthorized use of this Software for any purpose, including but not
+   limited to building competing products, white-labeling, or redistribution,
+   is strictly prohibited and may result in legal action.
+
+TO REQUEST PERMISSION
+
+Submit a written request describing your intended use to the Owners. Approval
+is granted solely at the discretion of both Owners and may be subject to
+additional terms or a commercial licensing agreement.
+
+DISCLAIMER
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED. IN NO EVENT SHALL THE OWNERS BE LIABLE FOR ANY CLAIM, DAMAGES, OR
+OTHER LIABILITY ARISING FROM THE USE OF OR INABILITY TO USE THE SOFTWARE.

freelancer_payment_protection_cli-0.1.0/PKG-INFO

@@ -0,0 +1,246 @@
+Metadata-Version: 2.4
+Name: freelancer-payment-protection-cli
+Version: 0.1.0
+Summary: Command-line client for freelancer-payment-protection: automated invoice escalation, legal document generation, and client risk scoring for freelancers.
+Project-URL: Homepage, https://github.com/RudrenduPaul/freelancer-payment-protection
+Project-URL: Repository, https://github.com/RudrenduPaul/freelancer-payment-protection
+Project-URL: Bug Tracker, https://github.com/RudrenduPaul/freelancer-payment-protection/issues
+Author: Rudrendu Paul, Sourav Nandy
+License: Proprietary
+License-File: LICENSE
+Keywords: agent-native,cli,fastapi,freelance,invoice-escalation,invoicing,risk-scoring,supabase
+Classifier: Development Status :: 3 - Alpha
+Classifier: Environment :: Console
+Classifier: Intended Audience :: Developers
+Classifier: Operating System :: OS Independent
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.10
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Topic :: Office/Business :: Financial :: Accounting
+Classifier: Topic :: Utilities
+Requires-Python: >=3.10
+Requires-Dist: click<9,>=8.1
+Requires-Dist: httpx<1,>=0.27
+Provides-Extra: dev
+Requires-Dist: build<2,>=1.0; extra == 'dev'
+Requires-Dist: pytest-cov<7,>=5.0; extra == 'dev'
+Requires-Dist: pytest<9,>=8.0; extra == 'dev'
+Requires-Dist: respx<1,>=0.21; extra == 'dev'
+Requires-Dist: twine<7,>=5.0; extra == 'dev'
+Description-Content-Type: text/markdown
+
+# freelancer-payment-protection-cli
+
+Command-line client for [freelancer-payment-protection](https://github.com/RudrenduPaul/freelancer-payment-protection):
+automated invoice escalation, legal document generation, and client risk
+scoring for freelancers. This package wraps the project's FastAPI backend
+(`apps/api/app/routers/*.py`) so the same clients, invoices, escalations,
+and risk-scoring data you'd otherwise reach through the dashboard or the
+raw HTTP API is scriptable from a terminal or an agent.
+
+![Login and first command](../../docs/demo.gif)
+
+## Install
+
+```bash
+pip install freelancer-payment-protection-cli
+```
+
+Or with [uv](https://docs.astral.sh/uv/) / [pipx](https://pipx.pypa.io/):
+
+```bash
+uvx freelancer-payment-protection-cli --help
+pipx install freelancer-payment-protection-cli
+```
+
+Requires Python 3.10+. The console command is installed as both `fpp`
+(short form) and `freelancer-payment-protection` (full form) — they are the
+same entry point.
+
+## Configuration
+
+The CLI needs to know two things: which backend API to talk to, and which
+Supabase project issues your login tokens.
+
+| Variable | Purpose | Default |
+|---|---|---|
+| `FPP_API_URL` | Backend API base URL | `http://localhost:8000` |
+| `FPP_SUPABASE_URL` (or `SUPABASE_URL`) | Your Supabase project URL | none, required for `login` |
+| `FPP_SUPABASE_ANON_KEY` (or `SUPABASE_ANON_KEY`) | Your Supabase project's anon key | none, required for `login` |
+
+The anon key is the same public key the web app's Supabase client uses —
+it is not a secret, and it's the key already in `apps/web/.env.example` as
+`NEXT_PUBLIC_SUPABASE_ANON_KEY`.
+
+## Login and authentication
+
+```bash
+export FPP_SUPABASE_URL="https://your-project.supabase.co"
+export FPP_SUPABASE_ANON_KEY="your-anon-key"
+fpp login
+```
+
+`fpp login` prompts for your email and password, then calls Supabase's own
+REST auth endpoint directly:
+
+```
+POST {SUPABASE_URL}/auth/v1/token?grant_type=password
+Header: apikey: <anon key>
+Body:   {"email": ..., "password": ...}
+```
+
+This is the same call the web dashboard's Supabase client makes — the CLI
+never talks to a login endpoint of its own, because the backend
+(`apps/api/app/middleware/auth.py`) doesn't mint tokens; it only validates
+Supabase-issued JWTs. On success, the returned `access_token` and
+`refresh_token` are cached to `~/.config/freelancer-payment-protection-cli/credentials.json`
+(mode 600). Every later command reads the JWT's `workspace_id` claim the
+same way `get_current_workspace()` does server-side, and transparently
+refreshes the access token with the cached refresh token once it expires.
+
+Run `fpp logout` to delete the cached credentials, or `fpp whoami` to see
+which workspace and email the cached token resolves to.
+
+## Commands
+
+Every data-returning command supports `--json` for scripting and agent use.
+
+```
+fpp login                                   Log in (prompts for email/password)
+fpp logout                                  Remove cached credentials
+fpp whoami [--json]                         Show cached workspace/session info
+
+fpp invoice list [--status] [--client-id] [--page] [--page-size] [--json]
+fpp invoice create --client-id --invoice-number --amount --due-date [...] [--json]
+fpp invoice show <invoice-id> [--json]
+fpp invoice set-status <invoice-id> <status> [--json]
+
+fpp escalation list [--json]                Active escalations, grouped by stage
+fpp escalation status <invoice-id> [--json] Current stage + full history
+fpp escalation advance <invoice-id> [--json] AI-draft the next stage's email
+
+fpp client list [--risk-level] [--search] [--page] [--page-size] [--json]
+fpp client show <client-id> [--json]
+fpp client risk <client-id> [--json]        Compute/refresh the AI risk score
+```
+
+Run `fpp --help` or `fpp <command> --help` for full flag references.
+
+![Filtering invoices, scoring a client, and checking escalation status](../../docs/usage.gif)
+
+### A note on `escalation advance`
+
+The backend's escalation router (`apps/api/app/routers/escalations.py`)
+exposes exactly three routes: list active escalations, draft the next
+stage's email, and read history. There is no route that persists a stage
+change — `draft_escalation_email` in `escalation_service.py` computes and
+returns what the next stage's email would say, but never writes
+`escalation_stage` back to the database. `fpp escalation advance` calls
+that draft endpoint and shows you the preview; it does not claim to move
+the invoice to the next stage, because the API it wraps doesn't do that
+either.
+
+### JSON output for agents/scripts
+
+```bash
+fpp invoice list --status overdue --json | jq '.[] | {id, invoiceNumber, daysPastDue}'
+fpp client risk "$CLIENT_ID" --json | jq '.level'
+```
+
+Field names in `--json` output match the backend's actual Pydantic response
+models exactly (camelCase, e.g. `invoiceNumber`, `daysPastDue`,
+`escalationStage`) since the CLI passes the API's response straight
+through rather than remapping it.
+
+## FAQ
+
+**What is this, and how is it different from just calling the API with curl?**
+It's a typed command-line wrapper around the same backend the web
+dashboard uses — invoices, escalations, and client risk scoring — with
+persistent login (so you're not re-attaching a bearer token to every
+request), human-readable tables by default, and a `--json` flag on every
+data command for piping into `jq`, scripts, or an agent's tool-calling
+loop. The differentiator versus curl is session handling (login once,
+silent token refresh after) and consistent, documented output shapes
+instead of hand-rolled request construction.
+
+**What platforms and Python versions does it support?**
+Python 3.10 through 3.13, on any OS `pip`/`uvx`/`pipx` runs on (Linux,
+macOS, Windows). It has no compiled dependencies — the only runtime
+dependencies are `click` and `httpx`, both pure-Python-installable wheels.
+
+**How do I log in, and where are my credentials stored?**
+Run `fpp login`, enter your email and password when prompted. The CLI
+calls Supabase's password-grant token endpoint directly (see "Login and
+authentication" above) and caches the resulting access and refresh tokens
+to `~/.config/freelancer-payment-protection-cli/credentials.json` with
+file mode 600 (owner read/write only). Nothing is sent anywhere except
+Supabase's own auth endpoint and the backend API you configure via
+`FPP_API_URL`.
+
+**I ran a command and got `Error: Internal Server Error` — is that a CLI bug?**
+Usually not. The CLI's error handling surfaces whatever the backend
+returned; a 500 means the backend itself failed. Two real, backend-side
+causes to check first: (1) `fpp client risk` and `fpp escalation advance`
+both trigger AI calls through `packages/legal_ai/client.py` — if
+`ANTHROPIC_API_KEY` isn't a real key on the server, `client risk` falls
+back to a heuristic score automatically, but `escalation advance` has no
+such fallback and will 500. (2) Confirm you're running a backend build
+that includes the `packages/legal_ai` module-name fix and the
+`risk_scoring.py` request-parameter fix — both were real bugs in this
+repo (a hyphenated `packages/legal-ai` directory that the code imports as
+`packages.legal_ai`, and a rate-limiter/parameter-name collision on
+`/api/v1/risk/score`) that this CLI's own end-to-end testing surfaced and
+this same change fixed. A plain 401 means your cached token expired and
+couldn't refresh — run `fpp login` again.
+
+**Does `fpp escalation advance` actually send the escalation email or move the invoice to the next stage?**
+No. It calls the backend's `/api/v1/escalations/{id}/draft` endpoint,
+which only returns an AI-drafted preview of what the next stage's email
+would say. The backend has no endpoint today that persists a stage change
+or sends the email — see "A note on `escalation advance`" above.
+
+**Can I point this at a self-hosted or non-default backend?**
+Yes. Set `FPP_API_URL` to your backend's base URL (default is
+`http://localhost:8000`, matching the FastAPI dev server's default port).
+Every command reads that variable at call time, so switching environments
+is just re-exporting it.
+
+**What's the licensing situation — can I use or modify this commercially?**
+This CLI ships from the same repository as, and under the same license
+as, freelancer-payment-protection itself: a proprietary license, copyright
+Rudrendu Paul and Sourav Nandy, all rights reserved. Personal, academic,
+commercial, or scheduled use requires explicit written permission from
+both owners — see the `LICENSE` file. This is not an MIT/Apache-style
+open-source license; publishing it to PyPI makes it installable, not
+freely reusable.
+
+**Why isn't there a hosted/default API URL I can just start using?**
+freelancer-payment-protection is self-hosted software, not a hosted
+multi-tenant SaaS with a public API endpoint today. You (or whoever
+operates your workspace) runs the backend; the CLI just needs its URL.
+
+## Development
+
+```bash
+cd packages/cli
+python -m venv .venv && source .venv/bin/activate
+pip install -e ".[dev]"
+pytest
+```
+
+All HTTP calls (to Supabase and to the backend API) are mocked in tests
+with `respx` — the test suite makes no live network calls.
+
+## Contributing
+
+This package lives inside the freelancer-payment-protection monorepo. See
+the repository root for contribution guidelines.
+
+## License
+
+Proprietary — see [`LICENSE`](./LICENSE). Contact the owners (see
+`LICENSE`) before any use beyond installing and running the package as
+published.

freelancer_payment_protection_cli-0.1.0/README.md

@@ -0,0 +1,213 @@
+# freelancer-payment-protection-cli
+
+Command-line client for [freelancer-payment-protection](https://github.com/RudrenduPaul/freelancer-payment-protection):
+automated invoice escalation, legal document generation, and client risk
+scoring for freelancers. This package wraps the project's FastAPI backend
+(`apps/api/app/routers/*.py`) so the same clients, invoices, escalations,
+and risk-scoring data you'd otherwise reach through the dashboard or the
+raw HTTP API is scriptable from a terminal or an agent.
+
+![Login and first command](../../docs/demo.gif)
+
+## Install
+
+```bash
+pip install freelancer-payment-protection-cli
+```
+
+Or with [uv](https://docs.astral.sh/uv/) / [pipx](https://pipx.pypa.io/):
+
+```bash
+uvx freelancer-payment-protection-cli --help
+pipx install freelancer-payment-protection-cli
+```
+
+Requires Python 3.10+. The console command is installed as both `fpp`
+(short form) and `freelancer-payment-protection` (full form) — they are the
+same entry point.
+
+## Configuration
+
+The CLI needs to know two things: which backend API to talk to, and which
+Supabase project issues your login tokens.
+
+| Variable | Purpose | Default |
+|---|---|---|
+| `FPP_API_URL` | Backend API base URL | `http://localhost:8000` |
+| `FPP_SUPABASE_URL` (or `SUPABASE_URL`) | Your Supabase project URL | none, required for `login` |
+| `FPP_SUPABASE_ANON_KEY` (or `SUPABASE_ANON_KEY`) | Your Supabase project's anon key | none, required for `login` |
+
+The anon key is the same public key the web app's Supabase client uses —
+it is not a secret, and it's the key already in `apps/web/.env.example` as
+`NEXT_PUBLIC_SUPABASE_ANON_KEY`.
+
+## Login and authentication
+
+```bash
+export FPP_SUPABASE_URL="https://your-project.supabase.co"
+export FPP_SUPABASE_ANON_KEY="your-anon-key"
+fpp login
+```
+
+`fpp login` prompts for your email and password, then calls Supabase's own
+REST auth endpoint directly:
+
+```
+POST {SUPABASE_URL}/auth/v1/token?grant_type=password
+Header: apikey: <anon key>
+Body:   {"email": ..., "password": ...}
+```
+
+This is the same call the web dashboard's Supabase client makes — the CLI
+never talks to a login endpoint of its own, because the backend
+(`apps/api/app/middleware/auth.py`) doesn't mint tokens; it only validates
+Supabase-issued JWTs. On success, the returned `access_token` and
+`refresh_token` are cached to `~/.config/freelancer-payment-protection-cli/credentials.json`
+(mode 600). Every later command reads the JWT's `workspace_id` claim the
+same way `get_current_workspace()` does server-side, and transparently
+refreshes the access token with the cached refresh token once it expires.
+
+Run `fpp logout` to delete the cached credentials, or `fpp whoami` to see
+which workspace and email the cached token resolves to.
+
+## Commands
+
+Every data-returning command supports `--json` for scripting and agent use.
+
+```
+fpp login                                   Log in (prompts for email/password)
+fpp logout                                  Remove cached credentials
+fpp whoami [--json]                         Show cached workspace/session info
+
+fpp invoice list [--status] [--client-id] [--page] [--page-size] [--json]
+fpp invoice create --client-id --invoice-number --amount --due-date [...] [--json]
+fpp invoice show <invoice-id> [--json]
+fpp invoice set-status <invoice-id> <status> [--json]
+
+fpp escalation list [--json]                Active escalations, grouped by stage
+fpp escalation status <invoice-id> [--json] Current stage + full history
+fpp escalation advance <invoice-id> [--json] AI-draft the next stage's email
+
+fpp client list [--risk-level] [--search] [--page] [--page-size] [--json]
+fpp client show <client-id> [--json]
+fpp client risk <client-id> [--json]        Compute/refresh the AI risk score
+```
+
+Run `fpp --help` or `fpp <command> --help` for full flag references.
+
+![Filtering invoices, scoring a client, and checking escalation status](../../docs/usage.gif)
+
+### A note on `escalation advance`
+
+The backend's escalation router (`apps/api/app/routers/escalations.py`)
+exposes exactly three routes: list active escalations, draft the next
+stage's email, and read history. There is no route that persists a stage
+change — `draft_escalation_email` in `escalation_service.py` computes and
+returns what the next stage's email would say, but never writes
+`escalation_stage` back to the database. `fpp escalation advance` calls
+that draft endpoint and shows you the preview; it does not claim to move
+the invoice to the next stage, because the API it wraps doesn't do that
+either.
+
+### JSON output for agents/scripts
+
+```bash
+fpp invoice list --status overdue --json | jq '.[] | {id, invoiceNumber, daysPastDue}'
+fpp client risk "$CLIENT_ID" --json | jq '.level'
+```
+
+Field names in `--json` output match the backend's actual Pydantic response
+models exactly (camelCase, e.g. `invoiceNumber`, `daysPastDue`,
+`escalationStage`) since the CLI passes the API's response straight
+through rather than remapping it.
+
+## FAQ
+
+**What is this, and how is it different from just calling the API with curl?**
+It's a typed command-line wrapper around the same backend the web
+dashboard uses — invoices, escalations, and client risk scoring — with
+persistent login (so you're not re-attaching a bearer token to every
+request), human-readable tables by default, and a `--json` flag on every
+data command for piping into `jq`, scripts, or an agent's tool-calling
+loop. The differentiator versus curl is session handling (login once,
+silent token refresh after) and consistent, documented output shapes
+instead of hand-rolled request construction.
+
+**What platforms and Python versions does it support?**
+Python 3.10 through 3.13, on any OS `pip`/`uvx`/`pipx` runs on (Linux,
+macOS, Windows). It has no compiled dependencies — the only runtime
+dependencies are `click` and `httpx`, both pure-Python-installable wheels.
+
+**How do I log in, and where are my credentials stored?**
+Run `fpp login`, enter your email and password when prompted. The CLI
+calls Supabase's password-grant token endpoint directly (see "Login and
+authentication" above) and caches the resulting access and refresh tokens
+to `~/.config/freelancer-payment-protection-cli/credentials.json` with
+file mode 600 (owner read/write only). Nothing is sent anywhere except
+Supabase's own auth endpoint and the backend API you configure via
+`FPP_API_URL`.
+
+**I ran a command and got `Error: Internal Server Error` — is that a CLI bug?**
+Usually not. The CLI's error handling surfaces whatever the backend
+returned; a 500 means the backend itself failed. Two real, backend-side
+causes to check first: (1) `fpp client risk` and `fpp escalation advance`
+both trigger AI calls through `packages/legal_ai/client.py` — if
+`ANTHROPIC_API_KEY` isn't a real key on the server, `client risk` falls
+back to a heuristic score automatically, but `escalation advance` has no
+such fallback and will 500. (2) Confirm you're running a backend build
+that includes the `packages/legal_ai` module-name fix and the
+`risk_scoring.py` request-parameter fix — both were real bugs in this
+repo (a hyphenated `packages/legal-ai` directory that the code imports as
+`packages.legal_ai`, and a rate-limiter/parameter-name collision on
+`/api/v1/risk/score`) that this CLI's own end-to-end testing surfaced and
+this same change fixed. A plain 401 means your cached token expired and
+couldn't refresh — run `fpp login` again.
+
+**Does `fpp escalation advance` actually send the escalation email or move the invoice to the next stage?**
+No. It calls the backend's `/api/v1/escalations/{id}/draft` endpoint,
+which only returns an AI-drafted preview of what the next stage's email
+would say. The backend has no endpoint today that persists a stage change
+or sends the email — see "A note on `escalation advance`" above.
+
+**Can I point this at a self-hosted or non-default backend?**
+Yes. Set `FPP_API_URL` to your backend's base URL (default is
+`http://localhost:8000`, matching the FastAPI dev server's default port).
+Every command reads that variable at call time, so switching environments
+is just re-exporting it.
+
+**What's the licensing situation — can I use or modify this commercially?**
+This CLI ships from the same repository as, and under the same license
+as, freelancer-payment-protection itself: a proprietary license, copyright
+Rudrendu Paul and Sourav Nandy, all rights reserved. Personal, academic,
+commercial, or scheduled use requires explicit written permission from
+both owners — see the `LICENSE` file. This is not an MIT/Apache-style
+open-source license; publishing it to PyPI makes it installable, not
+freely reusable.
+
+**Why isn't there a hosted/default API URL I can just start using?**
+freelancer-payment-protection is self-hosted software, not a hosted
+multi-tenant SaaS with a public API endpoint today. You (or whoever
+operates your workspace) runs the backend; the CLI just needs its URL.
+
+## Development
+
+```bash
+cd packages/cli
+python -m venv .venv && source .venv/bin/activate
+pip install -e ".[dev]"
+pytest
+```
+
+All HTTP calls (to Supabase and to the backend API) are mocked in tests
+with `respx` — the test suite makes no live network calls.
+
+## Contributing
+
+This package lives inside the freelancer-payment-protection monorepo. See
+the repository root for contribution guidelines.
+
+## License
+
+Proprietary — see [`LICENSE`](./LICENSE). Contact the owners (see
+`LICENSE`) before any use beyond installing and running the package as
+published.

freelancer_payment_protection_cli-0.1.0/pyproject.toml

@@ -0,0 +1,71 @@
+[build-system]
+requires = ["hatchling"]
+build-backend = "hatchling.build"
+
+[project]
+name = "freelancer-payment-protection-cli"
+version = "0.1.0"
+description = "Command-line client for freelancer-payment-protection: automated invoice escalation, legal document generation, and client risk scoring for freelancers."
+readme = "README.md"
+requires-python = ">=3.10"
+license = { text = "Proprietary" }
+authors = [
+  { name = "Rudrendu Paul" },
+  { name = "Sourav Nandy" },
+]
+keywords = ["invoicing", "freelance", "cli", "invoice-escalation", "risk-scoring", "agent-native", "supabase", "fastapi"]
+classifiers = [
+  "Development Status :: 3 - Alpha",
+  "Environment :: Console",
+  "Intended Audience :: Developers",
+  "Operating System :: OS Independent",
+  "Programming Language :: Python :: 3",
+  "Programming Language :: Python :: 3.10",
+  "Programming Language :: Python :: 3.11",
+  "Programming Language :: Python :: 3.12",
+  "Programming Language :: Python :: 3.13",
+  "Topic :: Office/Business :: Financial :: Accounting",
+  "Topic :: Utilities",
+]
+dependencies = [
+  "click>=8.1,<9",
+  "httpx>=0.27,<1",
+]
+
+[project.optional-dependencies]
+dev = [
+  "pytest>=8.0,<9",
+  "pytest-cov>=5.0,<7",
+  "respx>=0.21,<1",
+  "build>=1.0,<2",
+  "twine>=5.0,<7",
+]
+
+[project.urls]
+Homepage = "https://github.com/RudrenduPaul/freelancer-payment-protection"
+Repository = "https://github.com/RudrenduPaul/freelancer-payment-protection"
+"Bug Tracker" = "https://github.com/RudrenduPaul/freelancer-payment-protection/issues"
+
+[project.scripts]
+fpp = "freelancer_payment_protection_cli.main:main"
+freelancer-payment-protection = "freelancer_payment_protection_cli.main:main"
+
+[tool.hatch.build]
+# This package lives in a subdirectory (packages/cli/) of a larger
+# monorepo whose .git directory is at the repo root, alongside Node/
+# Turborepo config that has nothing to do with this Python package.
+ignore-vcs = true
+
+[tool.hatch.build.targets.wheel]
+packages = ["src/freelancer_payment_protection_cli"]
+
+[tool.hatch.build.targets.sdist]
+only-include = [
+  "src/freelancer_payment_protection_cli",
+  "tests",
+  "README.md",
+  "LICENSE",
+]
+
+[tool.pytest.ini_options]
+testpaths = ["tests"]

freelancer_payment_protection_cli-0.1.0/src/freelancer_payment_protection_cli/__init__.py

@@ -0,0 +1,6 @@
+"""freelancer-payment-protection-cli — command-line client for the
+freelancer-payment-protection API (invoice escalation, legal document
+generation, and client risk scoring for freelancers).
+"""
+
+__version__ = "0.1.0"