fix: target the network, not an environment, in synced icp commands

Author: marc0olo

docs/guides/frontends/static-site/verifying-contents.md

@@ -65,7 +65,7 @@ that produce the served directory).
    an *update* call, so the reply is consensus-backed and trustworthy:
 
    ```sh
-   icp canister call <canister-id> state_hash '()' -e ic
+   icp canister call <canister-id> state_hash '()' -n ic
    # (blob "\81\50\a6\5e…")
    ```
 

scripts/sync-static-site.mjs

@@ -86,13 +86,16 @@ const PROSE_RULES = [
 // `dfx` is banned in this repo (AGENTS.md "Never"), and a command reaches a
 // reader from inside a fence, where the prose rules deliberately do not go. Only
 // this exact shape is rewritten, checked against `icp canister call` in icp-cli
-// v1.5.0: <CANISTER> accepts a principal, `-e` selects the network, and the
-// argument has to be written out, because `icp canister call` with no argument
-// opens an interactive prompt instead of sending an empty one. dfx infers `()`;
-// icp does not, so the rewrite adds it. Any other `dfx` occurrence fails the
-// sync rather than being guessed at.
+// v1.5.0: <CANISTER> accepts a principal, and the argument has to be written
+// out, because `icp canister call` with no argument opens an interactive prompt
+// instead of sending an empty one. dfx infers `()`; icp does not, so the rewrite
+// adds it. `--network ic` becomes `-n ic`, which names a network the way dfx's
+// flag does. The environment flag is not the translation: `-e` resolves a
+// canister name out of a local project, and these pages target a canister by
+// principal, from wherever the reader happens to be. Any other `dfx` occurrence
+// fails the sync rather than being guessed at.
 const DFX_CALL = /^(\s*)dfx canister call (\S+) (\S+) --network ic[ \t]*$/gm;
-const rewriteDfx = (text) => text.replace(DFX_CALL, "$1icp canister call $2 $3 '()' -e ic");
+const rewriteDfx = (text) => text.replace(DFX_CALL, "$1icp canister call $2 $3 '()' -n ic");
 
 // Prose means prose: not a fenced block, not the frontmatter, and within a line,
 // not an inline code span and not a link destination. A rule that reached into