microsoft_graph_v4

No catalog snapshot found for this source yet. It's in the KNOWN_SOURCES list but no one has run the catalog export yet.

To claim this source

File a lock issue so the other laptop knows you're working on it:

gh issue create \
  --label source,claiming,laptop-B \
  --title "[claim] microsoft_graph_v4 on laptop-B" \
  --body "Source: microsoft_graph_v4\nLaptop: B\nStarted: $(date -u +%Y-%m-%dT%H:%M:%SZ)\nExpected end: loop"

Then sweep the source

# 1. Refresh catalog (needs the coral CLI on PATH and source credentials)
python3 scripts/catalog_export.py --source microsoft_graph_v4 --out reports/microsoft_graph_v4/catalog.json

# 2. Probe every table in parallel (4 workers, 2 trials each)
python3 scripts/probe_batch.py --source microsoft_graph_v4 --workers 4 --runs 2

# 3. Re-classify failures (coral_bug vs upstream vs auth)
python3 scripts/analyze_failures.py --source microsoft_graph_v4

# 4. Build the site (Next.js picks up the new JSON automatically)
cd app && npm run build

# 5. Commit + PR
git checkout -b probe/microsoft_graph_v4-sweep
git add reports/microsoft_graph_v4/
git commit -m "probe(microsoft_graph_v4): full sweep — $(jq '.tables | length' reports/microsoft_graph_v4/catalog.json) tables + $(jq '.functions | length' reports/microsoft_graph_v4/catalog.json) functions"
gh pr create --fill --label probe,microsoft_graph_v4

See CONTRIBUTING.md for the two-laptop rule and SKILL.md guidance in skills/coral-test/.