Close Cut 7's npm question: nothing publishes, nothing unpublishes

The operator's ruling carries a Body fact the maps had not recorded: npmjs
is unreachable from this network, so no GameCult package can be published
there. Cut 7 needed no publish. The QUIC map's Q5 assumed one; that is
raised there separately.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>

notes/eureka-pipeline-state-cut.md

@@ -1826,6 +1826,11 @@ states the new invariant, the CultNet surface, the Qdrant dependency, and that
 - **Operator:** confirm `npm` publication of `@gamecult/huginn` is not expected
   to continue. The package was never published to a registry consumer this map
   can find, but unpublishing is the operator's call.
+  **Ruled 2026-09-16:** not publishing, nothing to unpublish. Body fact from
+  the operator: "we don't even have npm access and cannot get it because our
+  entire subnet is blocked." No GameCult package can be published to npmjs
+  from this network, so any plan that assumes a registry publish is a plan
+  that assumes a token nobody can mint. Raised against the QUIC map's Q5.
 
 **Subtraction ledger:** −307 lines, −16 files, −1 npm package, −1 CLI
 entrypoint, −1 sibling `file:` dependency. +about 30 lines of workspace