Add stencil size and LFS cost

peps/pep-0774.rst

@@ -85,6 +85,7 @@ difference between the actual commits and the same commits with stencils added
 amounts to a difference of 0.03 MB per stencil file. This is a small increase in
 the context of the overall repository size, which has grown by 2.55 MB in the
 same time period. For six stencil files, this amounts to an upper bound of 0.18 MB.
+The current total size of the stencil files for all six platforms is 7.2MB.
 
 These stencils could become larger in the future with changes to register
 allocation, which would introduce 5-6 variants per instruction in each stencil
@@ -233,11 +234,14 @@ additional cost, which we’d like to avoid.
 Using Git LFS
 -------------
 
-Git Large File Storage (LFS) adds a tool dependency for contributors, complicating the development
-workflow, especially for those who may not already use Git LFS. Git LFS does not
-work well with offline workflows since files managed by LFS require an internet
-connection to fetch when checking out specific commits, which is disruptive for
-even basic Git workflows. 
+Git Large File Storage (LFS) adds a tool dependency for contributors,
+complicating the development workflow, especially for those who may not already
+use Git LFS. Git LFS does not work well with offline workflows since files
+managed by LFS require an internet connection to fetch when checking out
+specific commits, which is disruptive for even basic Git workflows. Git LFS has
+some free quota but there are `additional
+costs <https://docs.github.com/en/billing/managing-billing-for-your-products/managing-billing-for-git-large-file-storage/about-billing-for-git-large-file-storage>`__.
+for exceeding that quota which are also undesirable.
 
 Maintain the status quo with LLVM as a build-time dependency
 ------------------------------------------------------------