diff --git a/.github/workflows/build.yml b/.github/workflows/build.yml
index 60fe105..01caab0 100644
--- a/.github/workflows/build.yml
+++ b/.github/workflows/build.yml
@@ -2,7 +2,6 @@ name: Build SmartGears bundle
 
 on:
   push:
-    branches: ["**"]
   workflow_dispatch:
   release:
     types: [published]
@@ -33,11 +32,11 @@ jobs:
           path: SmartGears.lsp
 
       - name: Create draft release with bundle
-        if: github.ref == 'refs/heads/main' || github.event_name == 'workflow_dispatch'
+        if: github.event_name == 'push' || github.event_name == 'workflow_dispatch'
         uses: softprops/action-gh-release@v2
         with:
-          tag_name: draft-${{ github.run_number }}
-          name: SmartGears draft build #${{ github.run_number }}
+          tag_name: draft-${{ github.run_id }}-${{ github.run_attempt }}
+          name: SmartGears draft build #${{ github.run_id }}.${{ github.run_attempt }}
           draft: true
           generate_release_notes: true
           files: SmartGears.lsp
diff --git a/AGENTS.md b/AGENTS.md
index 6b06659..d447f3e 100644
--- a/AGENTS.md
+++ b/AGENTS.md
@@ -54,10 +54,17 @@ When a bug is reported, follow this exact workflow:
 ## 9. Summary: Core Imperatives  
 
 - Always treat documentation as first-class — read before writing.  
-- Always test before committing.  
-- Separate concerns — keep code modular.  
-- Document assumptions and references.  
-- Manage context window actively to avoid noise, repetition, and hallucination drift.  
-- Seek human input when uncertain.  
+- Always test before committing.
+- Separate concerns — keep code modular.
+- Document assumptions and references.
+- Manage context window actively to avoid noise, repetition, and hallucination drift.
+- Seek human input when uncertain.
 
-If at any point you can’t satisfy these conditions, **abort or request review** before proceeding.  
\ No newline at end of file
+### CI/Release Guardrail
+- Do not disable, bypass, or remove GitHub Actions steps that bundle sources, run smoke tests, or publish draft releases; keep the automated build-and-test pipeline intact when modifying workflows.
+
+### Status reporting in final responses
+- Always include an explicit readiness statement in the final summary (e.g., "Ready to push" or "Not ready to push").
+- If not ready, list the blockers.
+
+If at any point you can’t satisfy these conditions, **abort or request review** before proceeding.
\ No newline at end of file