/diagnose-missing-node

Diagnose a missing mesh node, unregistered NodeType, Area not found, or failed compilation by locating the first broken step between source, publication, installation, compilation and rendering. Use for a missing feature or a PR that appears shipped but is absent on an instance.

• Instructions: # Diagnose a missing mesh feature Identify the first broken boundary before changing anything. An HTTP 200, a green PR, a successful compile and a working view are four different observations. Report the instance, exact path, checked revision and decisive evidence; mark anything not measured as unknown. ## Establish the target and documentation Always search the `memex` MCP at `https://memex.meshweaver.cloud/mcp` for the feature and relevant skills, then read the matching nodes. Do not filter general documentation to `nodeType:Documentation`: many official docs are Markdown nodes. Cloud is the feature reference; `memex.systemorph.com` is a separate company instance. Confirm which server every probe addresses. Keep the requested URL, error text, whether the browser is anonymous, and the expected source PR or commit. Do not equate the MCP caller's access with the browser user's access. ## Follow the evidence in order | Boundary | Probe | What the result establishes | |---|---|---| | Source | Read the node file on the PR head and on the target branch. A directory alone is not a node: it needs `index.json`, `index.md`, or its supported sibling node file. | The definition exists in that revision. Local files do not establish publication. | | Merge | GitHub REST `GET repos/{owner}/{repo}/pulls/{number}`: inspect `merged`, `merged_at` and `head.sha`. Once merged, record `merge_commit_sha` as the revision placed on the base branch and use it to locate delivery jobs. | An open PR is unshipped source: its `merge_commit_sha` may be speculative. After merge/squash, the delivered commit can differ from the PR head. | | Publication | Read the publishing workflow's jobs for the actual merged revision, its publication identity and source-commit marker. Check its delivery/adoption result. | A green PR or image build does not prove that publish/seal/delivery ran. Skipped or absent required work is not success. | | Installation | Query the exact node and owning package on the ta…
• Auto mount: yes
• Launches sub thread: no