zeo-integrations 0.1.0.post14__tar.gz

zeo_integrations-0.1.0.post14/.gitignore

@@ -0,0 +1,9 @@
+.venv/
+__pycache__/
+*.py[cod]
+.ruff_cache/
+.coverage
+dist/
+*.egg-info/
+.env
+.env.*

zeo_integrations-0.1.0.post14/LICENSE

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

zeo_integrations-0.1.0.post14/NOTICE

@@ -0,0 +1,65 @@
+zeointegrations
+Copyright (c) 2026 Zero Employee Organizations
+Distributed under the MIT License; see LICENSE.
+
+The initial skeleton copied no implementation source. docs/inventory contains
+source-derived metadata, not provider code. Later package ports are listed below.
+
+Canonical source: VeyraX/veyrax-platform; inventoried through the local
+rodriveracom/veyrax-platform fork at the identical
+commit 1cdddde9d5d76b9891896ca78a95e069647e81df.
+Its MIT license states Copyright (c) 2025 VeyraX.
+The full source notice is preserved in docs/licenses/VeyraX-MIT.txt.
+
+Inventory source: zeroemployeeorg/zeocore,
+commit 2e7cb11fa9aaf133876c02c1eea8f1ccd94bba04 (MIT).
+Its MIT license states Copyright (c) 2026 Rod Rivera.
+
+Future ports must add a per-file source-to-destination provenance map here and
+in their package NOTICE, and retain source copyright and permission notices.
+
+Kit read-only client port: zeroemployeeorg/zeocore at
+25a9c899c17ac6cdf54f4949e54b0fcc800cce91, Copyright (c) 2026 Rod Rivera.
+MIT permission and copyright notice are retained verbatim in packages/kit/LICENSE
+and referenced in packages/kit/NOTICE; adapted modules retain per-file headers.
+Source-to-destination mapping:
+src/zeo_core/integrations/kit/client.py -> packages/kit/src/zeo_integrations/kit/client.py
+src/zeo_core/integrations/kit/models.py -> packages/kit/src/zeo_integrations/kit/models.py
+src/zeo_core/integrations/kit/transport.py -> packages/kit/src/zeo_integrations/kit/transport.py
+LICENSE -> packages/kit/LICENSE
+Only the current-API read-only subset is adapted; service, registry, credential
+custody and private Broker fixtures are excluded. See package NOTICE for details.
+
+HubSpot provider port: zeroemployeeorg/zeocore@6bd62fbbfc4453908ab464219c2a304d7420b15b,
+Copyright (c) 2026 Rod Rivera, MIT permission retained in packages/hubspot/LICENSE.
+Exact source/destination/blob mapping (prefix src/zeo_core/integrations/hubspot/
+-> packages/hubspot/src/zeo_integrations/hubspot/):
+client.py -> client.py; e36ec1c646b1d1b16184e500bdb9bb6008d97a7c
+models.py -> models.py; a0d95437b736cf7a3198acf1d0f88849aad32903
+transport.py -> transport.py; 7e5b9d0be1f54e33ffe999704a042d125beb67a3
+workflow.py -> workflow.py; 97d628d4b42986332c134dfd2d2db25a24bd67b9
+LICENSE [blob ff593bd47616c4602615f901b800f4d0965c805b] -> packages/hubspot/LICENSE; original MIT copyright and permission.
+See package NOTICE for byte-identical first move and separately reviewed changes.
+
+Aggregate test support copied without behaviour changes from
+zeroemployeeorg/zeocore@7c9923e6fd93cabb8601040f3e431760be3a18ee:
+tests/conftest.py and tests/__init__.py.
+The initially empty tests/test_integrations/__init__.py now contains an authored
+unittest discovery adapter: provider tests run via the explicit full-gate pytest
+invocation, keeping dependency-free smoke discovery separate.
+MIT Copyright(c)2026 Rod Rivera; repository LICENSE retains the full terms.
+
+Whole-provider migration batch1 from zeroemployeeorg/zeocore commit
+7c9923e6fd93cabb8601040f3e431760be3a18ee, MIT Copyright(c)2026 Rod Rivera.
+HubSpot, Kit (legacy full API), Revolut and Supabase plus their tests move
+mechanically with import/module references adapted. Complete per-file old/new
+paths and Git blob provenance: docs/migrations/core-7c9923e6-batch1.json.
+Core contracts, services infrastructure and signer custody remain in zeocore;
+this collection depends on that published framework. Older standalone
+read-only/hardened package artifacts remain separately preserved evidence.
+
+Whole-batch test ownership partition, Core7c9923e6: 217 original test functions;
+194 portable functions move here; 23 Core tool, entrypoint or setup-catalog
+functions remain unchanged in Core until the post-PyPI shim. No skips or aliases.
+Per-function ownership, original/moved hashes and assertion counts cover every
+original Python test/support file in docs/migrations/core-7c9923e6-batch1.json.

