From 74144288348cb126e3874498e7588a652ead4344 Mon Sep 17 00:00:00 2001 From: Rami Mohamed Date: Mon, 7 Sep 2026 00:14:49 +0400 Subject: [PATCH] docs: record payment state event delivery plan --- docs/project-handoff.md | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/docs/project-handoff.md b/docs/project-handoff.md index c6bdfd5..a4b7f6f 100644 --- a/docs/project-handoff.md +++ b/docs/project-handoff.md @@ -826,3 +826,12 @@ Consult GitHub Project #1 for the authoritative Sprint hierarchy and current iss - The runbook records the access and lifecycle boundary: Docker Desktop only, temporary port-forwards to `ClusterIP` Services, synthetic SIT data, one-node/5Gi local storage, no external notification destination, and no UAT/PROD/AWS implementation. - Read-only verification reached the deployed `opensearch`, `opensearch-dashboards`, and `fluent-bit` releases, all `1/1` Ready. OpenSearch was `yellow` with one node, 11 active shards, and 6 unassigned replica shards. The checked 15-minute collector window contained 3,410 `logging_parse_status=valid` records and zero invalid/unstructured records. - The same field-presence query found `@timestamp` and `structured.level` only; `structured.service`, `structured.environment`, `structured.correlation_id`, `structured.trace_id`, and `structured.timestamp` were absent from the current deployed workload. This is a documented application-logging acceptance blocker for [`.github#91`](https://github.com/digital-bank-java/.github/issues/91), not a collector failure and not evidence to close the story. + +### 2026-09-07 - Payment instruction state-event implementation + +- Created parented Sprint 5 Story [`.github#250`](https://github.com/digital-bank-java/.github/issues/250) under [`.github#31`](https://github.com/digital-bank-java/.github/issues/31) for the missing durable payment instruction state-event capability. The story remains `In review` in Project #1; payment-provider adapters, provider credentials, public payment routes, account/ledger mutation, and transfer saga orchestration remain out of scope. +- Opened coordinated review PRs [payment-service #13](https://github.com/digital-bank-java/payment-service/pull/13), [config-repo #48](https://github.com/digital-bank-java/config-repo/pull/48), [infra-sit #41](https://github.com/digital-bank-java/infra-sit/pull/41), and contract PR [`.github` #251](https://github.com/digital-bank-java/.github/pull/251). They are normal, non-draft PRs; none targets a direct merge to `main`. +- Payment Service now writes PENDING, COMPLETED, and FAILED state facts to a PostgreSQL outbox in the same transaction as the instruction change, then publishes the stored payload through `payment.instruction.state.v1` with stable event identity, governed headers, leased at-least-once delivery, bounded retries, and durable failure visibility. A replay does not create a second business transition. +- SIT Config Repository wiring points Payment Service to the in-cluster Kafka broker, and the SIT Kafka chart explicitly provisions `payment.instruction.state.v1` and its `.dlq` because topic auto-creation is disabled. The organization AsyncAPI contract defines `PaymentInstructionStateChanged.v1` and its envelope/header conventions. +- Payment Service `./mvnw --batch-mode --no-transfer-progress verify -DskipUnitTests=true` passed with 19 tests using Docker/Testcontainers. The Kafka chart passed strict Helm lint and template rendering, including both payment topics. The three implementation PRs must merge before post-merge SIT rollout and AKHQ/PostgreSQL outbox evidence are recorded. +- No provider integration, public route, direct balance mutation, redundant CI workflow, or broad redundant unit-test suite was added. The next acceptance step after merge is to deploy Payment Service in SIT, create one instruction, observe its outbox record and Kafka event, complete or fail it, and verify duplicate publication/restart behavior without duplicate business state.