fix: harden authorization and fleet execution integrity - #3985
Draft
ToddHebebrand wants to merge 50 commits into
Draft
fix: harden authorization and fleet execution integrity#3985ToddHebebrand wants to merge 50 commits into
ToddHebebrand wants to merge 50 commits into
Conversation
…facts Corrections and additions after verifying the approved design against the baseline code: - Track A: per-table ownership predicates (XOR vs denormalized partner_id, is_system as the only global flag); two confirmed site-authorization defects in the restore path; the six registration points for the new backup:cross_site_restore permission. - Track B: /devices/options mount-order requirement; enumerated selector migration targets; re-enrollment currently forces online + lastSeenAt; stale DEVICE_STATUSES constant; empty inventory report wipes all rows and NULL-links vulnerability findings. - Track C: /ready already exists as a live evaluator (#2974) — extend it, consolidate /health/ready; compose healthchecks must be switched at rollout. Offline detector is already chunked — reframed as deltas (durable continuation, identity-keyed transitions, throughput). - Track D: current first-match-wins distributor behavior; precedence gains an ownership tier (org-owned over partner-wide); partner fan-out and system-context distribution rules. - Track E: no cleanup command exists today; reuse the intent_outbox pattern. - Cross-cutting: FK KEY SHARE deadlock rule for hot agent-write tables (40P01, #3739/#3911); no epoch-aligned repeatable jobs; integration-suite placement/runIf evidence rule. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
added 12 commits
August 24, 2026 16:59
Deploying breeze with
|
| Latest commit: |
d914d0a
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://559da85c.breeze-9te.pages.dev |
| Branch Preview URL: | https://fix-s0-fleet-integrity-progr.breeze-9te.pages.dev |
Collaborator
Author
|
Reviewer-held findings — recorded for review, not acted on in this draft:
|
added 8 commits
August 25, 2026 15:54
…y-program # Conflicts: # apps/api/src/routes/agents/inventory.ts # apps/api/src/routes/automations.test.ts # apps/api/src/routes/devices/core.ts # apps/api/src/services/automationRuntime.ts
This was referenced Aug 26, 2026
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
1 participant
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 draft hardens the highest-priority authorization and fleet-integrity paths identified by the S0 revalidation.
Authorization and queued recovery
Fleet execution truth
Consolidated verification
Draft / do not merge yet
TestConsentGate_NoHelper_Proceedinside native screen capture; Task 13 focused heartbeat coverage passes.packages/shared/src/validators/quotes.test.ts.streamingUpload.test.tspost-testReadableStream already closedrejection.Follow-up scope
Readiness/offline scaling, device-control lifecycle, and PAM actuation are intentionally planned as follow-up PRs to keep review and rollback boundaries manageable.