Clarify implementation requirements for auto-save and inline editing

[emilylordahl]

As part of the designs created in #79, there is additional implementation annotations needed to clarify the behavior of auto save + inline editing.

Things to consider:

• If elements are required, throwing an error is required but at what point in the interaction?
• Given the empty sections behavior (providing a message and options to add or remove), can that behavior be reused?
• If elements are all options, that likely solves the implementation complexity. However, the user will need a path to error recovery when testing the form. Assess the tradeoffs of this.
• • In Google Forms
  • questions are optional but the input cannot be deleted
  • If a field is in focus and user leaves the page, the draft text persisted when user returns

ACs

• [ ] Clarifications are provided via appropriate design documentation such as mocks, prototypes or annotations

[JennyRichards-Flexion]

9/6/24: In conversation with Jim, this item is MEDIUM priority.