2 Commits

Include renames

Author	SHA1	Message	Date
ducoterra	872a07cee7	feat(ui): rename nav items — "Sources" becomes "RAG", "Git sources" becomes "Sources" ... Owner request (2026-08-28): the two admin-only nav items read like the same thing, so they are relabeled — the document-catalog link (#nav-sources, /sources.html) becomes "RAG" and the source-manager link (#nav-git-sources, /git-sources.html) becomes "Sources". Phase 48 (48_nav_rename_sources), label-only per the locked decision: - all six pages (index, sources, git-sources, tuning, document, login): the two <a> texts swap; ids, hrefs, hidden defaults, is-active / aria-current placement, and nav order (Chat, RAG, Sources, Tuning) are byte-unchanged otherwise. - header.js: comment/docstring label mentions only — the reveal-by-id logic is untouched (ship-hidden/reveal contract intact). - test_git_sources_admin.py / test_mobile_hamburger_nav.py: the two suites that asserted the old label text are updated; comment-only label fixes in test_shared_header.py / test_nav_consistency.py. - tests/e2e/test_nav_rename_sources.py: the story E2E (green in isolation) — renamed labels + unchanged hrefs/order/markers on all six pages, click navigation with the active marker, the anonymous ship-hidden contract, and regression guards for the untouched controls (#sync-label "Sync sources", viewer #doc-back "Sources"). - All eight surrounding header/nav suites stay green in isolation; unit+integration green, app/ coverage 99% (frontend-only change), ruff + pyright clean. Note: per this phase file-level staging, the six page files and header.js also carry the same-day in-flight owner rework that was already in the working tree when phase 48 ran (mobile sign-in dropdown copy, sync button ship-hidden on the Sources page); the label rename itself is the two-text swap on each page.	2026-08-28 12:33:18 -04:00
ducoterra	6be692d999	feat(header): hamburger dropdown nav on mobile (owner permission) ... TODO.md L9 (owner permission 2026-08-27, roadmap A5): "The navbar on mobile is way too squished. Make it a hamburger dropdown menu with a nice animation." At <=640px the nav links leave the bar — a 44px #nav-toggle opens #app-nav as an animated (180ms slide+fade) edge-to-edge dropdown with comfortable rows and the auth visibility contract intact inside the menu; at >640px the bar is byte-identical to pre-phase-46 (hamburger absent, inline pills as before). - frontend/*.html (all six pages): the shared bar gains the #nav-toggle button (type=button, aria-expanded=false, aria-controls="app-nav", aria-label="Menu", aria-hidden 3-line SVG icon) immediately before the nav, and the nav gains id="app-nav" — one <nav>, no duplicated links, so the whoami reveal works inside the menu unchanged (phase-34 same-bar contract intact). - frontend/assets/styles.css: .nav-toggle is display:none outside media queries (desktop untouched); the <=640px block adds the 44px toggle (+hover in the .steering-toggle:hover family, sized 20px icon), turns .app-nav into the dropdown (absolute top:100% edge-to-edge under the sticky header, surface + hairline + --shadow-lg, z-index 21 = header+1, closed state invisible + non-interactive with the 180ms opacity/transform/visibility-delayed pair, .is-open the only opener), and comfortable 1rem/0.75rem menu rows — superseding the phase-34/35 pill-squeeze rules for .nav-link/.app-nav (the 900px tablet block, action pills, and 58px bar height untouched). The reduced-motion block stills BOTH the closed and .is-open states: the .is-open rule (0,2,0) out-specifies a bare .app-nav (0,1,0), so the override must name both — verified live in Chromium (task 03). - frontend/assets/header.js: ONE module-owned binding (import-time, null-safe like the sign-out binding): click toggles .is-open + aria-expanded in sync, a delegated nav-link click closes, Esc closes and refocuses the toggle, and matchMedia("(max-width: 640px)") change drops the state on resize back to desktop. The binding touches only the container — ship-hidden whoami links stay hidden. - tests/unit/test_hamburger_nav.py (new): the markup/CSS/JS contract pins (six identical toggles in the shared row, desktop byte- identical, dropdown + .is-open + 180ms + reduced-motion rules, the superseded squeeze rules gone, the one-binding behavior). - tests/e2e/test_shared_header.py: assert_shared_bar gains mobile=True (at <=640px the bar shows the hamburger + the closed nav; the per-role menu contents are pinned by the story suite). - tests/e2e/test_mobile_hamburger_nav.py (new, story suite, 375x812): toggle is a visible >=44px target, menu closed (opacity 0 / visibility hidden), no horizontal overflow; anonymous menu shows exactly "Chat" (admin-only links stay hidden inside); admin menu shows all four links (whoami reveal inside the menu); a link click navigates + the arrival page ships closed; Esc closes and refocuses the toggle (outside click does NOT close — accepted: the locked close set is Esc + link + resize, no backdrop); the 180ms opacity/transform pair is live and reducedMotion:reduce stills both states with open/close still working; 1280x800 regression — toggle display:none, all four inline links inside the header band. Gates: unit+integration 773 passed; app/ coverage TOTAL 99% (unchanged — frontend-only phase); story E2E 7 passed in isolation (mock LLM, DB up); regression suites test_nav_consistency (6) / test_header_consistency (3) / test_shared_header (6) / test_responsive_polish (7) / test_tuning_nav_link (4) all pass in isolation; ruff check + pyright clean. A11 honored: no CDN, no new assets. Also records the 46_mobile_hamburger_nav todo/ -> complete/ move.	2026-08-28 06:07:02 -04:00