REGRESSION: codex doesnt know defs and refs

docs/wf_mcp_end_to_end_runbook.md

@@ -324,6 +324,22 @@ The `wf.std` self-binding is present when the saved graph depends on standard
 library capabilities. This tiny echo graph does not need much from `wf.std`, but
 keeping local system-source bindings explicit is the current general pattern.
 
+System-source bindings can look redundant:
+
+```json
+{
+  "wf.std": "wf.std",
+  "wf.mcp": "wf.mcp"
+}
+```
+
+They mean "bind the artifact's logical local source to the concrete local source
+with the same id." They are not external account bindings. Keep them explicit
+for now when validation reports `binding_missing` for `wf.std` or `wf.mcp`.
+Later the platform may make system-source self-bindings implicit, but current
+artifacts and deployments use one uniform binding mechanism for both local and
+external sources.
+
 ## 8. Validate Before Running
 
 ```yaml

docs/wf_mcp_troubleshooting.md

@@ -150,8 +150,14 @@ deployment bindings: {}
 Fix:
 
 - add a binding such as `"demo": "demo.personal"`
+- if the missing logical source is local, add a self-binding such as
+  `"wf.std": "wf.std"` or `"wf.mcp": "wf.mcp"`
 - then validate again
 
+System-source self-bindings look redundant, but they mean "use the local
+standard source with the same id." Current deployments bind local and external
+sources through the same field.
+
 Use:
 
 ```text

docs/workflow_artifacts.md

@@ -396,6 +396,21 @@ artifact reference: context7.query-docs
 runtime binding:    context7 -> context7.default
 ```
 
+Local system sources use the same binding mechanism. For example:
+
+```text
+artifact reference: wf.std.replace
+runtime binding:    wf.std -> wf.std
+
+artifact reference: wf.mcp.call_tool
+runtime binding:    wf.mcp -> wf.mcp
+```
+
+These self-bindings are not external account choices. They keep dependency
+resolution uniform across local system sources and upstream connection sources.
+They may become implicit later, but today deployments should include them when
+validation reports `binding_missing` for `wf.std` or `wf.mcp`.
+
 or:
 
 ```text