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_systems.py

@@ -129,7 +129,11 @@ async def test_untagged_hint_escalates_in_a_mature_zero_systems_project():
     assert "282 records" in hint
     assert "Fix scrape retry backoff" in hint      # the project's own evidence
     assert "3-6" in hint and "create_system" in hint
-    assert "propose" in hint
+    # NOT an approval flow (#2798): the agent mints directly, and the
+    # standard cross-project names carry the consistency instead.
+    assert "without asking permission" in hint
+    assert "propose" not in hint and "confirmed" not in hint
+    assert "CI & Release" in hint and "Auth & Access" in hint
     # The generic wording is REPLACED, not appended — two questions is noise.
     assert "no Systems yet" not in hint