[codex] Add authenticated MyPayTag portal UI

[KazanderDad]

Summary

• Replaces the mock portal session gate with Cubid/SIWC login.
• Adds receive-path priority settings UI.
• Replaces static history with backend-backed resolve, quote, intent, and receipt summaries.
• Covers site tree: Goal: Site auth, settings, and history UI #8, Replace static history with backend-backed summaries #9, Replace mock session gate with real Cubid/SIWC login #10, Add receive-path priority settings UI #11.

Validation

• pnpm check:i18n passed locally during implementation.
• pnpm typecheck passed locally during implementation.
• pnpm lint passed locally during implementation.
• pnpm build passed locally during implementation.
• pnpm scan:browser-secrets passed locally during implementation.

Boundary Notes

• Real staged smoke still depends on backend deployment and Vercel/Supabase env configuration tracked in the backend staging goal.

Orchestrator Lifecycle

worktree_path: /Users/botmaster/src/myPayTag/mypaytag-site-5-user-portal
branch: codex/5-user-portal-site
base_branch: dev
pr_number: pending
safe_to_remove_after_merge: true
backup_branches_to_retire: none

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
my-pay-tag-site	Ready	Preview, Comment	Jul 21, 2026 7:29pm

[KazanderDad]

@codex review

[KazanderDad]

@codex review

[KazanderDad]

@codex review

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 7ef460e62a

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Stabilize the translation function used by fetch effects

useTypedTranslation creates a new t wrapper on every render, so including t here causes every completed history fetch to update state, render again, and immediately start another fetch. An authenticated visitor therefore continuously calls the history backend; the identical dependency pattern in ReceivePathSettingsPanel does the same to /api/portal/preferences. Memoize the typed wrapper or otherwise make the effect depend only on stable values.

Useful? React with 👍 / 👎.

[chatgpt-codex-connector]

Preserve question context when grouping filtered history

When the backend honors type=quotes, type=answers, type=intents, or type=receipts by returning only the requested kinds, this lookup contains no question records, while those item contracts do not carry payingDapp. Consequently the default paying-app view places every filtered result under Unknown PayingDapp. Include grouping context in each summary/response or resolve the referenced questions separately so type-filtered views retain meaningful groups.

Useful? React with 👍 / 👎.

[chatgpt-codex-connector]

Load remaining history pages

When the backend returns a nextCursor, this function returns only the first response and no caller consumes that cursor or offers a load-more action. Accounts exceeding the backend page size therefore see an incomplete transaction history with no indication that older records exist. Follow nextCursor or expose pagination controls that request subsequent pages.

Useful? React with 👍 / 👎.