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": 22049, "html_url": "https://gitea.hmac.kr/Kyeongmin/C.E.L_Slide_test2/issues/40#issuecomment-22049", "pull_request_url": "", "issue_url": "https://gitea.hmac.kr/Kyeongmin/C.E.L_Slide_test2/issues/40", "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-31 AI-assisted frame-aware adaptation (restructure / reject routes)\n\n### Root-cause framing\n\nThe route_hint metadata for `restructure → ai_adaptation_required` and `reject → design_reference_only` is already emitted (IMP-05 L2, `src/phase_z2_pipeline.py:572-577,580-584,664`) and already surfaced to the frontend (IMP-29, `Front/client/src/types/designAgent.ts:168-169` + `Front/client/src/components/FramePanel.tsx:254-268`). What does **not** exist is a runtime consumer that turns `ai_adaptation_required` into a real adaptation step — restructure candidates today are filtered out of direct execution (`filtered_for_direct_execution=True` at `src/phase_z2_pipeline.py:663`, MVP1_ALLOWED_STATUSES skip path at `src/phase_z2_pipeline.py:678-680`). The route_hint is \"dead-end\" metadata, exactly as IMP-17 carve-out §Activation gate condition 3 describes (`docs/architecture/IMP-17-CARVE-OUT.md:29`).\n\n**Key axis identity question (must lock before Stage 2):** Issue #40 is filed as **IMP-31** but the source comment + carve-out doc explicitly say this axis belongs to the **IMP-17 slot**:\n- `src/phase_z2_pipeline.py:570` says `(deferred to IMP-17 — carve-out, AI fallback only, normal path 밖)` — corrected from a prior stale \"IMP-31\" reference by commit `e10ec36` (IMP-17 anchor sync).\n- `docs/architecture/IMP-17-CARVE-OUT.md:23` line: `신규 IMP ID 발급 (이 carve-out 은 IMP-17 슬롯에 영구 귀속)`.\n- IMP-17 backlog row 68 still marked `documented (deferred)` (`docs/architecture/PHASE-Z-IMPLEMENTATION-ISSUE-BACKLOG.md:68`).\n- The IMP-17 Stage 1 exit report (`.orchestrator/issues/17_stage_problem-review_exit.md:14,46`) explicitly bans new IMP IDs: \"신규 IMP ID 발급 (IMP-29 이상) — 본 axis 는 IMP-17 슬롯 그대로 사용\".\n\nSo Issue #40 (IMP-31) is the **activation issue for the IMP-17 carve-out** — the runtime work IMP-17 deferred. Either we rename / re-slot to keep registry consistency, or we lock IMP-31 explicitly as the activation tracking issue with IMP-17 as the permanent design slot. **Recommend the latter (cheaper anchor surface)**, with the IMP-17 doc + comment updated to reference IMP-31 as the live activation issue. Codex r1 must adjudicate before Stage 2.\n\n### Verified facts (value + path + upstream)\n\n- Route_hint emission site = `src/phase_z2_pipeline.py:572-584` (`_IMP05_ROUTE_HINTS` dict + `_imp05_route_hint()`). Mapping: `use_as_is→direct_render`, `light_edit→deterministic_minor_adjustment`, `restructure→ai_adaptation_required`, `reject→design_reference_only`.\n- Route_hint consumer count (runtime) = **0**. Grep `grep -rln \"ai_adaptation_required\" src/` returns only `src/phase_z2_pipeline.py` (emission) + `tests/test_phase_z2_v4_fallback.py` (assertion). No adapter / proposal / planner consumer exists.\n- Frontend reader = `Front/client/src/components/FramePanel.tsx:262-265` shows `ai req` / `ref` / `adapt` chips. IMP-29 closed this loop on the display side only.\n- Filter behavior = `src/phase_z2_pipeline.py:663` records `filtered_for_direct_execution=True` for restructure/reject; `src/phase_z2_pipeline.py:678-680` skips them with `phase_z_status_not_allowed` reason.\n- **Issue cross-ref is stale**: issue body cites `_imp05_route_hint()` at `src/phase_z2_pipeline.py:452` but actual line in HEAD `1efbf67` is **580** (line 452 is `force_drill_parents` sub-section drilling, unrelated). Issue body needs anchor refresh.\n- IMP-17 carve-out 3-condition AND activation gate (`docs/architecture/IMP-17-CARVE-OUT.md:25-31`):\n  1. **User GO** — explicit axis activation request.\n  2. **B4 frame_selection evidence integration complete** — Step 9 frame_selection V4 evidence integration must be stable.\n  3. **IMP-04 catalog + IMP-05 V4 fallback live**.\n- Gate condition status (current HEAD):\n  - Cond 1 (User GO): not visible in issue body as explicit lock. Filing #40 may imply GO; needs user confirmation.\n  - Cond 2 (B4 frame_selection evidence integration): **NOT satisfied**. `docs/architecture/PHASE-Z-PIPELINLine truncated
				`@@ -0,0 +1 @@`
				[{"id": 22049, "html_url": "https://gitea.hmac.kr/Kyeongmin/C.E.L_Slide_test2/issues/40#issuecomment-22049", "pull_request_url": "", "issue_url": "https://gitea.hmac.kr/Kyeongmin/C.E.L_Slide_test2/issues/40", "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-31 AI-assisted frame-aware adaptation (restructure / reject routes)\n\n### Root-cause framing\n\nThe route_hint metadata for `restructure → ai_adaptation_required` and `reject → design_reference_only` is already emitted (IMP-05 L2, `src/phase_z2_pipeline.py:572-577,580-584,664`) and already surfaced to the frontend (IMP-29, `Front/client/src/types/designAgent.ts:168-169` + `Front/client/src/components/FramePanel.tsx:254-268`). What does not exist is a runtime consumer that turns `ai_adaptation_required` into a real adaptation step — restructure candidates today are filtered out of direct execution (`filtered_for_direct_execution=True` at `src/phase_z2_pipeline.py:663`, MVP1_ALLOWED_STATUSES skip path at `src/phase_z2_pipeline.py:678-680`). The route_hint is \"dead-end\" metadata, exactly as IMP-17 carve-out §Activation gate condition 3 describes (`docs/architecture/IMP-17-CARVE-OUT.md:29`).\n\nKey axis identity question (must lock before Stage 2): Issue #40 is filed as IMP-31 but the source comment + carve-out doc explicitly say this axis belongs to the IMP-17 slot:\n- `src/phase_z2_pipeline.py:570` says `(deferred to IMP-17 — carve-out, AI fallback only, normal path 밖)` — corrected from a prior stale \"IMP-31\" reference by commit `e10ec36` (IMP-17 anchor sync).\n- `docs/architecture/IMP-17-CARVE-OUT.md:23` line: `신규 IMP ID 발급 (이 carve-out 은 IMP-17 슬롯에 영구 귀속)`.\n- IMP-17 backlog row 68 still marked `documented (deferred)` (`docs/architecture/PHASE-Z-IMPLEMENTATION-ISSUE-BACKLOG.md:68`).\n- The IMP-17 Stage 1 exit report (`.orchestrator/issues/17_stage_problem-review_exit.md:14,46`) explicitly bans new IMP IDs: \"신규 IMP ID 발급 (IMP-29 이상) — 본 axis 는 IMP-17 슬롯 그대로 사용\".\n\nSo Issue #40 (IMP-31) is the activation issue for the IMP-17 carve-out — the runtime work IMP-17 deferred. Either we rename / re-slot to keep registry consistency, or we lock IMP-31 explicitly as the activation tracking issue with IMP-17 as the permanent design slot. Recommend the latter (cheaper anchor surface), with the IMP-17 doc + comment updated to reference IMP-31 as the live activation issue. Codex r1 must adjudicate before Stage 2.\n\n### Verified facts (value + path + upstream)\n\n- Route_hint emission site = `src/phase_z2_pipeline.py:572-584` (`_IMP05_ROUTE_HINTS` dict + `_imp05_route_hint()`). Mapping: `use_as_is→direct_render`, `light_edit→deterministic_minor_adjustment`, `restructure→ai_adaptation_required`, `reject→design_reference_only`.\n- Route_hint consumer count (runtime) = 0. Grep `grep -rln \"ai_adaptation_required\" src/` returns only `src/phase_z2_pipeline.py` (emission) + `tests/test_phase_z2_v4_fallback.py` (assertion). No adapter / proposal / planner consumer exists.\n- Frontend reader = `Front/client/src/components/FramePanel.tsx:262-265` shows `ai req` / `ref` / `adapt` chips. IMP-29 closed this loop on the display side only.\n- Filter behavior = `src/phase_z2_pipeline.py:663` records `filtered_for_direct_execution=True` for restructure/reject; `src/phase_z2_pipeline.py:678-680` skips them with `phase_z_status_not_allowed` reason.\n- Issue cross-ref is stale: issue body cites `_imp05_route_hint()` at `src/phase_z2_pipeline.py:452` but actual line in HEAD `1efbf67` is 580 (line 452 is `force_drill_parents` sub-section drilling, unrelated). Issue body needs anchor refresh.\n- IMP-17 carve-out 3-condition AND activation gate (`docs/architecture/IMP-17-CARVE-OUT.md:25-31`):\n 1. User GO — explicit axis activation request.\n 2. B4 frame_selection evidence integration complete — Step 9 frame_selection V4 evidence integration must be stable.\n 3. IMP-04 catalog + IMP-05 V4 fallback live.\n- Gate condition status (current HEAD):\n - Cond 1 (User GO): not visible in issue body as explicit lock. Filing #40 may imply GO; needs user confirmation.\n - Cond 2 (B4 frame_selection evidence integration): NOT satisfied. `docs/architecture/PHASE-Z-PIPELINLine truncated