TASK22269: tidy azurestorage blob path split locals

memory-bank/change-log.md

@@ -3007,3 +3007,34 @@ Validation:
 Follow-ups:
 
 - Optional next bounded slice: add an explicit assertion for encoded `casefolderID` variants containing reserved query characters (`?`, `&`) if those inputs are expected in future flows.
+
+---
+
+### CL-084: TASK22269 Slice B1.9 — azurestorage local split-value tidy in touched helper consumers
+
+date: 2026-03-26
+author: Cline
+scope: `actions/azurestorage.js`
+type: change
+rationale: Execute the selected next bounded readability-only slice by reducing repeated `blob.name.split("/")` access in the recently touched helper-consumer functions.
+impact: Non-behavioral maintainability improvement in azurestorage helper-consumer paths; no API/route contract changes.
+status: completed
+
+Summary:
+
+- In targeted functions (`getBlobs`, `getProgressBlobs`, `getRepsFilesBlobs`), introduced local path-part variables to avoid repeated inline splitting:
+    - `blobPathParts`
+    - `fileName` / `appealBlobName` / `repFileName`
+    - `casefolderPath`
+- Replaced repeated field reads and helper arguments with these locals in object construction and hash metadata composition.
+- Preserved existing query composition and output shape/keys (including hashed path metadata fields).
+
+Validation:
+
+- `npm run lint` -> pass with warnings only (pre-existing `react-hooks/exhaustive-deps`; no new lint errors)
+- `node tests/phase22/index.test.cjs` -> pass
+- `node tests/phase7/service-behaviour.test.cjs` -> pass (13/13)
+
+Follow-ups:
+
+- Optional next bounded slice: logging-only normalization in these same azurestorage functions (no behavior change), done separately from structural refactors.