fix(release): re-enable hard E404 failure in publish_one() once @aimasteracc npm scope is registered

[aimasteracc]

Context

PR #533 (merged to develop) added graceful degradation in release.yml's publish_one() function: when npm returns E404 / Scope not found, it currently warns and exits 0 instead of failing hard.

This was necessary for v0.2.0 because the @aimasteracc scope has never been registered on npmjs.com. Blocking the release ceremony on npm infrastructure registration would have prevented shipping the binary release, which is the primary deliverable.

Codex P1 review (PR #533 discussion_r3355193388) correctly flagged that this creates a false-green release gate: the finalize step can complete while npm packages were not actually published.

Required action (post-scope-registration)

Once the founder registers @aimasteracc on npmjs.com:

1. In .github/workflows/release.yml, change publish_one() to remove the E404 graceful degradation:

   # Before (graceful, v0.2.0 workaround):
   if echo "$npm_err" | grep -qE "E404|Scope not found"; then
     echo "::warning::..."
     return 0
   fi
   
   # After (strict, once scope is registered):
   # Remove the E404 check entirely — let the publish fail hard

2. Verify on a dry-run that npm publish --access public --provenance --dry-run succeeds for all 6 platform packages.

3. Ship the change in the v0.2.1 or v0.2.2 release cycle.

Acceptance criteria

• @aimasteracc scope registered on npmjs.com by founder
• publish_one() E404 grace removed from release.yml
• Release dry-run shows all 6 packages publishable
• publish to npm CI job succeeds (no longer exits 0 on scope error)

References

• PR ci(release): graceful npm publish — token absent + E404 scope-not-found + PM dispatch v41 #533 (Codex P1: discussion_r3355193388)
• RFC-0110 (npm/bun distribution)
• Issue fix(npm): use 128+signal exit code in mycelium.cjs launcher for SIGTERM/SIGINT #525 (npm signal exit codes — related npm work)

Signed-off-by: orchestrator