fix: mark resolved SDK doc gaps already covered in sdk-overview.md - #30
Closed
9Olive wants to merge 1 commit into
Closed
fix: mark resolved SDK doc gaps already covered in sdk-overview.md#309Olive wants to merge 1 commit into
9Olive wants to merge 1 commit into
Conversation
Contributor
Author
|
Closing as a duplicate of #69, which flips the same doc-006..009 gap entries to resolved. #69 uses an accurate 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). |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
context/_gaps.yaml still listed doc-006 through doc-009 (batch_prediction_result inspection methods, batch_prediction_job.progress(), training_job.cancel()/batch_prediction_job.cancel(), JobStatusReport.event_log) as open documentation gaps, but context/platform/sdk-overview.md already documents all four (summary(), predictions_urls(), embeddings_df(), export(), progress(), cancel(), event_log with stage_name/last_updated_at/detail), synced from the same 2026-03-31 kumo-sdk pass that resolved doc-001 through doc-004 and doc-010. This flips those four entries to status: resolved with resolved: 2026-03-31 so the gap manifest matches the doc it is meant to track; doc-005 (training_table.data_df()/.export()/.update()), doc-011 (BaselineJobResult.metrics()), and doc-012 (prediction_table.anchor_time() readback) were checked against the same doc and confirmed still genuinely undocumented, so they are left open.