@owlmeans/payment 0.1.19-rc.0 → 0.1.20-alpha.0

package/README.md

@@ -8,7 +8,7 @@ server integration (`@owlmeans/server-payment`) implements against these contrac
 ## Installation
 
 ```bash
-bun add @owlmeans/payment@^0.1.19-rc.0
+bun add @owlmeans/payment@0.1.20-alpha.0
 ```
 
 ## Concepts
@@ -129,7 +129,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@^0.1.19-rc.0
+npx @owlmeans/agent-skills@0.1.20-alpha.0
 ```
 
 The embedded files are version-matched to this package release. Do not edit them

package/agent-meta/manifest.json

@@ -1,8 +1,8 @@
 {
   "schemaVersion": 3,
   "package": "@owlmeans/payment",
-  "version": "0.1.19-rc.0",
-  "generatedAt": "2026-10-31T12:13:02.392Z",
+  "version": "0.1.20-alpha.0",
+  "generatedAt": "2026-11-03T05:44:27.344Z",
   "canonicalRepo": "https://github.com/owlmeans/common",
   "entries": [
     {

package/agent-meta/skills/entitlements/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: entitlements
-description: "The OwlMeans entitlement model across @owlmeans/payment, @owlmeans/server-payment and @owlmeans/web-payment — ranked plans with a real free plan, capabilities versus counted limits, the three limit kinds, promos and grandfathering, the admission-first usage ledger and its may-over-count-never-over-admit invariant, the entitlement view the server gate and the browser both read, the two gate services, and the refusal errors. Use when deciding what a plan grants, gating a route on a feature or a quota, consuming or releasing a limit, or rendering plan state in a UI."
+description: "The OwlMeans entitlement model across @owlmeans/payment, @owlmeans/server-payment and @owlmeans/web-payment — ranked plans with a real free plan, capabilities versus counted limits, the three limit kinds, promos and grandfathering, entitlement grants (units and capabilities for one organization beside its plan), the admission-first usage ledger and its may-over-count-never-over-admit invariant, the entitlement view the server gate and the browser both read, the two gate services, and the refusal errors. Use when deciding what a plan grants, gating a route on a feature or a quota, consuming or releasing a limit, or rendering plan state in a UI."
 user-invocable: false
 ---
 <!-- AUTO-GENERATED — do not edit. Regenerate via sync-agent-meta. -->
@@ -39,6 +39,25 @@ answer from the same pure functions, so a disabled button and a 403 cannot disag
 - A plan names its keys, never a product's copy: every limit key an application gates on appears
   on every plan (with `limit: 0` where not included), so "not included" is an answer, not a
   missing row.
+- **An operator's plan is an internal grant**: `grantInternalPlan(…, { force: true, periodEnd })`
+  gives any plan without a paygate, `revokeInternalPlan` ends it (observers hear `canceled`); a
+  re-grant after a lapse re-activates the same row and keeps its first `createdAt` (`restartedAt`
+  marks the restart) — the `server-payment` skill, § The subscription store.
+
+## Entitlement grants — more than the plan, for one organization
+
+A `payment-grant` record (`entitlementGrantsOf(ctx)`, `server-payment` § Entitlement grants) adds to
+ONE organization, beside whatever plan it holds, until it ends or is revoked:
+
+- **units** of a limit key — consumed only AFTER the plan's own allowance, folded into the limit's
+  `limit` / `used` / `remaining` everywhere the limit is read (the entitlement view and the gates
+  carry no extra field); a revoke drops the unused units, the used ones stay consumed, and an
+  occupancy held past the new ceiling follows the ordinary over-limit flag;
+- **a capability** (`scope:permission[>=n]`) — merged into the effective plan while in force; a
+  units grant may carry the capability its units need (published sites need the publish feature).
+- Read limits and capabilities from the effective plan or the view, never from the catalogue, or a
+  grant is missed exactly as an override would be. `onEntitlementGrant` is the application's hook
+  to provision on a gain and withdraw on a loss.
 
 ## Capabilities versus limits
 

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

@@ -8,7 +8,7 @@ user-invocable: false
 # @owlmeans/payment
 
 **Layer:** Core
-**Install:** `"@owlmeans/payment": "^0.1.19-rc.0"` in `dependencies`
+**Install:** `"@owlmeans/payment": "0.1.20-alpha.0"` in `dependencies`
 
 The contracts half of payments: the catalogue (products, plans, localizations), amount- and
 quantity-priced checkout, the entitlement model — plan capabilities, counted limits, promos,

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@owlmeans/payment",
-  "version": "0.1.19-rc.0",
+  "version": "0.1.20-alpha.0",
   "license": "MIT",
   "type": "module",
   "scripts": {
@@ -32,19 +32,19 @@
     "ajv": "*"
   },
   "dependencies": {
-    "@owlmeans/api-config": "^0.1.19-rc.0",
-    "@owlmeans/auth": "^0.1.19-rc.0",
-    "@owlmeans/basic-envelope": "^0.1.19-rc.0",
-    "@owlmeans/config": "^0.1.19-rc.0",
-    "@owlmeans/context": "^0.1.18",
-    "@owlmeans/error": "^0.1.18",
-    "@owlmeans/i18n": "^0.1.18",
-    "@owlmeans/entrypoint": "^0.1.19-rc.0",
-    "@owlmeans/resource": "^0.1.19-rc.0",
-    "@owlmeans/route": "^0.1.18"
+    "@owlmeans/api-config": "^0.1.19",
+    "@owlmeans/auth": "^0.1.19",
+    "@owlmeans/basic-envelope": "0.1.20-alpha.0",
+    "@owlmeans/config": "^0.1.19",
+    "@owlmeans/context": "^0.1.19",
+    "@owlmeans/error": "^0.1.19",
+    "@owlmeans/i18n": "^0.1.19",
+    "@owlmeans/entrypoint": "^0.1.19",
+    "@owlmeans/resource": "^0.1.19",
+    "@owlmeans/route": "^0.1.19"
   },
   "devDependencies": {
-    "@owlmeans/dep-config": "^0.1.18",
+    "@owlmeans/dep-config": "^0.1.19",
     "nodemon": "^3.1.14",
     "typescript": "^7.0.2"
   },