yadflow 2.7.0 → 2.9.0

package/skills/yad-docs/templates/app/src/components/Navigation/TopNavBar.tsx

@@ -1,13 +1,12 @@
 import { useNavigate } from 'react-router-dom';
 import { Icon } from '../shared/Icon';
+import { Tooltip } from '../shared/Tooltip';
 import { useFlowStore } from '../../store/useFlowStore';
-import { useAuthStore } from '../../store/useAuthStore';
 
 export function TopNavBar() {
   const navigate = useNavigate();
   const toggleReferencePanel = useFlowStore((s) => s.toggleReferencePanel);
   const toggleCommandPalette = useFlowStore((s) => s.toggleCommandPalette);
-  const logout = useAuthStore((s) => s.logout);
 
   return (
     <header className="flex-none flex items-center justify-between whitespace-nowrap border-b px-6 py-3 z-20"
@@ -17,8 +16,9 @@ export function TopNavBar() {
       }}
     >
       <div className="flex items-center gap-8">
-        <div className="flex items-center gap-3 text-white">
-          <img src="/logo.svg" alt="Logo" className="h-8" />
+        <div className="flex items-center gap-2 text-white">
+          <img src={`${import.meta.env.BASE_URL}yadflow-icon.png`} alt="yadflow" className="h-9 w-9 object-contain" />
+          <span className="text-lg font-bold font-display text-white tracking-tight">yadflow</span>
         </div>
         <button
           onClick={toggleCommandPalette}
@@ -58,31 +58,15 @@ export function TopNavBar() {
             <Icon name="description" size={18} className="mr-2" />
             Docs
           </button>
-          <button
-            className="flex items-center justify-center px-4 py-2 rounded-full text-slate-300 text-sm font-medium transition-colors"
-            onMouseEnter={(e) => e.currentTarget.style.background = 'var(--color-surface-highlight)'}
-            onMouseLeave={(e) => e.currentTarget.style.background = 'transparent'}
-          >
-            <Icon name="settings" size={18} className="mr-2" />
-            Settings
-          </button>
-        </div>
-        <div className="h-6 w-px mx-2" style={{ background: 'var(--color-surface-highlight)' }} />
-        <div className="flex items-center gap-3">
-          <div className="text-right hidden sm:block">
-            <p className="text-sm font-medium text-white">AbdelRahman Nasr</p>
-            <p className="text-xs text-slate-400">Admin</p>
-          </div>
-          <button
-            onClick={logout}
-            title="Sign out"
-            className="h-10 w-10 rounded-full ring-2 ring-[#2f2938] flex items-center justify-center cursor-pointer transition-opacity hover:opacity-80"
-            style={{
-              background: 'linear-gradient(135deg, var(--color-primary) 0%, #a855f7 100%)',
-            }}
-          >
-            <Icon name="logout" size={20} className="text-white" />
-          </button>
+          <Tooltip content="Coming soon">
+            <button
+              disabled
+              className="flex items-center justify-center px-4 py-2 rounded-full text-slate-300 text-sm font-medium opacity-50 cursor-not-allowed"
+            >
+              <Icon name="settings" size={18} className="mr-2" />
+              Settings
+            </button>
+          </Tooltip>
         </div>
       </div>
     </header>

package/skills/yad-docs/templates/app/src/components/Reference/RulesLegendPanel.tsx

@@ -1,6 +1,7 @@
 import { motion, AnimatePresence } from 'framer-motion';
 import { useFlowStore } from '../../store/useFlowStore';
 import { Icon } from '../shared/Icon';
+import { Tooltip } from '../shared/Tooltip';
 import { MESSAGE_COLORS } from '../../data/types';
 import { MESSAGE_TYPE_ICONS } from '../../utils/iconMap';
 import { StakeholderToggle } from './StakeholderToggle';
@@ -197,17 +198,21 @@ export function RulesLegendPanel() {
                 background: 'var(--color-surface-dark)',
               }}
             >
-              <button className="flex-1 py-3 px-4 rounded-lg text-white text-sm font-bold transition-colors flex items-center justify-center gap-2"
-                style={{ background: 'var(--color-primary)' }}
-              >
-                <Icon name="download" size={18} />
-                Export Rules PDF
-              </button>
-              <button className="p-3 rounded-lg text-slate-300 transition-colors"
-                style={{ background: 'rgba(255,255,255,0.05)' }}
-              >
-                <Icon name="settings" size={20} />
-              </button>
+              <Tooltip content="Coming soon" className="flex-1">
+                <button disabled className="w-full py-3 px-4 rounded-lg text-white text-sm font-bold flex items-center justify-center gap-2 opacity-50 cursor-not-allowed"
+                  style={{ background: 'var(--color-primary)' }}
+                >
+                  <Icon name="download" size={18} />
+                  Export Rules PDF
+                </button>
+              </Tooltip>
+              <Tooltip content="Coming soon">
+                <button disabled className="p-3 rounded-lg text-slate-300 opacity-50 cursor-not-allowed"
+                  style={{ background: 'rgba(255,255,255,0.05)' }}
+                >
+                  <Icon name="settings" size={20} />
+                </button>
+              </Tooltip>
             </div>
           </motion.div>
         </>

package/skills/yad-docs/templates/app/src/components/Sidebar/PathSelector.tsx

@@ -5,6 +5,7 @@ import { useFlowStore } from '../../store/useFlowStore';
 import { PATHS } from '../../data/paths';
 import type { PathCategory } from '../../data/types';
 import { Icon } from '../shared/Icon';
+import { Tooltip } from '../shared/Tooltip';
 import { CATEGORY_ICONS } from '../../utils/iconMap';
 
 const CATEGORY_LABELS: Record<PathCategory, string> = {
@@ -51,9 +52,11 @@ export const PathSelector = () => {
         <h3 className="text-slate-100 text-sm font-bold font-display uppercase tracking-wider">
           Path Selection
         </h3>
-        <button className="text-xs font-medium" style={{ color: 'var(--color-primary)' }}>
-          View All
-        </button>
+        <Tooltip content="Coming soon">
+          <button disabled className="text-xs font-medium opacity-50 cursor-not-allowed" style={{ color: 'var(--color-primary)' }}>
+            View All
+          </button>
+        </Tooltip>
       </div>
 
       {/* Search */}

package/skills/yad-docs/templates/app/src/components/shared/Tooltip.tsx

@@ -4,14 +4,15 @@ import { motion, AnimatePresence } from "framer-motion";
 interface TooltipProps {
   content: string;
   children: React.ReactNode;
+  className?: string;
 }
 
-export const Tooltip: React.FC<TooltipProps> = ({ content, children }) => {
+export const Tooltip: React.FC<TooltipProps> = ({ content, children, className = "" }) => {
   const [show, setShow] = useState(false);
 
   return (
     <div
-      className="relative inline-block"
+      className={`relative inline-block ${className}`}
       onMouseEnter={() => setShow(true)}
       onMouseLeave={() => setShow(false)}
       onFocus={() => setShow(true)}

package/skills/yad-docs-overview/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: yad-docs-overview
-description: 'Generates the project-level SDLC-overview interactive site — the same React/Vite/Tailwind shell as the per-epic docs — showing every yadflow stage from setup → ship: the pipeline as a flow canvas, each skill/gate as a flow step, the durable .sdlc state objects as system components, and the lenses as stakeholder roles. Themed with yadflow''s own brand palette for continuity, built from config.yaml + module-help.csv + the overview diagram. Supersedes docs/index.html with a thin redirect and deploys via `yad docs deploy --overview`. This is project documentation, not a gated state — it never touches any epic''s state or approvals. Use when the user says "generate the overview site", "build the SDLC overview docs", or after the pipeline (module-help.csv / config.yaml / skill count) changes.'
+description: 'Generates the project-level SDLC-overview interactive site — the same React/Vite/Tailwind shell as the per-epic docs — showing every yadflow stage from setup → ship: the pipeline as a flow canvas, each skill/gate as a flow step, the durable .sdlc state objects as system components, and the lenses as stakeholder roles. Themed with yadflow''s own brand palette for continuity, built from config.yaml + module-help.csv + the overview diagram. Folds the legacy hand-maintained docs/index.html report into the site as report.html (linked from the nav) and deploys via `yad docs deploy --overview`. This is project documentation, not a gated state — it never touches any epic''s state or approvals. Use when the user says "generate the overview site", "build the SDLC overview docs", or after the pipeline (module-help.csv / config.yaml / skill count) changes.'
 ---
 
 # SDLC — Author the Overview Site (project-level, the pipeline as a living map)
@@ -9,7 +9,7 @@ description: 'Generates the project-level SDLC-overview interactive site — the
 reusing the same shell as the per-epic docs (`skills/yad-docs/templates/app/`). Where `yad-docs`
 animates one epic's flows, this animates the **workflow itself**: the front gates, the build half, the
 automation dial, the setup connectors. It is the regenerable successor to the hand-maintained
-`docs/index.html` overview.
+overview report, which is folded into this site as `public/report.html`.
 
 This is **project documentation, not a gated state** — there is no epic, no `state.json`, no approvals.
 It only reads the pipeline definition and writes a project-level site. When a docs target is connected
@@ -22,7 +22,7 @@ It only reads the pipeline definition and writes a project-level site. When a do
   the generated **source is committed**. The overview build manifest is `docs/sdlc-site/.docs-build.json`.
 - The shell template is `skills/yad-docs/templates/app/` — copied **verbatim**, themed only in the
   `:root` of `index.css`. Generated data satisfies `src/data/types.ts`.
-- Theme: **yadflow's own brand palette** (the `:root` of `docs/index.html`) — for visual continuity with
+- Theme: **yadflow's own brand palette** (the `:root` of the legacy report, now `docs/sdlc-site/public/report.html`) — for visual continuity with
   the existing overview, not an epic's design tokens.
 - Speak in the configured `communication_language`; write documents in `document_output_language`.
 
@@ -68,7 +68,7 @@ Map the pipeline onto the same data structures `yad-docs` uses (concrete mapping
 Copy the shell from `templates/app/` **verbatim**, generate `src/data/*.ts` deterministically (same
 determinism rules as `yad-docs`: stable-ID sort by skill pipeline order / phase, fixed key order, no
 timestamps in the data files), theme the `:root` of `index.css` from **yadflow's brand palette** — the
-`docs/index.html` `:root`: `--accent: #2471a3` and the node colors (`--artifact-*`, `--gate-*`,
+the legacy report's `:root`: `--accent: #2471a3` and the node colors (`--artifact-*`, `--gate-*`,
 `--earns-*`, `--locked-*`, `--sentinel-*`) — and substitute the Vite base from `.sdlc/docs.json`
 `basePath` (the overview sits at the base root, e.g. `/<repo>/`).
 
@@ -91,11 +91,13 @@ doc-shell upgrade triggers a rebuild). `skillCount` rides along in the manifest
 — it is **not** a separate hash input, since `module-help.csv` already moves whenever the skill set does.
 Not per-epic artifacts/repo heads.
 
-### Step 5 — Supersede `docs/index.html` (one release)
-Turn `docs/index.html` into a **thin redirect** to `docs/sdlc-site/` (e.g. a `<meta http-equiv="refresh">`
-+ a one-line link), and **note in the report** that the hand-maintained overview is superseded by the
-generated site for this release. This generalizes the standing rule that feature work hand-updates
-`docs/index.html`: the overview site now **regenerates** instead.
+### Step 5 — Fold the legacy report into the site
+Relocate the hand-maintained static report into the generated site as `docs/sdlc-site/public/report.html`
+(Vite copies `public/` verbatim into `dist/`, so it publishes alongside the app at `<base>/report.html`),
+and link it from the app nav (a "Full report" link in `TopNavBar`). The interactive overview becomes the
+primary documentation and the legacy report rides along as its detailed companion — no orphaned
+`docs/index.html` at the repo root. This generalizes the standing rule that feature work hand-updates the
+report: the overview site now **regenerates** instead.
 
 ### Step 6 — Build / deploy (`action`)
 - `action: generate` (default) — generate source + manifest; stop.
@@ -104,8 +106,8 @@ generated site for this release. This generalizes the standing rule that feature
 
 ### Step 7 — Stop. Report (no gate, no epic)
 Report: the site path (`docs/sdlc-site/`), the data files produced, that the theme is the yadflow brand
-palette, the deploy URL or "build-only", the staleness baseline, and that `docs/index.html` now
-redirects to the generated site. Never touches any epic state.
+palette, the deploy URL or "build-only", the staleness baseline, and that the legacy report is folded in
+at `public/report.html` (linked from the nav). Never touches any epic state.
 
 ## Hard rules
 

package/skills/yad-docs-overview/references/pipeline-model.md

@@ -97,6 +97,6 @@ The eight yadflow lenses, each to its relevant phase sections + paths:
 ## Determinism + theme
 Same discipline as `yad-docs`: stable-sort steps by phase then pipeline order, fixed key order, **no
 timestamps** in `src/data/*.ts` (build time lives only in `.docs-build.json`). Theme the `:root` from
-**yadflow's brand palette** (`docs/index.html` `:root`): `--accent: #2471a3`, and carry the node-class
+**yadflow's brand palette** (the legacy report's `:root`): `--accent: #2471a3`, and carry the node-class
 colors through to step/path colors — `--artifact-* #b7950b`, `--gate-* #ca6f1e`, `--earns-* #2471a3`,
 `--locked-* #566573`, `--sentinel-* #1e8449` — so the canvas reads like the existing diagram.

package/skills/yad-hub-bridge/references/login-roster.md

@@ -3,6 +3,7 @@
 The roster lives in `.sdlc/hub.json` (`roster: [...]`) and is the only thing that turns a platform
 **login** into an SDLC **name + role** for the ledger. Schema and the no-tokens rule are documented once
 in `../../yad-connect-repos/references/hub-config.md`; this file covers how the bridge *uses* it.
+It is populated/edited any time with the `yad roster` CLI command (see that reference).
 
 ## Entry