Final editorial spec text plan

[ptomato]

At the time of writing, we have merged all normative changes from the 2024-07 plenary into the proposal and have no new ones on the horizon. We've worked through most of the editorial requests in the issue tracker. This is a roadmap for the remaining ones so that observers can see the status at a glance.

• Editorial: Various fine-tooth comb changes #2944
  • Blocked on fixing the codecov uploader Update ecmarkup and codecov #2945
• Editorial: Option values should use spec enums instead of strings #2946 @ptomato
  • PR Use specification values (enums) instead of strings #2952
• Editorial: Split out total() code path from RoundRelativeDuration #2947 @ptomato
  • Investigate whether this is an improvement
  • PR Editorial: Split total() code path out of RoundRelativeDuration #2987 - needs review
• Editorial: Consider recombining ISO 8601 and calendar-specific operations #2948 @ptomato
  • Investigate whether this is an improvement
  • PR Editorial: Combine ISO8601 and calendar operations #2996
• Editorial: Use ISO Date and Date-Time Records in more places #2949 @ptomato
  • PR Editorial: Use ISO Date, ISO Date-Time, and Time Records in more places #3003
• Clarify timeStyle:long/full for Plain types #2795 @ptomato
  • Discuss in next champions meeting what, if anything, needs to change
  • PR fixing spec text to match existing consensus Editorial: Fixes for remaining issues from Anba #2995
  • test262 coverage Temporal: Add additional coverage based on issues reported by Anba test262#4248
• PrepareCalendarFields: Replace TO-PRIMITIVE-AND-REQUIRE-STRING conversion #2962 @ptomato
  • PR Editorial: Fixes for remaining issues from Anba #2995
• Consider renaming NormalizeDuration and UnnormalizeDuration #2953 @ptomato
  • PR Editorial: Rename "normalize" and "unnormalize" for durations #3007
• Editorial: Introduce Record for relativeTo #2837
  • Code prototype @arshaw
  • Decide whether this is an improvement
  • Spec text @ptomato
  • PR
• CalendarDateToISO: Constrain behaviour for regnal years? #2865 @gibson042
  • PR Editorial: Recommend "remapping" for dates exceeding era year bounds  #2986

These issues should be the contents of https://github.com/tc39/proposal-temporal/milestone/11. Don't add anything new there without checking.

[ptomato]

All right, that was all the editorial refactors that we'd wanted to do. Of course we'll still fix typos and mistakes if they are pointed out by implementations, but nothing else is planned.

The next steps are

• do what we can to help the in-progress implementations
• increase test262 coverage by addressing the issues in the issue tracker labelled "test262"
• land the open cookbook PRs
• address the remaining issues with documentation/developer education in the issue tracker labelled "documentation"

[justingrant]

Great work @ptomato! 🙏