Composite: resolve a TELA dURL (e.g. "vault.tela") to its on-chain SCID(s) by discovering TELA apps directly from chain — no external Gnomon indexer required. TELA apps advertise a human-readable dURL; this finds the contract(s) that claim it.
When to call: when a user asks "what's the SCID for <something>.tela", "find the TELA app called X", or gives a dURL and wants the contract. IMPORTANT routing: for a registered DERO NAME like "quickbrownfox" (no dot, not a dURL), use dero_name_to_address instead — that is a name to address lookup, not a TELA app. This tool is only for TELA dURLs (they contain a dot / .tela / a dero:// prefix).
Input Requirements:
- `durl` is REQUIRED. A TELA dURL such as "vault.tela", "feed.tela", or "dero://cipherchess.tela". Case- and prefix-insensitive.
Output: `{ query, normalized, found, match_count, scid, primary, collision, other_candidates[], narrative, related_docs }` on a hit; `{ query, normalized, found:false, match_count:0, hint }` on a miss. dURLs are NOT unique — when multiple contracts claim one, the NEWEST is returned as `scid`/`primary` and the rest are disclosed in `other_candidates` with `collision:true`. The first call triggers a ~10s one-time discovery scan of the newest chain contracts (cached afterward). Feed the returned scid to tela_inspect to view the app.