Why: after IAM U4 (#115) gated member management via rdm.perm.check, ordinary project members still trigger a 403 because the members section requests rdm.role.options (authorized by member.manage) on every visit; and the live status bar shows an enormous elapsed time when a run arrives with the zero start time 0001-01-01T00:00:00Z.
Changes:
RdmMembersSection requests rdm.role.options only once manage.canManage is true (re-requested on project change; late responses dropped).
eventTime falls back to now for non-positive parsed timestamps.
Evidence: CI on PR HEAD is authoritative; worker ran tsc/vitest in its isolated workspace (SELF).
Impact: Frontend members section and store helper only. Supersedes #116.
Refs: Dev task fix/multiuser-project-collab; agent-exec transport d997d4a (PI).
Why: after IAM U4 (#115) gated member management via rdm.perm.check, ordinary project members still trigger a 403 because the members section requests `rdm.role.options` (authorized by member.manage) on every visit; and the live status bar shows an enormous elapsed time when a run arrives with the zero start time `0001-01-01T00:00:00Z`.
Changes:
- RdmMembersSection requests `rdm.role.options` only once `manage.canManage` is true (re-requested on project change; late responses dropped).
- `eventTime` falls back to now for non-positive parsed timestamps.
- Tests: `test/event-time.test.ts`, `test/rdm-members-options-gate.test.tsx`.
Evidence: CI on PR HEAD is authoritative; worker ran tsc/vitest in its isolated workspace (SELF).
Impact: Frontend members section and store helper only. Supersedes #116.
Refs: Dev task fix/multiuser-project-collab; agent-exec transport d997d4a (PI).
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Why: after IAM U4 (#115) gated member management via rdm.perm.check, ordinary project members still trigger a 403 because the members section requests
rdm.role.options(authorized by member.manage) on every visit; and the live status bar shows an enormous elapsed time when a run arrives with the zero start time0001-01-01T00:00:00Z.Changes:
rdm.role.optionsonly oncemanage.canManageis true (re-requested on project change; late responses dropped).eventTimefalls back to now for non-positive parsed timestamps.test/event-time.test.ts,test/rdm-members-options-gate.test.tsx.Evidence: CI on PR HEAD is authoritative; worker ran tsc/vitest in its isolated workspace (SELF).
Impact: Frontend members section and store helper only. Supersedes #116.
Refs: Dev task fix/multiuser-project-collab; agent-exec transport
d997d4a(PI).