zeo_integrations-0.1.0.post14/PKG-INFO

@@ -0,0 +1,119 @@
+Metadata-Version: 2.4
+Name: zeo-integrations
+Version: 0.1.0.post14
+Summary: Zeo integration collection; provider SDKs are optional
+License-Expression: MIT
+License-File: LICENSE
+License-File: NOTICE
+Requires-Python: >=3.12
+Requires-Dist: httpx<1,>=0.28.1
+Requires-Dist: pydantic<3,>=2.13.4
+Requires-Dist: zeocore<1,>=0.43.0
+Provides-Extra: bluesky
+Requires-Dist: platformdirs>=4; extra == 'bluesky'
+Requires-Dist: requests; extra == 'bluesky'
+Provides-Extra: calendar
+Requires-Dist: google-api-python-client>=2; extra == 'calendar'
+Requires-Dist: google-auth-httplib2>=0.1; extra == 'calendar'
+Requires-Dist: google-auth-oauthlib>=0.4; extra == 'calendar'
+Requires-Dist: platformdirs>=4; extra == 'calendar'
+Provides-Extra: docs
+Requires-Dist: google-api-python-client>=2; extra == 'docs'
+Requires-Dist: google-auth-httplib2>=0.1; extra == 'docs'
+Requires-Dist: google-auth-oauthlib>=0.4; extra == 'docs'
+Requires-Dist: platformdirs>=4; extra == 'docs'
+Provides-Extra: drive
+Requires-Dist: google-api-python-client>=2; extra == 'drive'
+Requires-Dist: google-auth-httplib2>=0.1; extra == 'drive'
+Requires-Dist: google-auth-oauthlib>=0.4; extra == 'drive'
+Requires-Dist: platformdirs>=4; extra == 'drive'
+Provides-Extra: ffmpeg
+Requires-Dist: ffmpeg-zeo>=0.1; extra == 'ffmpeg'
+Provides-Extra: github
+Requires-Dist: requests; extra == 'github'
+Provides-Extra: gmail
+Requires-Dist: google-api-python-client>=2; extra == 'gmail'
+Requires-Dist: google-auth-httplib2>=0.1; extra == 'gmail'
+Requires-Dist: google-auth-oauthlib>=0.4; extra == 'gmail'
+Requires-Dist: platformdirs>=4; extra == 'gmail'
+Provides-Extra: google
+Requires-Dist: google-api-python-client>=2; extra == 'google'
+Requires-Dist: google-auth-httplib2>=0.1; extra == 'google'
+Requires-Dist: google-auth-oauthlib>=0.4; extra == 'google'
+Requires-Dist: platformdirs>=4; extra == 'google'
+Provides-Extra: jupytext
+Requires-Dist: jupytext>=1.16; extra == 'jupytext'
+Requires-Dist: nbformat>=5.10; extra == 'jupytext'
+Provides-Extra: llms
+Requires-Dist: anthropic; extra == 'llms'
+Requires-Dist: openai; extra == 'llms'
+Requires-Dist: tiktoken; extra == 'llms'
+Provides-Extra: notion
+Requires-Dist: notion-client>=3.1.0; extra == 'notion'
+Provides-Extra: pandoc
+Requires-Dist: beautifulsoup4; extra == 'pandoc'
+Requires-Dist: pypandoc; extra == 'pandoc'
+Provides-Extra: revolut
+Requires-Dist: cryptography>=45; extra == 'revolut'
+Requires-Dist: platformdirs>=4; extra == 'revolut'
+Provides-Extra: sheets
+Requires-Dist: google-api-python-client>=2; extra == 'sheets'
+Requires-Dist: google-auth-httplib2>=0.1; extra == 'sheets'
+Requires-Dist: google-auth-oauthlib>=0.4; extra == 'sheets'
+Requires-Dist: platformdirs>=4; extra == 'sheets'
+Provides-Extra: slides
+Requires-Dist: google-api-python-client>=2; extra == 'slides'
+Requires-Dist: google-auth-httplib2>=0.1; extra == 'slides'
+Requires-Dist: google-auth-oauthlib>=0.4; extra == 'slides'
+Requires-Dist: platformdirs>=4; extra == 'slides'
+Provides-Extra: supabase
+Requires-Dist: supabase<3,>=2.31.0; extra == 'supabase'
+Provides-Extra: youtube
+Requires-Dist: google-api-python-client>=2; extra == 'youtube'
+Requires-Dist: google-auth-httplib2>=0.1; extra == 'youtube'
+Requires-Dist: google-auth-oauthlib>=0.4; extra == 'youtube'
+Requires-Dist: platformdirs>=4; extra == 'youtube'
+Requires-Dist: requests; extra == 'youtube'
+Description-Content-Type: text/markdown
+
+# Zeo integrations
+
+One distribution, `zeo-integrations`, containing provider modules under
+`zeo_integrations.<provider>`. The collection depends on published `zeocore`;
+Core does not import the collection at import time. Provider SDKs are optional
+extras, for example `pip install 'zeo-integrations[google]'` after the single
+aggregate publication exists. During migration, install from this repository
+at an exact reviewed commit. Do not register per-provider PyPI projects.
+
+This first foundation supplies shared packaging for the provider move PRs;
+it does not claim every provider is present yet. Google remains one family.
+Existing Core entry-point names stay in Core, so installing the collection does
+not register duplicate plugins. Core's optional lazy compatibility shims follow
+actual aggregate PyPI publication. No base-contract extraction or injected ports.
+
+The older per-provider source directories and hash-bound release files remain
+historical/consumer evidence during transition; they are not additional future
+PyPI distributions. Core-shaped whole provider moves and earlier standalone
+hardened/read-only APIs have different scope and must not be silently co-installed.
+
+# zeointegrations
+
+Integrations for zeo tools: install only the packages a tool needs, discovered
+through `zeo_core.integrations`. Split out of zeocore under zeocore-SOW-36.
+
+External services use `zeo-integration-<name>`; local capabilities use
+`zeo-plugin-<name>`. Google is one package with six existing entry-point names.
+Credentialed integrations execute inside ZEOconnect with injected credentials.
+
+This initial repository contains the development skeleton and a
+[read-only source inventory](docs/inventory/README.md). No provider package is
+installable yet. PyPI publication requires the approved trusted-publisher setup.
+The first slice is tracked as `zeointegrations-SOW-01`, minted by zeo-rt.
+
+```sh
+make setup
+make verify
+```
+
+See [CONTRIBUTING.md](CONTRIBUTING.md) for layout, qualification, migration and
+review rules; [NOTICE](NOTICE) records source attribution.

