Release: develop -> main - #1444
Merged
Merged
Conversation
Customer LimitRequests are filed under Department.Compliance. Support's issue list is restricted to Department.Support, so the Limit Requests tab listing assertion uses Compliance. Co-authored-by: TaprootFreakAI <315477232+TaprootFreakAI@users.noreply.github.com>
github-actions
Bot
requested review from
TaprootFreak and
davidleomay
as code owners
September 1, 2026 09:41
…page (#1445) * Add RealUnit wallet addresses to the compliance customer page Show user-table addresses filtered to the RealUnit app wallet, before Buy Routes. * Match Addresses table to other collections and declare the e2e fake --------- Co-authored-by: TaprootFreakAI <315477232+TaprootFreakAI@users.noreply.github.com>
* fix(kyc): join overlapping continue calls after ident * fix(kyc): keep continue and info single-flights separate * fix(kyc): ignore stale continue/info reloads * fix(kyc): route initial continue through the continue flight * fix(kyc): keep initial GET errors and invalidate the other flight * fix(kyc): join same-key KYC loads and queue the rest * fix(kyc): join continues even when an info load is queued * fix(kyc): clean keyed serial inflight without unhandled rejection * fix(kyc): flush microtasks in serial tests; clear error after startStep --------- Co-authored-by: TaprootFreakAI <315477232+TaprootFreakAI@users.noreply.github.com>
* test(e2e): prove 13 parallel KYC continues create one FinancialData step * test(e2e): cover 13 parallel KYC continues against the production unique index Recreate the kyc_step unique index with NULLS NOT DISTINCT, fire 13 overlapping PUT /v2/kyc after ident, and require one FinancialData row with no unique-violation rollbacks. Also covers a follow-up continue and two users in one burst. * docs: declare SQL-completed KYC steps in the continue-race e2e spec A green run does not prove ContactData, PersonalData, NationalityData or Ident complete through the product path. --------- Co-authored-by: TaprootFreakAI <315477232+TaprootFreakAI@users.noreply.github.com>
* Route write-mandate Safe orders through the account resource A Write grant on someone else's Safe now offers Deposit/Withdraw/Swap and posts to custody/account/:id/order so the order books against that Safe. Read stays view-only. Confirm is unchanged. * Reuse accountPath for write-mandate orders and test isOwnAccount Drop the duplicate orderUrl helper. Own vs shared account identity is covered in unit tests.
#1451) * fix(e2e): wait for KYC and financial screens to settle * Fix nullable KYC race fixture inputs --------- Co-authored-by: TaprootFreakAI <315477232+TaprootFreakAI@users.noreply.github.com>
Co-authored-by: TaprootFreakAI <315477232+TaprootFreakAI@users.noreply.github.com>
* Report displayed ErrorHint and ConnectError failures to the client error log The crash screen already posted failures to POST /v1/log/clientError. In-flow ErrorHint and wallet ConnectError did not, so a customer-visible failure never reached the error log. Both now report through useReportDisplayedError. * Do not re-report a displayed error when the account hydrates The ingest treats a later account id as a different failure. Match the crash screen: send once with whatever account is known at first fire. * Report QuoteErrorHint process blockers as QuoteError KYC, limit and similar in-flow blockers now post to the client error ingest with type QuoteError so they are recorded without being treated as crashes. --------- Co-authored-by: TaprootFreakAI <315477232+TaprootFreakAI@users.noreply.github.com>
* feat(realunit): add referral-admin operator UI Add a RealUnit Referral admin screen to the operator dashboard for the referral/ promo backend endpoints: list referral relations with a held-for-review filter, a detail view with the review/reward history, and approve / reject / manual-prize actions (each requiring a reason). Wired through useGuardedApi + useRealunitGuard, routed under /realunit/referral, with de/fr/it strings. * fix(realunit): clear stale relation and stabilize detail effect deps Address review: reset the loaded relation at the top of the id-change effect so the loading/not-found guards work on an in-SPA id switch, and add getRelations to the effect deps (matching the realunit-compliance-user single-fetch sibling). * chore(realunit): register referral routes and handbook entry Address review conformity: add the /realunit/referral and /realunit/referral/:id route claims to the e2e registry and a RealUnit Referral entry to the handbook metadata, matching the existing realunit admin screens. * test(realunit): cover the referral-admin hook and screens Add unit tests for the referral-admin UI: the hook's four operator calls, the list screen (held-for-review filter, count, navigation, empty + load-error states), the detail screen (action gating, required-reason guard, approve/reject/manual-prize flows, optional-field/history rendering, cancel, back, not-found, load error), and the dto enum values. Hook 100%, screens 100% line/function coverage. * test(realunit): claim the referral routes in the e2e route list Add /realunit/referral and /realunit/referral/:id to REALUNIT_ROUTES so the full-stack route-guard spec visits them, satisfying the e2e registry claim. * test(realunit): add referral-admin visual regression spec Add e2e/realunit-referral.spec.ts (mirroring realunit-compliance.spec.ts): real admin auth, the referral-admin relations endpoint mocked with synthetic fixtures, screenshotting the held-for-review list and a relation detail with review actions. Baseline PNGs are generated separately on the macOS visual runner. * test(realunit): add referral-admin visual regression baselines --------- Co-authored-by: TaprootFreakAI <315477232+TaprootFreakAI@users.noreply.github.com> Co-authored-by: TaprootFreak <142087526+TaprootFreak@users.noreply.github.com>
TaprootFreak
approved these changes
Sep 7, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Automatic Release PR
This PR was automatically created after changes were pushed to develop.
Commits: 1 new commit(s)
Checklist