chore(rebar): Pier_T_rebar 작업 폴더 초기 구성 및 외부 의존 파일 통합

- Code\rebar_pipeline, review_pipeline, pier-program을 정션에서 실제 폴더로 전환
- Code\rhino_mcp 및 CLAUDE_rhino배경.md 추가, .mcp.json은 PYTHONPATH로 새 위치 사용
- pier-program 내부 .git 제거(이력은 backup\pier-program_20261028.bundle에 보관)
- worktree 가이드 반영(CLAUDE.local.md, HANDOFF.md)
- D:\Rhino-MCP 경로 참조를 새 위치로 치환

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>

context-migration/memory/feedback_rhino_connection_check.md

@@ -0,0 +1,15 @@
+---
+name: feedback-rhino-connection-check
+description: "is_server_available checks the Grasshopper socket server, not Rhino — use get_scene_info or get_layers to verify the Rhino connection instead"
+metadata: 
+  node_type: memory
+  type: feedback
+  originSessionId: 63928af6-71fe-4cd0-ac03-4b5401fe375c
+  modified: 2026-09-21T23:41:14.343Z
+---
+
+`mcp__rhino__is_server_available` checks whether the **Grasshopper** socket server is running (see `rhino_mcp/rhino_mcp/grasshopper_tools.py:280` — `GrasshopperTools.is_server_available`), not the Rhino RhinoScript connection. It returns `False` whenever Grasshopper itself isn't open, even when Rhino (`rhino_mcp_client.py`) is running fine and fully connected.
+
+**Why:** user reported "라이노 연결이 안 된다" (Rhino won't connect) after confirming `rhino_mcp_client.py` was on; `is_server_available` returned `False` but `get_scene_info` succeeded immediately after — the tool name is misleading (sounds like a general Rhino MCP check) but is Grasshopper-specific.
+
+**How to apply:** to verify the Rhino connection (not Grasshopper), call `get_scene_info` or `get_layers` directly instead of `is_server_available`. Only use `is_server_available` when actually checking Grasshopper's server.