zeo_integrations-0.1.0.post14/README.md

@@ -0,0 +1,41 @@
+# Zeo integrations
+
+One distribution, `zeo-integrations`, containing provider modules under
+`zeo_integrations.<provider>`. The collection depends on published `zeocore`;
+Core does not import the collection at import time. Provider SDKs are optional
+extras, for example `pip install 'zeo-integrations[google]'` after the single
+aggregate publication exists. During migration, install from this repository
+at an exact reviewed commit. Do not register per-provider PyPI projects.
+
+This first foundation supplies shared packaging for the provider move PRs;
+it does not claim every provider is present yet. Google remains one family.
+Existing Core entry-point names stay in Core, so installing the collection does
+not register duplicate plugins. Core's optional lazy compatibility shims follow
+actual aggregate PyPI publication. No base-contract extraction or injected ports.
+
+The older per-provider source directories and hash-bound release files remain
+historical/consumer evidence during transition; they are not additional future
+PyPI distributions. Core-shaped whole provider moves and earlier standalone
+hardened/read-only APIs have different scope and must not be silently co-installed.
+
+# zeointegrations
+
+Integrations for zeo tools: install only the packages a tool needs, discovered
+through `zeo_core.integrations`. Split out of zeocore under zeocore-SOW-36.
+
+External services use `zeo-integration-<name>`; local capabilities use
+`zeo-plugin-<name>`. Google is one package with six existing entry-point names.
+Credentialed integrations execute inside ZEOconnect with injected credentials.
+
+This initial repository contains the development skeleton and a
+[read-only source inventory](docs/inventory/README.md). No provider package is
+installable yet. PyPI publication requires the approved trusted-publisher setup.
+The first slice is tracked as `zeointegrations-SOW-01`, minted by zeo-rt.
+
+```sh
+make setup
+make verify
+```
+
+See [CONTRIBUTING.md](CONTRIBUTING.md) for layout, qualification, migration and
+review rules; [NOTICE](NOTICE) records source attribution.

