Formalize build_notes.md path and artifact handling

.github/agents/technical-writer.agent.md

@@ -39,8 +39,8 @@ docs/
     justifications.md    # Generated by ReqStream  
   requirements_report/
     trace_matrix.md      # Generated by ReqStream
+  build_notes.md         # Generated by BuildMark
   build_notes/
-    build_notes.md       # Generated by BuildMark
     versions.md          # Generated by VersionMark
   code_quality/
     sonar-quality.md     # Generated by SonarMark
@@ -100,7 +100,7 @@ docs/
 - **❌ Avoid**: Tool version numbers, specific counts (requirements, tests, files), current dates, "latest" references
 - **❌ Examples**: "Currently using Node.js 18.2.1", "The system has 47 requirements", "As of March 2024"
 - **✅ Instead**: Reference auto-generated reports, use relative descriptions, focus on stable concepts
-- **✅ Examples**: "See build_notes.md for current tool versions", "The requirements are organized by subsystem",
+- **✅ Examples**: "See docs/build_notes.md for current tool versions", "The requirements are organized by subsystem",
   "The architecture follows..."
 
 **Exception**: Include transitory information only when documenting specific releases, version history, or

.github/workflows/release.yaml

@@ -63,18 +63,13 @@ jobs:
           name: documents
           path: artifacts
 
-      - name: Move build_notes.md to root
-        run: |
-          set -e
-          mv artifacts/build_notes.md build_notes.md
-
       - name: Create GitHub Release
         if: inputs.publish == 'release' || inputs.publish == 'publish'
         uses: ncipollo/release-action@v1
         with:
           tag: ${{ inputs.version }}
           artifacts: artifacts/*
-          bodyFile: build_notes.md
+          bodyFile: artifacts/build_notes.md
           generateReleaseNotes: false
 
       - name: Publish to NuGet.org