Clarify grammar focus in correction repair conversations
This commit is contained in:
@@ -33,6 +33,18 @@ and [developer guide](../development.md) for the applicable policies.
|
||||
|
||||
## Stage 2 — Review Proposal and Repair Conversations
|
||||
|
||||
**Complete.** The shipped and operator-replaced grammar requests retained the
|
||||
proposal context, including a synthetic glossary entry and protected spelling.
|
||||
The wire schema changed from a correction set to one repair result. The second
|
||||
turn retained its branch's prior revision, and the other branch started from
|
||||
the original proposal exchange. The adapter fixture confirmed separate proposal
|
||||
and repair profiles. Runner fixtures confirmed updated previews after retargeting,
|
||||
omission of an inapplicable after-preview, and withdrawal.
|
||||
|
||||
The shipped grammar repair wording could read as a blanket restriction on
|
||||
changes to other words. The revised text describes the grammar focus and leaves
|
||||
the shared editorial allowance explicit in the rendered request.
|
||||
|
||||
1. Use the existing subprocess fixture to exercise the production adapter and
|
||||
coordinator with scripted responses. Inspect its captured request messages
|
||||
and response schemas for the initial proposal and the two-turn repair.
|
||||
|
||||
Reference in New Issue
Block a user