[HasToBeJames]

Description

Implements investor facing tranche, issuer credit tier, impact report, and compliance hold UI for the four assigned invoice issues. Optional fields preserve the current experience when an invoice has no feature data.

Closes #538
Closes #539
Closes #540
Closes #541

Type of Change

• 🐛 Bug fix (non-breaking change which fixes an issue)
• ✨ New feature (non-breaking change which adds functionality)
• 💥 Breaking change
• 📝 Documentation update
• 🎨 UI/UX improvement
• ♻️ Code refactoring
• ✅ Test addition or update
• 🔧 Configuration change

Checklist

• My code follows the code style of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published

Testing

npx tsc --noEmit — passed after syncing dev and resolving the merge. git diff --check — passed. npm run lint was started but stalled without output and was interrupted; no lint pass is claimed. No tests were added or run.

How to Test

1. Provide invoice detail responses with the optional tranche_status, greylist, and impact_report fields.
2. Provide GET /issuers/:wallet/credit-score responses for each supported tier.
3. Confirm the tranche selector sends tranche_type 1 (senior) or 2 (junior), the greylist blocks investment until cleared, and settled impact metrics render from IPFS.

Test Coverage

• Unit tests added/updated
• Integration tests added/updated
• E2E tests added/updated (if applicable)
• Manual testing completed

Screenshots (if applicable)

Not captured.

Additional Notes

The UI expects the backend to provide the documented optional invoice fields and the credit-score endpoint, and to forward tranche_type to the invoice-tranche contract. Those server-side APIs are not part of this frontend repository or PR.

For Reviewers

• Code quality and readability
• Test coverage
• Security implications
• Performance impact
• Breaking changes

[drips-wave]

@HasToBeJames Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits.

You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀

Learn more about application limits

[TS-mfon]

Conflicts

[TS-mfon]

⚠️ Merge Conflict Detected

This PR currently has a merge conflict and cannot be merged until it is resolved.

Please rebase or merge the latest changes from the base branch into your branch and push again.

[HasToBeJames]

Superseded by a replacement PR from the synced feature branch because GitHub continued to report this PR head as conflicting after the conflict-resolution merge was pushed.