Clarify person name lookup routing

[daveosterjr]

Summary

• route specific-person name requests to dealmachine_enrich_name or dm enrich name in the portable Agent Plugin skill
• distinguish filter-defined People Search audiences from person enrichment in the skill, reference, bundled Playbook, CLI bootstrap, and README
• document city place ID discovery and credit-safe name estimates
• add regression assertions to the agent command tests and plugin package validator

Root cause

The standalone CLI and Agent Plugin package mentioned name enrichment, but did not state that People Search has no person-name filter. That ambiguity could send an agent into filter discovery instead of the dedicated name enrichment workflow. The public README also omitted the supported county and city options from the name command table.

Impact

Agents that install the public skill or load dm agents playbook will select name enrichment directly, resolve city names to place IDs when needed, and estimate broad matches before retrieving paid records.

Validation

• npm test (plugin validation and 47 tests)
• npm run build
• npm pack --dry-run --json
• verified the built Playbook and CLI agent guide contain the new routing guidance