Keep validated candidates recoverable until exact mappings exist - #27
Merged
Merged
Conversation
|
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.
Missing field mappings are an operator-owned dependency, not evidence failure. Return a non-persistent deferred result and preserve the validated candidate, while all provenance, dual-extraction, field type, amount, and quarantine gates remain unchanged. Filter complete enabled mappings before the scheduler LIMIT so older unmapped candidates cannot starve healthy work; acknowledge deferred queue messages and rediscover them after mappings are repaired. Historical quarantined candidates are never reopened. Validation: 16 Publisher SQLite tests, typecheck, lint, diff checks, and Wrangler deploy dry-run all passed. Regressions cover partial/disabled/missing definitions, recovery and idempotency, queue/DLQ behavior, malformed fact arrays, and unsafe candidates. No D1 migration or catalog fact changes.