Mark NWS forecast discussion resilience implemented

This commit is contained in:
2026-08-03 00:24:26 +00:00
parent 3740c779eb
commit 456a46e01b
2 changed files with 30 additions and 30 deletions

View File

@@ -2,10 +2,10 @@
## Purpose
Complete the remaining resilience work defined in
[`afd-section-heading-variants.md`](afd-section-heading-variants.md) without
changing the canonical forecast-discussion contract. Stages 1-8 summarize work
already completed. Implement Stages 9-13 in order.
All resilience work defined in
[`afd-section-heading-variants.md`](afd-section-heading-variants.md) is
complete without changing the canonical forecast-discussion contract. This plan
preserves the implementation details as a historical record.
## Cross-Stage Constraints
@@ -80,7 +80,7 @@ Focused tests, the full repository suite, static analysis, and diff checks
passed. The public model and schemas remained unchanged, and the roadmap was
updated to describe the completed behavior.
## Stage 9: Add Parenthesized-Terminal Heading Syntax
## Stage 9: Add Parenthesized-Terminal Heading Syntax — Completed
Recognize the observed `.<IDENTITY> (<qualifier>)...` family without weakening
generic identity validation.
@@ -141,7 +141,7 @@ go test -count=1 ./internal/providers/nws
Do not proceed until all previous heading and scanner tests still pass.
## Stage 10: Add Explicit Canonical Role Aliases
## Stage 10: Add Explicit Canonical Role Aliases — Completed
Make true wording synonyms cheap to support while preserving semantic
distinctions.
@@ -180,7 +180,7 @@ go test -count=1 ./internal/providers/nws
Do not change the canonical model to expose near-term or discussion content.
## Stage 11: Harden Key-Message Metadata and Item Parsing
## Stage 11: Harden Key-Message Metadata and Item Parsing — Completed
Replace prefix-sensitive, hyphen-only parsing with conservative metadata and
list classifiers.
@@ -247,7 +247,7 @@ gofmt -w internal/providers/nws/forecast_discussion.go internal/providers/nws/fo
go test -count=1 ./internal/providers/nws
```
## Stage 12: Add Representative Numbered and Key-Points Fixtures
## Stage 12: Add Representative Numbered and Key-Points Fixtures — Completed
Prove the new extension points through provider and normalizer boundaries.
@@ -290,7 +290,7 @@ gofmt -w internal/providers/nws/forecast_discussion_test.go internal/normalizers
go test -count=1 ./internal/providers/nws ./internal/normalizers/nws
```
## Stage 13: Reconcile Documentation and Perform Final Validation
## Stage 13: Reconcile Documentation and Perform Final Validation — Completed
Close the second resilience follow-up only after all behavior is implemented and
verified.