Repository navigation
feat: keep source reconciliation inputs trustworthy - #238
Conversation
yordis
commented
Oct 23, 2026
- Source reconciliation needs stable input identity before native mappings or durable runs can be trusted.
- Supplied bytes must remain inert, bounded and traceable without implying native validity or external completeness.
Signed-off-by: Yordis Prieto <yordis.prieto@gmail.com>
PR SummaryLow Risk Overview Documentation now treats this profile as implemented (new Boundary and vector tests lock digest framing, partition/locator rules, duplicate-key rejection, JSON-depth limits, and error hygiene. Adds Reviewed by Cursor Bugbot for commit 44a73f8. Bugbot is set up for automated code reviews on this repo. Configure here. |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info
WalkthroughThe change adds a Rust ChangesSource Bundle Intake
Priority: ➖ Normal Estimated code review effort: 4 (Complex) | ~45 minutes Change: Feature Possibly related PRs
Merge Risk: ⚪ Minimal · up to
|
Signed-off-by: Yordis Prieto <yordis.prieto@gmail.com>