@sema-agent/core 7.17.0 → 7.17.2

package/test/export-surface.snapshot.json

@@ -1,7 +1,7 @@
 {
   "_comment": "design/87 L3 — frozen public export surface of src/index.ts (name -> kind). DO NOT edit by hand to silence a red test. A removed/changed entry = a SemVer-BREAKING change; bump MAJOR and update this fixture in the SAME commit (design/87 §4.2 / §5.2). Regenerate via REGEN in test/export-surface.test.ts.",
   "_tierComment": "#435 v1 — machine-readable layering of the public surface: stable = demonstrated by README.md / src/examples; internal = an `Internal`-marked name or a runner/engine deep-subtree declaration (the model seam src/engine/llm is excluded — it is the BYOM contract, not an engine internal); advanced = a supported export the front door does not walk you through. THIS IS AN INITIAL HEURISTIC, derived mechanically and expected to be refined ticket by ticket: no human reviewed these 1700+ entries one by one, and nothing here claims otherwise. Known bias: a short or English-word export name (ok, err, Result, Usage) can match ordinary prose in README.md and land `stable` on a coincidence. Every export MUST carry a tier — a new export with no row fails the gate in export-surface.test.ts.",
-  "count": 2333,
+  "count": 2335,
   "exports": {
     "A2ATaskState": "type",
     "A2ATaskStateReversal": "type",
@@ -2080,6 +2080,8 @@
     "peerSessionBoxHandle": "function",
     "permissionRuleSyncContract": "function",
     "pgQuery": "function",
+    "physicalPathOf": "function",
+    "physicalPathOfExisting": "function",
     "planParseRepairs": "function",
     "precheckEditedRuleText": "function",
     "predictMountedToolNames": "function",
@@ -4415,6 +4417,8 @@
     "peerSessionBoxHandle": "advanced",
     "permissionRuleSyncContract": "advanced",
     "pgQuery": "advanced",
+    "physicalPathOf": "advanced",
+    "physicalPathOfExisting": "advanced",
     "planParseRepairs": "advanced",
     "precheckEditedRuleText": "advanced",
     "predictMountedToolNames": "advanced",