[Exeloo]

What does this PR do?

No linked issue. It's a follow-up found while reviewing #281.

examples/breakout still pinned @nanoforge-dev/config and @nanoforge-dev/cli at ^2.3.0. #281 moves the editor's catalog to config ^3.0.1, and cli 3.0.1 depends on config 3.0.1, so both move to ^3.0.1.

-    "@nanoforge-dev/cli": "^2.3.0",
-    "@nanoforge-dev/config": "^2.3.0",
+    "@nanoforge-dev/cli": "^3.0.1",
+    "@nanoforge-dev/config": "^3.0.1",

Is it compatible? This comes from reading the CLI's changelogs and the config source diff. Nothing was run on v3:

• config 3 only adds an optional workspace network field (default dedicated). Breakout's two nanoforge.config.ts files stay valid.
• cli 3's only breaking change is nf install (No unit tests for ServerPluginHost and ProjectRegistry #263). nf start and nf build don't change.

How do you test this PR?

• Commands run, all exit 0:
  • pnpm turbo build --filter=@nanoforge-dev/editor...
  • pnpm lint
  • npx playwright test e2e/scene.spec.ts in apps/editor, with NANOFORGE_ENGINE/NANOFORGE_CLI: 5 passed.
• Limit: none of this installs these ranges. examples/ is outside the pnpm workspace, and the e2e prep and pnpm example link breakout's node_modules from the engine's example/pong-network, which is still on cli/config 2.3. So the e2e run shows nothing broke, not that v3 works. Running breakout with cli and config 3.0.1 linked in, then Play, is still to do.

Merge danger

Door: two-way (one file, two version ranges).
Blast radius: low. Only people who install breakout outside the repo get the new ranges. The file is not in the editor build or the workspace, so the editor that deploys on merge is unchanged.

Quality gate

Check	Result	Notes
Docs	N/A (no command, flag, config or setup step changes; the READMEs and AGENTS.md name no cli or config version)	docs-writer
Correctness	Pass	1 Minor: the e2e run doesn't install v3 (see the limit above)
Performance	N/A (no runtime source changed)
Accessibility	N/A (no UI changed)
Security	Pass	a version string; the e2e prep copies the file and runs no install
Style	Pass	lint: pass, commitlint: pass

Rounds run: 1. A single reviewer covered correctness, security and style.

Follow-up issues

None filed. Candidates, waiting on a decision:

• the engine's example/pong-network and the server-core pong-network fixture still pin cli ^2.3.0;
• the e2e breakout copy doesn't link NANOFORGE_CLI;
• Dockerfile installs @nanoforge-dev/cli@2.3.1.