BX Mobile-Web Parity Test Report

Date: 2026-04-29
Scope: bx/bx-mobile parity against bx/bx-web
Execution mode: Subagent-driven + inline continuation

1) Build and Runtime Verification

cd bx/bx-mobile && npm run build -> PASS
cd bx/bx-mobile && npm run dev -- --host 127.0.0.1 --port 5174 -> PASS (dev server started)

2) Page-Level 5-Point Checklist

page/menu	reachable	list	detail	actions	writeback	result
`advance-apply`	yes	yes	yes	yes	yes	PASS
`advance-approve`	yes	yes	yes	yes	yes	PASS
`advance-issue`	yes	yes	yes	yes	yes	PASS
`reimburse-apply`	yes	yes	yes	yes	yes	PASS
`reimburse-approve`	yes	yes	yes	yes	yes	PASS
`payment`	yes	yes	yes	yes	yes	PASS
`mine`	yes	yes	yes	yes	yes	PASS
`todo`	yes	yes	yes	yes	yes	PASS
`all`	yes	yes	yes	yes	yes	PASS
`user-manage`	yes	yes	yes	yes	yes	PASS
`role-manage`	yes	yes	yes	yes	yes	PASS
`menu-manage`	yes	yes	yes	yes	yes	PASS
`project`	yes	yes	yes	yes	yes	PASS
`wf-advance`	yes	yes	yes	yes	yes	PASS
`wf-reimburse`	yes	yes	yes	yes	yes	PASS

3) Role Matrix Regression

Covered in code-path and permission route guard checks:
- ADMIN
- FINANCE
- GENERAL_MANAGER
- APPLICANT
Result: no parity blockers identified in current implementation pass.

4) Key Fixes Landed in This Round

API parity: fixed mobile reimburseOffsetRecords endpoint path to align web.
Advance flow: rejected entries can submit directly; issue amount validation; detail writeback refresh.
Reimburse flow: create ID robustness, new-attachment binding only, rejected entries can submit.
Approval flow: active-step detection supports both approvalStatus and status.
Payment flow: detail fetch strengthened, issue validation tightened.

5) Blockers

No blocking issue found in current parity scope.