TASK22269: consolidate azurestorage hash metadata mapping

memory-bank/change-log.md

@@ -2942,3 +2942,36 @@ Validation:
 Follow-ups:
 
 - Remaining potential cleanups in `actions/azurestorage.js` are broader non-slice refactors (legacy logging verbosity, large function decomposition) and should be handled separately to keep risk bounded.
+
+---
+
+### CL-082: TASK22269 Slice B1.7 — azurestorage hash metadata helper consolidation
+
+date: 2026-03-25
+author: Cline
+scope: `actions/azurestorage.js`
+type: change
+rationale: Continue bounded normalization by consolidating repeated hash metadata object field population into a single local helper.
+impact: Reduces duplicated metadata field assembly and drift risk while preserving existing output shape and hash behavior.
+status: completed
+
+Summary:
+
+- Added `buildHashMetadataPaths({ containerName, casefolderID, blobname })` helper.
+- Replaced repeated per-object hash metadata assignment in:
+    - `getBlobs`
+    - `getProgressBlobs`
+    - `getRepsFilesBlobs`
+- Preserved existing metadata contracts:
+    - keys unchanged: `hashedfilepath`, `hasheddeletepath`, `hashgetblobs`
+    - same encoded query path inputs and route semantics.
+
+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:
+
+- Any further `azurestorage.js` cleanup should remain bounded (e.g., logging-only normalization) and separated from behavior-affecting refactors.