zeo_integrations-0.1.0.post14/docs/inventory/README.md

@@ -0,0 +1,148 @@
+# First-hour read-only inventory
+
+Prepared 2026-10-17 by the zeointegrations seat under charter v1 and runtime-minted
+`zeointegrations-SOW-01`. Mint record:
+`matorclawson/org-zeroemployeeorg@d72aba45ac75f20d302295352dd50f3572894ffb:projects/zeointegrations/sow/zeointegrations/zeointegrations-SOW-01-integration-inventory-packaging-skeleton-and.md`.
+Sources:
+
+- VeyraX: canonical `VeyraX/veyrax-platform@1cdddde9d5d76b9891896ca78a95e069647e81df`,
+  inventoried through the identical local `rodriveracom/veyrax-platform` fork.
+- zeocore: `zeroemployeeorg/zeocore@2e7cb11fa9aaf133876c02c1eea8f1ccd94bba04`.
+- Council-reviewed design: zeocore-SOW-36 rev 5,
+  `matorclawson/org-zeroemployeeorg@0f2bf62e2`, with Architect rulings
+  `ans_cbd9dfb83a794f92`.
+
+The [VeyraX table](veyrax.md) covers **84 directories, 79 registered routers,
+79,296 Python lines including tests, and 5,026,896 tracked bytes**. The
+[zeocore table](zeocore.md) covers all **17 registered entry points**. Exact
+sizes, direct import roots, test-only imports and existing dependency declarations
+are in [snapshot.json](snapshot.json). All inspected Python parsed successfully.
+
+## Findings that affect the order
+
+1. This VeyraX snapshot contains no HubSpot or Stripe integration. HubSpot already
+   exists in zeocore; Stripe requires another licensed source or a fresh
+   implementation. Neither should be represented as a VeyraX port.
+2. VeyraX has Gmail code, but `gmail_router` is only imported in `main.py`: it is
+   absent from `INTEGRATION_ROUTERS` and `catalog.json`. DocuSign, Hilvl and
+   veyrax-mcp also have source without registration. `common` is shared support.
+   Source presence does not establish a working deployed integration.
+3. Catalog auth `none` conceals server credentials for Apollo, Binance P2P,
+   Bybit P2P, OKX P2P, IPinfo, Skyscanner, Yelp and Zillow. Their routes/clients
+   read server API keys; they are credentialed integrations under this charter.
+4. Custom auth is not uniform: Amazon uses access/secret keys and associate tag;
+   Cloudinary uses key/secret/cloud name; mail uses SMTP/IMAP credentials;
+   Sentry uses API key/org slug (and has an OAuth branch). Facebook, Instagram,
+   LinkedIn and X combine profile inputs with server RapidAPI credentials.
+   `db_access` means database connection credentials; `api_key_with_base` also
+   accepts a base URL. WhatsApp uses a QR/session bridge. Port credential and
+   origin handling through the Broker's approved interface.
+5. VeyraX NeonDB and Supabase delegate to its PostgreSQL service. Its Supabase
+   SQL operations are not equivalent to zeocore's Supabase SDK integration.
+   Google Maps uses an API key, distinct from Google Workspace OAuth. Its
+   YouTube implementation does not establish coverage of zeocore's upload path.
+6. Shared VeyraX `common` code includes token lookup, refresh and custody. That
+   infrastructure belongs to ZEOconnect and will not be copied into packages.
+   Existing HTML/component assets need translation into zeocore's data-only
+   schema, not direct frontend copying.
+7. `veyrax_auth` is VeyraX's own Supabase-backed credential store with shared
+   encryption; catalog `none` is not credential-free execution. `veyrax` is
+   a per-user memory store over Supabase `users_memory`. Both remain outside
+   the provider-port queue.
+
+## Proposed order
+
+The approved SOW-36 package migration order and this charter's priority for new
+ports are separate queues. Coordinate each move with zeocore; keep one open PR.
+
+1. This skeleton and CI. After merge, the Architect adds the `verify` check to
+   the main ruleset. No publishing workflow or provider package in this slice.
+2. zeocore-owned groundwork: local App signer relocation and duplicate-entry
+   guard; then the credential-free **ffmpeg pilot** in its own package PR.
+   The pilot can prove packaging/discovery, not Broker credential custody.
+3. Local plugins: pandoc, jupytext, notebook (the last keeps no entry point).
+4. Existing credentialed moves in reviewed order: Bluesky; Google (one package,
+   six names); HubSpot; Kit; Notion; Supabase; GitHub; LLMs; Gemini; Meetings;
+   Revolut last. Google/YouTube has its own follow-on split. zeocore owns shims,
+   extras, removals and compatibility. Package moves alone admit no Broker route.
+5. New operation/port work by use: first review HubSpot gaps against its existing
+   package, then Gmail/Google gaps against the unified package; source Stripe
+   separately; then Notion, GitHub and Slack. Start credentialed proof with an
+   already admitted operation and a synthetic provider double agreed with
+   zeoconnect-integrations. Runtime priorities remain subject to owner agreement.
+6. Remaining VeyraX work only as a consumer needs it: task/workflow tools
+   (Linear, Jira, Asana, Todoist, Trello); mail/storage (Outlook, Dropbox, Resend,
+   SMTP); database family (PostgreSQL/Neon/Supabase SQL, ClickHouse, Snowflake);
+   search/research and remaining API-key tools; heavier browser, media, social,
+   QR bridge and unregistered adapters after their runtime dependencies are
+   reviewed. This is a proposed demand order, not authorization for 79 ports.
+
+## Contract and runtime boundary
+
+SOW-36 specifies manifest metadata, package names, entry-point preservation and
+qualification, but no implemented machine serialization or new Broker ABI.
+zeoconnect-tools confirmed this remains joint zeocore/maintainer/council design
+(`ans_a055ed6a622cf24d`). Its loader will bind explicitly pinned installed
+packages through ConnectorRevision and observation/effect dispatchers after
+admission and custody callback. No package-owned OAuth, refresh/store custody,
+caller-selected origin, or credentials in logs/results.
+
+The reviewed design says Broker composition covers two Gmail reads, HubSpot/Kit
+newsletter operations, and two Revolut reads that are HELD; it does not run
+zeocore integration packages today. This is a cited design snapshot, not a claim
+about current live allowlists. Confirm exact per-operation composition and
+admission with the owners before each migration. An existing entry point is not
+proof of an equivalent Broker operation.
+
+The source tree's distribution is named `zeocore`; the design sometimes spells
+it `zeo-core`. Package requirements must use the owner's confirmed actual name
+and minimum compatible version, with real installation proof.
+
+## Method and reproducibility
+
+`tools/inventory.py` obtains the source HEAD commits, uses `git archive` into
+memory, and parses Python AST, TOML and JSON. It executes no source code, loads
+no source environment, reads no live credentials, installs no provider packages,
+and writes only the report outside the source repositories. Dependency lists
+are direct static imports; they do not prove dynamic imports or full transitive
+closure. Lines include comments/blanks and tests. Shared-family sizes are
+identified explicitly rather than counted six times.
+
+```sh
+uv run --frozen python tools/inventory.py \
+  --veyrax /path/to/veyrax-platform \
+  --zeocore /path/to/zeocore \
+  --output docs/inventory/snapshot.json
+```
+
+Use checkouts at the cited commits to reproduce this snapshot. Tables are derived
+from the JSON with auth and overlap qualifications from source review. External
+import roots map to distributions as follows; exact VeyraX source pins appear in
+the JSON and require review for Python 3.14 rather than blind reuse.
+
+| Import root | Distribution |
+|---|---|
+| bs4 | beautifulsoup4 |
+| googleapiclient | google-api-python-client |
+| google | google-auth / google-auth-oauthlib (submodule dependent) |
+| dotenv | python-dotenv |
+| dateutil | python-dateutil (not directly pinned in source requirements) |
+| starlette | starlette (transitive through FastAPI) |
+| amazon_paapi | python-amazon-paapi |
+| clickhouse_driver | clickhouse-driver |
+| e2b_code_interpreter | e2b-code-interpreter |
+| psycopg2 | psycopg2-binary |
+| snowflake | snowflake-connector-python |
+| slack_sdk | slack-sdk |
+| sentry_sdk | sentry-sdk |
+| upstash_vector | upstash-vector |
+| yaml | PyYAML |
+| youtube_transcript_api | youtube-transcript-api |
+| pydantic_core | pydantic-core |
+| notion_client | notion-client (zeocore) |
+| ffmpeg_zeo | ffmpeg-zeo (zeocore) |
+| docx | python-docx in zeocore; VeyraX separately pins docx |
+
+Other displayed roots use their distribution spelling (normalizing underscores
+to hyphens where applicable). No VeyraX implementation is copied in this slice.
+Its complete MIT notice is preserved in [VeyraX-MIT.txt](../licenses/VeyraX-MIT.txt).

