test(semantics): ratchet inventory after deduplication

Signed-off-by: huangruiteng <14976749+huangruiteng@users.noreply.github.com>

Author: huangruiteng

examples/semantic-vocabulary-drift-smoke.py

@@ -27,10 +27,10 @@
     INVENTORY_SCHEMA_VERSION,
     SourceFile,
     build_inventory,
-    render_inventory,
     collect_string_constants,
     load_sources,
     python_facts,
+    render_inventory as render_inventory,
     string_constant_definitions,
     typescript_facts,
 )
@@ -232,16 +232,16 @@
 TWIN_ROOT_ANCHOR = "loopx/control_plane"
 TWIN_BUDGET_ANCHOR = 43
 BUDGET_ANCHOR = {
-    "same_runtime_forks": 18,
-    "same_runtime_fork_definitions": 41,
+    "same_runtime_forks": 17,
+    "same_runtime_fork_definitions": 39,
     "conflicting_values": 16,
     "conflicting_definitions": 55,
     "schema_version_same_runtime_forks": 7,
     "multi_value_twins": 13,
     "multi_value_forks": 2,
     "multi_value_forks_semantic": 1,
     "multi_value_fork_definitions": 6,
-    "same_runtime_forks_semantic": 11,
+    "same_runtime_forks_semantic": 10,
     "conflicting_values_semantic": 0,
 }
 # Budgets for the legacy should-run decision fields, anchored the same way so a

loopx/semantics/vocabulary_v0.json

@@ -1124,15 +1124,15 @@
   },
   "inventory_ratchets": {
     "meaning": "Counts read from the generated inventory. A same-runtime fork is one constant name with one value defined in two or more modules of the same runtime; a conflicting value is one name with different values. Both the number of affected names and the number of definitions are budgets, so a third spelling of an already-conflicting name is still a regression.",
-    "same_runtime_forks": 18,
-    "same_runtime_fork_definitions": 41,
+    "same_runtime_forks": 17,
+    "same_runtime_fork_definitions": 39,
     "conflicting_values": 16,
     "conflicting_definitions": 55,
     "schema_version_same_runtime_forks": 7,
     "multi_value_twins": 13,
     "multi_value_forks": 2,
     "multi_value_fork_definitions": 6,
-    "same_runtime_forks_semantic": 11,
+    "same_runtime_forks_semantic": 10,
     "conflicting_values_semantic": 0,
     "multi_value_meaning": "Enums, named closed sets, Literal aliases, and TypeScript as-const arrays are vocabulary exactly as a NAME = \"value\" constant is, so they get the same collision rule. One name defined in two modules with identical values is a twin; with different values it is a fork. The semantic multi-value-fork budget excludes only names declared in scope_declarations.",
     "multi_value_forks_note": "The 4 counted forks include SOURCE_SURFACES, whose four definitions are four CLI commands each listing its own data sources; that is bounded-context reuse of one name, not drift. It stays in the budget until M0.5 adds a scope field (RFC Section 5) and must not be removed by renaming.",