Repository navigation
Conversation
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.
V2 startup previously mixed the new four-table schema with the retired PolicyHost/Resource/Intent migration contract. Ordinary uploads could query incompatible Guard tables, and default legacy management routes still required historical tables.
This change delivers fixed, manually executed four-table SQL (initialization, preflight, offline upgrade, archive review and verification), makes startup read-only, removes owned legacy worker hooks, and rejects explicitly enabled retired route settings with their variable names. Disabled Checkout does not require or inspect Guard. The companion Server and Hub changes move C write barriers to path-keyed Guard and keep root routing on current V2 adapters. The planned per-library Checkout setting is not implemented and cf_library_storage is unchanged.
Companion PRs / source set:
Validation: 37 configuration, 5 read-only startup, 4 SQL package, 3 build policy and 5 SQL contract tests passed; bootstrap configuration checks passed. Nine isolated MariaDB scenarios passed, including initialization, old-layout migration, refusal cases and SQL extracted from the production C Guard readers. Companion C barrier/final-transaction tests cover 12 cases; Hub covers 28 tests and 7 subtests.
Deployment prerequisites: existing DEV history/backup tables must be archived with reviewed manual SQL before the strict startup check passes. Explicit legacy route settings require operator review; this PR does not mutate environment variables. Old Resource/Intent APIs are retired, not recreated by migration. Full Linux build, image integration and DEV deployment have not been performed. No live database changes or deployment are included in this delivery.