pi updates

.pi/agent/agents/sdd-spec.md

@@ -106,10 +106,13 @@ The system MUST ...
 ### Requirement: {Requirement Being Removed}
 
 (Reason: {why this requirement is being removed})
+(Migration: {consumer/data/docs/test migration guidance, or "None"})
 ```
 
 Omit empty operation sections only when they would add noise. Do not invent implementation details.
 
+`## RENAMED Requirements` is intentionally unsupported in gentle-pi until `lib/openspec-deltas.ts` implements executable rename semantics. Do not emit RENAMED sections; model renames as explicit ADDED/MODIFIED/REMOVED changes with Reason/Migration notes or block and ask for implementation support.
+
 ## MODIFIED Requirements Workflow
 
 `## MODIFIED Requirements` is destructive at archive time because it replaces the canonical requirement block. To avoid losing scenarios:
@@ -122,6 +125,10 @@ Omit empty operation sections only when they would add noise. Do not invent impl
 
 If you are only adding behavior without changing existing behavior, use `## ADDED Requirements` instead of `## MODIFIED Requirements`.
 
+## REMOVED Requirements Workflow
+
+For each removed requirement, include `(Reason: ...)`. Include `(Migration: ...)` when consumers, persisted behavior, documentation, tests, or follow-up cleanup are affected; use `(Migration: None)` only when there is no migration impact.
+
 ## Full Spec Format for New Domains
 
 If no canonical spec exists for the domain, write a full spec in the same change path: