feat(systems): bootstrap mints directly — the standard vocabulary replaces operator approval (#2798)

Operator directive: creating Systems is the agent's call, not an approval
flow — "propose to the operator, create each confirmed one" made the
operator a permission gate. The bootstrap ask now says create_system 3-6
directly, in-session, and the consistency that approval was covering moves
to a standard cross-project vocabulary (CI & Release, Auth & Access, Data
Model & Storage, API Surface, UI & Design, Import & Export, Background
Jobs, Observability): use the standard name verbatim where the area fits,
mint freely beyond it, the duplicate gate guards sprawl. create_system and
enter_project docstrings carry the same contract.

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

tests/test_mcp_tool_projects.py

@@ -285,7 +285,7 @@ def _enter_project_stubs(p):
 async def test_enter_project_carries_the_bootstrap_ask_when_it_fires():
     """The arrival-moment half of #2683: a mature zero-Systems project greets
     the session with the concrete bootstrap ask, before it is deep in a task —
-    the moment "propose a starter vocabulary" is cheapest."""
+    the moment minting a starter vocabulary is cheapest."""
     import contextlib
 
     ask = "This project has 282 records and NO Systems modelled — ..."