Merge pull request #1333 from cloudfoundry/assign-rfc-number3

Assigning number 0046 to RFC from PR #1251

Author: beyhan

…t-provide-custom-stacks-functionality.md …6-provide-custom-stacks-functionality.mdtoc/rfc/rfc-draft-provide-custom-stacks-functionality.md renamed to toc/rfc/rfc-0046-provide-custom-stacks-functionality.md toc/rfc/rfc-draft-provide-custom-stacks-functionality.md renamed to toc/rfc/rfc-0046-provide-custom-stacks-functionality.md

@@ -3,8 +3,8 @@
 - Name: Provide optional Custom Stacks Functionality in Cloud Foundry
 - Start Date: 2025-06-24
 - Author(s): @FloThinksPi
-- Status: Draft
-- RFC Pull Request: [community#1220](https://github.com/cloudfoundry/community/pull/1220)
+- Status: Accepted
+- RFC Pull Request: [community#1251](https://github.com/cloudfoundry/community/pull/1251)
 
 ## Summary
 
@@ -62,7 +62,7 @@ on the stack to produce the droplet. This in return means that:
   CAN just be instantiated to become an app instance when combining the droplet
   with the same stack it was built with at execution time
 
-![Current Stack Usage](rfc-draft-provide-custom-stacks-functionality/current_stack_usage.png)
+![Current Stack Usage](rfc-0046-provide-custom-stacks-functionality/current_stack_usage.png)
 Pictured in above diagram is how the stack is brought into a CF
 Foundation and used in a CF Foundation. The following problems occur
 when trying to remove/deprecate a stack towards users of a CF