Separate glossary context from prompt protection

docs/internal/prompts.md

@@ -17,8 +17,10 @@ The operator's prompt definition controls which variables its template uses.
 
 For a standard request preview or validation, select a native PromptKit profile
 and supply the template variables used by the selected prompt. The shipped
-proposal definitions use `TranscriptDescriptionBlock`, `GlossaryJSON`, and
-`SectionJSON`; the validator definitions use `TranscriptDescriptionBlock` and
+proposal definitions use `TranscriptDescriptionBlock`, `GlossaryJSON`,
+`ProtectedTermsJSON`, and `SectionJSON`. Glossary entries provide context,
+and the separate spelling list defines protection. Preview defaults the
+spelling list to `[]` when omitted. The validator definitions use `TranscriptDescriptionBlock` and
 `PayloadJSON`. The latter is supplied candidate JSON and does not require a
 proposal inference call. An operator replacement may use different variables.
 See the [upstream CLI reference](https://forge.maximumdirect.net/base-layer/commandkit/src/commit/f369d6a78253b6e6fcb1e023fb2e9c3af1d20ff0/docs/cli.md)

docs/roadmap/remediation.md

@@ -121,6 +121,8 @@ behavior and the recorded wider-root case.
 
 ## R3 — P2: Separate Glossary Context From Protection in Proposal Prompts
 
+**Status:** Completed. Proposal requests carry separate context and protected spellings, with an empty preview default.
+
 **Category**
 
 An unintended prompt restriction in Stage 11.