Skip to content

feat: Support tracking issue impact over time (#156)#177

Draft
duncanleo wants to merge 102 commits intomainfrom
duncanleo/data-overhaul
Draft

feat: Support tracking issue impact over time (#156)#177
duncanleo wants to merge 102 commits intomainfrom
duncanleo/data-overhaul

Conversation

@duncanleo
Copy link
Copy Markdown
Member

@duncanleo duncanleo commented Mar 21, 2026

Fixes #156

@duncanleo duncanleo self-assigned this Mar 21, 2026
@duncanleo duncanleo changed the title feat: Support tracking issue impact over time feat: Support tracking issue impact over time (#156) Mar 21, 2026
@duncanleo duncanleo force-pushed the duncanleo/data-overhaul branch 13 times, most recently from ca15f1a to 965bee3 Compare March 22, 2026 16:43
@duncanleo duncanleo force-pushed the duncanleo/data-overhaul branch from 0b0ff52 to 78cdc9d Compare March 23, 2026 16:07
@duncanleo duncanleo force-pushed the duncanleo/data-overhaul branch from 2e64332 to 46a53bb Compare April 4, 2026 10:27
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Add one-off collapse tooling that clusters maintenance/infra issues by slug, type, and overlapping or adjacent time ranges, then merges into deterministic canonical issues. Apply the merge to current duplicate groups and persist audit artifacts for traceability.

Made-with: Cursor
Drop the temporary collapse scripts and generated reports now that the one-off maintenance/infra merge has been applied to the data files.

Made-with: Cursor
duncanleo and others added 16 commits April 18, 2026 17:56
Update multilingual render text and translation source metadata for evidence rows that were rewritten from verifiable source articles, and keep deduped entries consistent with the revised text.

Made-with: Cursor
Ensure service-impact claims without time hints are anchored to the evidence timestamp so impact events are not dropped, while still allowing maintenance/infra metadata-only cause updates to persist without requiring service periods.

Made-with: Cursor
Add a deterministic relative-date tool with RRULE-style weekday inputs and tighten extraction guidance so planned weekend constraints become explicit timed claims instead of being dropped as advisory text. Also bump the OpenAI SDK to the latest workspace version.

Made-with: Cursor
Persist regenerated impact events from the latest empty-impact replay run, including recovered weekend maintenance windows and related issue updates that now produce concrete events.

Made-with: Cursor
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Delete the three CCL no-mobile-signals issue bundles to simplify the current cleanup pass and reduce unresolved issue validation failures.

Made-with: Cursor
Strengthen extraction guidance for single-platform degraded-service evidence, replay the affected bucket 2/3 issues, and update the temporary validation report to reflect the reduced failure count and remaining buckets.

Made-with: Cursor
Remove the temporary validation findings report from version control so it stays local-only and out of committed changes.

Made-with: Cursor
Prevent `mrtdown-cli show` from crashing when derived service/facility state omits a `causes` array by defaulting to an empty list before rendering.

Made-with: Cursor
Capture the source article's station-by-station rollout schedule in evidence and align impact periods so facilities are modeled in phased windows rather than one concurrent multi-year window.

Made-with: Cursor
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Support tracking impact over time

1 participant