@owlmeans/client-payment 0.1.18-rc.5 → 0.1.18-rc.51

package/README.md

@@ -12,7 +12,7 @@ Client-side payment service integration for the OwlMeans context system.
 ## Installation
 
 ```bash
-bun add @owlmeans/client-payment
+bun add @owlmeans/client-payment@^0.1.18-rc.51
 ```
 
 ## Usage
@@ -58,7 +58,7 @@ This package ships embedded agent skills under `agent-meta/`. After installing y
 your project's skill store (`.agents/skills/`):
 
 ```sh
-npx @owlmeans/agent-skills
+npx @owlmeans/agent-skills@^0.1.18-rc.42
 ```
 
 The embedded files are version-matched to this package release. Do not edit them

package/agent-meta/manifest.json

@@ -1,8 +1,8 @@
 {
   "schemaVersion": 2,
   "package": "@owlmeans/client-payment",
-  "version": "0.1.18-rc.0",
-  "generatedAt": "2026-08-16T22:20:50.504Z",
+  "version": "0.1.18-rc.51",
+  "generatedAt": "2026-09-29T08:01:58.123Z",
   "canonicalRepo": "https://github.com/owlmeans/common",
   "entries": [
     {

package/agent-meta/skills/client-payment/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: client-payment
-description: How to use @owlmeans/client-payment — client-side payment service that wraps @owlmeans/payment for use from a React app. Auto-invoked when importing client payment primitives.
+description: How to use @owlmeans/client-payment — the browser-side PaymentService, which adds a cached shallow identity on top of @owlmeans/payment so a returning visitor keeps their profile without re-presenting a token. Auto-invoked when registering the payment service in a client context or calling shallowAuthentication from a browser.
 user-invocable: false
 ---
 <!-- AUTO-GENERATED — do not edit. Regenerate via sync-agent-meta. -->
@@ -8,23 +8,52 @@ user-invocable: false
 # @owlmeans/client-payment
 
 **Layer:** Client
-**Install:** `"@owlmeans/client-payment": "^0.1.18-rc.0"` in `dependencies`
+**Install:** `"@owlmeans/client-payment": "^0.1.18-rc.51"` in `dependencies` (peer `react`)
 
-## Key Exports
+The same `PaymentService` as `@owlmeans/payment`, with one method adapted for a browser. Everything
+else — catalogue reads, entitlement helpers and protocol objects — comes from the core package.
+Reusable checkout hooks and UI live in `@owlmeans/web-payment`; this package remains the underlying
+browser service.
+
+## Key exports
 
 | Export | Description |
-|--------|-------------|
-| `makePaymentService()` | Client-side payment service factory |
-| Payment types | Re-exports / extends `@owlmeans/payment` types |
-| Constants | Service aliases |
+|---|---|
+| `makePaymentService(alias?)` · `appendPaymentService(ctx, alias?)` | The client service factory and its registration helper. Same signatures as the core package's. |
+| `SHALLOW_AUTH` | `'payment:shallow-auth'` — the record id the resolved profile is cached under. |
+| `DEFAULT_ALIAS` | Re-exported, so a client wires the service without also importing the core package. |
+| `PaymentService` | Re-exported type. |
+
+## What it changes: `shallowAuthentication`
+
+A checkout leaves the app and comes back, and the token that identified the visitor on the way out
+is gone by the time they return. So the client override persists the answer:
+
+- **With a token** — the core implementation reads the `profileId` out of it, then the result is
+  saved into the client auth resource (`AUTH_RESOURCE`) under `SHALLOW_AUTH`.
+- **Without one** — the saved record is loaded instead, and its `profileId` returned. When there is
+  no record, or it carries no profile, it throws `PaymentIdentificationError`.
 
-## Usage
+This is identification, not authorization: the token is read, never verified. Gate a paid
+capability with `entitled(...)` on the route rather than with anything this returns.
 
 ```typescript
-import { makePaymentService } from '@owlmeans/client-payment'
-context.registerService(makePaymentService())
+import { appendPaymentService } from '@owlmeans/client-payment'
+
+appendPaymentService(context)
 ```
 
+Registering under the core `DEFAULT_ALIAS` is what lets shared code resolve one payment service
+whichever side it runs on. The client auth resource must be registered too — the override reads it
+on every call.
+
 ## Depends On
 
-- `@owlmeans/payment`, `@owlmeans/client-context`, `@owlmeans/client-entrypoint`
+- `@owlmeans/payment` · `@owlmeans/client-auth` (`AUTH_RESOURCE`) · `@owlmeans/context`
+- peer `react`
+
+## Related
+
+- [[payment]] — the contracts, the catalogue and the entitlement grammar
+- `web-payment` — protocol-bound hooks, same-window checkout navigation and amount dialog
+- [[client-auth]] — the auth resource the shallow identity is cached in

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@owlmeans/client-payment",
-  "version": "0.1.18-rc.5",
+  "version": "0.1.18-rc.51",
   "license": "MIT",
   "type": "module",
   "scripts": {
@@ -21,9 +21,9 @@
     }
   },
   "dependencies": {
-    "@owlmeans/client-auth": "^0.1.18-rc.5",
-    "@owlmeans/context": "^0.1.18-rc.5",
-    "@owlmeans/payment": "^0.1.18-rc.5"
+    "@owlmeans/client-auth": "^0.1.18-rc.52",
+    "@owlmeans/context": "^0.1.18-rc.32",
+    "@owlmeans/payment": "^0.1.18-rc.42"
   },
   "peerDependencies": {
     "react": "*"