[Epic] Provide complete and correct answers about the user's Azure estate

## Problem statement

Resource questions fail when queries, filters, scope, pagination, or terminology are incorrect. Partial or fabricated estate answers undermine trust in every downstream workflow.

## Outcome

Users can discover, count, filter, and inspect their actual Azure resources with complete, correctly scoped answers.

## Goals

- Use authoritative Azure resource tools and current schemas
- Resolve tenant, subscription, resource group, name, and ID correctly
- Handle pagination, filtering, aggregation, and empty results
- Distinguish evidence from inference

## Non-goals

- Answering resource-state questions without live evidence
- Replacing Azure Resource Graph

## Success criteria

- [ ] Representative resource queries return complete and correct results
- [ ] Scope and filtering errors are detected and explained
- [ ] Evaluations cover multi-subscription and ambiguous resource names

## Dependencies

Azure Resource Graph, resource lookup, authentication, and query evaluation datasets.

Start by reviewing the stated dependencies: Azure Resource Graph, resource lookup, authentication, and query evaluation datasets. Define the scope around discovering, counting, filtering, and inspecting live Azure resources across subscriptions. Done means representative queries are complete and correctly scoped, errors are explained, and evaluations cover multi-subscription and ambiguous resource names.

Written by the indexing model from the issue text.