fix(create-feature): 생성 기능이 scope fence로 끝난 요청을 실패로 보고하지 않는다 #32
Closed
donghyeon.kang
wants to merge 0 commits from
donghyeon.kang/fix/r9-abort-telemetry AGit into main
pull from: donghyeon.kang/fix/r9-abort-telemetry
merge into: :main
:main
:fix/r9-structure-locale
:fix/r9-adapter-carryover
:test/shared-build-lock-order
:ci/dependency-cache-same-filesystem
:ci/release-tag-for-a11y-review
:ci/merge-dependency-cache
:fix/test-timeouts-measured
:fix/feature-residue-word-boundary
:fix/provider-wait-stderr
:fix/provider-job-host-requirements
:fix/ungated-vitest-spec
:fix/a11y-evidence-routes
:fix/verify-parts-diagnostics
:claude/w2-fe-ci-perf-dce080
:fix/child-process-test-timeouts
:chore/layout-rules-r2-r5
:claude/fe-b-docs-korean-645f55
:chore/ci-merge-jobs
:chore/layout-3-merge
:claude/fe-c-harness-0ae061
:chore/layout-2-sample-removal
:chore/layout-1-cleanup
:docs/review-guide-pointer
:fix/maturity-review-2026-11-06
:fix/maturity-review-2026-11-05-b
:docs/improvement-manual
:fix/maturity-review-2026-11-05
:fix/session-subject-required
:fix/ui-design-audit-2026-11-01
:fix/maturity-review-2026-09-25
:lane/D
:lane/B
:fix/src-review-round3
:refactor/domain-scalable
:develop
:feature-frontend-optional-adapter-recipes
:feature-frontend-supply-chain-verification
:feature-frontend-test-registry-evidence-hardening
:frontend-test-registry-evidence-hardening
:feature-frontend-diagnostics-telemetry-runtime
:feature-frontend-i18n-message-formatting-contract
:feature-frontend-design-system-platform
:feature-frontend-form-page-platform
:feature-frontend-reference-feature-vertical-slice
:feature-frontend-routing-release-recovery-runtime
:feature-frontend-http-query-contract-execution
:feature-frontend-application-boundary-runtime
:feature-frontend-typescript-tooling-foundation
:feature-frontend-platform-capability-review
:feature-frontend-performance-route-contract
:feature-frontend-starter-experience-quality-contract
:feature-frontend-responsive-theme-contract
:feature-frontend-ui-primitives-gallery-contract
:feature-frontend-app-shell-navigation-contract
:feature-frontend-runtime-composition-contract
:feature-frontend-ci-quality-gates-contract
:feature-web-vitals-performance-budget-contract
:feature-frontend-release-cache-rollback-contract
:feature-accessibility-baseline-contract
:feature-frontend-project-bootstrap-toolchain-contract
:feature-frontend-operational-runbook-contract
:feature-frontend-contract-compatibility-governance
:feature-frontend-contract-registry-governance
:feature-frontend-browser-security-boundary-contract
:feature-frontend-build-bundle-supply-chain-contract
:feature-tailwind-design-token-styling-contract
:feature-sample-feature-slice-contract-fixture
:feature-frontend-render-recovery-boundary-contract
:feature-routing-navigation-guard-contract
:feature-boundary-mapper-viewmodel-contract
:feature-async-ui-state-contract
:feature-frontend-observability-logging-trace-contract
:feature-frontend-storage-registry-contract
:feature-server-state-caching-contract
:feature-frontend-auth-session-integration-contract
:feature-frontend-error-classification-boundary-contract
:feature-runtime-schema-validation-contract
:feature-api-client-response-envelope-contract
:feature-frontend-env-runtime-config-contract
:feature-frontend-architecture-enforcement-lint-contract
:feature-frontend-test-taxonomy-contract
:feature-frontend-clean-architecture-layering-contract
No Reviewers
Labels
No items
No labels
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
donghyeon.kang (동현 강)
Clear assignees
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: donghyeon.kang/clean-architecture-frontend-template#32
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
무엇을, 왜
생성 기능의 입력(
create<Base>FeatureInput)은 실패한 읽기를 telemetry warning(<base>.list.failed등)으로 보낸다. abort 판정이REQUEST_ABORTED하나뿐이라, 로그아웃·계정 전환의 scope fence로 끝난 요청(SCOPE_GENERATION_CHANGED)이 실패로 보고된다. 시험 전략 7.1절은 abort를 telemetry 실패로 세지 않는다(1112/01-03).고른 방법과 버린 대안
src/contracts/errors.ts의isAbortFailure하나로 둔다(REQUEST_ABORTED,SCOPE_GENERATION_CHANGED). 생성 입력이 그것을 부른다.위험과 영향
isAbortFailure를 가져오면서 기능 모양 측정의 초기 JavaScript가 바뀌었다(context 하나당 4 B → 21 B, 첫 기능 6,327 → 6,355 B, 기능 하나 539 → 528 B). 첫 게이트 실행에서 기록 시험(feature-shape-growth.test.ts, 허용치 16 B)이 FE-GATE-005·020을 실패시켰다. 생성 코드를 바꾼 같은 커밋에서 측정 스크립트(--initial-baseline --write)로config/scale/feature-shape-ceilings.json을 다시 썼다. 초기 JS 예산 안이다.fix/r9-precache-bound-diagnostics)가 같은 기록 파일에 SW precache 축을 더하므로 이 PR 위에 쌓았다. 이 PR을 먼저 병합한다.*-feature-api.ts의result.error.kind !== "REQUEST_ABORTED"를!isAbortFailure(result.error)로 바꾼다(round9 마지막 CHANGELOG에 적는다).isAbortFailure는 contracts의 새 export다(추가만).검증
desktop, CI env,
scripts/verify.sh(flock).5250ff95에 새 시험만):tests/unit/abort-failure.test.ts·create-feature.test.ts3 failed, 48 passed. 로그/tmp/claude-gates/r9f3-red/.abort-failure·create-feature·error-classification65 passed. 로그/tmp/claude-gates/r9f3-green/.5250ff95위, 트리31d9450e= 그때 head 트리): FE-GATE-002·003·005·020 모두 rc=0. 생성 기능 안의 새 시험은 020 scaffold 드릴이 돈다. 로그/tmp/claude-gates/r9f3-gates2/.c5f29344(PR #19)를 merge했다. #19는src/·vite 설정·기능 모양 기록·생성 명령을 건드리지 않는다. merge 뒤 결과는 runner가 본다.리뷰어가 볼 곳
scripts/create-feature.ts의 생성 feature-api 템플릿과 생성 입력 시험 템플릿.관련
docs/reviews/2026-11-round9-01-react.md01-03(PR #23)#40으로 병합됐다(main
ee47480c). 이 PR의 head2a4d46fa가 #40 브랜치에 merge 커밋으로 들어 있고, #40의 runner merge job 셋이 그 합친 트리로 초록이었다. runner 대기를 줄이려고 이번만 쓴 방식이다(소유자 승인, 2026-11-13).Pull request closed