untracked files on main: dceb101 feat(#63): IMP-34 R1 donor capacity measured bound (u1+u2)

2026-05-21 22:07:41 +09:00
commit 8f085a28d3
@@ -0,0 +1 @@
+[{"id": 23011, "html_url": "https://gitea.hmac.kr/Kyeongmin/C.E.L_Slide_test2/issues/70#issuecomment-23011", "pull_request_url": "", "issue_url": "https://gitea.hmac.kr/Kyeongmin/C.E.L_Slide_test2/issues/70", "user": {"id": 28, "login": "Kyeongmin", "login_name": "", "source_id": 0, "full_name": "이경민", "email": "kyeongmin@noreply.localhost", "avatar_url": "https://gitea.hmac.kr/avatars/d883a35f9197b080b2a0c535c3f9357dcd5c7d40b3c42bd8f40218cb94609a8e", "html_url": "https://gitea.hmac.kr/Kyeongmin", "language": "", "is_admin": false, "last_login": "0001-01-01T00:00:00Z", "created": "2025-12-30T10:51:04+09:00", "restricted": false, "active": false, "prohibit_login": false, "location": "", "website": "", "description": "", "visibility": "public", "followers_count": 0, "following_count": 0, "starred_repos_count": 1, "username": "Kyeongmin"}, "original_author": "", "original_author_id": 0, "body": "[Claude #1] Stage 1 problem review — IMP-41 frame ranking label UI 차별 (배지 + tooltip)\n\n## Current state verification (what already exists vs what's missing)\n\n### A — V4 label color badges (issue spec item #1) — **ALREADY IMPLEMENTED**\n\nVerified path `Front/client/src/components/FramePanel.tsx:238-253`:\n\n```\ncandidate.label === \"use_as_is\"  → bg-emerald-100 text-emerald-700  (녹)  ✓\ncandidate.label === \"light_edit\" → bg-blue-100    text-blue-700     (청)  ✓\ncandidate.label === \"restructure\"→ bg-amber-100   text-amber-700    (황)  ✓\ncandidate.label === \"reject\"     → bg-red-100     text-red-700      (적)  ✓\n```\n\nColor spec matches issue 1:1. No recolor required.\n\n### B — Tooltip on V4 label badge (issue spec item #2) — **PARTIAL**\n\nVerified path `Front/client/src/components/FramePanel.tsx:249`:\n\n```tsx\ntitle={`V4 label: ${candidate.label}`}\n```\n\nCurrent tooltip = raw label string only. Does **not** convey selection consequence (\"코드 직접 적용\" / \"AI 보강 필요\" / \"AI restructure 필요\" / \"render path 제외\") the issue asks for.\n\nComposite tooltip at FramePanel.tsx:128-144 (`composedTitle`, on the outer `<button>`) already aggregates reject / catalog-missing / filtered / candidate_evidence lines, but neither it nor the inline V4 badge title surfaces `application_mode` semantics.\n\n### C — `APPLICATION_MODE_BY_V4_LABEL` forwarding (issue spec item #3) — **NOT WIRED**\n\nBackend mapping (single source of truth) lives at `src/phase_z2_pipeline.py:107-112`:\n\n```python\nAPPLICATION_MODE_BY_V4_LABEL = {\n    \"use_as_is\":   (\"direct_insert\",              True,  \"step10_contract_check\"),\n    \"light_edit\":  (\"same_frame_with_adjustment\", True,  \"step10_contract_check\"),\n    \"restructure\": (\"layout_or_region_change\",    False, \"human_review\"),\n    \"reject\":      (\"exclude\",                    False, None),\n}\n```\n\nStep 9 already emits per-candidate `application_mode` / `auto_applicable` / `delegated_to` into `unit.application_candidates[]` — verified at `src/phase_z2_pipeline.py:3071-3092` (`_application_candidates_for_unit`) + emitted at the application_plan unit at `src/phase_z2_pipeline.py:3227`. Fixture proof: `Front/client/public/data/runs/mdx03_f29_fix_check/steps/step09_application_plan.json:58, 67, 113, 122` all carry `\"application_mode\": \"...\"`.\n\nFrontend bridge `Front/client/src/services/designAgentApi.ts:484-562` iterates the same `units` array (line 484 `applicationPlan.data?.units`) and consumes `unit.candidate_evidence` / `unit.v4_all_judgments` / `unit.v4_candidates` to build `FrameCandidate[]`, but **does not read `unit.application_candidates`** anywhere. As a result, `FrameCandidate` type (`Front/client/src/types/designAgent.ts:137-178`) carries `label`, `routeHint`, `phaseZStatus`, `decision`, `reason`, `capacityFit` — but no `applicationMode` / `autoApplicable`.\n\nSo the data is already at the wire (Step 9 JSON) and reaches the bridge function; it is just dropped on the floor before FrameCandidate construction.\n\n### D — Dependency status\n\n- `#38` (IMP-29 frontend evidence bridge) — verified. The candidate_evidence join scaffolding is already present at `designAgentApi.ts:511-562`. Adding application_mode is a per-template_id sibling join — same shape.\n- `#10` (filtered_section_reasons UI) — verified. Independent surface; no conflict.\n- `#11` (Frame min_height 표시) — verified. Sibling badge already on FrameCandidate; pattern proven (additive, optional field, silent degradation on missing data).\n\nAll three deps locked, no waits.\n\n## Root cause summary\n\nStep 9 forwards `application_mode` correctly, the FramePanel renders label color badges correctly, but the frontend bridge does not project `application_mode` onto `FrameCandidate`. Hence FramePanel has no signal to display the human-readable selection-consequence tooltip that distinguishes `use_as_is` (직접 적용) from `light_edit` (deterministic same-frame adjustment) from `restructure` (human_rLine truncated
				`@@ -0,0 +1 @@`
				[{"id": 23011, "html_url": "https://gitea.hmac.kr/Kyeongmin/C.E.L_Slide_test2/issues/70#issuecomment-23011", "pull_request_url": "", "issue_url": "https://gitea.hmac.kr/Kyeongmin/C.E.L_Slide_test2/issues/70", "user": {"id": 28, "login": "Kyeongmin", "login_name": "", "source_id": 0, "full_name": "이경민", "email": "kyeongmin@noreply.localhost", "avatar_url": "https://gitea.hmac.kr/avatars/d883a35f9197b080b2a0c535c3f9357dcd5c7d40b3c42bd8f40218cb94609a8e", "html_url": "https://gitea.hmac.kr/Kyeongmin", "language": "", "is_admin": false, "last_login": "0001-01-01T00:00:00Z", "created": "2025-12-30T10:51:04+09:00", "restricted": false, "active": false, "prohibit_login": false, "location": "", "website": "", "description": "", "visibility": "public", "followers_count": 0, "following_count": 0, "starred_repos_count": 1, "username": "Kyeongmin"}, "original_author": "", "original_author_id": 0, "body": "[Claude #1] Stage 1 problem review — IMP-41 frame ranking label UI 차별 (배지 + tooltip)\n\n## Current state verification (what already exists vs what's missing)\n\n### A — V4 label color badges (issue spec item #1) — ALREADY IMPLEMENTED\n\nVerified path `Front/client/src/components/FramePanel.tsx:238-253`:\n\n```\ncandidate.label === \"use_as_is\" → bg-emerald-100 text-emerald-700 (녹) ✓\ncandidate.label === \"light_edit\" → bg-blue-100 text-blue-700 (청) ✓\ncandidate.label === \"restructure\"→ bg-amber-100 text-amber-700 (황) ✓\ncandidate.label === \"reject\" → bg-red-100 text-red-700 (적) ✓\n```\n\nColor spec matches issue 1:1. No recolor required.\n\n### B — Tooltip on V4 label badge (issue spec item #2) — PARTIAL\n\nVerified path `Front/client/src/components/FramePanel.tsx:249`:\n\n```tsx\ntitle={`V4 label: ${candidate.label}`}\n```\n\nCurrent tooltip = raw label string only. Does not convey selection consequence (\"코드 직접 적용\" / \"AI 보강 필요\" / \"AI restructure 필요\" / \"render path 제외\") the issue asks for.\n\nComposite tooltip at FramePanel.tsx:128-144 (`composedTitle`, on the outer `<button>`) already aggregates reject / catalog-missing / filtered / candidate_evidence lines, but neither it nor the inline V4 badge title surfaces `application_mode` semantics.\n\n### C — `APPLICATION_MODE_BY_V4_LABEL` forwarding (issue spec item #3) — NOT WIRED\n\nBackend mapping (single source of truth) lives at `src/phase_z2_pipeline.py:107-112`:\n\n```python\nAPPLICATION_MODE_BY_V4_LABEL = {\n \"use_as_is\": (\"direct_insert\", True, \"step10_contract_check\"),\n \"light_edit\": (\"same_frame_with_adjustment\", True, \"step10_contract_check\"),\n \"restructure\": (\"layout_or_region_change\", False, \"human_review\"),\n \"reject\": (\"exclude\", False, None),\n}\n```\n\nStep 9 already emits per-candidate `application_mode` / `auto_applicable` / `delegated_to` into `unit.application_candidates[]` — verified at `src/phase_z2_pipeline.py:3071-3092` (`_application_candidates_for_unit`) + emitted at the application_plan unit at `src/phase_z2_pipeline.py:3227`. Fixture proof: `Front/client/public/data/runs/mdx03_f29_fix_check/steps/step09_application_plan.json:58, 67, 113, 122` all carry `\"application_mode\": \"...\"`.\n\nFrontend bridge `Front/client/src/services/designAgentApi.ts:484-562` iterates the same `units` array (line 484 `applicationPlan.data?.units`) and consumes `unit.candidate_evidence` / `unit.v4_all_judgments` / `unit.v4_candidates` to build `FrameCandidate[]`, but does not read `unit.application_candidates` anywhere. As a result, `FrameCandidate` type (`Front/client/src/types/designAgent.ts:137-178`) carries `label`, `routeHint`, `phaseZStatus`, `decision`, `reason`, `capacityFit` — but no `applicationMode` / `autoApplicable`.\n\nSo the data is already at the wire (Step 9 JSON) and reaches the bridge function; it is just dropped on the floor before FrameCandidate construction.\n\n### D — Dependency status\n\n- `#38` (IMP-29 frontend evidence bridge) — verified. The candidate_evidence join scaffolding is already present at `designAgentApi.ts:511-562`. Adding application_mode is a per-template_id sibling join — same shape.\n- `#10` (filtered_section_reasons UI) — verified. Independent surface; no conflict.\n- `#11` (Frame min_height 표시) — verified. Sibling badge already on FrameCandidate; pattern proven (additive, optional field, silent degradation on missing data).\n\nAll three deps locked, no waits.\n\n## Root cause summary\n\nStep 9 forwards `application_mode` correctly, the FramePanel renders label color badges correctly, but the frontend bridge does not project `application_mode` onto `FrameCandidate`. Hence FramePanel has no signal to display the human-readable selection-consequence tooltip that distinguishes `use_as_is` (직접 적용) from `light_edit` (deterministic same-frame adjustment) from `restructure` (human_rLine truncated