Repository navigation
Conversation
Pin the proposed protocol release and add a real HTTP response-framing regression. Document unpublished-tag verification and the coordinated upgrade required for legacy listing and assignment signatures. Signed-off-by: Nirmal Khedkar <nirmalhk7@gmail.com>
Remove the stale statement that the pinned protocol has no storage opt-in field. Keep the existing boundary explicit: this agent does not advertise storage opt-in, and accepts or declines storage work locally. No runtime policy changes. Candidate-workspace race tests, build, vet and constructor regression pass. Standard lint adds no findings against main. Clean tagged-module verification remains blocked on unpublished protocol v0.4.0. Signed-off-by: Nirmal Khedkar <nirmalhk7@gmail.com>
nirmalhk7
marked this pull request as ready for review
November 17, 2026 19:15
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.
This draft prepares Cloudy to consume sohocloud-protocol v0.4.0 from protocol PR #16. The release is still unpublished, so real module checksums and clean tagged-module verification remain unavailable. Keep this PR draft; it is not ready to merge or deploy.
The dependency pin moves from v0.1.0 to v0.4.0.
TestCoordinatorResponseFramingexercises real HTTP throughDialandDialAsOperator: whitespace after jobs/fees remains accepted, while a second JSON value is rejected. Existing operator tests cover verifiable authentication headers and fail-closed decoration. The success-body budget remains zero/unbounded; this migration selects no deployment-wide limit.The agent comment now matches the conformance document: storage opt-in advertisement remains unwired and storage work is still accepted or declined locally. The dependency contains the newer field, so claiming the pinned protocol lacks it was stale. This correction changes no runtime behavior or storage policy.
Verification refreshed on November 16, 2026, using isolated copies of PR head
d3d17029e09462673769f17425d4a4b639233558and current merge tree8858e4c8c4397940c8de6db6ef9a3dbce24ac869, with the comment correction applied to both:d0acd07e56e12c3c95ac98877f040ae3ca79fb00through external Go workspaces, the fullgo test -race ./... -count=1, build, vet, and focused constructor regression pass on both trees. Formatting and patch whitespace pass.go mod download ...@v0.4.0fails withunknown revision v0.4.0; the clean test command fails on missing module checksums. The GitHub tag lookup also finds no v0.4.0 tag. Candidate-workspace results do not satisfy published-release verification.The upgrade is not wire-compatible with v0.1.0. Prior GPU/storage additions changed listing and assignment signing bytes under existing v0 domains, even when new fields are empty. The protocol's old-module fixtures demonstrate this incompatibility. An agreed and tested agent, frontend/relay, and coordinator rollout remains required before deployment; this PR adopts no persisted-signature migration policy.
After maintainers review and merge protocol #16 and publish its immutable v0.4.0 tag, acquire the real module checksums and rerun Cloudy's full checks and quality gate without any workspace override. No replacement dependency, fabricated checksum, tag publication, deployment, or Slack workflow update is included. Contributions follow NTARI's Bug-Build-Test guide, fork/PR and DCO requirements. Hosted CI and independent human review remain separate gates; the author must not merge the PR.