TASK22269: normalize touched azurestorage logging calls

This commit is contained in:
2026-03-26 11:15:33 +00:00
parent 9791270670
commit 427e1c4673
2 changed files with 36 additions and 3 deletions
+33
View File
@@ -3038,3 +3038,36 @@ Validation:
Follow-ups:
- Optional next bounded slice: logging-only normalization in these same azurestorage functions (no behavior change), done separately from structural refactors.
---
### CL-085: TASK22269 Slice B1.10 — azurestorage touched-function logging normalization
date: 2026-03-26
author: Cline
scope: `actions/azurestorage.js`
type: change
rationale: Execute the next bounded, logging-only slice by normalizing selected touched-function logs to `consoleLogger` for consistency with current helper/error logging style.
impact: Observability consistency improvement only; no API/route behavior or payload contract changes.
status: completed
Summary:
- In previously touched helper-consumer functions only:
- `getProgressBlobs`
- `getRepsFilesBlobs`
- Replaced selected direct `console.log(...)` calls with `consoleLogger(...)`:
- progress blob path-parts trace
- per-blob name trace in reps file listing
- final `blobObj` trace in reps file listing
- Scope intentionally excludes broader file-wide logging normalization to keep risk bounded.
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: prune currently-unused local `blobDocumentType` variables in the same touched functions (readability-only, no behavior change).