Feat/772 access requests

[vbeni30]

Review Ask Status

Here’s how each point maps:

Review ask	Status
Dialog tests (success, missing director, validation, service failure)	✅ Already covered by request-access-dialog.test.tsx (on dev, included in the rebased branch)
Verify /api/interactions/access-request fetch	✅ Covered by api.test.ts — asserts POST to the correct endpoint with JSON body + auth header
API/action-level assertion (not just mocked dialog action)	✅ Added actions.test.ts — submitAccessRequestAction delegates to submitAccessRequest and maps success/error
Entry-point check (report + collection)	✅ Added entry-point tests for report action rail (entity-engagement-rail-actions.test.tsx) and report cards in collection listings (entity-card-footer.test.tsx)
Merge conflict resolved	✅ PR is now MERGEABLE with mergeStateStatus: CLEAN

Test Coverage Stack

Dialog UI
  → request-access-dialog.test.tsx
    (mocks action — fine for UI)

Action wiring
  → actions.test.ts
    (NEW)

API fetch
  → api.test.ts
    (POST /api/interactions/access-request)

Entry points
  → entity-engagement-rail-actions.test.tsx
    (NEW — report rail)

  → entity-card-footer.test.tsx
    (NEW — collection report cards)

[Seme30]

Reviewed against issue #772. The PR adds passing dialog tests for successful submission, a missing director, backend validation feedback, and service failure. However, it still mocks submitAccessRequestAction, so it does not verify the /api/interactions/access-request request or confirm both report and collection entry points use it. Please add one API/action-level fetch assertion (or an integration test) and an entry-point check. PR #805 also needs its merge conflict resolved before it can merge.

Addressed in commit 05b38df.