docs: define domain-intelligence query architecture

[Teakowa]

Closes #323

Architecture

• Define domainIntelligence as a Wright-owned composition query, not a new semantic/knowledge store.
• Keep canonical Workshop facts in workshop-rs and source-language context in the owning source implementation/provider.
• Keep the public information model simple: fact, warning, and info. Provenance remains explicit, but consumers do not need a detailed runtime/heuristic/community evidence taxonomy.
• Make direct canonical lookup project-independent; only source-position lookup requires project/provider context.
• Start with a Wright-curated built-in guidance corpus. External/community/project-configured guidance sources are deferred until trust, provenance, conflict, and update behavior have an explicit contract.
• Do not add a domain-intelligence project-policy overlay in v1.
• Reuse Wright's common query/tooling surface across CLI, embedding, and transports; keep targetMetadata as broad catalog discovery.
• Treat the operation as additive within the existing v1 embedding/result contract; do not extend LPP or introduce a new major contract pre-emptively.

Design ablation

The design does not require a shadow Workshop catalog, detailed public evidence taxonomy, project-policy overlay, arbitrary external guidance loading, general knowledge database, package/plugin runtime, prompt schema, new LPP method, or new major protocol version. Removing the new query operation itself would fail #323 because the existing targetMetadata surface cannot express bounded subject-specific facts, source-owner resolution, or provenance-bearing guidance.

Verification

Docs-only change. Checked against the current ToolService/targetMetadata implementation and ADR-0015 ownership split. The contract now explicitly avoids making canonical reference queries depend on eager project loading.

Main advanced while this PR was open, so the branch now includes the current main history and records this decision as ADR-0017 after ADR-0016 was allocated to the current-directory/directory-project decision.

Independent design review/ablation is still required before merge; ADR-0017 remains Proposed until that review accepts the decision.