@nexalink/carecompass-sdk 0.2.0-beta.11 → 0.2.0-beta.13

package/dist/version.js

@@ -1,3 +1,3 @@
-export const CARECOMPASS_SDK_VERSION = "0.2.0-beta.11"; // x-release-please-version
+export const CARECOMPASS_SDK_VERSION = "0.2.0-beta.13"; // x-release-please-version
 export const CARECOMPASS_COMPONENT_VERSION = "1.0.0";
 export const CARECOMPASS_TELEMETRY_CONTRACT_VERSION = "1.0.0";

package/package.json

@@ -1,17 +1,10 @@
 {
   "name": "@nexalink/carecompass-sdk",
-  "version": "0.2.0-beta.11",
+  "version": "0.2.0-beta.13",
   "description": "Embeddable CareCompass SDK and CLI for healthcare ecosystem integrations with Nexalink onboarding, BAA coverage, and API keys.",
   "type": "module",
   "packageManager": "bun@1.3.9",
   "homepage": "https://nexalink.care",
-  "repository": {
-    "type": "git",
-    "url": "https://github.com/nexalink-care/carecompass-sdk.git"
-  },
-  "bugs": {
-    "url": "https://github.com/nexalink-care/carecompass-sdk/issues"
-  },
   "keywords": [
     "carecompass",
     "nexalink",
@@ -46,13 +39,8 @@
   "files": [
     "dist/**/*.js",
     "dist/**/*.d.ts",
-    "CHANGELOG.md",
     "README.md",
-    "TELEMETRY.md",
-    "LICENSE",
-    "RELEASE.md",
-    "SECURITY_AUDIT.md",
-    "RUNTIME_SECURITY_AUDIT.md"
+    "LICENSE"
   ],
   "engines": {
     "node": ">=18"

package/CHANGELOG.md

@@ -1,37 +0,0 @@
-# Changelog
-
-All notable changes to `@nexalink/carecompass-sdk` are documented in this file.
-
-This project uses [release-please](https://github.com/googleapis/release-please) and conventional commits to prepare changelog and version updates.
-
-## [0.2.0-beta.11](https://github.com/nexalink-care/carecompass-sdk/compare/v0.1.0-beta.11...v0.2.0-beta.11) (2026-06-07)
-
-
-### Features
-
-* baa self-serve ([3ff6d66](https://github.com/nexalink-care/carecompass-sdk/commit/3ff6d662dc83215b85615515eec01c54600fb9ea))
-* baa self-serve (CARE-155) ([92c11df](https://github.com/nexalink-care/carecompass-sdk/commit/92c11df5dfc85df195788f5b5aea03112c4c2420))
-* cli update ([99ef0e5](https://github.com/nexalink-care/carecompass-sdk/commit/99ef0e52166b519d8982bd67997fae4a0f1a4bb1))
-* implement telemetry (CARE-158) ([6337fd7](https://github.com/nexalink-care/carecompass-sdk/commit/6337fd791dc8bbf2192f2b683dbd2d0ef3bbf03a))
-* initial commit ([5369c40](https://github.com/nexalink-care/carecompass-sdk/commit/5369c409361be39caaa84db8d3ab1f98f5aec134))
-* initial commit ([26ec799](https://github.com/nexalink-care/carecompass-sdk/commit/26ec79928226e98235cd8c42a348a9e070b948c9))
-* necessary comments ([127c834](https://github.com/nexalink-care/carecompass-sdk/commit/127c8346bc865c5054b02490c890a53bd03db97a))
-* necessary comments ([d7f0d6b](https://github.com/nexalink-care/carecompass-sdk/commit/d7f0d6b7525b9e6282961b8172415e514305bed0))
-* security audit ([8115fe2](https://github.com/nexalink-care/carecompass-sdk/commit/8115fe2a75d522f2560ec1ec0f5d9ea1eb1feba4))
-* security audit ([0505ae1](https://github.com/nexalink-care/carecompass-sdk/commit/0505ae11937ab15d51b633c782494fe6af468217))
-* telemetry ([8f4dff3](https://github.com/nexalink-care/carecompass-sdk/commit/8f4dff3efc80e6e08ad6f0d19b12b7f85688b406))
-* telemetry update ([cd15546](https://github.com/nexalink-care/carecompass-sdk/commit/cd15546a756abfa30bf18705d204e9a21d12822f))
-* update cli flow ([69c55d5](https://github.com/nexalink-care/carecompass-sdk/commit/69c55d58d55ad64281384254852da468e20214f4))
-* updated init flow ([4bd0acf](https://github.com/nexalink-care/carecompass-sdk/commit/4bd0acfd08255b4614fb04b1d5c92b163fb8bcee))
-
-
-### Bug Fixes
-
-* whitespace issue ([764c7fc](https://github.com/nexalink-care/carecompass-sdk/commit/764c7fc23de945f4e358c944312c06c3567b0e5e))
-
-## [0.1.0-beta.11] - 2026-05-30
-
-### Added
-
-- Initial beta SDK package with React embed, vanilla mount helper, CLI setup flow, config validation, snippet generation, and local diagnostics.
-- Supply-chain and runtime security audit documentation for payer deployments.

package/RELEASE.md

@@ -1,65 +0,0 @@
-# CareCompass SDK Release Process
-
-This package is public, but production use requires Nexalink onboarding, BAA coverage where PHI may be involved, and Nexalink-issued credentials. Treat each package release as a supply-chain event.
-
-## Release Authority
-
-- Only approved Nexalink maintainers may publish `@nexalink/carecompass-sdk`.
-- Publish from the canonical GitHub repository: `https://github.com/nexalink-care/carecompass-sdk`.
-- Use the pinned package manager in `package.json` and keep `bun.lock` committed.
-- Do not publish from a dirty working tree or from a local branch that has not passed review.
-
-## Versioning
-
-- Version and changelog updates are managed by release-please on `main`.
-- Use beta versions for pre-production SDKs and avoid reusing a published version.
-- Record security-relevant dependency or packaging changes in the release notes.
-- Use conventional commit messages so release-please can classify release notes.
-
-## Required Validation
-
-Run the full local release check before publishing:
-
-```bash
-bun install --frozen-lockfile
-bun run release:check
-```
-
-`release:check` runs lint, tests, build, dependency audit, and a dry-run package assembly. The package dry run uses `bun pm pack --dry-run --ignore-scripts` so package assembly does not execute install lifecycle scripts.
-
-Before approval, review the dry-run file list and confirm it contains only:
-
-- `dist/**/*.js`
-- `dist/**/*.d.ts`
-- `CHANGELOG.md`
-- `README.md`
-- `TELEMETRY.md`
-- `LICENSE`
-- `RELEASE.md`
-- `SECURITY_AUDIT.md`
-- `RUNTIME_SECURITY_AUDIT.md`
-- `package.json`
-
-Do not publish source maps, local credentials, generated payer configs, test fixtures with secret-like values, `.env` files, package-manager caches, or build logs.
-
-## Dependency And Lockfile Controls
-
-- Use `bun install --frozen-lockfile` in CI to verify reproducible installs.
-- Run `bun audit` before every release.
-- Review `bun outdated` output during routine maintenance and update dev tooling deliberately.
-- Do not add install lifecycle scripts unless the security impact is documented and reviewed.
-- Do not trust transitive package lifecycle scripts in Bun unless there is a specific approved need.
-
-## Provenance, SBOM, And Publishing
-
-Preferred production publishing should use npm trusted publishing or `npm publish --provenance --access public` from CI after the release check passes. Local publishing is allowed only for emergency releases approved by the package owners.
-
-Generate an SBOM during CI when the release pipeline supports it, and retain the SBOM, audit output, package dry-run output, and final tarball integrity in release artifacts.
-
-Release PRs are opened by `.github/workflows/release-please.yml` using the manifest files under `.github/`. Merging the release PR updates `package.json`, `CHANGELOG.md`, and the release manifest, then creates the GitHub release.
-
-## Secret Handling
-
-- Never place Nexalink SDK API keys, payer credentials, SageMaker credentials, AppSync signing roles, or private endpoint URLs in source, docs, tests, generated snippets, package metadata, or release artifacts.
-- CLI credentials must stay in the local credentials file or environment variables described in `README.md`.
-- Generated browser embed files may include public payer configuration and prompt text. Review generated files before committing them to an integrating application.

package/RUNTIME_SECURITY_AUDIT.md

@@ -1,180 +0,0 @@
-# CARE-153 Runtime, API, And Tenant-Isolation Audit
-
-Audit date: 2026-05-30
-
-Scope: SDK-side runtime, embed, CLI validation, generated snippets, browser configuration, prompt configuration, sensitive-data handling, and documentation for payer deployments. Hosted Nexalink API route implementations, backend rate limiting, backend CORS enforcement, backend logs, analytics stores, and SageMaker/AppSync infrastructure are outside this repository and must be validated in the hosted API codebase.
-
-## Summary
-
-The SDK does not ship private SageMaker credentials, AppSync signing roles, privileged backend tokens, or secret Nexalink SDK API keys to the browser. Browser requests use public payer configuration and public embed headers; backend hosted routes remain the authoritative enforcement point for payer identity, embed-key authorization, allowed origins, rate limits, prompt guardrails, logs, analytics, and tenant isolation.
-
-This audit found and remediated two SDK-side runtime issues:
-
-- Staging and production configs could previously point `apiBaseUrl` at any HTTPS origin. The schema now requires a Nexalink-hosted HTTPS API URL for staging and production, with localhost allowed only for development.
-- Generated embed snippets previously serialized config with plain `JSON.stringify` inside a module script. Config values containing `</script>` could break the script context when served as raw HTML. Snippet generation now escapes script-sensitive JSON characters and iframe attributes.
-
-## Auth And API Access Model
-
-- CLI commands use the secret Nexalink SDK API key from `--api-key`, `CARECOMPASS_API_KEY`, or the local credentials file.
-- `init` uses that API key to check BAA status and submit execution metadata to Nexalink-hosted routes. The CLI never receives AWS credentials.
-- Browser/runtime code never receives the secret SDK API key.
-- Browser requests include:
-  - `x-carecompass-payer-id`
-  - `x-carecompass-embed-key`
-  - `x-carecompass-environment`
-- Browser requests target only these SDK paths under the configured Nexalink-hosted API base URL:
-  - `POST /api/carecompass/embed/config/validate`
-  - `POST /api/carecompass/embed/ask`
-  - `GET /api/carecompass/embed/status/:jobId`
-
-Backend requirements that must remain enforced outside this SDK:
-
-- payer ID and embed key binding
-- environment binding
-- exact allowed-origin checks
-- tenant isolation for configuration, prompts, requests, responses, logs, analytics, and usage records
-- rate limiting and request attribution by payer/deployment
-
-## Tenant Isolation Review
-
-SDK-side controls:
-
-- The config schema validates payer ID format, embed key format, deployment environment, allowed origins, API base URL, prompt structure, theme values, and public branding fields.
-- Staging and production cannot use localhost API base URLs or localhost allowed origins.
-- The client sends payer ID, embed key, and environment on every config-validation and inference request.
-- The SDK does not expose APIs for reading another payer's configuration, analytics, logs, prompt history, or user data.
-
-Backend-owned validation:
-
-- The SDK cannot prove cross-payer isolation by itself because tenant state lives in hosted Nexalink services.
-- Hosted routes must reject mismatched payer ID, embed key, environment, and origin tuples.
-- Hosted routes must scope job status lookups by payer/deployment, not only by `jobId`.
-
-## Allowed Origin And API Base URL Controls
-
-Resolved in this branch:
-
-- `apiBaseUrl` must be a Nexalink-hosted HTTPS URL, except localhost for development.
-- Staging and production configs reject localhost `apiBaseUrl`.
-- Staging and production configs reject localhost allowed origins.
-- Browser-hosted pages still fail fast if a non-local page tries to call a localhost API base URL.
-
-Follow-up for hosted API:
-
-- Test unauthorized origins against deployed staging and production routes.
-- Confirm CORS and origin checks happen server-side and are not based only on SDK validation.
-
-## Client-Side Token And Secret Handling
-
-No client-side secret exposure was found.
-
-- Secret SDK API keys are read by the CLI only.
-- The browser receives public `embedKey`, payer ID, environment, branding, labels, allowed origins, and prompt configuration.
-- Credential storage writes local keys with file mode `0600`.
-- CLI output prints the credentials path and source, not the API key value.
-- Executed BAA copies contain agreement metadata and terms, not the SDK API key
-  or private cloud credentials. The CLI writes local executed copies with
-  owner-only (`0600`) permissions.
-
-## Prompt Controls And Sensitive Data Handling
-
-SDK-side controls:
-
-- Prompt instructions are length-limited and checked for explicit guardrail-bypass patterns.
-- Generated setup guidance warns against secrets, raw PHI, diagnosis instructions, treatment instructions, and guardrail bypass attempts in prompt files.
-- `allowUserContext` defaults to `false`.
-
-Backend-owned validation:
-
-- Hosted routes must re-validate prompt configuration against Nexalink policy because browser config is attacker-controlled.
-- Hosted routes must treat user messages, prompt content, model responses, and optional user context as sensitive data.
-
-## Embed, XSS, And CSP Review
-
-Resolved in this branch:
-
-- Generated config JSON is escaped before insertion into `<script type="module">`.
-- Generated iframe `title` and `src` attributes are HTML-attribute escaped.
-
-Existing controls:
-
-- React renders labels and messages as text, not raw HTML.
-- The component does not use `dangerouslySetInnerHTML`, `innerHTML`, `eval`, or `new Function`.
-
-Integration guidance:
-
-- Prefer bundler mode over CDN mode for production.
-- If CDN mode is used for a raw browser demo, the integrating page should set CSP `script-src` for the approved CDN and Nexalink assets only.
-- Do not place unreviewed payer-provided HTML or third-party scripts in generated embed pages.
-
-## Logging, Diagnostics, Telemetry, And Errors
-
-CARE-158 adds an always-on privacy-safe telemetry transport documented in
-`TELEMETRY.md`. The SDK sends only allowlisted anonymous lifecycle metadata to
-PostHog's public ingestion API using a Nexalink-owned public ingestion token.
-Integrators do not configure telemetry or receive a disable switch. The SDK
-does not bundle `posthog-js`, enable session replay or autocapture, identify
-users, set cookies, or persist analytics state.
-
-The CLI sends fixed onboarding funnel events through the same transport. Each
-CLI process uses an ephemeral random session ID that is not persisted. CLI
-payloads exclude arguments, terminal input, file paths, API keys, and BAA signer
-details.
-
-Telemetry payloads exclude prompts, model responses, chat history, optional
-user context, PHI/PII, credentials, raw errors, stack traces, request payloads,
-and response bodies. Error telemetry uses fixed codes and categories. Telemetry
-delivery failures are swallowed so analytics cannot interrupt SDK workflows.
-Runtime errors shown in the component remain derived from local network
-failures or backend error responses.
-
-Backend-owned controls:
-
-- Hosted routes must avoid logging raw PHI/PII, credentials, raw prompts, raw model responses, or privileged backend tokens unless an explicitly approved secure diagnostic path exists.
-- Backend error responses should be sanitized because the component may display the error message.
-
-## Rate Limiting And Abuse Prevention
-
-The SDK can attribute requests by payer ID, embed key, and environment headers, but cannot enforce real rate limits or abuse controls because browser clients are untrusted.
-
-Hosted routes must enforce:
-
-- per-payer and per-origin rate limits
-- per-embed-key request attribution
-- abuse detection for prompt flooding and job-status polling
-- safe status lookup scoping by payer/deployment
-
-## Verification
-
-Commands run:
-
-| Command                 | Result                                                                                      |
-| ----------------------- | ------------------------------------------------------------------------------------------- |
-| `bun run test`          | Validates schema hardening, snippet escaping, CLI behavior, and component runtime requests. |
-| `bun run lint`          | Ensures code quality after remediation.                                                     |
-| `bun run build`         | Regenerates distributable JavaScript and declarations.                                      |
-| `bun run release:check` | Runs frozen install, lint, tests, build, audit, and package dry run.                        |
-
-New regression coverage:
-
-- Reject non-Nexalink `apiBaseUrl` values.
-- Allow localhost API/origin/support URLs only for development.
-- Reject unsafe branding URL schemes.
-- Escape `</script>`-style values in generated embed config JSON.
-- Escape iframe attributes.
-
-## Findings And Follow-Up
-
-Resolved:
-
-- Medium: staging/production `apiBaseUrl` allowed arbitrary HTTPS endpoints. Owner: SDK. Remediation: require Nexalink-hosted HTTPS API URLs outside development.
-- Medium: generated script snippets did not escape script-sensitive JSON characters. Owner: SDK. Remediation: escape `<`, `>`, `&`, U+2028, and U+2029 in serialized config JSON.
-
-No high or critical SDK-side runtime findings remain in this repository.
-
-Follow-up required outside this SDK repository:
-
-- Validate deployed hosted API CORS/origin enforcement with unauthorized origins.
-- Validate cross-payer tenant isolation for config, prompt, analytics, logs, job status, and model request data in the hosted API codebase.
-- Validate backend log/telemetry redaction for raw prompts, model responses, credentials, PHI/PII, and privileged tokens.
-- Validate backend rate limiting and request attribution by payer, environment, origin, and embed key.

package/SECURITY_AUDIT.md

@@ -1,78 +0,0 @@
-# CARE-152 Dependency And Supply-Chain Audit
-
-Audit date: 2026-05-30
-
-Scope: `@nexalink/carecompass-sdk` source, package metadata, Bun lockfile, generated `dist` artifacts, README guidance, local package assembly, and release-process documentation.
-
-## Summary
-
-No high or critical dependency vulnerabilities were found by the available package-manager audit. No hardcoded Nexalink API key, payer credential, SageMaker credential, AppSync signing role, private model endpoint, AWS access key, or private endpoint URL was found in the package source or generated distributable files.
-
-The audit found supply-chain process gaps rather than an active secret exposure: release provenance and SBOM expectations were not previously documented, the package manager was not pinned in `package.json`, and the package dry-run script delegated to `bunx --bun npm pack`. These have been remediated in this branch with pinned package-manager metadata, a safer dry-run pack script, explicit release documentation, and exclusion of source maps from the published package surface.
-
-## Commands Run
-
-| Command                                  | Result                                                                                                                                        |
-| ---------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------- |
-| `bun audit`                              | Passed. No vulnerabilities found.                                                                                                             |
-| `npm audit --audit-level=high`           | Not applicable because this repository uses `bun.lock` and has no `package-lock.json`.                                                        |
-| `bun outdated`                           | Runtime dependency `zod` current. Dev-tooling major updates available for `@eslint/js`, `eslint`, `@types/node`, `globals`, and `typescript`. |
-| `bun run build`                          | Passed after refreshing local Bun install links.                                                                                              |
-| `bun run lint`                           | Passed.                                                                                                                                       |
-| `bun run test`                           | Passed: 3 suites, 17 tests.                                                                                                                   |
-| `bun pm pack --dry-run --ignore-scripts` | Passed and confirmed the intended package contents.                                                                                           |
-
-## Dependency Review
-
-Runtime dependency:
-
-- `zod` `^4.4.3`
-
-Peer dependencies:
-
-- `react` `^18.3.0 || ^19.0.0`
-- `react-dom` `^18.3.0 || ^19.0.0`
-
-Development dependencies are limited to the React, Jest, ESLint, Prettier, TypeScript, and type-definition toolchain. The dependencies are mainstream packages, and the runtime package surface is small.
-
-`bun.lock` pins concrete transitive versions and integrity hashes for Bun installs. Non-Bun package managers are supported for consumers, but repository development and release validation are intentionally pinned to Bun with `bun install --frozen-lockfile`.
-
-## Package Script Review
-
-No `preinstall`, `install`, `postinstall`, `prepare`, `prepublish`, `publish`, or `postpublish` lifecycle scripts are declared by the root package.
-
-Package assembly now uses:
-
-```bash
-bun pm pack --dry-run --ignore-scripts
-```
-
-This avoids fetching or executing an external pack command through `bunx` and prevents lifecycle scripts during the dry run.
-
-## Generated Artifact Review
-
-The package publishes only `dist/**/*.js`, `dist/**/*.d.ts`, `README.md`, `LICENSE`, `RELEASE.md`, `SECURITY_AUDIT.md`, `RUNTIME_SECURITY_AUDIT.md`, and `package.json`.
-
-Source maps were removed from the published package surface. They did not contain embedded `sourcesContent`, but excluding them reduces accidental source-path and metadata disclosure in the public npm package.
-
-Searches for secret-like terms found only documented placeholders, public configuration examples, local credential handling code, and expected hosted API URLs. Credential writes use file mode `0600`, and CLI output does not print the secret API key.
-
-## Release-Process Risks And Remediation
-
-Resolved in this branch:
-
-- Added `packageManager` to pin Bun for development and release validation.
-- Added repository and issue metadata to `package.json`.
-- Added npm registry to `publishConfig`.
-- Added `audit` and `release:check` scripts.
-- Replaced `pack:dry-run` with a Bun-native dry run that ignores scripts.
-- Added `RELEASE.md` with versioning, validation, provenance, SBOM, and secret-handling expectations.
-- Excluded source maps from the package surface.
-
-Follow-up recommendations:
-
-- Add CI that runs `bun install --frozen-lockfile`, `bun run release:check`, and stores audit and package dry-run output as artifacts.
-- Publish through npm trusted publishing or `npm publish --provenance --access public`.
-- Generate and retain an SBOM for each production release.
-- Review major dev-tooling updates reported by `bun outdated` on a maintenance cadence.
-- Keep runtime dependency additions rare and require security review for any package with install lifecycle scripts or native binary behavior.

package/TELEMETRY.md

@@ -1,129 +0,0 @@
-# CareCompass SDK Telemetry Contract
-
-Contract version: `1.0.0`
-
-CareCompass SDK telemetry measures deployment health without collecting PHI,
-PII, chat content, or credentials. The web SDK sends allowlisted anonymous
-events directly to PostHog's public ingestion API. The CLI uses the same narrow
-transport for onboarding funnel events. React Native and Flutter SDKs should
-adopt the same event names and property contract.
-
-## Configuration
-
-Telemetry is enabled automatically for every web SDK deployment. Integrators do
-not need to run an additional CLI command, add a runtime config block, or manage
-a PostHog token.
-
-The web SDK sends events to Nexalink's PostHog project through the public US
-ingestion endpoint. It uses a Nexalink-owned public PostHog project token
-compiled into the SDK. The token permits event ingestion only; it is never a
-PostHog personal or admin API key.
-
-The anonymous deployment ID is derived from the public payer ID, environment,
-and web platform. For example, payer `acme-health` in staging is reported as
-`acme-health-staging-web`.
-
-CLI invocations use an ephemeral random `cli_session_id` as their anonymous
-PostHog `distinct_id`. It is created in memory for one process invocation and is
-not persisted. Before the CLI has public payer context, events use
-`anonymous-unknown-cli`; later events use the public payer ID and environment.
-
-## Event Taxonomy
-
-Initialization and configuration:
-
-- `carecompass_sdk_initialized`
-- `carecompass_sdk_initialization_failed`
-- `carecompass_sdk_configuration_validated`
-- `carecompass_sdk_configuration_failed`
-
-Component lifecycle:
-
-- `carecompass_component_rendered`
-- `carecompass_component_opened`
-- `carecompass_component_closed`
-- `carecompass_component_error`
-
-Inference lifecycle:
-
-- `carecompass_prompt_submitted`
-- `carecompass_inference_succeeded`
-- `carecompass_inference_failed`
-- `carecompass_inference_rate_limited`
-
-Customization and deployment health:
-
-- `carecompass_theme_loaded`
-- `carecompass_prompt_configuration_loaded`
-- `carecompass_prompt_configuration_failed`
-
-CLI onboarding:
-
-- `carecompass_cli_started`
-- `carecompass_cli_login_started`
-- `carecompass_cli_login_succeeded`
-- `carecompass_cli_login_failed`
-- `carecompass_cli_init_started`
-- `carecompass_cli_init_failed`
-- `carecompass_cli_setup_kit_generated`
-- `carecompass_cli_validation_succeeded`
-- `carecompass_cli_validation_failed`
-- `carecompass_cli_snippet_generated`
-- `carecompass_cli_doctor_completed`
-- `carecompass_cli_command_failed`
-
-For the always-visible web embed, opened and closed map to mount and unmount.
-Future mobile components should map these events to their equivalent visible
-screen lifecycle.
-
-## Allowed Properties
-
-Events contain only:
-
-- `contract_version`
-- `sdk_version`
-- `component_version`
-- `platform`
-- `environment`
-- `payer_id`
-- `deployment_id`
-- `event_timestamp`
-- `duration_bucket`, when applicable
-- `failure_category`, when applicable
-- `error_code`, when applicable
-- `cli_session_id`, for CLI events only
-- `$process_person_profile: false`
-
-The transport also sends the public PostHog project token, event name, anonymous
-`distinct_id`, and timestamp required by the PostHog ingestion API. Web events
-use the deployment ID as `distinct_id`; CLI events use the ephemeral
-`cli_session_id`. It does not identify individual users or create person
-profiles.
-
-## Prohibited Data
-
-Never send:
-
-- raw user prompts, model responses, chat history, or optional user context
-- PHI, PII, member IDs, policy IDs, names, emails, or phone numbers
-- API keys, access tokens, cookies, credentials, or session secrets
-- CLI arguments, terminal input, or file paths
-- SageMaker credentials, internal infrastructure details, or privileged tokens
-- raw error objects, stack traces, request payloads, or response bodies
-- payer prompt text; use an approved non-sensitive configuration ID in a future
-  contract version if needed
-
-The web SDK intentionally does not bundle `posthog-js`. It does not enable
-session replay, autocapture, DOM capture, form capture, cookies, persistence,
-surveys, feature flags, or user identification.
-
-Package download counts remain registry-owned metrics. CLI telemetry begins when
-the user invokes the installed package.
-
-## Verification
-
-1. Mount a development component, submit a non-PHI prompt, and complete an
-   inference.
-2. Confirm the expected lifecycle events arrive in Nexalink's PostHog project.
-3. Inspect event payloads and verify they contain only the allowlisted
-   properties above.