feat: add JASP OSF storage parity#76
Conversation
Commit notes: Mark track 18 in progress before implementing the JASP OSF storage parity contract.
Commit notes: Implement JASP OSF parity for provider-supplied MD5 metadata across the API client, CLI JSON, and MCP structured output. Add offline fixtures, dated source comparison, feature matrix updates, and explicit desktop-scope rationale. Full repository gates passed.
There was a problem hiding this comment.
Code Review
This pull request completes the JASP OSF integration parity track by implementing support for provider-supplied MD5 checksums. The changes introduce parsing for attributes.extra.hashes.md5 in the OSF API client and expose this metadata in both the CLI JSON output and the MCP server's structured file listings. Comprehensive offline tests, fixtures, and documentation (including the feature matrix and usage guides) have been updated to reflect these additions. There are no review comments to address.
Important
The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
Summary
attributes.extra.hashes.md5in API, CLI JSON, and MCP structured outputValidation
go test ./...go test -race ./...go vet ./...golangci-lint rungo run ./tools/checkstubsgo run ./tools/checkreviewsgo run ./tools/checkfeaturematrixgo run ./tools/checkregistriesgo run ./tools/checkreleasecontractgovulncheck ./...git diff --checkCloses #18