refactor(actions): adopt endpoint client in case service posts

memory-bank/change-log.md

@@ -1798,3 +1798,35 @@ Validation:
 Follow-ups:
 
 - Optional next bounded slice: evaluate config-based POST helpers in `caseDirectService` (`createNewCase`, `createNewCaseBlob`, `updateCase`, `updateCaseBlob`) for selective `requestJson(...)` adoption while preserving existing side effects and error contracts.
+
+---
+
+### CL-050: TASK22260 next slice — case direct service POST helper requestJson adoption
+
+date: 2026-03-25
+author: Cline
+scope: `actions/services/caseDirectService.js`
+type: change
+rationale: Continue bounded client-layer migration by moving config-based case service POST helpers from direct `axios(config)` usage to shared `requestJson(...)` while preserving current behavior and error semantics.
+impact: Reduces duplicated config-execution/response-extraction boilerplate and aligns case service write-helper internals with existing endpoint client conventions.
+status: completed
+
+Summary:
+
+- Migrated selected case service POST helpers to `requestJson(config)`:
+    - `createNewCase`
+    - `createNewCaseBlob`
+    - `updateCase`
+    - `updateCaseBlob`
+- Preserved behavior contracts:
+    - unchanged payload/query construction and URLs
+    - unchanged catch-path logging via `consoleLogger`
+    - no changes to non-targeted helper logic (`getAppealID`, `patchCase`, and already-migrated GET helpers)
+
+Validation:
+
+- `npm run lint` -> warnings only (pre-existing `react-hooks/exhaustive-deps`; no new lint errors)
+
+Follow-ups:
+
+- Optional next bounded slice: assess `patchCase` and `getAppealID` for migration opportunities (if/when preserving their specific behavior contracts remains straightforward).