docs: align pipeline and dataset guidance - #34
Merged
Conversation
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
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.
Summary
This is the smallest appropriate change because executable code and configs already implement the target pipeline; the remaining drift was in repository documentation.
Validation
docs/architecture-status.mdand retain existing contract coverageDetailed checks:
task.mdpackages and zerotask.tomlfilesSpend and external systems
No spendful validation. This PR uses the already-preserved public canary evidence and no GPU, provider, Daytona, or paid HF Job was launched. A paid HF Jobs run for the current Docker/OpenCode/two-GPU topology remains an explicit manual validation item.