feat(legal): scheduled multi-document legal updates - #87
Merged
Merged
Conversation
New legal_document_versions table holds published and scheduled versions per document; the current version is the highest one whose effective_at has passed, so a future-dated insert activates the re-accept gate on its own — several documents at once when they share an effective_at. legal_documents stays as the kind registry. API computes effective versions at read time (no cron); response shape unchanged, so the CropWatch accept-terms page needs no changes. Update-Legal.sql is now the scheduling template (auto version numbering, review/cancel queries). Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
CropWatchDevelopment
temporarily deployed
to
Production
July 30, 2026 15:05 — with 
GitHub Actions
Inactive
GitHub Actions
Inactive
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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.
New legal_document_versions table holds published and scheduled versions per document; the current version is the highest one whose effective_at has passed, so a future-dated insert activates the re-accept gate on its own — several documents at once when they share an effective_at. legal_documents stays as the kind registry. API computes effective versions at read time (no cron); response shape unchanged, so the CropWatch accept-terms page needs no changes. Update-Legal.sql is now the scheduling template (auto version numbering, review/cancel queries).