feat(feedback): durably persist feedback labels - #9
Merged
Merged
Conversation
logger.audit() only writes to the daily log file, which on Railway is on the ephemeral filesystem and wiped on every redeploy — so the "was this helpful?" labels would not survive. Add src/feedback-store.js: each feedback record (now enriched with the verdict it rates — is_fraud, warning_level, confidence, fraud_type) is appended as one JSON line to <sessionStorage>/feedback.jsonl, which lives on the existing persistent session volume, so labels accumulate across deploys. If FEEDBACK_WEBHOOK is set, the record is also POSTed there for live review. Path overridable via FEEDBACK_LOG_PATH. Test: offline case writes to a temp path (no webhook) and asserts JSONL lines are appended and parseable. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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.
logger.audit() only writes to the daily log file, which on Railway is on the ephemeral filesystem and wiped on every redeploy — so the "was this helpful?" labels would not survive.
Add src/feedback-store.js: each feedback record (now enriched with the verdict it rates — is_fraud, warning_level, confidence, fraud_type) is appended as one JSON line to /feedback.jsonl, which lives on the existing persistent session volume, so labels accumulate across deploys. If FEEDBACK_WEBHOOK is set, the record is also POSTed there for live review. Path overridable via FEEDBACK_LOG_PATH.
Test: offline case writes to a temp path (no webhook) and asserts JSONL lines are appended and parseable.