Licensing rules (add-on)

Every licensing rule in the store with the catalog beside it, plus the rule kinds, the subscription endings, the placeholder legend the delivery copy is written in and the store's default key layout with a sample key. A rule decides which products earn keys, how many, and on what terms. Rules resolve variant over product: a rule with no variant covers every variant of its product, and a rule naming a variant replaces it for that variant only. Call this before writing a rule, to see what is already there and to get the product and variant ids.

Whether one order's lines earn license keys, how many it has been given already, and which event the store mints them on — paid waits for the money to land, completed issues the moment the order is placed. Use it to tell an order that sells nothing licensed from one whose keys have not been minted yet, which is the difference an empty key list cannot show. The count is the issuer's own plan, so a rule naming one variant, a disabled rule and the quantity models are all accounted for. Renewal lines are not counted: a renewal adds time to a key the customer already holds and mints nothing. addons lists every product the order put on an existing key, each with the key it landed on, including the extra products a bundle variant grants. An unknown order answers 404.

Create or replace the product-wide licensing rule, which governs every variant that has no rule of its own. Addressed by the product rather than by a rule id, so saving the same body twice writes the same row twice and there is no "did I already create this" question to get wrong. Only the fields sent are written, and each is judged against the rule as it will be after the save, not against this request alone. A renewal with no renews_product_id and an addon with no attaches_product_id are refused with 422, as is a rule pointing at itself, an unknown product, a bad key prefix or format, and a license file with no name or no contents. An unknown product answers 404. Changing the key layout only affects keys issued from then on.

Create or replace one variant's own licensing rule, which replaces the product-wide rule for that variant and leaves every other variant on the product's. Use it to license a "Team" variant on different terms without writing a rule for every other variant, or to sell renewal lengths as variants that differ only in price and updates_days. The body, the validation and the refusals are exactly save_product_rule's; a variant belonging to a different product answers 422.

Remove the product-wide licensing rule, so the product stops earning keys unless one of its variants has a rule of its own. Keys already issued keep working, because a rule is about issuance and never about the keys already sold; suspend or revoke those individually. A product with no rule answers 404.