docs: add entity resolution guide composing Worlds primitives

[EthanThatOneKid]

Summary

Worlds does not ship a write-path entity resolver — identity is IRI-based,
memory is curated, and facts enter deliberately. That is a design decision,
not a missing capability: RDF is the substrate, and Worlds' primitives (items,
facts, the append-only ledger, hybrid search, SPARQL, provenance, SHACL)
compose into anything, including entity resolution.

This PR adds the official Entity resolution with Worlds guide
(guides/entity-resolution.mdx), registered under Guides in docs.json:

• The primitives — a table mapping each resolution need (identity, aliases,
  co-occurrence, recency, merges) to the Worlds primitive that provides it.
• Pattern A: retrieval-time resolution (native) — aliases as labels on one
  IRI resolved by hybrid search, co-occurrence disambiguation via SPARQL, and
  ontology grounding with discoverSchema.
• Pattern B: write-time resolution (conservative three-signal) — the full
  pipeline built on primitives: extraction with provenance, candidate search,
  a 0.5/0.3/0.2 weighted score (name similarity, co-occurrence overlap,
  recency) with the two SPARQL queries and a TS resolver sketch, a 0.6
  conservative decision written as wazoo:resolvesTo ledger patches, and an
  audit query replaying every decision.
• What you build vs what Worlds gives you, Check for success, Use cases,
  and Next steps, matching the company-brain guide format.

Notes

• The wazoo:source / wazoo:assertedAt / wazoo:resolvesTo predicates are
  explicitly flagged as example vocabulary from the guide's example ontology —
  the guide tells readers to define them and validate with SHACL.
• No third-party product names are mentioned.

Validation

• prettier --check passes on both changed files.
• All internal links resolve (worlds/index, worlds/search, worlds/query,
  worlds/update, integrations/ai-sdk, console/tokens,
  guides/company-brain).

mintlify validate is network-dependent and runs in CI.