# UX Improvements for Navigation and Categories

## Objective
Implement a series of 5 subjective UX improvements requested by the user, focusing on the categorical navigation filters, back button behavior, and global logo routing.

## Background
The previous UX had several navigational and visual inconsistencies:
1. The `My Private Space` (My) tab lacked the category filter mechanism present in the `Knowledge Wiki` (Wiki) tab.
2. The UI of the category filter (using floating pills) felt dated and disconnected.
3. The "← 목록으로" (Back to List) button in `DocumentClient.tsx` always navigated to `/` (`Wiki` tab), confusing users viewing `My` or `Daily` notes.
4. The global `InsuWiki` logo in the header navigated to `/` which technically preserved the last used tab via client-side logic, but the user explicitly requested it force navigation specifically to the `Wiki` tab.

## Proposed Changes
### Next.js Core Pages & Components
1. **`src/app/page.tsx`**: 
   - Moved the `CATEGORY_TABS` rendering block outside the pure `activeTab === 'wiki'` check to `(activeTab === 'wiki' || activeTab === 'my')`.
   - Redesigned the JSX for the tabs from a flex-wrap wrap pill to an overflow-x-auto bottom-border Tab bar UI matching modern aesthetic standards.
2. **`src/components/GlobalHeader.tsx`**:
   - Modified the `<Link>` wrapping the `InsuWiki` text to point exactly to `/?tab=wiki` rather than `/`.
3. **`src/app/docs/[id]/DocumentClient.tsx`**:
   - Updated the `onClick` handler of the back button to evaluate `docType` and `document.visibility` to accurately inject the correct `/?tab=...` parameter before routing back.

## Verification Plan
1. ✅ **Typescript Compilation**: Run `tsc --noEmit` and confirm zero errors in the refactored code blocks.
2. 🔄 **Manual Navigation (Pending Deploy)**:
   - Click `InsuWiki` to ensure `/?tab=wiki` is triggered.
   - Enter a `My Note`, click Back, ensure `/?tab=my` is used.
   - Ensure the Category filter renders in `My Note` and correctly filters the private documents.