Repository navigation
Require current telemetry receipts and explicit Store migration - #4315
Merged
Merged
Conversation
…ion/final-source-protected-core-20261008
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.
Workspace telemetry returns one bounded JSON receipt for local and remote publication. The adapter rejects obsolete status-only responses and preserves ambiguous pending intent. Normal Store initialization and restore require schema14; the preserved schema13 transition requires explicit
migrate13orimport13. The dashboard consumes the current scoped response-aware shape.The coherent source candidate uses version0.100.0 and prospective journal
utel-rel-18. Published versions, historical SQL/digests and installed pending state are preserved. The change also integrates telemetry inventory/batch validation, board outcome corrections and SVG source guidance from the recovered source branch with protected main. Existing Host0.5.0 publication facts are reconciled against their release evidence.The mutation runner stops only after an explicit failed assertion; infrastructure failures remain inconclusive. Full controls, all enumerated subjects/operators, eight workers and the30-minute limit remain. A focused protocol preflight gates the hosted sweep. Harness fixtures retain current migration/framing contracts and locked dependency restores.
Validation: all14 historical SQL literals remain exact. The preceding head passed the hosted engine, standalone telemetry qualification, framing proof and mutation sweep. Those results do not transfer to this head: its full CI suite must pass before merge. Package publication, installed migration and native runtime qualification remain pending.
architecture-map: unaffected