@pulsepairs/sdk 0.9.0 → 0.9.1

package/README.md

@@ -475,11 +475,25 @@ would otherwise see each other's half-applied state. Both cap at 20 per request.
 UPND_INTEGRATION=1 PRIVATE_KEY=0x… npm run test:integration
 ```
 
-It rests an order, amends it, bulk-places two, bulk-amends those, and cancels
-everything in a `finally` — including on failure. It defaults to dev and refuses
-to run against prod without `UPND_ALLOW_PROD=1`, because it places real orders
-and only dev's USDT is play money. Needs a live 5m market with >120s left, so
-the keeper has to be cycling.
+It grants the collateral allowance, rests an order, amends it, bulk-places two,
+bulk-amends those, and cancels everything in a `finally` — including on failure.
+It defaults to dev and refuses to run against prod without `UPND_ALLOW_PROD=1`,
+because it places real orders and only dev's USDT is play money. Needs a live 5m
+market with >120s left, so the keeper has to be cycling.
+
+The key needs mock USDT and a little gas ETH. On dev the public faucet gives
+both in one call:
+
+```bash
+curl -X POST https://dev-api-updown.rain.trade/test/devmint \
+  -H 'Content-Type: application/json' \
+  -d '{"address":"0x…","amount":"100000000"}'
+```
+
+The **allowance is granted by the test itself**, not by hand — a freshly
+deployed Settlement has no approvals from anyone, and requiring a manual
+approve made "run the acceptance test" a two-step nobody had written down. Use a
+throwaway key: the faucet is public, so nothing valuable should sit on it.
 
 ---
 

package/dist/http.d.ts

@@ -112,7 +112,10 @@ export declare class UpDownHttpClient {
      * amend's outcome in the body, so a rejection never reaches `parseJson`'s
      * throw. `bulkFailures()` below exists to make that hard to forget.
      *
-     * Results are positional: `results[i]` is the outcome of `amends[i]`.
+     * Results are positional: `results[i]` is the outcome of `amends[i]`, and a
+     * successful entry NESTS the replacement — `results[i].order.id`, not
+     * `results[i].id`. That differs from the single `amendOrder` above, which
+     * spreads the order at the top level; the asymmetry is the server's.
      *
      * Server-side these run SERIALLY, not concurrently — two amends racing on
      * neighbouring price levels would otherwise see each other's half-applied

package/dist/http.js

@@ -215,7 +215,10 @@ export class UpDownHttpClient {
      * amend's outcome in the body, so a rejection never reaches `parseJson`'s
      * throw. `bulkFailures()` below exists to make that hard to forget.
      *
-     * Results are positional: `results[i]` is the outcome of `amends[i]`.
+     * Results are positional: `results[i]` is the outcome of `amends[i]`, and a
+     * successful entry NESTS the replacement — `results[i].order.id`, not
+     * `results[i].id`. That differs from the single `amendOrder` above, which
+     * spreads the order at the top level; the asymmetry is the server's.
      *
      * Server-side these run SERIALLY, not concurrently — two amends racing on
      * neighbouring price levels would otherwise see each other's half-applied

package/dist/index.d.ts

@@ -7,4 +7,4 @@ export { readOnChainHolderShares, reconcileFills, reportedFromPositions, type On
 export { UpDownAccountKitSigner, bareErc1271Signer, stripErc6492Wrapper, isErc6492Signature, type UpDownAccountKitConfig, type Eip1193Provider, type GrantSessionResult, type RawTypedDataSigner, } from "./accountKit.js";
 export { buildApproveSettlementTx, buildInstallOrderSessionTx, signWithOrderSession, type RawTransaction, type OrderSessionRecord, } from "./accountKit.js";
 export { PRICE_BPS_SCALE, WIN_MARK_BPS, LOSE_MARK_BPS, DEFAULT_USDT_DECIMALS, atomicToUsdt, markValueAtomic, midBps, markForOption, isResolvedWinner, positionPnl, feesPaidByWallet, portfolioPnl, computePortfolioPnl, type MarkSource, type PositionPnl, type PortfolioPnl, type PositionPnlOptions, } from "./pnl.js";
-export { OrderType, OrderSide, Option, takerPriceBps, type AmendOrderBody, type AmendOrderResult, type ApiConfig, type Balance, type BulkAmendBody, type BulkAmendResults, type BulkFailure, type BulkOrdersBody, type BulkOrdersResults, type CancelOrderBody, type Eip712Domain, type MarketDetail, type MarketListItem, type OptionValue, type OrderBookFull, type OrderBookLevel, type OrderBookSide, type OrderRow, type OrderSideKey, type OrderSideValue, type OrderStatus, type OrderTypeKey, type OrderTypeValue, type OrdersResponse, type PairConfig, type PairSymbol, type PostOrderBody, type Position, type SubmittedOrder, type Stats, type Trade, type Version, } from "./types.js";
+export { OrderType, OrderSide, Option, takerPriceBps, type AmendOrderBody, type AmendOrderResult, type ApiConfig, type Balance, type BulkAmendBody, type BulkAmendResults, type BulkAmendSuccess, type BulkFailure, type BulkOrdersBody, type BulkOrdersResults, type CancelOrderBody, type Eip712Domain, type MarketDetail, type MarketListItem, type OptionValue, type OrderBookFull, type OrderBookLevel, type OrderBookSide, type OrderRow, type OrderSideKey, type OrderSideValue, type OrderStatus, type OrderTypeKey, type OrderTypeValue, type OrdersResponse, type PairConfig, type PairSymbol, type PostOrderBody, type Position, type SubmittedOrder, type Stats, type Trade, type Version, } from "./types.js";

package/dist/types.d.ts

@@ -315,10 +315,35 @@ export type AmendOrderResult = SubmittedOrder & {
 export type BulkAmendBody = {
     amends: AmendOrderBody[];
 };
+/**
+ * One successful entry of a bulk amend.
+ *
+ * NOTE THE SHAPE DIFFERS FROM THE SINGLE ROUTE, and this is the server's
+ * asymmetry rather than a choice made here. `POST /orders/amend` SPREADS the
+ * replacement order at the top level, so its id is `res.id`.
+ * `POST /orders/amend/bulk` NESTS it, so the id is `results[i].order.id` —
+ * matching `POST /orders/bulk`, which also nests.
+ *
+ * Typed wrongly in 0.9.0 (as the single route's flat shape), which made
+ * `results[i].id` read `undefined` for every entry. Caught by the live
+ * round-trip against dev, not by the stubbed tests — those used a fixture
+ * written from the same wrong assumption, so they agreed with themselves.
+ */
+export type BulkAmendSuccess = {
+    ok: true;
+    /** The replacement, nested — NOT spread, unlike `POST /orders/amend`. */
+    order: SubmittedOrder;
+    /** Echo of the `cancelOrderId` that was retired. */
+    replaced: string;
+    /** Whether the replacement kept the original's queue position. */
+    priorityKept: boolean;
+    /** Atomic USDT already filled on the ORIGINAL before it was retired. */
+    filled: string;
+    /** Atomic USDT that was still resting and has moved to the replacement. */
+    remaining: string;
+};
 export type BulkAmendResults = {
-    results: Array<({
-        ok: true;
-    } & AmendOrderResult) | BulkFailure>;
+    results: Array<BulkAmendSuccess | BulkFailure>;
 };
 /** `POST /orders/bulk` — orders fan out CONCURRENTLY server-side. */
 export type BulkOrdersBody = {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@pulsepairs/sdk",
-  "version": "0.9.0",
+  "version": "0.9.1",
   "description": "Standalone SDK for the UpDown (PulsePairs) up/down prediction markets \u2014 matcher REST/WS client, EIP-712 order signing, trade-math, and Alchemy Account Kit (smart-account) order signing for rain.trade integration.",
   "license": "UNLICENSED",
   "type": "module",