refactor(actions): adopt endpoint client in portal involvement helpers

actions/services/portalDirectService.js

@@ -288,8 +288,7 @@ export const setRepInvolvment = async (caseid, contactid) => {
     };
 
     try {
-        const res = await axios(config);
+        return await requestJson(config);
-        return res.data;
     } catch (error) {
         consoleLogger(error);
     }
@@ -306,8 +305,7 @@ export const setCaseInvolvment = async (caseid, contactid) => {
     };
 
     try {
-        const res = await axios(config);
+        return await requestJson(config);
-        return res.data;
     } catch (error) {
         consoleLogger(error);
     }

memory-bank/change-log.md

@@ -1572,3 +1572,31 @@ Validation:
 Follow-ups:
 
 - Optional next bounded slice: migrate remaining non-hash POST helpers in `portalDirectService` (`setRepInvolvment`, `setCaseInvolvment`) to `requestJson` for full internal consistency.
+
+---
+
+### CL-043: TASK22260 next slice — portal involvement helper endpointClient completion
+
+date: 2026-03-25
+author: Cline
+scope: `actions/services/portalDirectService.js`
+type: change
+rationale: Complete the next bounded internal-consistency slice by migrating remaining non-hash portal involvement POST helpers to shared endpoint client request plumbing.
+impact: Aligns portal service POST helper internals with established `requestJson` usage while preserving route semantics and error handling.
+status: completed
+
+Summary:
+
+- Migrated remaining portal involvement helper POST functions to shared endpoint client:
+    - `setRepInvolvment`
+    - `setCaseInvolvment`
+- Both now use `requestJson(config)` while preserving existing payload shape, endpoint URLs, and catch-path logging behavior.
+- No changes made to hash-sensitive delete/message pathways.
+
+Validation:
+
+- `npm run lint` -> warnings only (pre-existing `react-hooks/exhaustive-deps`; no new lint errors)
+
+Follow-ups:
+
+- Optional next bounded slice: begin selective `requestJson` adoption for remaining config-based calls in `documentDirectService` where hash flow is already centralized.