diff --git a/.agent/references/repository-rules.md b/.agent/references/repository-rules.md index c7ba0b4..79f1e7b 100644 --- a/.agent/references/repository-rules.md +++ b/.agent/references/repository-rules.md @@ -180,7 +180,7 @@ - User approved: userRole 1001 has no authenticated-team/assignment limit in project list/summary. This intentionally unifies legacy admin 0 and DCO 1. Existing business search/exclusion filters still apply. - Controller RequestUserContext is authoritative for role/team/id for JWT and API Key. No permission enums/grants or user-submitted authorization claims. Missing project identity metadata fails instead of broadening visibility. -- Preserve current frontend v2 KON/KIWI list branching for other roles: team != M101 excludes GKEY M101; R-prefixed teams additionally require own GKEY; team M101 list has no extra team filter. Summary: M101 team only own GKEY, all other teams exclude M101, and (user decision 2026-10-22, replacing the legacy else-if) R-prefixed teams additionally require own GKEY, matching the list. +- Preserve current frontend v2 KON/KIWI list branching for other roles: team != M101 excludes GKEY M101; R-prefixed teams additionally require own GKEY; team M101 list has no extra team filter. Summary: M101 team only own GKEY, all other teams exclude M101, and (user decision 2026-10-22, replacing the legacy else-if) R-prefixed teams additionally require own GKEY, matching the list. Per the same user decision, summary candidates also apply the list's title NOT LIKE '%사례비%' and status IN (2, 3) before TOP 50; the list's date/surveyclass/must-view window is intentionally not added. - Role 9001 additionally intersects REPORT_ASSIGN by exact member_mail=verified userId. Query the kart session (Report DB) once per request for both survey sources, do not add is_use (not used by original), do not append email domains, and empty assignments return no rows. REPORT_MEMBER emits exact member_mail as userId; other authentication also uses verified userId verbatim. - Apply team/assignment before candidate TOP 50 and ordering, never after Java merge/TOP 6. Must-view does not override authorization. Linked list retains its business query team and adds separately named authenticated-team/role/assignment constraints. - Derived management list: role 1001 sees all project definitions; others see matching GKEY only. Keep normal questions/report metadata unfiltered by this management rule. diff --git a/src/main/resources/mybatis/mapper/ProjectMapper.xml b/src/main/resources/mybatis/mapper/ProjectMapper.xml index 6b09279..d5c1e5e 100644 --- a/src/main/resources/mybatis/mapper/ProjectMapper.xml +++ b/src/main/resources/mybatis/mapper/ProjectMapper.xml @@ -82,6 +82,8 @@ SELECT TOP(50) * FROM PROJECT WITH(NOLOCK) WHERE JSON_VALUE(JSON_QUERY(PROJECTJSON, '$.must'), '$.status') != 1 AND JSON_VALUE(PROJECTJSON, '$.must.companytype') NOT IN ('4', '5') + AND JSON_VALUE(PROJECTJSON, '$.must.title_inner') NOT LIKE '%사례비%' + AND JSON_VALUE(PROJECTJSON, '$.must.status') IN (2, 3) ORDER BY create_date DESC