Enhance project packing and markdown processing

- Added logging in Build-LocalPackages.ps1 to indicate
  which project is being packed and ensured each project
  is processed individually with the correct version and
  output path.

- Refactored SiteGenerator.cs to improve markdown file
  handling by moving the pipeline instantiation inside
  the loop for each markdown page, ensuring statelessness
  and deterministic behavior. Added comments for clarity.

Author: matt-goldman

Build-LocalPackages.ps1

@@ -47,6 +47,9 @@ if ($Version -notlike "*-alpha*") {
 Write-Host "Packing all projects with version $Version..."
 
 foreach ($proj in $projects) {
+    Write-Host "`nPacking project: $proj"
+    dotnet restore $proj
+    dotnet build $proj -c Release
     dotnet pack $proj -c Release -p:PackageVersion=$Version -o $OutputPath
 }
 

src/Blake.BuildTools/Generator/SiteGenerator.cs

@@ -126,14 +126,15 @@ public static async Task BuildAsync(GenerationOptions? options = null)
         }
 
 
-        // Bake: Process each markdown file and generate Razor pages
-        var mdPipeline = context.PipelineBuilder.Build();
-        using var sw = new StringWriter();
-        var renderer = new HtmlRenderer(sw);
-        mdPipeline.Setup(renderer);
-
         foreach (var mdPage in context.MarkdownPages)
-        { 
+        {
+            // Pipeline is instantiated for each page
+            // This ensures statelessness and guarantees deterministic behavior
+            var mdPipeline = context.PipelineBuilder.Build();
+            using var sw = new StringWriter();
+            var renderer = new HtmlRenderer(sw);
+            mdPipeline.Setup(renderer);
+
             var mdContent = mdPage.RawMarkdown;
 
             var frontmatter = FrontmatterHelper.ParseFrontmatter(mdContent, cleanedContent: out _);