Per-Split Audit Log Emitter

[Kingsman-99]

Description

src/auditLogger.ts logs aggregate invoice-level events but does not emit a granular per-split-leg audit record with the exact amount, recipient, operation ID, and ledger sequence for each leg of a multi-recipient payment. Without per-leg records, compliance and dispute resolution require reconstructing individual payments from raw Horizon data. A per-split audit emitter should write a structured record for each leg at the moment it settles.

Technical Context

Extend src/auditLogger.ts. Reads SplitLeg and SplitResult from src/types.ts. Hooks into src/paymentProgressTracker.ts onLegSettled callback. Writes SplitAuditEntry records to the configured audit sink (file, remote endpoint, or in-memory store). Integrates with src/complianceExporter.ts for export. Adds SplitAuditEntry to src/types.ts.

Acceptance Criteria

• Each settled split leg produces a SplitAuditEntry with fields: invoiceId, legIndex, recipientId, assetCode, amount, operationId, ledgerSequence, settledAt
• SplitAuditEntry records are written to the audit sink immediately upon leg settlement, not batched
• AuditLogger.exportSplitAuditTrail(invoiceId): Promise<SplitAuditEntry[]> returns all recorded entries for an invoice
• Integrates with src/complianceExporter.ts so audit entries appear in compliance reports
• Unit tests assert a two-recipient split produces exactly two SplitAuditEntry records with correct field values
• All CI checks (npm test, npm run build, ESLint/TypeScript) pass and the branch has no merge conflicts

---

[neyij]

@neyij has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

hi, i would like to work on this.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @neyij to this issue.

[Calebstack]

@Calebstack has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

Hello maintainer, i’ve got this covered! Ready to drop a high-impact, clean PR that gets this merged seamlessly

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Calebstack to this issue.

[Purity-Euphemia]

@Purity-Euphemia has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

Please I can work on this 🙏 😭

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Purity-Euphemia to this issue.

[DNight-King]

@DNight-King has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

I can work on this.
Please assign

ℹ️ Repo Maintainers: To accept this application, review their application or assign @DNight-King to this issue.

[drips-wave]

Congratulations, @DNight-King! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on July 30, 2026.

🧑‍💻 @DNight-King: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊

[drips-wave]

This issue has been completed by @DNight-King as part of the Stellar Wave Program's 7th Wave 🥳

😎 @DNight-King: You earned 200 Points for completing this issue! After the current Wave ends, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here. You can also Leave a review to share your experience working on this issue.

🧑‍💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.