structured error_type·context length 분류 규칙 (OLD #288 rule port) #123
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
목표: OLD fork #288(cca1cbbfc16, 10-13) 가운데 routingerr 분류 규칙만 native 에 port 한다: structured provider error_type 기반 분류와 context length exceeded 분류. 조사 [확인]: NATIVE deb3815d1 이 structured provider 신호를 보존하지만 structured_error_type/context_length_exceeded rule 은 0건. account-block 봉투는 native(#4448)에 이미 있으니 중복 구현하지 않는다. 완료: fork native-main 대상 PR 병합 + routingerr 순수 단위 시험 결과. 근거: 운영 세션 2026-10-20 07:1x KST 등록 지시, 사용자 원문 2026-10-20 「…최소 8개 이상의 작업 workAI 가 동시에 최소 1시간 이상 꾸준히 돌아가도록 자율적으로 개선 진행 계속해줘.」. 출처 old-fork-failure-handling-survey.md Q3 #12.
KANDEV-FH-1020-ERRTYPE: routingerr native port merged - PR dreampiler/kandev#345 squash 74f25f503c8 into native-main; added provider.structured_error_type.v1 and provider.context_length_exceeded.v1 in provider_neutral_rules.go plus co-located provider_structured_rules_test.go; pure unit test on ./internal/agent/runtime/routingerr/ passed; go vet and golangci-lint clean; account-block not touched (#4448 native). Independent review unavailable (get_code_review_kandev not exposed in session; fork GitHub Actions disabled), author-run review per repo code-review skill recorded in task plan with no findings.
[ERRTYPE #345 필수1 - 읽기 전용 대조 + 임시 재현 1회]
[VER11-ALIGN-20261023] 최초 요청 원문·기존 flow/issue/이력 보존. 최신 기준 _Knowledge/references/최종목표구조설계_ver11/20_통합설계서.md 및 명세11/13/14, 절차·잔여·비용은42_현행정합_실행절차.md. 2026-10-23 읽기 관측 explicit task: d116a3fe-516c-4d4e-a0c4-5f4b20477cf0 (REVIEW); 958e8218-1f6a-4f33-8a97-9cd746f4c89c (COMPLETED, archived)
task description의 최신3차판 읽기전용 운영확인 범위가 원 코드수정 대기를 구체화함. 실제 사례/인수 부족은 그대로 유지, 구현/시험/정상대기 해제/종결을 자동 추가하지 않음.
이번 갱신은 결과/다음담당 연결이며 상태 일괄종결·task이동/삭제·모델순서/한도·상시시험·해시 확인 추가0.
ERRTYPE original acceptance: The stated scope was the two routingerr rules merged to dreampiler/kandev native-main plus the pure unit test. Fork PR #345 merged on 2026-10-19 at 74f25f503c8045bb7a9a88e2b1f16dccb86e8f06. The original source report records the focused unit test PASS 0.125s, go vet and golangci-lint clean, and the Windows HOME fixture failure reproduced with the change reverted; review was author-run because an independent reviewer was unavailable. Exact upstream commit a2ff19251415847f4ece4c2d9eee95a1af752ed8 contains the named rules and the PhasePromptSend consumer guard. Direct reads of default kdlbs/kandev main still show the older predicate and no same consumer change, so this close does not claim upstream-main integration or independent review. Keep that upstream follow-up separate.
Reflect/cleanup complete; the workflow advanced (final step).
Done
dreampiler/kandev#345squash-merged to forknative-main(commit74f25f503c8);origin/native-main2328c0740eb..74f25f503c8. Verified bothprovider.structured_error_type.v1andprovider.context_length_exceeded.v1andprovider_structured_rules_test.goonnative-main.feature/kandev-fh-1020-errty-w82deleted; shared checkout and the Kandev task folder untouched; no other copies/branches created.flow report-progressvia the AIWS gate (flow_id KANDEV-FH-1020-ERRTYPE, callCALL-20261020-9b8ef7fd8df7, succeeded).8e3eb6b7(queued).Completion condition met: fork
native-mainPR merged + routingerr pure unit test result recorded in the plan.go test -trimpath -run '…' ./internal/agent/runtime/routingerr/→ ok;go vet/golangci-lintclean; only pre-existing WindowsTestRemediateNpxCache_*env failure unrelated to the change.Left as control decisions (reported, not blocking the task): formal queue closure (item still
created; closure is control-owned) and obtaining a real independent semantic review (fork Actions disabled;get_code_review_kandevunavailable — author-run review recorded with no findings).