spaps 0.6.2__tar.gz → 0.8.3__tar.gz

{spaps-0.6.2 → spaps-0.8.3}/.gitignore

@@ -1,5 +1,5 @@
 # Dependencies
-node_modules/
+node_modules
 *.log
 npm-debug.log*
 yarn-debug.log*
@@ -13,7 +13,7 @@ sweet-potato-threat-model.md
 *.py[cod]
 *.pyo
 *.pyd
-.venv/
+.venv
 *.egg-info/
 
 # Testing
@@ -30,6 +30,7 @@ coverage-*/
 **/.testmondata
 **/.testmondata-shm
 **/.testmondata-wal
+packages/python-server-quickstart/tests/benchmarks/.artifacts/
 *.lcov
 **/lcov.info
 **/lcov-report/
@@ -165,6 +166,8 @@ backup-feb8.sql
 .ntm/
 .skillbox/
 artifacts/openapi-contract/
+# Local-only secret inventory; canonical is docs/security/SECRET_EXPOSURE_REPORT.md
+artifacts/SECRET_EXPOSURE_REPORT.md
 MODES_ANALYSIS_PROGRESS.md
 MODES_OF_REASONING_REPORT_AND_ANALYSIS_OF_PROJECT.md
 MODE_OUTPUT_*.md
@@ -204,3 +207,30 @@ refactor/
 
 # Beads compliance audit dir (managed by /beads-compliance-and-completion-verification skill)
 /beads_compliance_audit/
+
+# Local agent ideation and graph-export artifacts
+/.agent-artifacts/
+/DUELING_*
+/WIZARD_*
+/MODE_OUTPUT_*
+/.beads-public-client-graph.sh
+.release/
+
+# Amp Orb repository hooks/config are tracked. Only generated runtime state is
+# ignored; do not blanket-ignore .agents/ or .amp/.
+/.agents/cache/
+/.agents/skills/
+/.agents/logs/
+/.agents/state/
+/.agents/tools/
+/.agents/amp-context/__pycache__/
+/.amp/live-sync.pid
+/.amp/portals/
+/.amp/resume-last-ran.txt
+
+# Production environment drafts belong in the out-of-tree environment manager.
+python-prod.env.draft
+**/python-prod.env.draft
+
+# Generated Authentication reference app (see packages/spaps/scripts/serve-auth-reference.mjs)
+packages/spaps/.auth-reference/

spaps-0.8.3/CHANGELOG.md

