fix(gaps): mark doc-006/007/008/009 resolved in _gaps.yaml

[9Olive]

context/_gaps.yaml lists doc-006 (batch_prediction_result inspection methods), doc-007 (batch_prediction_job.progress()), doc-008 (.cancel()), and doc-009 (JobStatusReport.event_log) as status: open.

All four are already documented in context/platform/sdk-overview.md:

• doc-006: pred_result.summary(), .predictions_urls(), .embeddings_df(), .export(output_config) — lines 518-522
• doc-007: pred_job.progress() — line 514
• doc-008: training_job.cancel() (line 404) and pred_job.cancel() (line 515)
• doc-009: training_job.status() mentions event_log (line 402) and a full usage example iterates status.event_log (line 450)

This gap manifest is read by meta/skills/sync-from-source.md and meta/skills/verify-content.md during sync/verify passes, so a stale open status on already-resolved gaps risks a future sync re-flagging real content as missing, or masking genuinely new gaps in the noise of already-closed ones.

Flips all four entries to status: resolved with resolved: "2026-07-01", matching the format already used for doc-001/002/003/004/010. No other content changed — 1 file, 4 additions, 4 deletions.

Leaves doc-005, doc-011, doc-012, plat-001/002/003 untouched (still genuinely open, or already covered by other pending PRs #61/#63/#68).

[9Olive]

Verified: doc-006..009 are all genuinely documented now (sdk-overview.md:514-522,637-639; train-model.md:250), so resolving them is correct. Recommend merge. Duplicates #30 on the same four lines - prefer this one; its resolved: 2026-07-01 date is accurate vs #30's back-dated 2026-03-31. #30 is being closed.

---

Automated internal-consistency review (cross-checked against the repo's own authoritative docs; a few SDK-surface claims spot-checked against installed kumoai 2.22.0).

[Manushpm8]

Leaving open for maintainer triage. Flips doc-006/007/008/009 to resolved in the internal _gaps.yaml. The four features do exist, but 'resolved' should mean the docs were actually updated — worth confirming the corresponding docs cover them before flipping. @9Olive's call.

[leena-kang]

Changes needed before merge

Accuracy fix — required: Keep doc-006 through doc-009 open, or update every file listed under each gap’s affects field before marking them resolved.

The SDK exposes these capabilities:

/home/leena/code/kumo/kumo-sdk/kumoai/trainer/job.py
371: batch result summary
401: export
445: predictions_urls
478,491: embeddings_urls / embeddings_df
767: training cancel
984,995: batch progress / cancel
930,1134: event_log consumption

The target documentation remains incomplete:

context/platform/sdk-overview.md:510
  Omits embeddings_urls.

skills/train-model.md:286
  Batch workflow omits result inspection, progress, and cancellation.

skills/debug-prediction.md
  Contains no event_log debugging workflow.

Therefore, the changed resolved statuses currently overstate documentation coverage. The exact progress/event-log schemas imported from kumoapi cannot be independently verified from permitted evidence, but that uncertainty does not affect the documented omissions above.

Accurate checks

• The YAML edits are structurally consistent and use the existing resolved-date format.
• No broad SDK test is useful for this manifest-only change. Direct export tests cover only one method and are unnecessary here.

Local checks

git diff --check origin/main...HEAD
PASS

/tmp/kumo-coding-agent-pr-reviews/.venv/bin/python -c "import sys, yaml; [yaml.safe_load(open(p)) for p in sys.argv[1:]]" context/_gaps.yaml
PASS

Targeted rg inspection: sdk-overview.md documents most capabilities, while the omissions listed above remain.

Grammar/spelling: No issues found.