@mohasinac/appkit 4.62.1 → 4.63.0

package/dist/_internal/shared/actions/action-registry.js

@@ -64,6 +64,73 @@ export function actionLabel(def) {
 // just establishes the shape + a few "obvious" actions that other Phase 5
 // flows can reference today.
 export const ACTIONS = {
+    /*
+     * D56 — self-serve ad bookings.
+     *
+     * 🛑 `book-ad-slot` carries a confirmation because it is a PURCHASE of a
+     * named month, and cancelling it does not free that month for re-sale —
+     * the booking document IS the availability lock and keeping it is
+     * deliberate. A control that spends money and cannot be undone by the
+     * person who clicked it is exactly what Rule #7's confirmation is for.
+     */
+    ADS: {
+        "book-ad-slot": {
+            iconKey: "create",
+            id: "ads.book-ad-slot",
+            label: "Book this slot",
+            ariaLabel: "Book this ad slot for the selected month",
+            description: "Reserves one placement for one month at the listed flat fee. The creative is reviewed by a person before it appears anywhere.",
+            kind: "primary",
+            permissions: ["user"],
+            confirmation: {
+                title: "Book this slot?",
+                body: "This reserves the placement for the whole month at the listed price. Cancelling later does not release the month for someone else to buy.",
+                confirmLabel: "Yes, book it",
+            },
+        },
+        "cancel-ad-booking": {
+            iconKey: "cancel",
+            id: "ads.cancel-ad-booking",
+            label: "Cancel booking",
+            ariaLabel: "Cancel this ad booking",
+            description: "Stops the creative running. 🛑 Does NOT free the month — the slot stays yours for the period you booked; releasing it is a separate admin act with a refund behind it.",
+            kind: "danger",
+            permissions: ["user"],
+            confirmation: {
+                title: "Cancel this booking?",
+                body: "Your ad stops running. The month is NOT released for another advertiser, and this does not issue a refund on its own.",
+                confirmLabel: "Yes, cancel",
+            },
+        },
+        "approve-ad-creative": {
+            iconKey: "verify",
+            id: "ads.approve-ad-creative",
+            label: "Approve creative",
+            ariaLabel: "Approve this ad creative so it can render",
+            description: "Clears the creative to render for its booked month. Approval is of THIS creative — an edit returns it to review.",
+            kind: "primary",
+            permissions: ["admin", "moderator"],
+            confirmation: {
+                title: "Approve this creative?",
+                body: "It will render on the public site for its booked month once the booking is paid.",
+                confirmLabel: "Yes, approve",
+            },
+        },
+        "reject-ad-creative": {
+            iconKey: "reject",
+            id: "ads.reject-ad-creative",
+            label: "Reject creative",
+            ariaLabel: "Reject this ad creative and tell the advertiser why",
+            description: "Sends it back with your note. A note is REQUIRED — without one the advertiser resubmits the same creative and you review it twice.",
+            kind: "danger",
+            permissions: ["admin", "moderator"],
+            confirmation: {
+                title: "Reject this creative?",
+                body: "The advertiser sees your note and can submit a new creative against the same booking. The slot stays theirs.",
+                confirmLabel: "Yes, reject",
+            },
+        },
+    },
     PRODUCT: {
         /*
          * The buyer-facing verbs below shipped long ago; the four CRUD entries
@@ -929,6 +996,36 @@ export const ACTIONS = {
             kind: "primary",
             permissions: ["seller", "admin"],
         },
+        "dispatch-custom": {
+            iconKey: "ship",
+            id: "store.dispatch-custom",
+            label: "Record dispatch",
+            ariaLabel: "Record a parcel you posted yourself",
+            description: "Record the carrier and tracking id for a parcel the seller posted themselves.",
+            kind: "primary",
+            permissions: ["seller", "admin"],
+        },
+        "dispatch-platform": {
+            iconKey: "ship",
+            id: "store.dispatch-platform",
+            label: "Book through the platform",
+            ariaLabel: "Book this parcel through the platform's courier account",
+            description: "Book a pickup on the platform's own carrier account. The tracking id comes back from the courier.",
+            kind: "primary",
+            permissions: ["seller", "admin"],
+            /*
+             * 🛑 Confirmed because it SPENDS MONEY and cannot be undone from this
+             * screen. A booking debits the platform's carrier wallet and schedules
+             * a real pickup; `bookShipment` then refuses a second attempt on the
+             * same order, so a mis-click is not a thing the seller can take back by
+             * pressing the button again.
+             */
+            confirmation: {
+                title: "Book this parcel through the platform?",
+                body: "A courier pickup will be scheduled at the address you picked and the cost charged to the platform's carrier account. This cannot be undone from here.",
+                confirmLabel: "Book pickup",
+            },
+        },
         "mark-installment-paid": {
             iconKey: "confirm",
             id: "store.mark-installment-paid",
@@ -1727,6 +1824,137 @@ export const ACTIONS = {
         },
     },
     ADMIN: {
+        /*
+         * ── Integration switches (12b) ──────────────────────────────────
+         *
+         * 🛑 The confirmation BODY is deliberately empty on `disable-integration`,
+         * and that is not an omission.
+         *
+         * `INTEGRATIONS[id].offConsequence` is the real body, and it differs per
+         * integration by design — "payments off" abandons in-flight payments,
+         * "support off" hides a contact route, "shipping off" selects a working
+         * manual path and stops nothing. A generic "are you sure?" here would
+         * flatten exactly the distinction that file exists to preserve, and a COPY
+         * of each consequence string would be a second place for it to drift from
+         * (Root Cause #42). `AdminIntegrationsView` composes the dialog body from
+         * the descriptor at render time.
+         *
+         * The registry still owns the label, the aria-label, the kind, and the fact
+         * that a confirmation is REQUIRED — which is what Rule #7 is about.
+         */
+        "enable-integration": {
+            iconKey: "approve",
+            id: "admin.enable-integration",
+            label: "Enable",
+            ariaLabel: "Enable this integration",
+            description: "Turn an integration on. Writes the authoritative settings field for it.",
+            kind: "primary",
+            permissions: ["admin"],
+        },
+        "update-pricing": {
+            iconKey: "save",
+            id: "admin.update-pricing",
+            label: "Save new rate",
+            ariaLabel: "Save the new rate",
+            description: "Change one platform rate from now on. Orders, invoices and payouts already recorded keep the rate they were charged at — a rate change never restates history.",
+            kind: "primary",
+            permissions: ["admin"],
+            /*
+             * 🛑 A confirmation even though `kind` is "primary" rather than "danger".
+             * The registry requires one for destructive actions; this one is here
+             * because the act is IRREVERSIBLE IN A WAY THAT DOES NOT LOOK IT — the
+             * rate moves forward only, so "undo" means a second change with a second
+             * audit row, and nothing restores what was charged in between.
+             */
+            confirmation: {
+                title: "Change this rate?",
+                body: "Every checkout from now on uses the new value. Past orders, invoices and payouts are untouched and keep the rate they were charged at.",
+                confirmLabel: "Change the rate",
+            },
+        },
+        "add-dispute-reason": {
+            iconKey: "create",
+            id: "admin.add-dispute-reason",
+            label: "Add reason",
+            ariaLabel: "Add a dispute reason",
+            description: "Add a reason buyers can pick when reporting a problem. The reason's KIND decides which gate it is subject to; the wording is yours.",
+            kind: "primary",
+            permissions: ["admin"],
+        },
+        "retire-dispute-reason": {
+            iconKey: "reject",
+            id: "admin.retire-dispute-reason",
+            label: "Retire",
+            ariaLabel: "Retire this dispute reason",
+            description: "Take a reason out of the buyer's picker. Never a delete — past disputes name it, and the order snapshots its label so history survives either way.",
+            kind: "danger",
+            permissions: ["admin"],
+            confirmation: {
+                title: "Retire this reason?",
+                /*
+                 * Names what retiring does NOT do, because that is the part an agent
+                 * is most likely to be unsure about and the reason this is not a
+                 * delete. A vague "are you sure" would invite exactly the hesitation
+                 * the schema's soft-retire design exists to remove.
+                 */
+                body: "Buyers will stop seeing it on the dispute form. Disputes already raised under it keep their wording, and you can put it back at any time.",
+                confirmLabel: "Retire it",
+                confirmKind: "danger",
+            },
+        },
+        "reactivate-dispute-reason": {
+            iconKey: "approve",
+            id: "admin.reactivate-dispute-reason",
+            label: "Reactivate",
+            ariaLabel: "Put this dispute reason back in the picker",
+            description: "Offer a retired reason to buyers again. The original author is kept.",
+            kind: "primary",
+            permissions: ["admin"],
+        },
+        "disable-integration": {
+            iconKey: "reject",
+            id: "admin.disable-integration",
+            label: "Disable",
+            ariaLabel: "Disable this integration",
+            description: "Turn an integration off. The consequence differs per integration and is stated on the row.",
+            kind: "danger",
+            permissions: ["admin"],
+            confirmation: {
+                title: "Switch this integration off?",
+                body: "",
+                confirmLabel: "Switch it off",
+                confirmKind: "danger",
+            },
+        },
+        "enable-all-integrations": {
+            iconKey: "approve",
+            id: "admin.enable-all-integrations",
+            label: "Enable all",
+            ariaLabel: "Enable every integration",
+            description: "Turn every integration on in a single write.",
+            kind: "secondary",
+            permissions: ["admin"],
+            confirmation: {
+                title: "Enable every integration?",
+                body: "Online payments, customer email, courier booking and the support surface will all be switched on. One write, one audit-log entry.",
+                confirmLabel: "Enable everything",
+            },
+        },
+        "disable-all-integrations": {
+            iconKey: "reject",
+            id: "admin.disable-all-integrations",
+            label: "Disable all",
+            ariaLabel: "Disable every integration",
+            description: "Turn every integration off in a single write.",
+            kind: "danger",
+            permissions: ["admin"],
+            confirmation: {
+                title: "Disable every integration?",
+                body: "This stops online payments, customer email and courier booking, and hides the buyer support surface. 🛑 Payments already in progress are abandoned — a buyer part-way through the gateway may be charged with no order placed. Staff email and open tickets stay workable. One write, one audit-log entry.",
+                confirmLabel: "Disable everything",
+                confirmKind: "danger",
+            },
+        },
         // ── Product moderation ─────────────────────────────────────────────────
         "approve-product": {
             iconKey: "approve",
@@ -1883,6 +2111,46 @@ export const ACTIONS = {
                 confirmKind: "danger",
             },
         },
+        /*
+         * D55 — the pre-order BALANCE's two review verdicts.
+         *
+         * 🛑 Deliberately separate from `verify-payment` / `reject-payment-fraud`
+         * above, which review the DEPOSIT. A pre-order's two payments are months
+         * apart, and the consequences do not match: rejecting a deposit proof
+         * cancels the order, restores stock and bans the account for 7 days,
+         * because the order had no legitimate basis. Rejecting a BALANCE proof on
+         * goods already made and allocated must do none of that — it asks for a
+         * better screenshot. Reusing the deposit's action would attach a 7-day
+         * ban to a blurry photo.
+         */
+        "verify-balance": {
+            iconKey: "verify",
+            id: "admin.verify-balance",
+            label: "Accept Balance",
+            ariaLabel: "Accept the pre-order balance payment proof",
+            description: "Confirms the pre-order balance was received. The order becomes shippable. Does NOT post a ledger entry — the sale was recognised in full at order creation.",
+            kind: "primary",
+            permissions: ["admin", "moderator"],
+            confirmation: {
+                title: "Accept the balance payment?",
+                body: "This records the remaining balance as received and clears the order to ship. Check the reference against your bank first.",
+                confirmLabel: "Yes, accept",
+            },
+        },
+        "reject-balance": {
+            iconKey: "reject",
+            id: "admin.reject-balance",
+            label: "Reject Balance Proof",
+            ariaLabel: "Reject the pre-order balance proof and ask the buyer to resend",
+            description: "Sends the proof back with your note. The buyer can submit again — no cancellation, no stock change, no ban: the goods are already made and allocated to them.",
+            kind: "secondary",
+            permissions: ["admin", "moderator"],
+            confirmation: {
+                title: "Reject this balance proof?",
+                body: "The buyer is told why and can send another. The order stays open and the item stays theirs.",
+                confirmLabel: "Reject and ask again",
+            },
+        },
         "verify-vendor": {
             iconKey: "verify",
             id: "admin.verify-vendor",

package/dist/_internal/shared/checkout/order-math.d.ts

@@ -521,10 +521,39 @@ export declare function resolvePointsTender(input: {
  * shown and charged figures diverge on exactly the carts where the balance is
  * tight.
  */
-export declare function allocatePointsAcrossGroups(groups: readonly {
+/** One order group's payable total, and whether its store takes points. */
+export interface PointsBase {
     total: number;
     accepted: boolean;
-}[], balance: number, optedIn: boolean): {
+}
+/** Everything one group contributes to its own payable total. */
+export interface PointsBaseParts {
+    /** Goods subtotal for the group, before any discount. */
+    goods: number;
+    couponDiscount: number;
+    shippingFee: number;
+    /** Gift wrap + shipment protection + any other per-store add-on. */
+    addonFee: number;
+    platformFee: number;
+    gstOnFee: number;
+    acceptsPoints: boolean;
+}
+/**
+ * The payable total a points allocation is measured against.
+ *
+ * 🛑 ONE implementation, because it was two. `POST /api/payment/create-order`
+ * and `verifyAndPlaceRazorpayOrderAction`'s amount guard each built this sum
+ * by hand, in the same shape, from the same six parts — and they are the
+ * *shown* figure and the *charged* figure for the same cart. Two hand-written
+ * copies of one money rule is Root Cause #75 exactly, and the failure mode is
+ * the worst kind: they only disagree on carts where the arithmetic differs, so
+ * nothing errors and the buyer is quoted one number and charged another.
+ *
+ * The coupon is floored at zero before the fees are added, never after — a
+ * discount larger than the goods must not eat the shipping and platform fee.
+ */
+export declare function pointsBaseForGroup(parts: PointsBaseParts): PointsBase;
+export declare function allocatePointsAcrossGroups(groups: readonly PointsBase[], balance: number, optedIn: boolean): {
     perGroup: number[];
     pointsApplied: number;
 };

package/dist/_internal/shared/checkout/order-math.js

@@ -715,43 +715,29 @@ export function resolvePointsTender(input) {
     return { pointsApplied, amountDue: roundRupees(total - pointsApplied) };
 }
 /**
- * Draw one balance down across a checkout's order groups, in group order.
- *
- * ## Why this exists rather than each caller looping
- *
- * The tender is applied PER GROUP (decision 3 — the accepting store absorbs
- * its own redemption), so "how many points does this checkout use" is a
- * sequential draw-down, not a single `min`. Four surfaces need the same answer
- * and must not each write the loop:
- *
- * | surface | why it needs the total |
- * |---|---|
- * | `previewCheckoutPricing` | the figure shown to the buyer |
- * | `POST /api/payment/create-order` | the figure CAPTURED |
- * | the post-capture guard | the figure compared |
- * | the two order paths | the per-group figure recorded |
- *
- * D37 is the record of what happens when one of those four is left out: the
- * coupon discount reached three of them and not the capture route, so the
- * buyer was shown one number, charged another, and the order recorded the
- * first — invisible in our own data because the guard was one-sided.
- *
- * 🛑 The order paths deliberately do NOT call this. They apply
- * `resolvePointsTender` to their own group as they create it, drawing down a
- * shared remainder — which is the same function applied in the same order, so
- * the sum is identical by construction. Making them call this instead would
- * mean computing every group's final total before creating any of them, which
- * is a restructure of two 200-line functions for an answer they already have.
- *
- * ## The cap is per group, and the ORDER of the groups therefore matters
- *
- * A balance smaller than the whole checkout's 50% allowance is consumed by the
- * earliest groups. That is arbitrary but it must be *consistently* arbitrary:
- * every caller iterates `orderGroups` in the order `splitCartIntoOrderGroups`
- * produced, so all four agree. Sorting differently anywhere would make the
- * shown and charged figures diverge on exactly the carts where the balance is
- * tight.
+ * The payable total a points allocation is measured against.
+ *
+ * 🛑 ONE implementation, because it was two. `POST /api/payment/create-order`
+ * and `verifyAndPlaceRazorpayOrderAction`'s amount guard each built this sum
+ * by hand, in the same shape, from the same six parts — and they are the
+ * *shown* figure and the *charged* figure for the same cart. Two hand-written
+ * copies of one money rule is Root Cause #75 exactly, and the failure mode is
+ * the worst kind: they only disagree on carts where the arithmetic differs, so
+ * nothing errors and the buyer is quoted one number and charged another.
+ *
+ * The coupon is floored at zero before the fees are added, never after — a
+ * discount larger than the goods must not eat the shipping and platform fee.
  */
+export function pointsBaseForGroup(parts) {
+    return {
+        total: roundRupees(Math.max(0, parts.goods - parts.couponDiscount) +
+            parts.shippingFee +
+            parts.addonFee +
+            parts.platformFee +
+            parts.gstOnFee),
+        accepted: parts.acceptsPoints,
+    };
+}
 export function allocatePointsAcrossGroups(groups, balance, optedIn) {
     const perGroup = groups.map(() => 0);
     if (!optedIn)

package/dist/_internal/shared/checkout/rules/index.d.ts

@@ -1,6 +1,6 @@
 export type { ListingCheckoutRule, CategoryCheckoutRule, CartItemProductPair, OrderItemInput, RefundPolicy, } from "./types";
 export { CHECKOUT_RULES, CATEGORY_CHECKOUT_RULES, getListingRule, getCategoryRule, pickOrderType, getSplitKey, runSyncPreflight, } from "./_registry";
-export { assertPaymentMethodAllowed, blockedMethodsForCart, type BlockedMethod, } from "./payment-gate";
+export { assertPaymentMethodAllowed, assertEmiOptInAllowed, blockedMethodsForCart, type BlockedMethod, } from "./payment-gate";
 export { CART_MAX_ITEMS, CHECKOUT_MAX_ORDERS_PER_TX, PRIZE_DRAW_MAX_REVEALS_PER_ORDER, PRIZE_DRAW_DURATION_DAYS_MIN, PRIZE_DRAW_DURATION_DAYS_MAX, BUNDLE_MAX_QTY_PER_TX, STANDARD_MAX_QTY_PER_LINE, } from "./_limits";
 export { standardRule } from "./standard.rule";
 export { auctionRule } from "./auction.rule";

package/dist/_internal/shared/checkout/rules/index.js

@@ -6,7 +6,7 @@ export { CHECKOUT_RULES, CATEGORY_CHECKOUT_RULES, getListingRule, getCategoryRul
  * apart is what stops someone folding it back into preflight, where it would
  * silently stop covering bundles and grouped lines.
  */
-export { assertPaymentMethodAllowed, blockedMethodsForCart, } from "./payment-gate.js";
+export { assertPaymentMethodAllowed, assertEmiOptInAllowed, blockedMethodsForCart, } from "./payment-gate.js";
 export { CART_MAX_ITEMS, CHECKOUT_MAX_ORDERS_PER_TX, PRIZE_DRAW_MAX_REVEALS_PER_ORDER, PRIZE_DRAW_DURATION_DAYS_MIN, PRIZE_DRAW_DURATION_DAYS_MAX, BUNDLE_MAX_QTY_PER_TX, STANDARD_MAX_QTY_PER_LINE, } from "./_limits.js";
 // Individual rules — exported for tests and direct access.
 export { standardRule } from "./standard.rule.js";

package/dist/_internal/shared/checkout/rules/payment-gate.d.ts

@@ -24,3 +24,21 @@ export declare function blockedMethodsForCart(items: readonly CartItemDocument[]
  * decision.
  */
 export declare function assertPaymentMethodAllowed(items: readonly CartItemDocument[], productById: ReadonlyMap<string, ProductDocument>, paymentMethod: CheckoutPaymentMethod | undefined): void;
+/**
+ * Throw when anything in the cart forbids an instalment plan.
+ *
+ * 🛑 Reads the SAME `blockedPaymentMethods` declaration, under the key
+ * `"emi"`, rather than introducing a parallel `blocksEmi` field. The listing
+ * rules already say "this listing type cannot be paid in instalments" — they
+ * said it by naming a payment method, because that is what EMI was. Once EMI
+ * became an order-level opt-in, that declaration needed a second reader, not
+ * a second declaration: a rule stated twice is a rule that drifts (Root Cause
+ * #61), and `prizeDrawRule`'s entry would otherwise have gone inert the day
+ * the tender disappeared.
+ *
+ * `blockedPaymentMessage` is reused verbatim for the same reason the gate
+ * above prefers it to a generated sentence: it names the REASON (winner
+ * assignment waits on confirmed payment), which is what lets a buyer choose
+ * differently instead of abandoning.
+ */
+export declare function assertEmiOptInAllowed(items: readonly CartItemDocument[], productById: ReadonlyMap<string, ProductDocument>, emiOptIn: boolean): void;

package/dist/_internal/shared/checkout/rules/payment-gate.js

@@ -131,3 +131,28 @@ export function assertPaymentMethodAllowed(items, productById, paymentMethod) {
         ? `${offender.message} Available instead: ${allowed.join(", ")}.`
         : `${offender.message} Nothing in this cart's combination can be paid for — remove the item and buy it on its own.`), { code: "PAYMENT_METHOD_BLOCKED" });
 }
+/**
+ * Throw when anything in the cart forbids an instalment plan.
+ *
+ * 🛑 Reads the SAME `blockedPaymentMethods` declaration, under the key
+ * `"emi"`, rather than introducing a parallel `blocksEmi` field. The listing
+ * rules already say "this listing type cannot be paid in instalments" — they
+ * said it by naming a payment method, because that is what EMI was. Once EMI
+ * became an order-level opt-in, that declaration needed a second reader, not
+ * a second declaration: a rule stated twice is a rule that drifts (Root Cause
+ * #61), and `prizeDrawRule`'s entry would otherwise have gone inert the day
+ * the tender disappeared.
+ *
+ * `blockedPaymentMessage` is reused verbatim for the same reason the gate
+ * above prefers it to a generated sentence: it names the REASON (winner
+ * assignment waits on confirmed payment), which is what lets a buyer choose
+ * differently instead of abandoning.
+ */
+export function assertEmiOptInAllowed(items, productById, emiOptIn) {
+    if (!emiOptIn)
+        return;
+    const offender = blockedMethodsForCart(items, productById).get("emi");
+    if (!offender)
+        return;
+    throw Object.assign(new ValidationError(`${offender.message} Pay for this order in full instead, or remove the item and buy it on its own.`), { code: "EMI_NOT_ALLOWED" });
+}

package/dist/_internal/shared/checkout/split.d.ts

@@ -53,18 +53,6 @@ export interface SplitResolution {
     /** The invariant holds. A caller must refuse to commit when false. */
     valid: boolean;
 }
-/**
- * Resolve contributions against a landed cost.
- *
- * Pure. No I/O, no clock — the landed cost is computed by the caller from the
- * order group it already has.
- *
- * 🛑 ROUNDS ONCE, at the end of each member's amount, and then puts the
- * ROUNDING REMAINDER on the last member. Rounding each percentage
- * independently and summing is how a 3-way 33.33% split charges a rupee less
- * than the agreed total and the surplus silently goes negative — the same
- * remainder discipline `allocateAcrossMembers` uses for bundle tax.
- */
 export declare function resolveSplit(contributions: readonly SplitContribution[], landedCost: number): SplitResolution;
 /**
  * The price to lock on the line, given the goods subtotal and a surplus.

package/dist/_internal/shared/checkout/split.js

@@ -41,10 +41,30 @@ import { roundRupees } from "../../../utils/number.formatter.js";
  * than the agreed total and the surplus silently goes negative — the same
  * remainder discipline `allocateAcrossMembers` uses for bundle tax.
  */
+/**
+ * `percent` of `amount`, where `percent` is 0–100.
+ *
+ * 🛑 A NAMED HELPER rather than the division written inline, for legibility
+ * to a reader AND to `audit-money-units`. That audit flags a scale division
+ * beside a money identifier because it is the exact shape of the 2026-05
+ * minor-unit bug — a conversion left behind by a migration — and a
+ * percentage conversion is visually identical to it. Two such lines are two
+ * judgement calls; one helper is a single place to establish that this
+ * divisor is about PERCENTAGES and never about currency scale.
+ *
+ * 🛑 That audit reads COMMENTS as well as code, so this one cannot quote the
+ * expression it is about: a worked example of the shape is indistinguishable
+ * from the shape. Reading comments is correct of it — a stale "stored in
+ * minor units" remark in prose is one of the things it hunts, and Root Cause
+ * #87 is the opposite mistake, an audit that stripped comments and so
+ * counted a commented-out registration as live.
+ */
+// audit-money-units-ok: a percent-to-fraction conversion, not a minor-unit conversion
+const applyPercent = (percent, amount) => (percent / 100) * amount;
 export function resolveSplit(contributions, landedCost) {
     const resolved = [];
     for (const c of contributions) {
-        const raw = c.splitMode === "percent" ? ((c.percent ?? 0) / 100) * landedCost : (c.amount ?? 0);
+        const raw = c.splitMode === "percent" ? applyPercent(c.percent ?? 0, landedCost) : (c.amount ?? 0);
         resolved.push({ productId: c.productId, amount: roundRupees(raw) });
     }
     /*
@@ -59,7 +79,7 @@ export function resolveSplit(contributions, landedCost) {
     const allPercent = contributions.every((c) => c.splitMode === "percent");
     if (allPercent && resolved.length > 0) {
         const pctTotal = contributions.reduce((s, c) => s + (c.percent ?? 0), 0);
-        const target = roundRupees((pctTotal / 100) * landedCost);
+        const target = roundRupees(applyPercent(pctTotal, landedCost));
         const sum = resolved.reduce((s, r) => s + r.amount, 0);
         const drift = roundRupees(target - sum);
         if (drift !== 0) {

package/dist/_internal/shared/content/disclaimers.js

@@ -78,7 +78,7 @@ export const DISCLAIMERS = {
         body: "Entry requires a purchase and is void where prohibited by local law. Residents of states that " +
             "restrict prize draws or games of chance are not eligible, and an entry from such a state will be " +
             "refunded rather than drawn. Prizes are as described on the listing, are not transferable and cannot " +
-            "be exchanged for cash. The draw is run by LetItRip and is not affiliated with any government lottery.",
+            "be exchanged for cash. The draw is run by {{siteName}} and is not affiliated with any government lottery.",
         tone: "warning",
         surfaces: ["PrizeDrawDetailPageView", "/prize-draws", "/lottery", "PrizeRevealModal"],
     },
@@ -90,7 +90,7 @@ export const DISCLAIMERS = {
      */
     "not-investment-advice": {
         body: "Prices shown are past transactions, not a valuation, a projection or a guarantee. Collectibles can " +
-            "fall in value as easily as rise, may be difficult to sell at any price, and LetItRip does not provide " +
+            "fall in value as easily as rise, may be difficult to sell at any price, and {{siteName}} does not provide " +
             "investment advice. Nothing here should be relied on as a reason to buy.",
         tone: "legal",
         surfaces: ["PriceIndexView", "RealisedPriceStrip", "/franchise", "ProductDetailPageView"],
@@ -108,7 +108,7 @@ export const DISCLAIMERS = {
         surfaces: ["PriceIndexView", "PriceBandChart"],
     },
     "authenticity": {
-        body: "LetItRip is not an authentication or grading service. We do not inspect, test or re-grade items, " +
+        body: "{{siteName}} is not an authentication or grading service. We do not inspect, test or re-grade items, " +
             "and a grade shown on a listing is the one the seller states a third-party grader assigned. " +
             "Guidance on spotting a counterfeit is general information, not a verification of any particular item.",
         tone: "legal",
@@ -125,7 +125,7 @@ export const DISCLAIMERS = {
      */
     "protection-cover": {
         heading: "What protection covers",
-        body: "Buyer protection is cover provided by LetItRip. It is **not insurance** and there is no insurer. " +
+        body: "Buyer protection is cover provided by {{siteName}}. It is **not insurance** and there is no insurer. " +
             "Shipment protection covers loss or damage in transit and must be claimed within " +
             "{{shipmentClaimHours}} hours of delivery. Sale protection covers an item up to " +
             "{{saleProtectionMaxValue}} and must be claimed within {{saleClaimHours}} hours of delivery. " +
@@ -142,7 +142,7 @@ export const DISCLAIMERS = {
     "accounting-output": {
         body: "These are management figures produced from this platform's own records. They are not audited " +
             "accounts and have not been reviewed by an accountant. The GSTR-1 export is a draft for your " +
-            "accountant to check and use — nothing here is filed with any tax authority, and LetItRip has no " +
+            "accountant to check and use — nothing here is filed with any tax authority, and {{siteName}} has no " +
             "connection to the GST portal.",
         tone: "warning",
         surfaces: ["AdminInvoicingView", "AdminAnalyticsView", "ProfitLossView", "TrialBalanceView"],
@@ -172,7 +172,7 @@ export const DISCLAIMERS = {
     },
     "emi": {
         body: "EMI adds a surcharge to the order total, shown before you pay. The instalment plan is between you " +
-            "and LetItRip rather than a bank, and a missed instalment may suspend access to the order and is " +
+            "and {{siteName}} rather than a bank, and a missed instalment may suspend access to the order and is " +
             "recoverable as a debt.",
         tone: "legal",
         surfaces: ["CheckoutRouteClient", "/fees", "EmiScheduleTable"],
@@ -185,7 +185,7 @@ export const DISCLAIMERS = {
     },
     "user-content": {
         body: "Reviews, catalogue entries and comments are the opinions of the people who wrote them, not " +
-            "LetItRip's. We remove content that breaks our rules when it is reported, but we do not verify every " +
+            "{{siteName}}'s. We remove content that breaks our rules when it is reported, but we do not verify every " +
             "claim made in it.",
         tone: "legal",
         surfaces: ["ReviewsList", "ReviewDetailShell", "PublicProfileView", "BlogPostView"],

package/dist/_internal/shared/content/published-values.d.ts

@@ -44,7 +44,7 @@
  * sentence with a word missing, which nobody reports, while `{{wrongKey}}` on
  * a live page gets reported in minutes.
  */
-export type PublishedValueKey = "returnWindowDays" | "sellerAcceptDays" | "sellerDispatchBusinessDays" | "returnRespondHours" | "returnPostDays" | "offerCheckoutHours" | "paymentWindowMinutes" | "deliveryConfirmDays" | "orderCompleteDays" | "shipmentClaimHours" | "saleClaimHours" | "disputeTransitWindowDays" | "disputeNotReachedGraceDays" | "platformFeeMax" | "platformFeePercent" | "shipmentProtectionPercent" | "shipmentProtectionMin" | "saleProtectionPercent" | "saleProtectionMin" | "saleProtectionMaxValue" | "codHandlingPercent" | "codDepositPercent" | "giftWrapFee" | "pointsEarnPercent" | "pointsMaxRedemptionPercent" | "pointsExpiryMonths" | "refundBusinessDaysMin" | "refundBusinessDaysMax";
+export type PublishedValueKey = "returnWindowDays" | "sellerAcceptDays" | "sellerDispatchBusinessDays" | "returnRespondHours" | "returnPostDays" | "offerCheckoutHours" | "paymentWindowMinutes" | "deliveryConfirmDays" | "orderCompleteDays" | "shipmentClaimHours" | "saleClaimHours" | "disputeTransitWindowDays" | "disputeNotReachedGraceDays" | "platformFeeMax" | "platformFeePercent" | "shipmentProtectionPercent" | "shipmentProtectionMin" | "saleProtectionPercent" | "saleProtectionMin" | "saleProtectionMaxValue" | "codHandlingPercent" | "codDepositPercent" | "giftWrapFee" | "pointsEarnPercent" | "pointsMaxRedemptionPercent" | "pointsExpiryMonths" | "refundBusinessDaysMin" | "refundBusinessDaysMax" | "siteName";
 export type PublishedValues = Record<PublishedValueKey, string>;
 /**
  * The settings this registry reads, where a value genuinely is configurable.
@@ -56,6 +56,11 @@ export type PublishedValues = Record<PublishedValueKey, string>;
  * TypeScript's structural typing strips nothing at runtime).
  */
 export interface PublishedValueSettings {
+    /**
+     * The operator's display name, for the disclaimers that name who is making
+     * the statement. Falls back to `SITE_CONFIG.brand.name`.
+     */
+    siteName?: string;
     platformFeeMax?: number;
     platformFeePercent?: number;
     shipmentProtectionFeePercent?: number;

package/dist/_internal/shared/content/published-values.js

@@ -40,6 +40,7 @@
  * somebody has to remember — and it is why there is no literal for the offer
  * deadline or the claim windows even though both appear in published copy.
  */
+import { SITE_CONFIG } from "../../../core/site-config.js";
 import { OBLIGATION_POLICIES } from "../../../features/obligations/constants/policies.js";
 import { POINTS_EARN_PERCENT, POINTS_EXPIRY_MONTHS, POINTS_MAX_REDEMPTION_PERCENT, } from "../../../features/points/schemas/firestore.js";
 import { PAYMENT_WINDOW_MINUTES } from "../../../features/orders/constants/payment-window.js";
@@ -171,6 +172,13 @@ export function resolvePublishedValues(settings) {
          */
         refundBusinessDaysMin: "5",
         refundBusinessDaysMax: "7",
+        /*
+         * `SITE_CONFIG.brand.name` is appkit's own neutral default ("App") until a
+         * consumer overrides it, which is exactly the right failure mode here: a
+         * fork that forgets to configure its brand publishes a visibly generic
+         * disclaimer rather than silently attributing its legal statements to us.
+         */
+        siteName: settings?.siteName ?? SITE_CONFIG.brand.name,
     };
 }
 /**