@@ -0,0 +1,260 @@
+# Changelog
+
+All notable changes to this project are documented in this file.
+
+The format follows [Keep a Changelog](https://keepachangelog.com/en/1.1.0/) and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
+
+## [Unreleased]
+
+- No changes yet.
+
+## [0.8.3] - 2026-10-24
+
+**Unpublished source candidate.** This date records candidate preparation, not
+registry publication or downstream deployment.
+
+- Prepare the `0.8.3.dev0` checkout as `0.8.3` alongside server `0.9.1`
+  ([54a0059a](https://github.com/build000r/sweet-potato/commit/54a0059aba568f750da284496c4863a0db695cf4)).
+- Include sync/async purchase-journey and developer-portal helpers, scoped
+  dashboard controls, capability decisions, and authenticated CFO action-journey
+  helpers added since the retained public `0.8.2` baseline.
+
+## [0.8.3.dev0] - 2026-10-22
+
+**Unpublished development checkout.**
+
+- Separate the expanded checkout API from the public `0.8.2` artifact observed
+  on 2026-10-22. The offline surface guard rejects different APIs using the same
+  version and validates retained artifact provenance before comparing them.
+
+## [0.8.2] - 2026-10-01
+
+**Public artifact observed 2026-10-22.** This heading originally described a
+source candidate. Registry observation does not establish its publication date.
+The original candidate superseded tagged but unpublished `0.8.1`.
+
+- Repack the reviewed source cohort with corrected exact-artifact inspection; no Python client API change.
+
+## [0.8.1] - 2026-09-30
+
+**Unpublished source candidate.** Supersedes the tagged but unpublished
+`0.8.0` candidate in the coordinated package release.
+
+## [0.8.0] - 2026-09-30
+
+**Unpublished source candidate.** This version has not passed the coordinated
+package review or been published. The last published version is `0.6.2`;
+`0.8.0` also includes the changes recorded under the unpublished `0.7.x`
+checkpoints below.
+
+This candidate includes the source changes after the `0.7.2` checkpoint.
+The pair-scoped secure-message API and removal of offset paging are breaking
+changes; migrate callers before upgrading.
+
+### Added
+
+- Added the secure-message **authorship contract** (server revision `000000000094`) to the sync
+  `SecureMessagesClient` and async `AsyncSecureMessagesClient`: responses now carry
+  `sender_user_id`, `sender_role`, and `client_message_id`, and `SecureMessage.has_known_sender`
+  is the branch point for messages written before that revision, whose authorship is genuinely
+  unknown and is never back-filled from `patient_id` / `practitioner_id`.
+- Added idempotent sends via `create_message(..., client_message_id=...)`. The token is bounded to
+  1-200 characters locally, mirroring the server `CHECK` constraint
+  `ck_secure_messages_client_message_id_len`, so an oversized token is a `ValueError` instead of a
+  round trip that ends in a 400. Retrying with the same token, as the same authenticated sender and
+  with the same pair/content/metadata, returns the original message; reusing it for a different
+  message is `409 SECURE_MESSAGES_IDEMPOTENCY_CONFLICT`.
+- Added `iter_messages(patient_id=..., practitioner_id=...)` on both surfaces, which follows the
+  keyset `next_cursor` to the end of one conversation.
+- Exported `SENDER_ROLE_PATIENT`, `SENDER_ROLE_PRACTITIONER`, `MIN_CLIENT_MESSAGE_ID_LENGTH`,
+  `MAX_CLIENT_MESSAGE_ID_LENGTH` from `spaps_client`, and `FORBIDDEN_SENDER_KEYS` plus the
+  `SECURE_MESSAGES_*` error codes from `spaps_client.secure_messages`, so consumers branch on the
+  server vocabulary instead of hand-copied strings.
+
+### Changed
+
+- **BREAKING.** `GET /api/secure-messages` is now pair-scoped. `list_messages` and `iter_messages`
+  take `patient_id` and `practitioner_id` as required keyword arguments on both the sync and async
+  surfaces; there is no "all my messages" read. An empty id raises `ValueError` locally rather than
+  issuing a request the server will reject.
+- **BREAKING.** `offset` paging is gone. The server answers a non-zero `offset` with
+  `400 SECURE_MESSAGES_OFFSET_UNSUPPORTED` because offset paging over an append-only conversation
+  drops or repeats messages, so the clients have no `offset` parameter at all and never emit the
+  query key. Replace any offset loop with `iter_messages(...)` or a manual `cursor` loop.
+- The message author is derived server-side from the authenticated JWT and can never be supplied by
+  a caller. Neither `create_message` accepts a sender argument in any spelling, and
+  `FORBIDDEN_SENDER_KEYS` (`senderUserId`, `sender_user_id`, `senderRole`, `sender_role`) is
+  asserted absent from every outgoing body before the request is built.
+- The async client delegates to the same `build_create_payload` / `build_list_params` / `build_page`
+  helpers as the sync client, so the two surfaces cannot drift on which keys they send.
+
+### Fixed
+
+- Local `0.7.2` candidate: accept explicit `wallets: null` as an empty wallet list when public
+  sync and async auth clients decode user profiles, while retaining validation for malformed
+  non-null wallet values.
+
+## [0.7.2] - 2026-09-14
+
+**Unreleased source checkpoint.** This date records source commit
+`c52a7b0d82e5991f3abd807f5ccf5949af81c651`, not package publication.
+The Unreleased entries above remain pending; this checkpoint does not
+assign them to a release.
+
+### Fixed
+
+- Accept explicit `wallets: null` as an empty wallet list when sync and
+  async auth clients decode user profiles. Malformed non-null values
+  still fail validation.
+
+## [0.7.1] - 2026-07-28
+
+### Fixed
+
+- Excluded generated coverage databases from source distributions and made the
+  release inspector reject build-host coverage material.
+- Pinned the release-gate Ruff version and made package timestamps derive from
+  the exact source commit.
+- Superseded the quarantined unpublished `0.7.0` manifest; its wheel and sdist
+  remain rejected audit history.
+
+## [0.7.0] - 2026-07-15
+
+### Added
+
+- Added inverse sync/async Python helpers and typed models for all 23 passkey operations: raw ceremonies, passkey-first bootstrap, credential lifecycle, application profiles, action-bound step-up, user recovery, and administrator recovery.
+- Added explicit WebAuthn `Origin` forwarding, exact public/user/admin authentication behavior, typed recovery grant rotation, and token storage only for token-issuing passkey responses.
+
+### Fixed
+
+- Preserved passkey API error details and top-level request IDs in `AuthError`, while keeping response-header request IDs authoritative.
+
+## [0.6.2] - 2026-06-16
+
+### Fixed
+
+- Accepted `stream`, `owner_id`, `subject_override`, and `body_override` on `EmailClient.send()` and accepted `stream` on `AsyncEmailClient.send()` so Python consumers can delegate SPAPS email sends without hand-rolling the `/api/email/send` envelope.
+
+### Changed
+
+- Bumped the Python client package metadata to `0.6.2`.
+
+## [0.6.1] - 2026-06-14
+
+### Added
+
+- Added sync `DayrateClient` helpers and sync/async `AppLinksClient` helpers, with high-level `SpapsClient.dayrate`, `SpapsClient.app_links`, and `AsyncSpapsClient.app_links` accessors.
+- Added sync and async `UsersClient.memberships` helpers for listing, inviting/adding, and removing app account users.
+- Added sync and async `EntitlementsClient.project_grants` helpers for granting, revoking, listing, checking, and claiming project access grants.
+
+### Fixed
+
+- Accepted canonical SPAPS password reset request envelopes that return `success`, `data.email`, `data.sent_at`, `request_id`, and `timestamp` without requiring a top-level English `message`.
+- Exposed omitted password reset request messages as `None` instead of an empty string placeholder so apps keep ownership of success copy.
+- Preserved password reset confirmation parsing for canonical envelopes where the success copy lives at `data.message`.
+
+### Changed
+
+- Bumped the Python client package metadata to `0.6.1`; HTMA should consume `spaps>=0.6.1` or the matching unreleased local wheel/source checkout before retrying the reset flow.
+
+## [0.6.0] - 2026-06-13
+
+### Added
+
+- Added sync and async auth helpers for OIDC nonce/sign-in, WebAuthn registration/assertion, TOTP MFA enrollment/verification/disable, and SMS OTP request/verify flows.
+- Added typed MFA challenge responses so token-issuing auth methods can return either tokens or an MFA challenge without storing incomplete credentials.
+
+### Changed
+
+- Bumped the Python client package metadata to `0.6.0`.
+
+## [0.5.1] - 2026-06-04
+
+### Added
+
+- Added sync and async issue-reporting screenshot attachment helpers for private upload, list, access URL, delete, and attach-by-ID create/update/reply flows.
+
+## [0.5.0] - 2026-03-29
+
+### Added
+
+- End-user issue-report flows across the Python client surface.
+- Support-telemetry helpers aligned with the current SPAPS platform APIs.
+
+### Changed
+
+- Refreshed package docs and OSS-facing references for the published client surface.
+
+## [0.4.1] - 2026-02-18
+
+### Changed
+
+- Relaxed required fields in email and entitlement schemas for forward compatibility.
+- Relaxed `Entitlement.source` from `Literal` to `str` to accept newly introduced source types without forcing immediate client upgrades.
+
+## [0.4.0] - 2026-02-17
+
+### Added
+
+- `UsersClient` and `AsyncUsersClient` for user management operations.
+- Async quickstart parity wrappers aligned with server-side helpers.
+- Referral fields in registration flow.
+
+## [0.3.0] - 2026-02-11
+
+### Changed
+
+- Consolidated SPAPS integration patterns into published packages.
+- Aligned Python client surface area with production SPAPS APIs.
+
+## [0.2.0] - 2025-12-30
+
+### Added
+
+- Broader SDK coverage to support production cutover requirements.
+- Email-service and set-password endpoint client stubs.
+
+### Changed
+
+- Standardized configuration defaults (including port `3301` and environment symlink conventions).
+
+## [0.1.4] - 2025-11-09
+
+### Fixed
+
+- Session validation response parsing for the `valid` field contract.
+
+## [0.1.3] - 2025-10-14
+
+### Added
+
+- Subscription list/detail/cancel/swap helpers to match TypeScript SDK behavior.
+- Checkout session lookup/list/expire and guest checkout lifecycle helpers.
+- Stripe payment history summaries and payment-detail retrieval.
+- Client-side role/permission utilities in `spaps_client.permissions`.
+
+### Changed
+
+- Refreshed README examples for newly added helpers.
+
+## [0.1.2] - 2025-10-12
+
+### Changed
+
+- Standardized crypto invoice lookup helper behavior and logging paths.
+
+## [0.1.1] - 2025-10-11
+
+### Changed
+
+- Widened `httpx` dependency range to `<0.29` for FastAPI default-stack compatibility (`0.28.x`).
+
+## [0.1.0] - 2025-10-11
+
+### Added
+
+- Initial public PyPI release under the `spaps` distribution name.
+- Sync and async clients for sessions, payments (including crypto), usage, whitelist, secure messages, and metrics.
+- Configurable retry/backoff behavior, logging hooks, and token storage abstractions.
+- Linting/type-checking/coverage gates integrated with the release workflow.
+- Python quickstart documentation and backend integration guide.

spaps-0.8.3/LICENSE

@@ -0,0 +1,34 @@
+SWEET POTATO / SPAPS PROPRIETARY LICENSE NOTICE
+
+Copyright (c) 2025-2026 build000r. All rights reserved.
+
+Sweet Potato / SPAPS, including its source code, documentation, first-party
+packages, schemas, designs, and related materials (collectively, the
+"Software"), is proprietary.
+
+No license or permission is granted to use, copy, modify, merge, publish,
+distribute, sublicense, sell, host, operate, reverse engineer, expose as a
+service, or create derivative works from the Software except as expressly
+authorized by a separate written agreement with build000r.
+
+Authorized customers may use first-party client packages and documentation
+solely to integrate with the hosted Sweet Potato / SPAPS service while their
+paid subscription remains active and subject to the applicable service terms.
+Possession of source code, a package artifact, a container image, documentation,
+or an API credential does not grant ownership of the Software or a right to
+deploy, redistribute, resell, or operate the SPAPS backend.
+
+Third-party software included with or used by the Software remains governed by
+its own license terms.
+
+Versions of any material that were previously distributed with a different
+license remain governed by the license that accompanied those versions. This
+notice does not retroactively revoke rights that were already granted under an
+earlier license.
+
+THE SOFTWARE AND HOSTED SERVICE ARE PROVIDED "AS IS" AND "AS AVAILABLE," WITHOUT
+WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO WARRANTIES
+OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE, AND
+NONINFRINGEMENT. TO THE MAXIMUM EXTENT PERMITTED BY LAW, BUILD000R SHALL NOT BE
+LIABLE FOR ANY CLAIM, DAMAGES, OR OTHER LIABILITY ARISING FROM OR RELATED TO THE
+SOFTWARE, THE HOSTED SERVICE, OR THEIR USE.