[oncall-telemetry] Default report window to rolling 7 days ending today, Fixes AB#3683194

[shahzaibj]

Fixes AB#3683194

Feedback

From Fadi Durah's ★4 skill-effectiveness survey (Jun 2026, oncall-weekly-telemetry-report):

"The telemetry skill was certainly helpful, the biggest feedback is that it seemed to capture the wrong timeframe (didn't capture the most recent 6 days). I'm sure I could've spent some time with it to get it to target the right date, but this is probably something that should happen by default in order to save more time for the developer, and something moumita has been pushing for."

Root cause (repro'd on today's clock, Thu 2026-07-09)

bootstrap-report.ps1 was computing "reporting Sunday" as the most recent Sunday strictly before today — which is the Sunday of the currently in-progress week. Run on a Thursday it picked Sun 2026-07-05 → Sat 2026-07-11 where Saturday is 2 days in the future, so the WoW section queried a 4-day partial window and dropped the last complete week. Exactly Fadi's "missed the last 6 days" complaint. SKILL.md then compounded it by asking the model to confirm the Sunday with the user — the manual coax that the developer shouldn't have to do.

Today (UTC)	Old default (broken)	New default
Thu 2026-07-09	Sun 07-05 → Sat 07-11 (future!)	Thu 07-02 → Thu 07-09 ✅
Mon 2026-07-13	Sun 07-12 → Sat 07-18 (future!)	Mon 07-06 → Mon 07-13 ✅

Fix

Per the user's direction, deep rewrite: rolling [today−7d, today) for the primary WoW view, keeping Sun-Sat weekly bucketing only for the 60-day trend (where stable weekly denominators still matter).

• bootstrap-report.ps1 — new -EndDate param (default: today UTC). Computes curStart = curEnd−7d, prevStart = curEnd−14d, and trendEnd = startofweek(curEnd). Stamps the resolved window into the <title>, <div class="meta"> block, and Generated banner so header dates can never drift from what was queried (this is the ADO acceptance criterion). Refuses future end-dates. Collision fingerprint stopped keying off title/meta (which bootstrap now rewrites unconditionally) — uses firstKpi + size ratio only.

• 15 KQL templates — 12 primary/WoW queries switched to half-open [prevStart, curEnd) with wk = iff(EventInfo_Time >= curStart, curStart, prevStart); downstream JS helpers unchanged because wk still sorts lexicographically. The 3 60-day-trend queries keep startofweek() bucketing; only <END> renamed to <TREND_END> with clarified startofweek(today)-exclusive semantics. Placeholder audit is now consistent across all 15 files.

• SKILL.md — rewrote Inputs to confirm §1: do NOT ask the user for a date by default; just run bootstrap. Override via -EndDate only when the user explicitly requests a non-default window. Filename convention <sunday> → <end-date> throughout. All KQL placeholder examples switched to the rolling-window form.

• validate-report.ps1 — new check Migrate to AndroidX #11 asserts the meta-line "Last 7 days" dates are self-consistent with the filename's end-date. Catches any hand-edit that broke the auto-stamp, or a stale template stub being published fresh.

• Docs — template-readme.md § Date fields rewritten (bootstrap owns every date field; author never edits them). kusto-cheatsheet.md gains § 3 Rolling 7-day WoW window with the canonical let curStart/curEnd/prevStart template; the pre-existing startofweek()-alignment section is now scoped explicitly to the 60-day trend.

Breaking changes (intentional)

• bootstrap-report.ps1: -ReportingSunday parameter removed; use -EndDate. The old parameter name encoded the exact semantic mismatch that caused the bug — keeping it would have preserved the footgun.
• Output filename: oncall-wow-report-<end-date>.html (was <sunday>.html). Old on-disk reports are unaffected.

Verification

• Run on 2026-07-09 → correctly resolves to [2026-07-02, 2026-07-09).
• -EndDate 2026-07-02 → [2026-06-25, 2026-07-02).
• -EndDate 2027-01-01 → refused (future-date guard).
• Same-day re-bootstrap of unfilled stub → silently overwrites.
• Same-day re-bootstrap after author populated KPI → HARD HALT exit 2 unless -Force.
• Validator check Migrate to AndroidX #11 passes on fresh stub, FAILs on a hand-mutated meta line.
• Placeholder audit across all 15 rewritten .kql files — no stale <START>/<END>/<CURR_*>/<PREV_WEEK> references remain.

[github-actions]

✅ Work item link check complete. Description contains link AB#3683194 to an Azure Boards work item.

[github-actions]

✅ Work item link check complete. Description contains link AB#3683194 to an Azure Boards work item.

[github-actions]

❌ Invalid work item number: AB#3683194

##. Work item number must be a valid integer.

Click here to learn more.