Repository navigation
feat(readme): show inquiry speech and source revisits - #56
Merged
Merged
Conversation
…sits Behind generation.policy_version readme-focus-v1 the Lab page now reads inquiry/updated/parked/revisit/observation/speech events into the same question history and memos the sheet already draws, settles still-open inquiries at the end on the client, checks state versions on the focus stream, and keeps older policies untouched. Presentation: one fixed phrase per verified change rests beside the gaze after the pen (a second phrase follows after a breath), a revisit glances back to its target sentence, parked questions are labelled, and the memo detail lists revisits and the phrases. A hand-authored focus fixture replays under ?sample=focus in sample mode only. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Observations are keyed by the server note_id with the action/method/ outcome/reason/boundary/plan kinds; a retracted event marks the earlier observation 참고 · 이전 and adds a correction memo; speech revised is a fixed phrase without a question; withdrawn and correction evidence are kept on the snapshot and the correction unit leads a reopened question's flow; a revisit is applied once per question per window and is listed before the change it led to. The sample focus fixture now has the shape the backend validator accepts: no adopted evidence at inquiry, a revisit to the origin before every update, resolved questions parked, proofs with unit-local offsets, speech naming its unit. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
…fixtures Adds a verification-only FixtureSource that replays a recorded run (work24-readme docs/fixtures/readme-lab/focus-*.json) through the same job-view path the API uses: cumulative events from incremental snapshots at a fixed pace, cursor filtering, the recorded reconnect replay held at its cursor, invalid_cursor and cancel. It is chosen by ?fixture=<name> only where the page is not the deployed copy. The eight fixtures are copied verbatim under __fixtures__ and driven through the page's cursor, integrity, ingest and reducer in focus-fixtures.test.ts. Focus-policy copy now separates inquiry reading from the final requirement comparison (scope line, requirements panel, method page). A stop before any sentence reads 첫 문장을 읽기 전에. Reopened questions keep 다시 열림 at the end, matching the final report. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
The pre-job disclosure (처리되는 곳) and the upload help now cover both methods accurately before the policy is known: the legacy reader sends the posting criteria, their check conditions and every sentence read so far; the inquiry-focused reader sends the current and recent sentences, short context/inquiry indexes, the earlier sentences it needs and only the posting's main duties as background. Providers, data categories and the consent sentence are unchanged. After the policy is known the report's generation line and the limits line state the focus scope. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
|
Warning Review limit reachedYou've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Next included review available in 24 minutes. View limit detailsLimit details: You’ve used the included review currently available. Review configuration: ⚙️ Run configuration
📒 Files selected for processing (12)
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 |
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
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.
읽기 메모가 모집 요건 확인에 치우쳐 문장에서 생긴 의문과 뒤의 설명을 따라가기 어려웠습니다. 새
readme-focus-v1결과를 받아 물방울 말풍선, 과거 원문 재방문, 보관한 질문과 정정·철회 기록을 표시합니다. 기존 읽기 정책은 유지하고, 요건 대조는 최종 리포트에서 진행한다는 안내와 실제 전송 범위를 반영했습니다.실제 Jev 출력 fixture 8개로 재접속·정정·철회·중간 실패·질문 없는 장문을 검증했습니다. 프런트 38개 테스트·빌드·브라우저 검증, 실제 HTTP→Jev→GPT 완료 및 새로고침 복원, 별도 읽기 전용 리뷰를 통과했습니다. 최신 main을 통합했으며 Lab 소스는 Claude가 검증한 760b87b와 같습니다.
이 소비자를 먼저 배포한 뒤 백엔드 엔진을 명시적으로 전환합니다. 새 이벤트는 해당 정책에서만 활성화됩니다.