Changelog

Use this page to track operator-facing contract changes only.

What belongs here

• new operator API endpoints
• removed or deprecated operator API endpoints
• new webhook event types
• payload shape changes
• wallet adapter contract changes
• status or error-code changes

What does not belong here

• internal refactors with no contract impact
• infrastructure-only deploy notes
• design-only content edits with no integration impact

Entry template

## YYYY-MM-DD

### Added
- item

### Changed
- item

### Deprecated
- item

### Removed
- item

### Operator action
- required migration or "none"

2026-09-16

Added

• product: "polyflight" launch selection while omitted product remains Opinion
• native-IDR Polyflight wallet reasons, stable keys, and additive metadata on existing REST v1 paths
• eight mini_app.polyflight.* webhook events with camelCase data
• read-only Polyflight overview, flight, ticket, wallet-operation, terms, signed-statement, payment-history, and export routes
• scopes polyflight:read, polyflight_terms:read, and polyflight_settlements:read
• v5 mixed-money anonymous proof and comparison-only frozen Indodax evidence

Operator action

• update wallet allowlists/idempotency handling and webhook subscriptions before Polyflight enablement
• grant new read scopes explicitly; existing restricted grants are unchanged
• validate dashboard-hosted simulation and the separate real REST v1 contract in staging
• obtain separate production authorization before production deployment, enablement, or wallet activity

2026-07-11

Added

• GET /api/operator/trades/{marketId}/{externalUserId} for operator-scoped market/user trade-history HTML
• GET /api/operator/redemptions in the documented Operator API and Playground catalog
• required wallet mutation metadata matrices for buy, sell, compensation, and redemption flows

Changed

• ambiguous primary wallet mutations now require manual review instead of remote lookup or automatic replay
• buy compensation includes marketId and may retry only with its original idempotency key
• full-contract wallet testing keeps balance and mutation coverage without operation-lookup steps

Removed

• REST v1 operation-lookup configuration and runtime APIs
• staging simulator operation-lookup route

Operator action

• continue durable same-key mutation deduplication and stop implementing or calling lookup-by-key
• persist marketId from all trade mutation metadata
• use Balance Ops, operator wallet logs, remote_reference, and UTC timestamps for ambiguous reconciliation
• never replay the same business action with a new idempotency key

Initial release

2026-06-20

Added

• operator documentation app initial structure
• operator API reference
• wallet adapter reference
• webhook reference

Operator action

• use current pages as source of truth for v1 integration