- Add project_phases section: schema, purpose, why it exists
- Document the tasks.project_id backfill mechanism (Autotask Tasks API
omits projectID; resolved post-sync via phase_id join)
- Add query for tasks whose parent project is archived (project_id NULL
but resolvable via project_phases)
- Update domain table to include project_phases (~2.7K rows)
- Add Auvik Network Management section (§4): auvik_tenants and
auvik_tenant_mappings schema, sample data, join patterns, note that
device inventory is fetched live from API not stored in DB
- Add Auvik hostname naming convention note (ynghynswp27 pattern)
- Expand projects section with full column list and relationship to tickets
- Expand tasks section with clear tickets vs projects vs tasks distinction,
real-world examples (Switch [Config/Build/Deploy] task naming), and
query patterns for project tasks vs ticket sub-tasks
- Add project/task/Auvik join pattern examples to §13
- Update §14 Important Notes: Auvik cross-platform link, tickets/projects/tasks
guidance for query intent, updated row counts (March 2026)
- Renumber sections 5-12 → 6-13 to accommodate new Auvik section
- Update domain table to include Auvik row
- AUTOTASK_API_GUIDE.md — auth, query patterns, entity examples, gotchas
- PULSE_DATABASE_SKILL.md — full DB schema reference for all data domains
- DATTO_RMM_OPENCLAW_SKILL.md — read-only OpenClaw API for devices/sites/alerts
