외부 오류 규칙 카탈로그 #190
Assignees
dreampiler (dreampiler)
Clear assignees
dreampiler (dreampiler)
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: dreampiler/kandev#190
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?
원승인: D:/260720_Ai_Workspace/_UserHub/_task/kandev-ops/261026_provider_error_consolidation.md §2.5/§3의PR-3,규칙을JSON/YAML로외부로드하되기본은내장규칙을쓴다. PR-1기존W11713a3a856/#4738의CSV43서명일괄·오늘Free/Go usage/빈endturn을유지하고PR-2 KANDEV-PROVIDER-KEYCTX-1026/task7f814a31-86b2-4ac0-a44c-7e164f34d1ad의기본OFF핵심어×상황단계와고정규칙우선·정본규칙모델/회로범위·기간/reset계약을소비한다. 사용자명시 자식2개중PR3만이task,같은기능활성task발견시원pointer인수·중복등록0.
NativeKanban1수준이라기존공통parent93c6b4d0 아래PR1의논리후속자식으로결속. 실제blocked_byPR2(task7f814..)에연결하며PR1은그선행,공통classify/prefilter/flag·config등록glue와외부규칙schema를PR2실결과/해제후순차인수할의존이다. 선행미완/등록을착수·완료로세지않는다. 14작업10관제4/WIP/동적모델순서유지,정상선행해소/대기pull로시작.
필수동작:기존registry/설정패턴으로옵션경로를지정하면JSON/YAML외부카탈로그를읽고규칙을분류pipeline에연결;경로미지정이면기존내장규칙/기본동작그대로. 정확지원형식/필드·버전/규칙키·우선순위/기존고정규칙·핵심어조건/계정·경로·모델scope/기간reset표현의최소범용계약을현재설계와실PR2모델에맞춰문서화,CM변환기가후속으로쓸입력·샘플과실결과를반환. 외부입력의파싱/필수필드·알수없는분류/잘못된값/경로문제를기존오류/로그패턴으로명확히다루고내장기본을소실하거나비밀을로그로출력하지않음. 설정으로덮어쓰기의정확우선순위·오류시동작은정본설계/기존컨벤션에서정해Plan에명시;사용자필수기능을외부파일존재만으로완료라하지말고실분류진입점에서소비됨을확인. 원필수guard/고정규칙우선/PR2기본OFF·모델순서·profile순서불변,불명확사항을자기선호로새게이트/새플래그/전역정책으로승격0.
소유경계:새독립catalog loader/규칙자료형변환/최소설정경로및문서,공통분류glue는PR2명시해제뒤. 기존카탈로그/정책/구현이이미있으면필요delta만소비. Nativenewworkspace/Worktree08eb자기source/branch/base refs/remotes/upstream/main을먼저확인,공용checkout/다른task/추가AIWSgate slot/clone·모델설정·운영DB/프로세스/재시작/외부network로드/상시hotwatcher·scheduler0. 로컬파일로드만으로충분하면remoteHTTP/동기화서비스/새daemon을만들지않음. 추가hash/signature/중복검증장부/권한issuer0. 내부일반파일작업의제약을새보안체계로강화하지않는다.
CM코드는이번범위밖: _Manage/tools/kandev-watchdog/provider_errors.py CSV제안분류→Kandev외부포맷변환기는PR3뒤AIWS관제별도요청이다. CM CSV정본은읽기참조만,CMsource/카탈로그writer/자동수집·원CSV전체를publicrepo에복사0. 실제공개외곽upstreamGithub에서는AIWS고유프로필/내부path/세션·로그/비밀없이범용schema/examples만쓴다.
Plan에원요구/현내장규칙/PR2입력·변경/완료조건→최소source구현→기존선택시험·자동수집제외임시fixture로기본내장동일/설정외부JSON·YAML실로드분류변화/오류경로·우선순위·기존guard를좁게확인→정상hooks→정확delta필수독립formalRV/필수수정0→93/5d단일publisher에정상커밋/실basehead·영문PR초안·검증·공개샘플/CM후속interface를인계하고실게시응답/새PR3번호readback. 상류사전승인은유효하나source가5d와중복push/댓글/PR0. 새상시시험/framework/불변전체시험·빌드/RV반복0,라이브공급자한도유발0. 실제source/result_ref/parentacceptance로이flow만종결;운영파일설정/featureON/CM변환기완료를이source성공으로과장하지않는다.
PR-3 unit A (task 9066d589) progress 2026-10-29: independent external catalog loader package apps/backend/internal/agent/runtime/routingerr/externalcatalog (JSON/YAML strict load, whole-file rejection with stable reasons, first-match rules, eligibility-gated terms/context, identity-safe scope, README draft + examples). Upstream-prep branch feature/kandev-provider-cata-rcv base fb4c2bc3ef9 head 3fb7f7b0e10 (pushed to fork origin, not merged). Formal RV: RV-RUN-261029_kandev_pr3_catalog_unitA_rv_packet.md-1793204057730074900-47380-mid-1 REQUEST_CHANGES (README terms/OR contradiction) fixed by 3fb7f7b; delta RV-RUN-261029_kandev_pr3_catalog_unitA_rv_delta1.md-1793204970560724400-2081-mid-1 APPROVE, 0 findings. go test externalcatalog ok (10 tests), lint-go-changed 0 issues, hooks passed. Fork PR dreampiler/kandev#373 closed without merge per controller 8e (upstream-prep task). Not done: Classify integration, config key/startup load, docs (unit B/C) wait for PR-2 7f814a31 release; then integrated delta RV and handoff to 93/5d publisher. Flow not closed: completion conditions unmet.
PR-3 (task 9066d589) progress 2026-10-29: unit B/C integrated on PR-2 head ef31b98 in upstream-prep branch feature/kandev-provider-catalog-pr3 (head bc9bc517e59, pushed to fork origin, not merged): Classify wiring before keyword fallback, providerErrors.catalogFile startup setting, docs REQ-003. Formal RV: unitBC_rv_packet REQUEST_CHANGES (scope finding, not reproducible, answered with evidence+test) then unitBC_rv_delta1 APPROVE, 0 open findings. Main-based judgment: local branch feature/kandev-provider-catalog-loader-main (base upstream/main 3a740c6911a, head 0624b06e790, unit A cherry-pick, identical, RV reused); standalone loader PR not recommended (no consumer on main, upstream docs-coverage needs PR-2-owned specs, #4917 cross-repo). Recommendation to 93/5d via 8e (delivered, queued 7c6ce42c): one follow-up PR after #4917 merges or via maintainer topic base. Waiting: PR-2 reviewed fix head + delta (re-stack, conflict-only RV), 93/5d publication and PR number readback, acceptance. Flow not closed.
PR-3 (task 9066d589) progress 2026-10-29: re-stacked on PR-2 #4917 H2 a44a945d9fbb. Local upstream-prep branch feature/kandev-provider-catalog-pr3-h2 head e70f90ef8ac5 (26 files; only 2 docs conflicted and were resolved keeping H2 content). Conflict-only formal RV RV-RUN-261029_kandev_pr3_catalog_h2_restack_rv.md-1793220890424220700-7513-mid-1 APPROVE; 24 identical files reuse unit A and B/C APPROVE. Focused tests, docs validate, spec lint, lint and hooks passed (only pre-existing Windows HOME test fails, untouched). Handed to controller 8e for 5d publication (message 328e13ed, delivered). Not pushed, no upstream PR yet (5d owns push/PR). Remaining: 5d publication and PR number readback, 8e acceptance, flow close; blocker on PR-2 until #4917 merges.
PR-3 (task 9066d589) progress 2026-10-29: re-stacked on PR-2 #4917 H3 fec30f600571. Local upstream-prep branch feature/kandev-provider-catalog-pr3-h3 head ed5a3ae653a0 (26 files). One conflict (provider-error-signatures plan.md) resolved keeping upstream section; task-03 work order frontmatter completed after upstream pr-docs coverage check reported invalid (depends_on missing) - earlier candidates had the same gap. Formal RV RV-RUN-261029_kandev_pr3_catalog_h3_restack_rv.md-1793247557000228400-6428-mid-1 APPROVE; 24 identical files reuse prior APPROVE. Tests, docs validation and hooks passed (only pre-existing Windows HOME test fails, untouched). Handed to 8e for 5d publication (message 68e7641f, delivered). Not pushed; no upstream PR yet. Remaining: 5d publication and PR number readback, 8e acceptance, flow close.
8e receiving acceptance: ACCEPT PR-3 external provider-error catalog H3 re-stack (source task 9066d589-1164-4be1-a998-c11bbfb1a17d, single writer). Trigger: #4917 public head changed a44a945d -> fec30f60057197e11e9c2ca9e8446335777c6787 (7f main-sync CALL-20261029-e5ba0028f78f APPROVE). 8e read-only checks in the shared kandev repo: local branch feature/kandev-provider-catalog-pr3-h3 = ed5a3ae653a00aa47a4ec83148fc5e451e8f2e09, fec30f60 is ancestor, fec30f60..h3 = 5 commits (e9f3e02, d5128e0, a4941ac, 0581a8d = same 4 catalog commits from h2; ed5a3ae new docs frontmatter), diff 26 files +1734/-4 (PR-3 scope kept, #4917 35 files outside). Only conflict docs/plans/provider-error-signatures/plan.md (both sections kept). New authored delta: task-03 work order frontmatter fixed so upstream pr-docs validateCoverage reports covered (older candidates bc9bc51/e70f90e had the same missing depends_on defect). Formal RV for conflict + new delta only: RV-RUN-261029_kandev_pr3_catalog_h3_restack_rv.md-1793247557000228400-6428-mid-1 status completed, verdict APPROVE, findings 0 (8e read the record); unchanged 24 files reuse CALL-20261029-02b786e12d75 / -5d518b596a90 / -a2a5a49d543e APPROVE. Source-reported narrow checks: build ok, PR-3 tests ok (only the known Windows HOME test), docs validate/spec lint pass, normal hooks passed. Shared path: H3 diff touches apps/backend/internal/backendapp/services.go (one line installProviderErrorCatalog in initCoreTaskServices); C1 af3f625e (not yet started) was told to report adjacency; e80cef65 files untouched. Preserved: h2 e70f90ef8ac5, bc9bc51, loader-main 0624b06, old RVs. No push/PR/comment/force/reset/amend/branch deletion. Publication condition unchanged: upstream topic base -> separate stacked PR, otherwise exact delta after #4917 merge; sole publisher 93->5d. Flow stays open until publication, PR number readback and close.
PR-3 (task 9066d589) progress 2026-10-31: re-stacked on PR-2 #4917 exact head 6e498373b5a8. Local upstream-prep branch feature/kandev-provider-catalog-pr3-h4 head b9f9bf6b159f (26 files, same paths as H3). One docs conflict (system-design) resolved keeping upstream text; all 26 files changed lines identical to reviewed H3 candidate, so no new RV - H3 APPROVE verdicts reused (CALL-20261029-7aaf791f475e and prior). Build, focused catalog tests, docs validation, upstream pr-docs coverage (covered) and normal hooks passed; only the pre-existing Windows HOME test fails (untouched). Handed to 8e (message f510afee, delivered). Not pushed; no upstream PR yet. Remaining: maintainer topic base or #4917 merge, then 93/5d publication and PR number readback, 8e acceptance, flow close.
8e receiving accepts local H4 only: source task9066d589/session1e9a388b/branch feature/kandev-provider-catalog-pr3-h4, exact base6e498373b5a8e3e4115df15f2eb2451557585f03/headb9f9bf6b159f65c2536487dff188ae5df9176513 clean; five normal commits preserve H3 history and26paths+1734/-4. Direct Git added/deleted-line text comparison found no changed authored line across all26paths versus fec30..ed5; source hash comparison is NOT used as evidence or repeated. Existing H3 APPROVE CALL7aaf791f475e/02b786e12d75/5d518b596a90/a2a5a49d543e retain exact-snapshot scopes; no new RV. Original raw shell outputs confirm build/selected catalog8 and consumer/config tests/coverage covered/normal commit completion, with known Windows whole-routingerr cache fixture failure retained, not all-green. result_ref=task-plan300d40fd-d817-4b0b-9c2b-a1b9b307c81e H4 done section and stored source message agent-delivery-78ffc74b29dcc79229519be3f47f74cb; previous H3 receiving note20261029T042444993497Z preserved. Public4917 remains6e OPEN/unmerged; publication waits maintainer topic base or merge, then93/sole5d exact-base preflight and separate catalog PR readback. Return same task to external hold with actor/id/date/resume condition; keep flow open, no flowclose/reopen/public action/operational change.
2026-10-31 local re-entry after actual PR4917 head14a62bf2a88994a74c958416d109602a40ae8f71: original task9066d589/current primary1e9a388b reused, no newtask/session/manualspawn. 8e read original H4 cleanb9f9bf6b159f65c2536487dff188ae5df9176513 and Plan condition, preserved old26payload/RVs/branches. Normal external-hold to Plan move9cba6092 applied once/entry22150. Actual first Git shell38148eeb at23:28:21Z confirmed cleanH4/ref14a/main997bc; same actor then created H5 and normal no-commit merge14a. Exact conflict config/source.go only, catalogFile YAML/default/env must retain main SQLite reader rawYAML/env and webhook settings. Implementation/result not accepted yet; unchanged payload reviews reused and only new required seam evidence/delta checked. Source actual work differs from mere queue intake. Publication remains pending actual4917mainmerge or validated upstream topic base; no public PR/comment/topic edit/rerun or operating change. Existing P48 writer untouched; preserve local H4 acceptance and unfinished business flow.
8e local H5 receiving: same9066 source clean1c0147ac15396d68d8c16c871e0fed6a799da15c, normalparents preservedH4b9f9bf6b159+PR4917exact14a62bf2a889. Parent directly compared H4 relative6e and H5 relative14a:26paths identical +1734/-4,25 file change-line payloads exactly equal,only source.go map entry alignment differs one space. Sole manual conflict is yamlOnlyStartupKeys union retaining14a webhook/private-network and sqliteReaderConns plus catalogFile; default/env lines auto-merged, other source paths automatic. Existing H3/H4 review snapshots reused in original scope,no newRV/model/test/framework. Original stdout shows related routingerr0.031/externalcatalog0.266/backendapp0.239/dynamic0.047 PASS and normal applicable hooks/commitlint plus actual mergecommit. Config package genuinely FAIL5 at0.257; raw detailed failure paths show Windows quoted-path/HOME issues but no bare14a baseline execution,so baseline causation unverified and no package-wide green claim. Some commands piped through grep/tail and did not preserve Go child exit separately; wrapper0 not asserted as all Go success. Local preparation accepted, returning same task to non-autostart publication hold. Result_ref=_UserHub/_desk/261031_kandev_pr3_catalog_h5_result.md; acceptedcandidate base14a/head1c0147a/H4H3H2history preserved. Official4917stillOPEN/unmerged, no validated upstream topicbase observed; maintainer actualmerge/topic→93→sole5d catalog-only PR,not classifier43duplicate. No public/code/operating change by8e or premature flowclose.
8e receiving accepts local H6 only: source task9066d589/session1e9a388b/branch feature/kandev-provider-catalog-pr3-h6, exact base de65d68ffaba8765cb72b7e903848f132416578c / head b7d58ccd02ec9b8665e02c2c0496eca5165f2b17 (parents H5 1c0147ac1539 + de65), clean. no-ff normal merge of PR2 de65 onto H5; only config/source.go conflicted (purely additive: providerErrors.catalogFile ours + notifications.webPushSubject/AllowedHosts theirs both preserved). de65..H6 = 26 paths +1734/-4, exactly matching H5 original 26-set by direct added/deleted-line text comparison (no hash/fingerprint, not byte-identity claim). No new authored behavior delta. Review reuses accepted H5/H3/H4 catalog payload snapshots + PR2 de65 formal fffe APPROVE 4-scope producer reconciliation; no new RV. Build (routingerr/config/dynamic/backendapp) and narrow consumer tests passed; known H5 whole-config FAIL5 / unproven baseline / filtered child-exit limits retained, not all-green. 8e direct-verified clean/exact and accepted. result_ref=task-plan300d40fd-d817-4b0b-9c2b-a1b9b307c81e H6 sections. Public4917 remains de65 OPEN/unmerged, no exact upstream topic; publication waits maintainer topic base or merge, then93/sole5d exact-base preflight and separate catalog PR readback. Return same task to external hold 8a10b282 with actor/id/date/resume condition; keep flow open, no flowclose/reopen/public action/operational change.