zeo_integrations-0.1.0.post14/packages/README.md

@@ -0,0 +1,26 @@
+# Packages
+
+Each integration or local plugin will be added in its own reviewed PR. See
+[the package layout](../CONTRIBUTING.md#package-layout) and
+[the inventory and proposed order](../docs/inventory/README.md).
+
+`loops/` is the first API-client package source, consumed directly by Broker;
+it has no Core lifecycle entry point or credential custody. Qualification and
+release status are recorded in its README.
+
+`kit/` is a current-API, read-only migration/audit client for subscribers and
+their states, tags, forms and custom fields. It has no entry point, Core
+dependency, subscriber writes, broadcast or sequence surface. Core retains its
+legacy service and registry; legacy write consumers are not redirected here.
+Qualification, independent review and actual migration/audit consumer receiving
+remain unfinished until their separate receipts are recorded. No provider
+retirement or live readiness follows from package source.
+
+HubSpot follows under the operator's October 24 priority; the ffmpeg pilot
+remains parked.
+
+`hubspot/` extracts the existing provider client, models, transport and workflow
+validator, preserving reviewed guards. Core retains credential discovery, service,
+factory and sole entry point. Core forwarding and the pinned hard dependency wait
+for an actually installable, separately approved release; no consumer adoption
+or provider execution is established by this source package.

zeo_integrations-0.1.0.post14/packages/hubspot/LICENSE

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

zeo_integrations-0.1.0.post14/packages/hubspot/NOTICE

@@ -0,0 +1,21 @@
+zeo-integration-hubspot
+Copyright (c) 2026 Rod Rivera
+Licensed under the MIT License; full permission notice in LICENSE.
+
+Source: zeroemployeeorg/zeocore
+Commit: 6bd62fbbfc4453908ab464219c2a304d7420b15b
+Source prefix: src/zeo_core/integrations/hubspot/
+Destination prefix: packages/hubspot/src/zeo_integrations/hubspot/
+client.py -> client.py; source blob e36ec1c646b1d1b16184e500bdb9bb6008d97a7c
+models.py -> models.py; source blob a0d95437b736cf7a3198acf1d0f88849aad32903
+transport.py -> transport.py; source blob 7e5b9d0be1f54e33ffe999704a042d125beb67a3
+workflow.py -> workflow.py; source blob 97d628d4b42986332c134dfd2d2db25a24bd67b9
+LICENSE [blob ff593bd47616c4602615f901b800f4d0965c805b] -> packages/hubspot/LICENSE; MIT copyright and permission retained.
+
+The first source commit copies the four modules byte-for-byte. Subsequent
+transport hardening and formatting are separate reviewable changes, preserving
+the original blob pins above. Root exports are explicit provider-only exports;
+Core service, factory, environment discovery and entrypoint are excluded.
+No private Broker fixtures, credentials or custody machinery were copied.
+Tests are original synthetic controls. Package layout follows this repository's
+existing Loops and Kit packages; no new dependency family or runtime SDK.

zeo_integrations-0.1.0.post14/packages/hubspot/README.md

@@ -0,0 +1,37 @@
+# HubSpot marketing provider client
+
+sow: zeointegrations-SOW-02
+
+Provider extraction from Core 6bd62fbb; exact per-file source blobs are in NOTICE.
+Python >=3.12. Inject SecretStr credentials or an HTTP transport explicitly. No
+Core dependency, environment discovery, service factory or entry point is added.
+Core retains its lifecycle and the sole hubspot.marketing registration. Existing
+Core submodule forwarding and class identity are separate Core-owned receiving
+changes; this source does not claim those shims are installed.
+
+The existing client supports marketing email drafts and reviewed publishing,
+campaigns, subscription preferences and a strictly bounded linear email workflow
+subset. Existing confirmation/revision/content-digest/audience/consent guards
+remain. Package code grants no permission to send, schedule, enroll or change
+consent; actual credentialed execution remains inside Broker's approved workflow.
+No live provider or subscriber data is used in verification.
+
+The first commit preserves four Core module blobs exactly. Transport hardening
+is a separate tested commit. A full current-head gate, installed-source identity,
+namespace, wheel/sdist/license/NOTICE checks and compatibility controls are needed
+before source approval. Gates run only with present interpreters; unavailable
+Python 3.12 is NOT_RUN, never a fabricated pass. No interpreter download is
+implied by this package's declared floor.
+
+Release and adoption are separate: Architect requires the existing signed
+vendored-wheel route, no PyPI/new feed, and a pinned HARD dependency from Core
+once the wheel is actually installable. Core shims must not merge first.
+Newsroom and Broker install no separate extra; their exact released-Core locks
+and consumer checks must pass. No release grant, cryptographic wheel signature,
+publication, installed Core forwarding or consumer readiness is claimed here.
+A hash-bound lane record alone is not a cryptographic signature.
+
+Pagination returns one page; complete=true is not an atomic account snapshot.
+Callers bound cross-page cursor history and total reads. Mutation errors can have
+outcome_unknown and require provider-state reconciliation, never automatic retry.
+Dynamic audiences and mutable provider assets retain their existing race limits.

zeo_integrations-0.1.0.post14/packages/hubspot/pyproject.toml

@@ -0,0 +1,31 @@
+[build-system]
+requires = ["hatchling==1.27.0"]
+build-backend = "hatchling.build"
+
+[project]
+name = "zeo-integration-hubspot"
+version = "0.1.0"
+description = "Credential-injected HubSpot marketing client"
+requires-python = ">=3.12"
+license = "MIT"
+readme = "README.md"
+dependencies = ["httpx>=0.28.1,<1", "pydantic>=2.13.4,<3"]
+
+[dependency-groups]
+dev = ["ruff==0.15.5"]
+
+[tool.hatch.build.targets.wheel]
+packages = ["src/zeo_integrations"]
+
+[tool.hatch.build.targets.wheel.force-include]
+"NOTICE" = "zeo_integrations/hubspot/NOTICE"
+
+[tool.ruff]
+target-version = "py312"
+line-length = 88
+
+[tool.ruff.lint]
+select = ["E", "F", "I", "UP", "B"]
+
+[tool.uv]
+constraint-dependencies = ["certifi==2026.7.22", "idna==3.19"]

zeo_integrations-0.1.0.post14/packages/hubspot/src/zeo_integrations/hubspot/__init__.py

@@ -0,0 +1,38 @@
+"""HubSpot provider client; credential discovery and lifecycle remain in Core."""
+
+from .client import HubSpotClient
+from .models import (
+    Audience,
+    CampaignProperties,
+    EmailAddress,
+    EmailContent,
+    EmailDraft,
+    EmailSequence,
+    MarketingPage,
+    MarketingRecord,
+    PageRequest,
+    PublishRequest,
+    SequenceStep,
+    SubscriptionChange,
+    send_spec_digest,
+)
+from .transport import HubSpotAPIError, HubSpotTransport
+
+__all__ = [
+    "Audience",
+    "CampaignProperties",
+    "EmailAddress",
+    "EmailContent",
+    "EmailDraft",
+    "EmailSequence",
+    "HubSpotAPIError",
+    "HubSpotClient",
+    "HubSpotTransport",
+    "MarketingPage",
+    "MarketingRecord",
+    "PageRequest",
+    "PublishRequest",
+    "SequenceStep",
+    "SubscriptionChange",
+    "send_spec_digest",
+]