finding: duly_member wins the sys_user page assignment over the platform's sys_user_detail by list position only #113

Measured live while landing #13 (PR #112), on @objectstack/* 17.2.0.

GET /api/v1/meta/page returns two pages assigned to sys_user: our duly_member and the platform's own sys_user_detail. Ours renders because it comes first in the list and the console's assignment resolution is a stable sort over that order — usePageAssignment reads a priority key that PageSchema (a strictObject) does not let us declare (objectui#7298).

So the member page is reachable today by an ordering nothing pins. A platform change that emits sys_user_detail first, or sorts assignments differently, would make duly_member disappear with no error and no test failing — the same silent-absence shape as #86 and #96.

Not fixed here, because the only authorable fix is upstream: a declarable priority (or an explicit "this app's page overrides the platform default for object X" key). Two things worth doing app-side when someone is in the file:

1. A test that asserts duly_member is the first page returned for sys_user from the built artifact, so a platform reordering shows up as a red test rather than a missing screen.
2. A line in src/pages/member.page.ts's header saying the page's reachability rests on this ordering, with the upstream number.

Restart-when: closed objectstack-ai/objectui#7298.