Integrate Loom reliability program - #14
Merged
Merged
Conversation
matthewpeterkort
changed the title
matthewpeterkort
force-pushed
the
reliability/director-v2
branch
2 times, most recently
from
August 6, 2026 23:06
f9217ca to
9346e7a
Compare
matthewpeterkort
changed the base branch from
reliability/explorer
to
reliability/federation
August 6, 2026 23:07
matthewpeterkort
force-pushed
the
reliability/director-v2
branch
from
August 7, 2026 16:16
9346e7a to
41dfa22
Compare
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\n\nIntegrates the complete reliability program: versioned publication, immutable snapshots, atomic project releases, exact federation, snapshot ETL, Explorer UX, durable contract promotion, release-bound source selection, recovery and cleanup hardening, and operator-facing diagnostics.\n\n## Stack\n\nTop integration tier; targets reliability/explorer. This conventional head supersedes the stale conflict metadata on PR #12 while preserving the same verified director tree.\n\n## Validation\n\nVerified with GraphQL generation/checks, Explorer contract tests, full Go tests, ETL integration tests, race tests, go vet, and graphify update.\n\n## Operational follow-up\n\nRun the live ArangoDB/ClickHouse Gate 2 scenarios after the stack lands.