Repository navigation
feature(readme): steady reading pace, early report notice, resume or cover-letter input - #57
Conversation
The reading screen no longer speeds up when the server runs ahead: the backlog-derived dwell multiplier, skimming and jumping modes are gone and only the explicit 읽은 곳까지 바로 보기 / 끝까지 바로 보기 / 재생 건너뛰기 actions, reduced motion and refresh skip ahead. A report that is finished while the screen still replays is announced in a sticky bar row (리포트가 준비되었어요! / 리포트 보기) during running and paused playback without moving focus or navigating; a page turn in flight is cancelled on screen change so the report opens at its top. WEB-10 decision b4a542. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
The input screen asks for the document kind. A resume still sends the unchanged legacy /prepare body; a cover letter adds document_type and essay_prompts (trimmed, blanks dropped, order kept, client mirror of the 10 / 1,000 / 6,000 limits). Prompts never enter the sheet: the confirmation shows the server's document_context list apart from the text, the reading screen keeps a collapsed reference list, the report names them as context only. A newly requested cover letter whose record is missing, malformed, re-ordered or re-typed against the request snapshot blocks 읽기 시작; a refreshed pending preparation restores kind and prompts from the record. Copy and disclosures follow the kind. The sample stand-in validates and echoes the metadata for verification. docs/ESSAY_INPUT_CONTRACT.md v1, WEB-11. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
A new cover letter's record must number every prompt ep1…epN, so a missing or null id now counts as a mismatch. The ready-time restore of kind and prompts from the server record applies only to a preparation resumed after a refresh (no request snapshot); a fresh 준비하기 in the same tab keeps what was typed and a mismatched record is blocked. WEB-11 reviews 8294b2 / cb7128. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configuration
📒 Files selected for processing (3)
Included review availability: This review used your included allowance. Your plan provides up to 1 included review per hour; 0 remain after this review. Priority: ➖ Normal Change: Feature Merge Risk: ⚪ Minimal · up to No confirmed issue remains from this review. The stated OPS-04 backend prerequisite still needs release confirmation before merge. 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
Full details: Docstring CoverageExplanation Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff. Analyzed 7 functions across 2 files. (1 skipped: 1 unsupported.)
✨ Finishing Touches 💡 1📝 Generate docstrings 💡
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Summary
Release gate
Requires the OPS-04 backend release (594dec5 essay metadata) to be live first: the current production backend rejects the new fields. Do not merge before the backend-ready evidence is posted on the board (OPS-04).
Checks
Rollback
Previous main deploy: CI run 37554583915 (e8e7c8d). Revert this merge or redeploy that revision.
🤖 Generated with Claude Code
Summary by CodeRabbit