fix(kiloclaw): derive upgrade banner rollout subject#3603
Open
evanjacobson wants to merge 8 commits into
Open
Conversation
Contributor
Code Review SummaryStatus: No Issues Found | Recommendation: Merge Executive SummaryThe incremental commit ( Incremental Changes (commit 3c6098d)Pure rename of
The rename is complete and consistent. The remaining Previously Flagged Issues — Still Resolved
Files Reviewed (13 files total)
Reviewed by claude-sonnet-4.6 · 316,050 tokens Review guidance: REVIEW.md from base branch |
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
The upgrade banner could evaluate rollout eligibility with a different subject than the actual KiloClaw restart path, so users could see stale or incorrect upgrade availability. This change makes the banner resolve the rollout subject server-side from the authoritative instance row, matching the same legacy-vs-instance-keyed sandbox behavior used by
restartMachine({ imageTag: 'latest' }).It also keeps anonymous/latest-version lookups separate from instance-scoped rollout lookups, so callers cannot spoof Early Access state while existing non-instance consumers still get the public
:latestresult.Details
ki_instance-keyed rows.rolloutSubjectso the internal API matches the new semantics.Verification
No manual testing performed; this is a backend rollout-selection and internal API-contract change with no visual/manual flow changes.
Visual Changes
N/A
Reviewer Notes
The important review path is consistency between the banner endpoint and
restartMachine({ imageTag: 'latest' }): both should bucket byuserIdfor legacy sandbox IDs and by instance UUID forki_sandbox IDs. The HTTP query params remain backward-compatible; only the internal selector option was renamed to reflect that it now receives a rollout subject rather than always receiving an instance ID.