Inttegro demos 1.2.3

Inttegro demos 1.2.3

This patch release gives every order-producing demo a proper merchant order
number and restores a clean Spring Boot build.

Changes

• Sends story-specific, human-readable order numbers from every hosted web
  backend and from the shared Next.js mobile backend.
• Keeps each demo order number stable across an idempotent retry by deriving it
  from the validated logical checkout attempt.
• Uses KORA-… for Kora Market, AFTERGLOW-… for Afterglow Sessions, and
  INV-2048-… for Ledgerline instead of allowing the generated Inttegro or_…
  identifier to become the order number.
• Documents the boundary between merchant order numbers, idempotency keys,
  invoice numbers, Inttegro order IDs, and proof of payment for both people and
  machine readers.
• Fixes a shadowed lambda parameter that prevented the Spring Boot demo from
  compiling with the released Java SDK.
• Advances immutable suite, per-demo, and deployment references to version
  1.2.3. Version 1.2.2 remains unchanged for existing permalinks.

Verification

The Next.js and Nuxt demos passed type checking, tests, and production builds.
Express, Django, FastAPI, Go, Rails, Laravel, and Spring Boot passed their
framework-specific test suites using the exact SDK versions declared by each
demo. The repository-wide demo contract check also passed.

The live checkout verification creates a finalized order and confirms that the
returned order carries the expected merchant number. Verification stops before
payment authorization; no real payment is made.

Release safety

Order numbers contain only story prefixes and opaque checkout-attempt data.
They contain no customer names, email addresses, phone numbers, credentials,
or payment details. The dedicated API key remains in deployment secret stores
and is not included in source, artifacts, tags, or browser/mobile bundles.