Add decode refactor progress report #1
Conversation
Add comprehensive documentation for confidence scoring approach: - Size-based scaling rationale and formula - Detector-specific strategies (intrinsic vs constant confidence) - Base confidence values for magic (0.95/0.75) and charset-normalizer (0.85) - Examples and interaction with behavior thresholds Add analysis of text validation and confidence threshold: - text_validate_confidence is effectively unused (always 0.0 in main path) - Validation checks textuality, not detection confidence (orthogonal concerns) - Recommend removing confidence threshold, keeping tristate control Fix docstring in is_permissive_charset() to correctly reflect that CP1252 is not permissive (has 5 undefined bytes). 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
Add a progress report document summarizing the changes in the `decode-refactor` branch compared to `master`, highlighting completed work and remaining tasks/issues.
|
👋 Jules, reporting for duty! I'm here to lend a hand with this pull request. When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down. I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job! For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with For security, I will only act on instructions from the user who triggered this task. New to Jules? Learn more at jules.google/docs. |
emcd
force-pushed
the
decode-refactor
branch
from
b7bb52d to
f76b0a0
Compare
1 participant
This commit adds
decode-refactor--progress.md, which serves as a status report for thedecode-refactorbranch. It was generated by comparing the branch againstmasterand reviewing the design notes in.auxiliary/notes. The document outlines the implementation of the simplified trial order (User -> OS -> Python -> Detection), changes to charset handling (permissive vs restrictive), and identifies pending tasks such as fixing test failures and addressing TODOs.PR created automatically by Jules for task 17127987879177268606 started by @emcd