Repository navigation
Remove obsolete repository coupling and stabilize CI installs - #78
Merged
Merged
Conversation
Pitot coding-agent E2EThese results come from this repository's CI at the commit shown below; the README links to the latest
Runtime capabilities
Source commit: |
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.
Change contract
When: Contributors run repository checks or read Pitot's CI reports and SDK documentation.
Before: Historical import metadata and layout fallbacks remained, tests could select an adjacent checkout, and reports attributed verification to a retired source. DeepSeek's top-level version pin also allowed new transitive releases to change its installation between capture and verification.
After: Tests and reports describe this repository. The unused import snapshot is removed, SDK links resolve correctly, and DeepSeek's CI installation uses a checked-in dependency graph. Rejected captures name the differing fields; Qwen replay failures include bounded shell-result diagnostics.
Boundaries preserved
Evidence
8dad60572851; current report has 33 passing agent cells and 3 passing runtime cellsFailure and recovery
DeepSeek's dependency ranges admitted a transitive package published between a successful capture and later verification. A fresh diagnostic capture differed only in the complete installation-tree digest. The lock prevents that dependency resolution from changing on each install; the full-tree check still detects other differences. Revert source and its accompanying capture record together if needed.
Remaining limits
The original failed installation record and Qwen shell status were not retained, so their exact contents cannot be reconstructed. Qwen passed a later unchanged-source diagnostic run; the added diagnostics do not claim to fix an identified Qwen runtime defect. Fresh native capture and final PR checks passed. Two macOS jobs initially received no hosted runner; a same-commit failed-job retry passed. Git history and external repository settings are outside this cleanup; the broader README and reference-documentation work follows separately.