note about dormant SEPs

Author: dsp-ant

docs/community/governance.mdx

@@ -92,7 +92,7 @@ Both must:
 Projects and working groups without specified processes default to:
 
 - GitHub pull requests and issues for contributions
-- A public channel in the official MCP Discord
+- A public channel in the official MCP Discord (TBD)
 
 #### Maintenance Responsibilities
 

docs/community/sep-guidelines.mdx

@@ -46,6 +46,7 @@ The standard SEP workflow is:
 3. The sponsor will review and may request changes before formal review, based on community feedback. Once ready for review, the tag `in-review` is added.
 4. Once sponsored, the SEP enters formal review by the core team
 5. The SEP may be accepted, rejected, or returned for revision.
+6. If the SEP has not found a sponsor within three months, core-maintainers are free to close the SEP as `dormant`.
 
 ### SEP States
 
@@ -59,6 +60,7 @@ SEPs can be one one of the following states
 - `withdrawn`: SEP withdrawn.
 - `final`: SEP finalized.
 - `superseded`: SEP has been replaced by a newer SEP.
+- `dormant`: SEP that has not found sponsors and was subsequently closed.
 
 ### SEP Review & Resolution