Reduce ambient prompt surface in high-traffic workflows (#40695)

Author: Copilot

.github/agents/adr-writer.agent.md

@@ -34,8 +34,6 @@ docs/adr/
 
 ## ADR Template
 
-Two parts: **human-friendly narrative**, then **RFC 2119 normative specification** for machine-checkable conformance.
-
 ```markdown
 # ADR-{NNNN}: {Concise Decision Title}
 
@@ -45,8 +43,6 @@ Two parts: **human-friendly narrative**, then **RFC 2119 normative specification
 
 ---
 
-## Part 1 — Narrative (Human-Friendly)
-
 ### Context
 
 {Describe the situation, problem, and forces at play in plain language. What is the issue that motivated this decision? What constraints exist? What are the non-negotiable requirements? Write for a developer who is new to the codebase and needs background without reading the code. Keep this to 3–5 sentences.}
@@ -83,28 +79,6 @@ Two parts: **human-friendly narrative**, then **RFC 2119 normative specification
 
 ---
 
-## Part 2 — Normative Specification (RFC 2119)
-
-> The key words **MUST**, **MUST NOT**, **REQUIRED**, **SHALL**, **SHALL NOT**, **SHOULD**, **SHOULD NOT**, **RECOMMENDED**, **MAY**, and **OPTIONAL** in this section are to be interpreted as described in [RFC 2119](https://www.rfc-editor.org/rfc/rfc2119).
-
-### {Primary requirement area — e.g., "Data Storage", "API Design", "Authentication"}
-
-1. Implementations **MUST** {the non-negotiable core of the decision in imperative form}.
-2. Implementations **MUST NOT** {what is explicitly prohibited by this decision}.
-3. Implementations **SHOULD** {what is strongly recommended but has valid exceptions}.
-4. Implementations **MAY** {what is permitted but not required}.
-
-### {Secondary requirement area, if applicable}
-
-1. {Additional normative requirement}.
-2. {Additional normative requirement}.
-
-### Conformance
-
-An implementation is considered conformant with this ADR if it satisfies all **MUST** and **MUST NOT** requirements above. Failure to meet any **MUST** or **MUST NOT** requirement constitutes non-conformance.
-
----
-
 *ADR created by [adr-writer agent]. Review and finalize before changing status from Draft to Accepted.*
 ```
 
@@ -120,8 +94,6 @@ An implementation is considered conformant with this ADR if it satisfies all **M
 
 ## Writing Quality Standards
 
-### Part 1 — Narrative Sections
-
 #### Context (3–5 sentences)
 - *What problem? What constraints?* (technical, organizational, timeline)
 - Codebase state at decision time
@@ -143,31 +115,6 @@ An implementation is considered conformant with this ADR if it satisfies all **M
 - **Neutral**: side effects worth noting
 - ≥2 per category for non-trivial decisions
 
-### Part 2 — Normative Specification
-
-Translates the Decision into testable [RFC 2119](https://www.rfc-editor.org/rfc/rfc2119) requirements.
-
-#### RFC 2119 Keyword Usage
-
-| Keyword | Use when… |
-|---------|-----------|
-| **MUST** / **REQUIRED** / **SHALL** | Absolute, non-negotiable constraint |
-| **MUST NOT** / **SHALL NOT** | Absolute prohibition |
-| **SHOULD** / **RECOMMENDED** | Strong recommendation; valid exceptions may exist |
-| **SHOULD NOT** / **NOT RECOMMENDED** | Strong discouragement; valid exceptions may exist |
-| **MAY** / **OPTIONAL** | Truly optional |
-
-#### Writing Normative Requirements
-
-- Complete sentences ending with a period
-- Keywords (**MUST**, **SHOULD**, **MAY**, etc.) in **bold**
-- Atomic — one constraint per numbered item
-- Group into named subsections (e.g., "Storage", "API", "Authentication")
-- Every section ends with a **Conformance** paragraph
-- Stay consistent with the narrative Decision
-- "We will always use X" → "Implementations **MUST** use X"
-- "We prefer Y" → "Implementations **SHOULD** use Y"
-
 ## Procedure: Writing a New ADR
 
 ### Step 1: Next Sequence Number
@@ -206,7 +153,6 @@ Write to `docs/adr/{NNNN}-{title}.md`.
 
 ### Step 7: Validate
 
-**Part 1 — Narrative:**
 - [ ] Context, Decision, Alternatives, Consequences sections all present
 - [ ] Status is `Draft` for new ADRs
 - [ ] Date is today (YYYY-MM-DD format)
@@ -215,14 +161,6 @@ Write to `docs/adr/{NNNN}-{title}.md`.
 - [ ] Filename follows NNNN-kebab-case-title.md convention
 - [ ] ADR number in title matches filename number
 
-**Part 2 — Normative Specification:**
-- [ ] RFC 2119 boilerplate paragraph present
-- [ ] All normative keywords in **bold**
-- [ ] Each requirement atomic (one constraint per item)
-- [ ] Requirements grouped into named subsections
-- [ ] Conformance paragraph present
-- [ ] Normative requirements are consistent with the narrative Decision section
-
 ## Procedure: Analyzing a PR Diff for ADR Content
 
 Look for: