Restore npm release workflow execution in the renamed repository (#13)

The release pipeline was silently skipped because the workflow guard still targeted the old repository slug. Updating the guard to recodeecom/musafety ensures tagged releases can actually run publish with provenance.

Constraint: Keep release workflow restricted to the canonical maintainer repo

Rejected: Remove repository guard entirely | risks unintended publish attempts from forks

Confidence: high

Scope-risk: narrow

Reversibility: clean

Directive: If repository slug changes again, update both workflow guard and release tests together

Tested: npm test (41/41 pass)

Not-tested: live npm publish success from GitHub Actions with npm environment secrets

Co-authored-by: NagyVikt <nagy.viktordp@gmail.com>

Author: NagyVikt

.github/workflows/release.yml

@@ -14,7 +14,7 @@ permissions:
 
 jobs:
   publish:
-    if: github.repository == 'recodeecom/multiagent-safety'
+    if: github.repository == 'recodeecom/musafety'
     runs-on: ubuntu-latest
     environment: npm