AI-Cognitive-Leap/agnes-the-ai-analyst
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
agnes-the-ai-analyst/app/web/templates/catalog.html
Vojtech 001e5ce40e
feat(web): /home value-first redesign + unified page-shell across app (#366) 
* feat(web): value-first /home reskin (CEO mock palette + pillars + first-session)

Restructures `/home` to lead with product value instead of install steps,
matching the CEO mock proposed for the homepage:

- New intro hero on top — eyebrow `Welcome, {{ display_name }}`, H1
  `{{ instance_brand }} is your team's AI workspace`, lede framing the
  product as an "AI Chief of Staff", two CTAs (`Set up in ~15 min →`
  jumps to the wizard, `Just browse — no install needed` jumps to
  `#look-around`), and a four-pillar row (Data packages · Plugins ·
  Skills · Memory). Renders for both onboarded and not-onboarded users
  so the value framing is consistent across visits.
- New `first-session` narrative — five-beat walkthrough (launch → pick
  project → memory loads → ask → close) with mock terminal frames
  carrying traffic-light dots, prompts, and dimmed system output.
- Setup wizard chrome — progress chip (`Step 1 of N · ~15 min ·
  One-time · Reversible`), thin progress bar, and per-step number
  badges on each `.install-block` so the wizard reads as bounded
  instead of an open-ended scroll.
- Palette shift from blue to green/navy: `--hp-primary` aliases
  `#2ea877` (mint), `--hp-hero-bg` is navy `#0f1b3a`, code panels stay
  near-black `#0c1224` with warm-yellow `#ffd866` accents. The token
  alias is reused so downstream rules pick up the new accent
  automatically; instance theme overrides via
  `config.theme_overrides()` still win.
- VS Code surface tile carries a `Recommended` pill; the existing
  "Want to look around first?" section is renamed to `Explore your
  workspace` and gets the `#look-around` anchor.

All test-pinned class names and IDs (`install-hero`, `install-block`,
`home-mock`, `self-mark-btn`, `setupClaudeBtn`, `offboard-strip`,
`home-getting-started`, `home-gs-item`, `home-overview`,
`home-usage`) preserved as structural anchors; new visual language
overlays via additional classes. Existing onboarded/not-onboarded
branching, `/api/me/onboarded` POST, status frame gating, post-CTA
modal, and OS-tab switching JS unchanged. Stray `~/FoundryAI`
comment swapped for `~/{{ workspace_dir }}` to honor the
vendor-agnostic OSS rule.

51 home tests pass without modification.

* fix(web): /home palette inversion — dark intro hero on top, light setup card below

Previous reskin commit kept the install-hero as a dark navy gradient and
rendered the new intro hero as a light surface — opposite of what the CEO
mock specifies. Playwright comparison vs `data/ceo_home.html` confirmed:

- CEO mock: dark navy hero at TOP (with white pillars on navy), LIGHT
  white setup card BELOW with light step rows and dark code panels
  inset.
- Previous: light intro hero on top, dark setup card below. Inverted.

This patch flips both:

- `.home-hero-intro` now: dark navy gradient `#0f1b3a → #1a2a5f`, green
  radial glow in the corner, green eyebrow, white H1 (`accent` span
  green), rgba-white lede, green pill primary CTA, translucent-white
  secondary CTA, pillars row separated by hairline border-top with
  green square-dot bullets in front of each pillar header.
- `.install-hero` and `.install-block` now: white surface card with
  thin green accent strip across the top, light step rows split by
  hairline borders, green-tinted step-number circles (`#e6f9f0` bg,
  `#1f8a5e` ink), green progress chip + bar. Code panels
  (`.install-cmd`) and terminal frames stay dark — they're the "type
  this" surfaces.
- All previously-rgba-white descendants of `.install-hero`
  (close button, eyebrow, h1, lead, links, code chips, OS tabs,
  install notes, setup-CTA button, self-mark fallback, auto-detect
  badge, terminal-howto disclosure) re-skinned for light surface.

All 12 home page tests still pass (no markup changes, only CSS).

* fix(web): /home parity polish — system font + mock sizes + blue info hint + gray step-num

After v2 palette flip, user comparison vs CEO mock surfaced three
remaining gaps in the wizard area:

- Font stack mismatch: Agnes inherits Inter via `style-custom.css`,
  but the CEO mock uses the platform system stack (San Francisco on
  macOS, Segoe UI on Windows). The rendered weight/letterforms read
  noticeably different. `.home-mock` now declares
  `-apple-system, BlinkMacSystemFont, "Segoe UI", Roboto, sans-serif`
  for itself and all descendants, with the monospace stack reserved
  for `code`/`kbd`/`pre`, `.install-cmd`, and `.terminal-body`.
- Step number badges were green-tinted; mock uses neutral gray
  (`#f0f2f6` bg, `#4a5168` ink) — green is reserved for the "done"
  state. Switched to `--hp-surface-dim` + `--hp-text-secondary`.
- "Don't have a terminal open?" disclosure was an amber/yellow
  variant left over from the old dark-hero palette. Mock uses a
  blue info-hint vocabulary (`--info-bg: #eef3ff`,
  `--info-line: #4f7cf2`, `--info-ink: #1c3994`) with white kbd
  chips. Added the info-* tokens to the `:root` block and re-skinned
  `details.terminal-howto` (incl. summary, body, kbd) to match.

Step-body type sizes also brought in line with the mock spec —
`.install-block .label` (step h3 equivalent) is now 17px / 700 with
6px gap; `.install-note` body type is 14px / 1.55.

`--hp-info-bg / --hp-info-ink / --hp-info-line / --hp-warn-bg /
--hp-warn-ink / --hp-warn-line / --hp-surface-dim` added as
first-class tokens so future hint/warn callouts pick the same colors
without a duplicate vocabulary.

12/12 home tests pass.

* feat(web): centralize design tokens + reword /home wizard to 6 steps (CEO mock parity)

Two intertwined changes that touch both global design + /home structure:

GLOBAL TOKEN SHIFT (app/web/static/style-custom.css)
- `--primary` flipped from blue `#0073D1` to green `#2ea877` — same brand
  alias the rest of the app referenced, so every page picks up the new
  accent automatically. Old `--primary-dark` / `--primary-light` recolored
  to match.
- New tokens added: `--brand-accent`, `--hero-bg`, `--hero-ink`,
  `--surface-dim`, `--info-bg/ink/line`, `--warn-bg/ink/line`. Brings
  the global vocabulary in line with the CEO mock's `:root` block so
  callouts and hero surfaces don't have to invent local tokens.
- `--font-primary` switched from Inter-led stack to the system stack
  (`-apple-system, BlinkMacSystemFont, "Segoe UI", Roboto, "Inter",
  system-ui, sans-serif`) so weight/letterforms render identically on
  macOS (San Francisco) and Windows (Segoe UI) — matches the mock and
  avoids a font-loading flash for analysts without Inter installed.
- Shadow tints re-cast in navy `rgba(15,27,58,...)`; focus ring uses
  the new green `rgba(46,168,119,0.25)`.
- `.app-nav-link` font-size 13px → 14px, padding 6px 12px → 8px 14px,
  hover bg → `--primary-light` (mint), color → `--primary-dark`.
  `.app-nav-menu-item.is-active` re-tinted to the same green system.
- Sweep across 26 templates (style-custom.css + 25 template files)
  replacing every hardcoded `#0073D1` / `#005BA3` / `#E6F3FC` /
  `rgba(0,115,209,…)` / `rgba(0,86,163,…)` with token references or
  the new green hexes — 175 occurrences total. Pages that styled their
  own buttons / borders / shadows pick up the new brand color without
  per-page overrides.

/HOME WIZARD: 6 STEPS PER MOCK (app/web/templates/home_not_onboarded.html)
- Step 1 reworded `Install Claude Code on your computer` + `~3 min`
  subhead (mock copy).
- Step 2 renamed `Pick a folder for {{ instance_brand }}` (was
  `create your workspace folder`) — same `mkdir` command, mock-aligned
  framing.
- NEW Step 3 `Open a terminal inside that folder` — no shell command,
  just the "you are standing in the right directory" reassurance with
  a Finder/PowerShell/file-manager howto disclosure. Mirrors the CEO
  mock's Step 3.
- Step 4 (was Step 3, gated by `home_automode.show`) renamed
  `Launch Claude with auto-approve on`. Body copy lightly updated so
  it references "the next step" instead of "Step 4".
- Step 5 (was Step 4) renamed `Get the install script and paste it
  into Claude`. The setup-cta-lead now explicitly says
  "pasting the script into Claude Code will install {{ instance_brand
  }}…" so existing test assertions pinning the `install Agnes`
  substring still match.
- NEW Step 6 `Optional: create a one-word shortcut for next time` —
  prints an `echo 'alias {{workspace_dir|lower}}=…' >> ~/.zshrc`
  one-liner for Unix and an `Add-Content $PROFILE …` equivalent for
  Windows. OS tabs + copy buttons reuse the existing wizard chrome.
- Progress chip dynamic: `Step 1 of 6` when home_automode is on,
  `Step 1 of 5` when off. Progress bar fill `100 // total_steps` so
  the bar sits at 16-20 % on first paint.
- `.step-lede` token added for the new short body copy beneath each
  step label (14.5px / ink-soft).
- `macOS / Linux / WSL` tab labels changed to `macOS / Linux` per
  user instruction. Terminal-howto `WSL:` paragraph dropped; the
  paste-shortcut hint now reads `(Linux)` instead of `(Linux/WSL)`.
  Functional WSL handling in `connector_prompts.py` (it's a Linux
  detection fallback, not user-facing label) preserved.
- `setup_instructions.py` Claude Code install hint:
  `npm (Linux / WSL)` → `npm (Linux)`.

SURFACES — 4 CARDS PER MOCK
- Replaced the 3-tile `.home-usage-grid` with a 4-card grid:
  - VS Code (Recommended) — `.surface-card.feature`, green ring,
    DAILY USE eyebrow + 5-step numbered list + `Open VS Code setup
    guide →` link to `/setup-advanced#vscode`.
  - Terminal — QUICK ACCESS eyebrow + 4-step list.
  - Claude Code (Desktop app) — CONNECT IT eyebrow + 4-step list.
  - Cowork (claude.ai) — `.surface-card.incomplete`, warn-tinted
    border + `Instructions needed` badge + a TODO callout describing
    the missing content. The card is intentionally honest about the
    gap rather than hiding it.

TEST UPDATES
- `test_web_home_page.py` negative onboarded-state assertions
  rebased on the new step labels (6 entries instead of 4).
- `test_home_route_resolution.py` `test_home_renders_automode_block_by_default`
  + its `_when_env_off` counterpart now check the new
  `Step 4 — Launch Claude with auto-approve on` label.

* fix(web): /home section content + layout — verbatim mock match

User comparison flagged several remaining gaps; this patch rewrites
the three lower sections of /home to match the CEO mock spec exactly:

FIRST-SESSION (5 beats)
- h2 28px / 700 / -.5px tracking (was 19px / 600).
- lede 18px ink-soft (was 13.5px secondary).
- `.session-walk` wrapper, 36px gap between beats (mock spec).
- `.session-step` grid 48px / 1fr, gap 22px — number circle on
  the left, content on the right.
- `.session-num` 40 × 40 circle with SOLID GREEN bg (`--primary`)
  and WHITE text + soft green shadow (was 28px mint pill w/
  dark-green text).
- `.session-content h3` 18px / 600 (was 14.5px / 600).
- `.session-content > p` 15px.
- `.session-content .annotation` 13.5px ink-muted body type with
  `strong` for highlighting (replaces the upper-case "WHAT'S
  HAPPENING" eyebrow pattern that didn't match the mock).
- `.session-intro` callout card (white surface + mint icon block)
  framing the "five beats" tagline.
- `.session-tldr` summary box (brand-light bg + brand-dark left
  border) wrapping up the loop.
- Terminal frames re-skinned: `#0c1224` body / `#182241` bar /
  real macOS traffic-light colors `#ff5f57` / `#febc2e` / `#28c840`.
- Terminal body 13px / 1.65 line-height with mock-spec class
  vocabulary: `.you` (yellow input), `.ai-name` (brand bold),
  `.path` (light blue), `.dim` (translucent code-ink), `.caret`
  (blinking cursor).
- Five beats rewritten with mock's exact narrative flow (launch →
  menu → pick → ask → close), vendor-agnostic project names
  (`RevenueAnalysis`, `Onboarding`, etc.) replacing the customer-
  specific `GRPN_*` examples in the mock. Templated `{{
  instance_brand }}` / `{{ workspace_dir }}` / `{{ workspace_dir |
  lower }}` (the shortcut alias) everywhere.

SURFACES (4 cards)
- The section is no longer wrapped in a white rectangle; the
  `.home-usage` class loses its bg + border + padding (mock has the
  cards directly on the page bg).
- h2 28px (was 22px). Eyebrow 12px / 1.5px tracking / brand-dark.
- `.surface-card.feature` (VS Code) now uses 2px green border +
  vertical brand-light → white gradient (was 1px ring).
- `.surface-card.incomplete` (Cowork) uses 2px red border (`#e35e5e`)
  + vertical red-tint → white gradient (was yellow flat bg).
- `.surface-card .steps` panel: inner surface-dim bg + 8px radius
  + 13px font.
- `.surface-foot` top-border + ink-muted (mock spec).
- `.badge-warn` now a solid red box (`#e35e5e` bg + white ink + 4px
  radius) instead of a yellow pill, matching the mock.
- Header layout fixed: the global absorbed `header { display: flex;
  justify-content: space-between }` rule was making the h2 sit on
  the right of the eyebrow; explicit `display: block` override on
  `.home-mock section > header` puts the title on the LEFT under
  the eyebrow as the mock has.

BROWSE — Explore your workspace
- Wrapped in `<section class="browse-section">` with proper
  eyebrow + h2 + lede (was a bare `.section-label` div).
- `.browse-grid` 5-col grid (was responsive auto-fill, 4-card
  layout). Skills tile added as a 5th card linking to
  `/marketplace?type=skills`.
- `.browse-card` mock-spec: 22 20 padding, 28px icon, 15px title,
  12.5px ink-muted desc, hover lifts -2px with brand border +
  shadow-md.

Section wrappers (`.home-usage`, `.first-session`) no longer carry
the white card chrome — they sit directly on the page bg, matching
the mock. Only Getting Started + Overview keep their white cards.

GLOBAL eyebrow vocabulary (`.home-hero-intro .eyebrow`,
`.first-session > .eyebrow`, `.surfaces > header .eyebrow`,
`.browse-section .eyebrow`) all aligned to mock spec: 12px / 700 /
1.5px tracking / brand-dark color / 14px bottom margin.

Hero h1 bumped to 44px / 800 / -1px tracking (was 32px / 600).

51/51 home tests pass.

* fix(web): /home session-intro card + terminal-body verbatim mock match

User comparison flagged three remaining /home gaps; this patch
addresses each:

- `.session-intro` rule was missing — the "five beats" tagline
  rendered as a bare line with no card chrome. Added the mock-
  spec card: white surface, 14px radius, 20×24 padding, 1px
  border + shadow-sm, with a 44×44 brand-light icon block on the
  left.

- Beat 1 terminal-title was `~/{{ workspace_dir }} — zsh` (mock-
  style shell-pwd format), but the user wants every terminal
  frame across all 5 beats to read `claude — {{ instance_brand }}`.
  Updated.

- Terminal-body line structure for beats 2-5 rewritten verbatim
  from the CEO mock:
  - `<span class="prompt">&gt;</span><span class="you">…</span>`
    now has no space between the prompt and user input (mock
    pattern: zero gap, the .prompt's `margin-right: 8px` provides
    the visual separation).
  - Beat 2 menu items use `<strong>[N]</strong>` numbering with
    project entries on indented lines, each project name followed
    by a `<span class="dim">(N ago)</span>` timestamp at a fixed
    column — instead of my prior single-line concatenation.
  - Beat 3 narrative split into 4 stanzas separated by blank lines
    (matches mock): the "Switched to <strong>X</strong>" status,
    then dim Loaded/Last-session lines, then a stand-alone "One
    unprocessed input detected:" pair, then the "Want me to
    process …" question. My prior version dim-wrapped the entire
    block, which looked off.
  - Beat 4 narrative split into headline summary + risks section
    with <strong> heads + bullet lists separated by blank lines,
    matching the mock's "Q1 close summary" / "Open risks" rhythm.
    The Q1 question carries the mock's manual line-break + 2-
    space continuation indent inside the `.you` span — without
    that, terminal-body's `white-space: pre-wrap` would auto-wrap
    awkwardly at a different column than the mock.
  - Beat 5 exit narrative uses two separate dim lines + a
    standalone `.ai-name` "See you next time." line, then prompt
    + caret. My prior version collapsed everything into one dim
    block.
  - Project names changed from customer-specific (`GRPN_*`) to
    generic (RevenueAnalysis, WeeklyReview, Onboarding, OpsDb,
    HRHandShake) so the OSS distribution stays vendor-agnostic
    per CLAUDE.md.
  - `Marketing plan` examples replaced with `Q1 close` so the
    narrative stays plausible for an analyst audience.

12/12 home tests pass.

* fix(web): /home surfaces verbatim mock — VS Code thumb, Terminal expected-output, NEW badge

User comparison flagged three remaining surface-section gaps:

- VS Code surface card was rendering a generic "Screenshot pending"
  placeholder; the mock has a labeled inline mockup
  (`<a class="vscode-thumb">` w/ `.thumb-fallback`) showing the
  recommended 4-pane layout (EXPLORER yellow, TERMINAL 1 purple,
  TERMINAL 2 green, TERMINAL 3 orange) on a dark navy bg + a
  "Recommended layout" caption pill. CSS `.vscode-thumb` block
  added — uses gradient-strip backgrounds to draw the colored
  panel bars without needing a base64 image.

- "Recommended" badge was a pill (999px radius) with
  `--brand-accent` bg + navy text. Mock uses `.badge` instead of
  `.recommend-pill` — solid `--primary` (brand-dark green) bg
  with WHITE text and 4px radius. Replaced the class + CSS rule
  so the badge reads as a tag, not a pill.

- Terminal surface card was missing the "What you should see"
  subsection — mock has an `.expected-output` block showing a
  sample of the welcome menu inside a dim dashed panel. Added the
  block with the mock's exact rendered output (templated to
  `{{ instance_brand }}` + generic project names instead of
  customer-specific GRPN entries) plus the `.expected-output`
  CSS (surface-dim bg + dashed border + `::before` "WHAT YOU
  SHOULD SEE" eyebrow per mock spec).

Also addressed the explore-section feedback:

- Skills browse-card now carries the `new` class so it picks up
  the `.browse-card.new::after` corner badge ("NEW", green bg,
  white text, 10px / 700 / 0.5px tracking) per mock.
- Browse cards align same height via `align-self: stretch` (grid
  default) + `flex-grow: 1` on `.browse-desc` so descriptions
  fill remaining vertical space; previously the Skills tile sat
  shorter because its desc text was longer than others'.

Structural HTML changes to all four surface cards: dropped the
inner `<div class="surface-card-head">` wrapper + `<p
class="surface-pitch">` class in favor of mock's flat layout
(`.what` + `.steps` + `.when-to-use`). `<ol class="surface-steps">`
replaced with `<div class="steps"><strong
class="steps-eyebrow">DAILY USE / QUICK ACCESS / CONNECT IT</strong>
<ol>...</ol></div>` so the eyebrow + numbered list share the
mock's tinted surface-dim panel.

12/12 home tests pass.

* fix(web): align /home setup walkthrough to design spec

- Setup-section header (eyebrow + heading + lede) floats above the
  install hero; install card has no accent strip; step labels drop
  `Step N —` prefix; closing strip is single flex row.
- VS Code surface card renders recommended-layout screenshot from
  `/static/img/vscode-layout.png` with click-to-enlarge lightbox.
- Workspace install path cascades to `~/Desktop/{workspace_dir}` in
  every step, surface card, first-session annotation, and shortcut.
- Step 1 verify text restores Enterprise — Finance and Legal option.
- Step 6 shortcut installs a shell function with arg forwarding
  (`"$@"` unix / `@args` windows) and a user-facing Auto / YOLO
  permission-mode toggle.
- Step 5 manual-fallback details inline on the CTA row; description
  reads at step-lede size, not 13px chip.
- Setup-section heading no longer right-aligns (was inheriting
  `header { display: flex; justify-content: space-between }` from
  the legacy stylesheet; wrapper changed to `<div>`).
- Getting Started `<details>` block removed (duplicated links).

* test(web): align /home tests with restructured setup wizard

- Replace test_getting_started_card_renders_on_home with
  test_setup_section_renders_for_not_onboarded — asserts the new
  setup-section-header floats above the install hero and Getting
  Started markup is absent (block removed in the prior commit).
- Update automode-block test to match labels without the
  `Step N —` prefix.
- Update setup-CTA partial test to match the relabeled
  "Copy install script to clipboard" button.

Drop orphaned CSS for `.home-getting-started`, `.home-gs-summary*`,
and `.home-gs-item` — selectors had no matching markup after the
Getting Started block was removed.

Also: Step 3 `pwd` expected-output uses an absolute path
(`/Users/yourname/Desktop/{workspace_dir}`) instead of the
tilde-prefixed form, matching what the command actually prints.

* fix(web): repaint home_onboarded + setup_advanced; align CTA label

- home_onboarded + setup_advanced still carried the retired blue
  `#0056A3` as both `--hp-primary-dark` and the hero gradient
  endpoint. Both reference `var(--primary-dark)` now so the green
  palette cascades.
- setup_advanced YOLO snippet was the old `alias` form (no cd, no
  arg forwarding). Replaced with the shell function variant from
  /home Step 6 — drops into ~/Desktop/{workspace_dir} and forwards
  "\$@" (unix) / @args (Windows).
- setup_advanced ~/{workspace_dir} path references cascaded to
  ~/Desktop/{workspace_dir} so install story matches /home.
- Dashboard's "Setup a new Claude Code" button label aligned to the
  canonical "Copy install script to clipboard" — matches /home and
  the new docstring in _claude_setup_cta.jinja, which now mandates
  this label across consumers.

* fix(web): keep base brand blue; scope green palette to /home redesign

User noticed login + dashboard had turned green when the /home
redesign flipped --primary from blue (#0073D1) to green (#2ea877)
in commit 278f202e. The brand-wide flip went further than the
redesign needed — only /home, /home (onboarded), and /setup-advanced
intentionally use the green/navy spec; every other page (login,
dashboard, catalog, marketplace, admin, profile) was just inheriting
the green because --primary cascaded everywhere.

Revert the global brand colour to blue and lock the green into the
two outstanding redesign scopes:

- style-custom.css: --primary back to #0073D1, --primary-light back
  to rgba(0,115,209,0.1), --primary-dark back to #005BA3,
  --brand-accent back to a lighter blue.
- home_onboarded.html: .home-mock now sets --hp-primary,
  --hp-primary-dark, --hp-primary-light to explicit green hex
  (matching home_not_onboarded), so the hero stays green regardless
  of the global brand.
- setup_advanced.html: same lock — .advanced-mock pins the green
  palette in-scope.

Hero gradients on both pages now reference the local --hp-primary
chain (not the global --primary), so any future palette tweak inside
either scope cascades correctly without disturbing the rest of the app.

* refactor(web): hoist --hp-* into shared design-tokens.css (--ds-*)

PR 2 of the design-system extraction ladder. Pure mechanical rename
+ dedup; no visual diff on any rendered page (verified on /home,
/dashboard).

- New app/web/static/css/design-tokens.css declares the full token
  set on :root: brand surface (green primary, primary-dark, mint
  light, brand-accent), hero (navy bg + ink), code-panel (near-black
  bg + cool ink + warm-yellow), light surfaces (bg/surface/border),
  text (primary/secondary/muted), orange accent, info + warn
  callout vocabularies, navy-tinted elevation shadows, system font
  stack + mono.
- base.html loads it alongside style-custom.css so the tokens are
  globally available.
- Rename --hp-* -> --ds-* in home_not_onboarded (313 refs),
  home_onboarded (15), setup_advanced (39). 367 token references
  pointed at one of three local blocks; now all point at the
  global :root.
- Drop the three local token blocks. Each scope class
  (.home-mock / .advanced-mock) only keeps its base ink + font-size
  + line-height rules.

The legacy --primary family stays canonical for the blue base
brand — login, dashboard, catalog, marketplace, admin still read
blue. The design system is opt-in via the scope class.

* refactor(web): extract shared components.css; migrate /home markup

PR 3 of the design-system extraction ladder. First batch of
reusable components lifted out of home_not_onboarded.html into a
new shared stylesheet; markup migrated to consume them.

- New app/web/static/css/components.css with five components, all
  reusable on any page that loads design-tokens.css:
    .callout-rec        — amber lightbulb recommendation box
    .callout-hint       — blue info hint box
    .code-output        — "WHAT YOU SHOULD SEE" terminal output block
    .lightbox           — full-bleed image enlarge overlay
    .setup-section-header — wizard header (eyebrow + h2 + lede)
- base.html loads components.css after design-tokens.css.
- home_not_onboarded.html markup renamed:
    class="rec"             -> class="callout-rec"
    class="hint"            -> class="callout-hint"
    class="expected-output" -> class="code-output"
- Local CSS rules removed from home_not_onboarded.html for each of
  the extracted components — ~150 lines down to 5-line "extracted to
  components.css" comments. The bespoke wizard-specific styles
  (.install-cmd, .os-tabs, .mode-tabs, .terminal-frame) stay
  template-local for now since they only have one consumer.

Visual regression check: /home install hero renders the amber rec
callout, blue hint callout, dashed code-output block, green section
header, and click-to-enlarge VS Code thumb identically to the
pre-extraction render. 43 home tests pass.

* fix(web): unify page-headers — activity-center full-width, marketplace shares box

- /activity-center audit-log hero rendered as half-width because the
  _page_hero include was inside <header class="obs-topbar">, a flex
  row that pinned the time-range + auto-refresh controls next to it.
  The hero is now a sibling rendered before the <header>, so it
  spans the full container width like every other admin page; the
  controls keep their flex row underneath.
- Marketplace hero unified with .page-header--hero. Markup is now
  <section class="page-header page-header--hero mp-hero"> so the
  shared box drives padding/radius/gradient/max-width/shadow; the
  .mp-hero override block only carries the right-anchored cover
  image and the rules for the search row + scope checkboxes (which
  the canonical hero doesn't have). Inner text uses the canonical
  .page-header__eyebrow / __title / __subtitle classes.
- .page-header--hero shadow tint now follows the brand blue
  (rgba(0, 115, 209, 0.2)) instead of the leftover green from the
  prior palette flip; same depth highlight everywhere the gradient
  is blue.

* fix(web): unify remaining page heroes — admin, profile, install, store, stack

Sweep across pages that carried bespoke gradient hero markup so
every page-hero shares the canonical `.page-header--hero`
dimensions (padding 28/32/24, border-radius 14, max-width
var(--width-app), navy-tinted shadow, gradient with --primary →
--primary-dark). Inner text uses the .page-header__eyebrow /
__title / __subtitle classes so typography matches across the app.

- admin_tables: migrated to _page_hero.html include.
- admin_tokens: kept .tokens-hero wrapper for the counts-chip row
  but added the canonical class on the same element; stripped
  duplicate gradient + padding + typography rules.
- install: same pattern (kept hero-meta pill row).
- profile: migrated to _page_hero.html include.
- store_upload: kept .upload-hero wrapper for the .meta chip row;
  composite class with the canonical hero.
- setup_advanced: .advanced-mock .ad-hero now matches canonical
  dimensions; green palette retained via --ds-primary/dark.
- stack_card.css: .stack-hero (catalog + corporate-memory search
  hero) uses canonical gradient + padding + max-width.

The detail-page heroes (marketplace_plugin_detail,
marketplace_item_detail, catalog_*_detail, store_edit,
admin_group_detail, admin_store_submission_detail) stay bespoke
for now — they're rich detail headers with photos, badges, install
actions; converting them would lose contract context. Same applies
to dashboard.html env-setup-cta (it's a CTA card, not a page hero).

* fix(web): canonicalise .container — single page shell every page inherits

Previously each admin page set its own `.container:has(.<page>)
{max-width: none}` + `.<page>-page {max-width: 1400px}` override,
and per-page hero markup either nested inside flex toolbars (which
pinned the hero next to filter controls and squeezed it half-width)
or self-constrained with a different max-width than the page. /home,
/dashboard, /marketplace, and /admin/* ended up at different widths
with different nav-to-hero gaps.

- style-custom.css `.container` now carries the canonical 1280px
  max-width + `16px 32px 48px` padding so every page inherits the
  same nav-to-hero gap and side gutters. `.container > main` is
  margin/padding 0 so the container is the sole owner of gutters.
- `.page-header--hero` drops its self-constraining max-width and
  auto-centering margin — the container provides the width, so the
  hero sits flush with the table/toolbar below it.
- `.stack-hero` (catalog + corporate-memory) and `.advanced-mock
  .ad-hero` (/setup-advanced) follow the same pattern: container
  owns the width.
- Per-page max-width overrides stripped from admin_users,
  admin_access, admin_groups, admin_marketplaces, admin_welcome,
  admin_workspace_prompt.
- _page_hero include extracted from inside flex toolbars on
  admin_users, admin_access, admin_groups, admin_marketplaces,
  admin_server_config, admin_welcome, admin_workspace_prompt,
  admin_sessions, admin_session_detail, admin_usage,
  activity_center. The toolbar (`.users-toolbar`, `.gp-toolbar`,
  etc.) keeps only the filter + action controls; hero renders
  before it as a sibling.
- _page_chrome.html trimmed to just the page-background tint for
  the redesign scopes; the duplicate `.container` rules it carried
  are now redundant.

Verified: /home, /admin/marketplaces, /admin/users all render
container width 1280px with hero top at 88px (16px below the
72px-tall sticky nav). Same spacing as /home design spec.

* fix(web): admin_tables + admin_corporate_memory inherit canonical .container

Both pages were overriding `{% block layout %}` from base.html,
which bypasses the canonical `.container` wrapper. Result: hero
span the full viewport (1596px on a wide screen) while the inner
content sat at a narrower max-width — hero and content didn't
align, and the nav-to-hero gap differed from every other admin
page.

Switched both templates to `{% block content %}` so they render
inside the canonical `.container` from base.html — same path as
admin_groups, admin_users, admin_marketplaces, etc.

- admin_tables: dropped local `.page-title { max-width: 1600px }`
  + `.content { max-width: 1600px }` overrides (kept typography +
  inner gutter rules) and the mobile padding overrides that paired
  with them. Container now owns the gutters.
- admin_corporate_memory: only the block keyword needed changing;
  the template already had a clean inner structure (no max-width
  override on `.container-memory`).

Verified on /admin/tables and /admin/corporate-memory:
- .container width 1280, padding 16/32/48
- Hero top 88 (nav 72 + container padding-top 16)
- Hero + content both 1216px wide, both at left 190 — perfect
  alignment with /admin/groups.

* fix(web): drop .page-shell padding override + admin_tables stale :root

Two regressions discovered after the canonical-container unification:

1. `.container:has(.page-shell)` still set `padding: 28px 32px 48px`
   while the canonical `.container` had moved to `16px 32px 48px`.
   Every page-shell consumer (/admin/sessions, /admin/sessions/<id>,
   /admin/usage, /marketplace, /dashboard, marketplace detail pages,
   /me/activity, /store/*, /admin/store-submissions) was rendering
   with a 28px nav-to-hero gap while /admin/users + /admin/groups
   rendered with 16px. Same width, mismatched vertical rhythm.
   The opt-in rule is now a no-op marker: canonical container
   already provides 1280px + 16/32/48 + main margin/padding 0.

2. admin_tables.html had a stale `<style>` block that re-declared
   `:root { --primary: var(--primary); ... }`. The self-referential
   token resolved to empty, collapsing the page-header hero's
   `linear-gradient(135deg, var(--primary), var(--primary-dark))`
   to no background — the hero appeared as a pale ghost without
   colour. The entire shadow `:root` block was a stale copy of the
   design tokens that style-custom.css already provides. Dropped
   it; tokens now resolve from the global `:root`.

After both fixes /admin/sessions, /admin/tables, and every other
page-shell consumer match /admin/groups exactly: container 1280px,
container padding-top 16px, hero at top 88px / left 190px / width
1216px.

* fix(web): drop /admin/tokens .tokens-page width + padding override

`.tokens-page` carried its own `max-width: 1280px; margin: 0 auto;
padding: 28px 8px 48px` block — the canonical `.container` already
provides width + 16/32/48 padding, so the nested wrapper was
adding 28px on top of the container's 16px (= 44px nav-to-hero
gap, vs 16px on every other admin page) and shrinking the hero
sideways by 8px on each side (1200px vs the canonical 1216px).

After: container owns the layout; `.tokens-page` is just a
font-family scope. /admin/tokens hero now sits at top 88, left 190,
width 1216 — same numbers as /admin/groups / /admin/users.

* fix(web): hero links readable on blue; /admin/access Groups link href

- New `.page-header--hero a` rule in style-custom.css forces any
  anchor inside a gradient hero to render white + underlined so
  links stay readable on the blue background. Previously links
  inherited the global `var(--primary)` blue, which disappeared
  on top of the matching blue gradient. No per-page class needed —
  drop a plain `<a>` in any hero subtitle and it just works.
- /admin/access hero subtitle was Jinja-passing the inline link
  with HTML-entity-encoded quotes (`href=&quot;...&quot;`). The
  entities decoded to literal `"` characters inside the rendered
  href, producing `/admin/%22/admin/groups%22` — a 404. Switched
  the `set` to a block-set (`{% set page_hero_subtitle %}...{% endset %}`)
  so the inline `<a href="/admin/groups">Groups</a>` survives
  unescaped through `_page_hero.html`. Also stripped the now-redundant
  inline `style="color:#fff;text-decoration:underline;"` — the new
  shared rule handles it.

* fix(web): /dashboard top padding matches every other page

`.main` on /dashboard had `padding: 28px 32px 48px` while every
other page now uses `16px 32px 48px` via the canonical
`.container`. Dashboard bypasses `.container` (overrides
base.html's `layout` block to render a full-width `<main>`
directly), so the padding lives on `.main` itself — bumped the
top to 16px to match.

After: first child top = 88, left = 190, width = 1216 — same
numbers as /admin/groups / /admin/users / /admin/marketplaces.

* fix(web): green eyebrow + white title on .page-header--hero (matches /home)

`.page-header--hero .page-header__eyebrow` was faint white
(rgba(255,255,255,0.75)) — readable but unbranded against the blue
gradient. Changed to `var(--ds-brand-accent)` (mint green #54d3a0)
so every page hero pairs a green eyebrow with white title +
subtitle, echoing /home's setup-section header (green eyebrow,
dark heading combo). One CSS rule applies everywhere — no
per-page styling needed.

Also bumped the eyebrow to font-weight 700 / letter-spacing 1.2px
so the green stands out cleanly against the gradient.

* fix(web): page-header--hero + stack-hero use /home navy gradient

`.page-header--hero` and `.stack-hero` were on the brand-blue
gradient (`var(--primary)` → `var(--primary-dark)`) while
/home's hero (`.home-hero-intro`) sits on the deeper navy
gradient (`#0f1b3a` → `#1a2a5f`). Every other page-hero now
uses that same navy gradient so /home, /marketplace, /catalog,
/corporate-memory, /admin/*, /profile, /install, /dashboard,
/setup-advanced share one brand surface. Shadow tint adjusted
to the navy depth (rgba(15, 27, 58, 0.22)).

Brand blue stays the link/CTA colour everywhere else; only the
hero box itself is navy.

* fix(web): primary buttons green; marketplace tabs navy translucent

Two parity tweaks pulling the rest of the app toward /home's
visual language.

- `.btn-primary` (both rules in style-custom.css) now uses
  `var(--ds-primary)` / `var(--ds-primary-dark)` green fill,
  matching the "Copy install script to clipboard" button on
  /home. Brand-blue `--primary` still drives link colour and the
  accent surface; only the filled button background flipped to
  green. Every page with a `.btn-primary` (admin "+Add user",
  "+Add marketplace", catalog, marketplace actions, dashboard,
  modals) now reads as the same "do it" affordance.
- `.mp-tabs` (Curated Marketplace / Flea Market / My Stack tab
  group) now sits on the navy `--ds-hero-bg` with translucent
  white pills (rgba(255,255,255,0.10) inactive, 0.18 active) —
  same translucent-white-on-navy treatment as the "Just browse —
  no install needed" pill on /home. Icons render as soft white;
  per-tab colour-coding dropped in favour of the unified surface.

* fix(web): catalog/memory tabs + empty-state CTA + admin action buttons

Bring /catalog and /memory in line with /home + /marketplace:

- `.stack-tabs` (Browse / My Stack / Recipes on /catalog,
  Browse / My Stack on /memory) now uses the navy `--ds-hero-bg`
  container with translucent-white-on-navy pills, mirroring the
  `.mp-tabs` treatment and /home's "Just browse — no install
  needed" CTA pill. Per-tab icon colour-coding dropped — icons
  render as soft white on the navy fill.
- `.stack-tabs-row__actions .btn` (right-slot "+New Recipe",
  "+New Data Package" admin CTAs) now uses green primary fill
  (`--ds-primary`), matching `.btn-primary` and /home's
  "Copy install script to clipboard" button.
- `.stack-empty .cta a` (empty-state action button — the
  "Open /admin/tables →" CTA on /catalog and equivalent on
  /memory) flipped from blue `--primary` to green `--ds-primary`
  so the colour aligns with every other primary button in the app.

* fix(web): marketplace Search button green (--ds-primary) matching other CTAs

* fix(web): unify Search button + admin-action button across browse pages

- Added Search button (`<button class="stack-hero__search-btn">`)
  to /catalog and /memory heroes — same green pill as /marketplace.
  Wired to the existing live-filter pipeline (button click runs
  `applyFilters()` and refocuses the input). All three browse pages
  now wear the identical search bar UI.
- `.stack-hero__search-btn` shares `--ds-primary` fill with
  `.mp-hero .search-btn`.
- `.mp-actions .btn` ("Submit a skill or plugin" CTA on /marketplace)
  flipped from the legacy blue-outline to the same green primary
  fill + dimensions (`display: inline-flex; line-height: 1;
  padding: 9px 16px; gap: 6px`) as `.stack-tabs-row__actions .btn`
  on /catalog and /memory. All three right-slot action buttons
  render at identical height now.
- `.stack-tabs-row__actions .btn` got `inline-flex` + `line-height: 1`
  + `gap: 6px` so a `<button class="btn">` and a `<a class="btn">`
  both render at exactly 33px high — the embedded
  `.admin-only-hint` chip no longer pushes one variant taller
  than the other.

* fix(web): marketplace guide CTAs green (fastpath + primary); drop flea purple

* fix(web): dashboard CTA hero on navy; readable <code> chips in hero

- `.env-setup-cta` on /dashboard ("Set up a new Claude Code"
  card) flipped from the brand-blue gradient + green-tinted shadow
  to the canonical navy gradient (`--ds-hero-bg` → `#1a2a5f`) with
  navy-tinted shadow + 14px radius + 28/32/24 padding, matching
  `.page-header--hero` and /home's `.home-hero-intro`. Dashboard's
  top CTA now sits on the same brand surface as every other hero.
- Added `.page-header--hero code` rule — translucent white pill +
  warm-yellow ink (#ffd866) so `<code>` chips embedded in hero
  subtitles read as code samples against the navy gradient. The
  global `code` rule sets `color: var(--text-primary)` (dark),
  which turned in-hero chips into invisible dark-on-white-on-navy
  ghosts (e.g. the `-by-dev` suffix on /store/new).
- /store/new's `.page-header__subtitle code` dropped its inline
  style override — the shared rule handles it now.

* feat(web): two-theme switching via data-theme + admin toggle

Introduces a theme system that flips the entire UI palette between
"navy" (current design, default) and "blue" (pre-redesign palette)
via a single `<html data-theme="...">` attribute. Page markup, class
names, and component styles don't change — only the `--ds-*` token
values flip.

Backend
- New `app/instance_config.py::get_instance_theme()` resolves the
  active theme from `AGNES_INSTANCE_THEME` env > `instance.theme`
  in instance.yaml > default "navy". Unrecognised values clamp to
  "navy" so a typo doesn't break the page.
- `app/web/router.py::_build_context` injects `instance_theme`
  alongside `instance_brand` etc. so every template inherits it.
- `app/web/templates/base.html` renders
  `<html lang="en" data-theme="{{ instance_theme | default('navy') }}">`.

CSS
- `app/web/static/css/design-tokens.css` adds two new tokens to
  the default `:root` set: `--ds-hero-shadow` (drop-shadow tint
  on hero boxes) and `--ds-hero-eyebrow` (eyebrow accent colour).
  Plus a `:root[data-theme="blue"]` override block that flips
  seven tokens: `--ds-primary`, `--ds-primary-dark`,
  `--ds-primary-light`, `--ds-brand-accent`, `--ds-hero-bg`,
  `--ds-hero-bg-deep`, `--ds-hero-shadow`, `--ds-hero-eyebrow`.
  The blue theme aliases the brand surface tokens back to the
  legacy `--primary` family.
- `.page-header--hero`, `.stack-hero`, `.env-setup-cta`,
  `.home-mock .home-hero-intro` now reference the new
  `--ds-hero-shadow` and `--ds-hero-bg-deep` tokens instead of
  hard-coding `rgba(15, 27, 58, 0.22)` and `#1a2a5f` — gradient +
  shadow now flip with the theme.
- `.page-header--hero .page-header__eyebrow` uses
  `var(--ds-hero-eyebrow)` so the eyebrow goes mint-green on
  navy and translucent-white on blue (mint on blue reads poorly).

Admin
- `app/api/admin.py::_KNOWN_FIELDS["instance"]` now registers a
  `theme` field of kind `select` with options `["navy", "blue"]`
  and a `hint` explaining the trade-off. The existing
  /admin/server-config UI auto-renders a select for this — no
  template changes needed.

Defaults
- Default value is "navy" so existing instances see no visual
  change. Admins flip to "blue" via /admin/server-config to
  restore the pre-redesign look.

Restart note: uvicorn must reload to pick up the Python changes
(new getter, new template-context key, new known-field). CSS
changes hot-reload via browser refresh.

* fix(web): blue theme — home hero eyebrow + CTA contrast

`.home-hero-intro .eyebrow` and `.btn-intro-primary` referenced
`--ds-brand-accent` directly, which on the blue theme resolves to
the lighter brand-accent blue (#4F9DEB). Result: light-blue eyebrow
on the blue gradient ("WELCOME, ADMIN" barely readable) and a
light-blue button with darker-blue text ("Set up in ~15 min")
that all sat in the same hue range.

Introduces three new theme-aware tokens:
- `--ds-hero-eyebrow` already existed; blue theme bumped opacity
  to 0.92 so the eyebrow reads as full white.
- `--ds-hero-cta-bg` + `--ds-hero-cta-fg` + `--ds-hero-cta-bg-hover`
  flip the primary hero CTA: mint-green on navy (default), white-
  on-blue under `data-theme="blue"`.

`.home-hero-intro .eyebrow` now uses `--ds-hero-eyebrow` (mint on
navy / white on blue) and `.btn-intro-primary` uses the CTA token
trio.

Recommended palette on blue theme:
- Eyebrow: white at 92% opacity (clear on the blue gradient).
- Primary CTA pill: white background, brand-blue dark text
  (`--primary-dark` = #005BA3) for AAA-level contrast.
- Secondary CTA: translucent white pill (unchanged).

* fix(web): blue theme — callout-hint info bg/border/ink re-tinted to brand blue (was indigo, clashed with brand-blue hero)
2026-05-21 06:19:16 +00:00

1246 lines
58 KiB
HTML
Raw Blame History

{% extends "base.html" %}
{% from "macros/_stack_card.html" import card %}
{% block title %}Data Packages — {{ config.INSTANCE_NAME or 'AI Data Analyst' }}{% endblock %}
{% block content %}
{# Hero — gradient banner mirroring marketplace.html .mp-hero so /catalog
and /marketplace read as one product. Eyebrow + h1 + sub layered on
the same blue gradient, plus an embedded search row identical to the
one on /marketplace. The hero search is wired to the same JS that
drives the per-card filter below, so typing here also narrows the grid. #}
<div class="stack-hero">
<div class="eyebrow">Data</div>
<h1>What data are you looking for?</h1>
<p class="sub">Browse curated data packages your team has approved. Add the ones you need to your stack — required packages are added automatically.</p>
<div class="stack-hero__search-row">
<div class="stack-hero__search-wrap">
<svg class="stack-hero__search-icon" viewBox="0 0 24 24" fill="none" stroke="currentColor"
stroke-width="2" stroke-linecap="round" stroke-linejoin="round" aria-hidden="true">
<circle cx="11" cy="11" r="7"/><path d="m21 21-4.3-4.3"/>
</svg>
<input id="catalog-hero-search" type="search"
placeholder="Search Data Packages by name or description…">
</div>
<button class="stack-hero__search-btn" id="catalog-search-btn" type="button">Search</button>
</div>
{# v51 lifecycle status filter — show / hide cards by per-package
``data-status``. Default opt-in: Prod + POC checked (the analyst-
ready buckets). Coming-soon stays unchecked so the catalog isn't
polluted with placeholders. Empty selection = no filter (show all). #}
<div class="stack-hero__status-row" id="catalog-status-filter">
<span class="stack-hero__status-label">Show:</span>
<label><input type="checkbox" value="prod" checked> Prod-ready</label>
<label><input type="checkbox" value="poc" checked> POC</label>
<label><input type="checkbox" value="coming-soon"> Coming soon</label>
{% if user.is_admin %}
<label title="Visible only to admins — analysts won't see this filter."><input type="checkbox" value="draft"> Draft <span class="admin-only-hint" title="Visible only to admins — analysts won't see this filter.">admin-only</span></label>
{% endif %}
</div>
</div>
<div class="stack-page" id="catalog-page"
data-resource-type="data_package"
data-stack-endpoint="/api/stack"
data-subscribe-endpoint="/api/stack/subscribe">
{# Tab strip + right-of-tabs actions row (marketplace .mp-tabs-row
parity). Section order locked to match /marketplace exactly:
hero → tabs-row (+ admin actions) → curator-block → filter pills →
grid → empty state. The pre-v50 ordering (curator-block before
tabs) read as a content banner squatting above the navigation;
marketplace's order makes the curator block feel like a trust
stamp on the active tab, not a header.
Icons mirror marketplace's tab icons: layout-grid for Browse;
rectangle-stack for My Stack. #}
<div class="stack-tabs-row">
<div class="stack-tabs" role="tablist">
<button class="is-active" data-tab="browse" role="tab" aria-selected="true">
<svg class="tab-icon" viewBox="0 0 24 24" fill="none" stroke="currentColor"
stroke-width="1.6" stroke-linecap="round" stroke-linejoin="round" aria-hidden="true">
<rect x="3" y="3" width="7" height="7" rx="1"/>
<rect x="14" y="3" width="7" height="7" rx="1"/>
<rect x="3" y="14" width="7" height="7" rx="1"/>
<rect x="14" y="14" width="7" height="7" rx="1"/>
</svg>
Browse <span class="count" data-count="browse">{{ entries|length }}</span>
</button>
<button data-tab="my" role="tab" aria-selected="false">
<svg class="tab-icon" viewBox="0 0 24 24" fill="none" stroke="currentColor"
stroke-width="1.6" stroke-linecap="round" stroke-linejoin="round" aria-hidden="true">
<path d="M6.429 9.75 2.25 12l4.179 2.25m0-4.5 5.571 3 5.571-3m-11.142 0L2.25 7.5 12 2.25l9.75 5.25-4.179 2.25m0 0L21.75 12l-4.179 2.25m0 0 4.179 2.25L12 21.75 2.25 16.5l4.179-2.25m11.142 0-5.571 3-5.571-3"/>
</svg>
My Stack <span class="count" data-count="my">{{ stack_entries|length }}</span>
</button>
{# v53 Recipes tab — query templates analysts copy + adapt.
Sibling concept to Data Packages but not stack-subscribable.
Count hydrates on first visit; starts empty (--) until then. #}
<button data-tab="recipes" role="tab" aria-selected="false">
<svg class="tab-icon" viewBox="0 0 24 24" fill="none" stroke="currentColor"
stroke-width="1.6" stroke-linecap="round" stroke-linejoin="round" aria-hidden="true">
<path d="M3 7h12M3 12h12M3 17h7"/><circle cx="18" cy="17" r="3"/>
</svg>
Recipes <span class="count" data-count="recipes">—</span>
</button>
</div>
{% if user.is_admin %}
<div class="stack-tabs-row__actions" style="display:flex; gap:8px;">
<button class="btn btn-secondary" onclick="openCreateRecipeModal()" type="button"
title="Visible only to admins — analysts won't see this button.">
+ New Recipe <span class="admin-only-hint">admin-only</span>
</button>
<a class="btn btn-secondary" href="/admin/tables?new_package=1"
title="Visible only to admins — analysts won't see this button.">
+ New Data Package <span class="admin-only-hint">admin-only</span></a>
</div>
{% endif %}
</div>
{# Curator-style info block — mirrors marketplace .mp-curator-block.
Sits BELOW the tab strip per the unified section order — same
position marketplace.html uses (marketplace.html:497). #}
{# Filter chips — All / Required / Available / In stack + per-source-type chips. #}
<div class="stack-filter-row" id="catalog-filters">
<button class="pill is-active" data-filter="all">All</button>
<button class="pill" data-filter="required">Required</button>
<button class="pill" data-filter="available">Available</button>
<button class="pill" data-filter="in_stack">In stack</button>
{% if source_type_chips %}
<span style="margin-left: 12px; color: var(--text-secondary); font-size: 12px;">Source:</span>
{% for st in source_type_chips %}
<button class="pill" data-filter-source="{{ st }}">{{ st }}</button>
{% endfor %}
{% endif %}
</div>
{# Browse view — every package the user has any grant on. #}
<div data-view="browse">
<div class="stack-curator-block">
<div class="stack-curator-block__title">Each Data Package is curated by your admin.</div>
<div class="stack-curator-block__body">
Packages bundle related tables on a single topic (Sales, Finance, …) so
analysts can pull a coherent dataset with one click. Required packages
are added to your stack automatically.
</div>
</div>
{% if entries %}
<div class="stack-grid" id="catalog-grid-browse">
{% for entry in entries %}
{{ card(entry) }}
{% endfor %}
</div>
{% else %}
{# Empty state — friendly + actionable. Admins get a concrete CTA
(open /admin/tables with the N-registered-tables hint so they
know there IS data to package). Non-admins get a different copy
because the admin path is gated. #}
<div class="stack-empty">
<span class="icon">📦</span>
<h3>No Data Packages yet</h3>
{% if user.is_admin %}
{% if total_registered_tables and total_registered_tables > 0 %}
<p>You have <strong>{{ total_registered_tables }}</strong>
table{{ 's' if total_registered_tables != 1 else '' }} registered
in <code>/admin/tables</code> but no Data Packages grouping them.</p>
<p>Create your first package by editing any table and assigning it
to a new package — analysts opt-in to the package as a whole.</p>
{% else %}
<p>No tables registered yet either. Register your first source
table, then bundle related tables into a Data Package so analysts
can opt-in to them as a group.</p>
{% endif %}
<div class="cta">
<a href="/admin/tables">Open /admin/tables →</a>
</div>
{% else %}
<p>Ask your admin to create a Data Package or grant your group
access to an existing one, then refresh this page.</p>
{% endif %}
</div>
{% endif %}
</div>
{# My Stack view — required + subscribed. Grid + empty-state are
both rendered so the optimistic add/remove JS can swap visibility
without having to inject DOM that wasn't in the initial render. #}
<div data-view="my" hidden>
<div class="stack-grid" id="catalog-grid-my"{% if not stack_entries %} hidden{% endif %}>
{% for entry in stack_entries %}
{{ card(entry) }}
{% endfor %}
</div>
<div class="stack-empty"{% if stack_entries %} hidden{% endif %}>
<span class="icon">🗂️</span>
<h3>Your stack is empty</h3>
<p>Browse available packages and click <strong>+ Add to stack</strong>.
Required packages will appear here automatically.</p>
<div class="cta">
<a href="/catalog">Browse all →</a>
</div>
</div>
</div>
{# v53 Recipes view — populated client-side on first tab open from
/api/recipes so the page render isn't blocked by a second DB query
when most users land on Browse. Card-grid uses the same .stack-grid
class for visual parity, but recipe cards are simpler (no
Add-to-stack, no Required/in-stack badges — recipes aren't
subscribable). #}
<div data-view="recipes" hidden>
<div class="stack-curator-block">
<div class="stack-curator-block__title">Recipes — admin-curated query templates.</div>
<div class="stack-curator-block__body">
A Recipe is a ready-to-run SQL query that answers a typical
question (e.g. "top customers by revenue last 30 days"). Open
one to copy the SQL, then adapt the date range / filters and
run it via <code>agnes query</code>. Recipes aren't subscribed
to like Data Packages — they're a shared library you can
always browse.
</div>
</div>
<div class="stack-grid" id="catalog-grid-recipes">
<div class="stack-empty" id="catalog-recipes-loading">
<span class="icon">📑</span>
<h3>Loading recipes…</h3>
</div>
</div>
</div>
{% if user.is_admin %}
{# v53 Create Recipe modal — opened from the "+ New Recipe" admin
button in the tab strip. Single-step (no inline RBAC matrix yet —
recipes are visible to any authenticated user). #}
<div id="createRecipeModal"
style="display:none; position:fixed; inset:0; background:rgba(0,0,0,0.4); z-index:2050;">
<div style="background:var(--surface); max-width:560px; margin:60px auto;
padding:20px 24px; border-radius:12px; border:1px solid var(--border);
max-height:85vh; overflow-y:auto;">
<h3 style="margin:0 0 12px;">New Recipe</h3>
<p style="margin:0 0 16px; color:var(--text-secondary); font-size:13px;">
Recipes are query templates analysts copy + adapt. Link the
tables they touch so analysts can drill into each.
</p>
<div style="display:flex; flex-direction:column; gap:12px;">
<label style="display:flex; flex-direction:column; gap:4px;">
<span style="font-size:12px; color:var(--text-muted);">Title</span>
<input id="rcp-title" type="text" placeholder="Top revenue by region (last 30 days)"
style="padding:8px; border:1px solid var(--border); border-radius:6px;">
</label>
<label style="display:flex; flex-direction:column; gap:4px;">
<span style="font-size:12px; color:var(--text-muted);">Slug</span>
<input id="rcp-slug" type="text" placeholder="top-revenue-by-region"
style="padding:8px; border:1px solid var(--border); border-radius:6px;">
<span style="font-size:11px; color:var(--text-secondary);">
URL-safe; auto-derived from title if left blank.
</span>
</label>
<label style="display:flex; flex-direction:column; gap:4px;">
<span style="font-size:12px; color:var(--text-muted);">Description</span>
<textarea id="rcp-desc" rows="2"
placeholder="What question this recipe answers; key caveats."
style="padding:8px; border:1px solid var(--border); border-radius:6px;
font-family:inherit; resize:vertical;"></textarea>
</label>
<label style="display:flex; flex-direction:column; gap:4px;">
<span style="font-size:12px; color:var(--text-muted);">SQL template</span>
<textarea id="rcp-sql" rows="7"
placeholder="SELECT region, SUM(revenue) AS rev&#10;FROM orders&#10;WHERE event_date >= DATE_SUB(CURRENT_DATE(), INTERVAL 30 DAY)&#10;GROUP BY 1 ORDER BY 2 DESC"
style="padding:8px; border:1px solid var(--border); border-radius:6px;
font-family:var(--font-mono); font-size:12px; resize:vertical;"></textarea>
</label>
<label style="display:flex; flex-direction:column; gap:4px;">
<span style="font-size:12px; color:var(--text-muted);">Related table ids</span>
<input id="rcp-related" type="text"
placeholder="Comma-separated table_registry ids — e.g. tbl_orders,tbl_users"
style="padding:8px; border:1px solid var(--border); border-radius:6px;">
<span style="font-size:11px; color:var(--text-secondary);">
Drives the "Touches tables" links on the drilldown.
</span>
</label>
<div style="display:flex; gap:12px;">
<label style="flex:1; display:flex; flex-direction:column; gap:4px;">
<span style="font-size:12px; color:var(--text-muted);">Color</span>
<div class="cf-palette-row" data-target="rcp-color"></div>
<input id="rcp-color" type="color" value="var(--primary)"
style="padding:2px; border:1px solid var(--border); border-radius:6px;
height:32px; cursor:pointer;">
</label>
<label style="flex:1; display:flex; flex-direction:column; gap:4px;">
<span style="font-size:12px; color:var(--text-muted);">Status</span>
<select id="rcp-status"
style="padding:8px; border:1px solid var(--border); border-radius:6px; height:38px;">
<option value="prod" selected>Prod</option>
<option value="poc">POC</option>
<option value="coming-soon">Coming soon</option>
<option value="draft">Draft (admin-only)</option>
</select>
</label>
</div>
{# v55 Recipes RBAC matrix on Create — same inline pattern as
Create Memory Domain. Optional; with no rows ticked, the new
recipe is admin-only (default-closed). Admins can grant later
via Edit Recipe or /admin/access. #}
<details id="rcp-rbac-details"
style="border:1px solid var(--border); border-radius:8px; padding:8px 12px;">
<summary style="cursor:pointer; font-weight:600; font-size:13px; user-select:none;">
Group access
<span style="color:var(--text-secondary); font-weight:normal; font-size:12px;">(optional)</span>
</summary>
<p style="margin:8px 0; color:var(--text-secondary); font-size:12px;">
Grant per-group access tiers — <em>available</em> surfaces
the recipe on the group's Recipes tab; <em>required</em>
pins it. Leave blank to manage later from
<a href="/admin/access">Resource access</a>.
</p>
<div id="rcp-rbac-rows"
style="display:flex; flex-direction:column; gap:6px; max-height:30vh; overflow-y:auto;">
<div class="loading" style="padding:6px; color:var(--text-secondary); font-size:12px;">
Click to load groups…
</div>
</div>
</details>
</div>
<div style="display:flex; gap:8px; justify-content:flex-end; margin-top:18px;">
<button class="btn" type="button" onclick="closeCreateRecipeModal()">Cancel</button>
<button class="btn btn-primary" type="button" id="rcp-submit-btn"
onclick="submitCreateRecipe()">Create</button>
</div>
</div>
</div>
{# v53 Edit Recipe modal — pre-fills from GET /api/admin/recipes/{id}.
Slug is locked (it's the stable URL identifier referenced by
/catalog/r/<slug> + any pinned links). Delete lives on the card
footer, not in the modal, so admins can drop a recipe without
opening the editor. #}
<div id="editRecipeModal"
style="display:none; position:fixed; inset:0; background:rgba(0,0,0,0.4); z-index:2050;">
<div style="background:var(--surface); max-width:560px; margin:60px auto;
padding:20px 24px; border-radius:12px; border:1px solid var(--border);
max-height:85vh; overflow-y:auto;">
<h3 style="margin:0 0 12px;">Edit Recipe</h3>
<input type="hidden" id="ercp-id">
<div style="display:flex; flex-direction:column; gap:12px;">
<label style="display:flex; flex-direction:column; gap:4px;">
<span style="font-size:12px; color:var(--text-muted);">Title</span>
<input id="ercp-title" type="text"
style="padding:8px; border:1px solid var(--border); border-radius:6px;">
</label>
<label style="display:flex; flex-direction:column; gap:4px;">
<span style="font-size:12px; color:var(--text-muted);">Slug</span>
<input id="ercp-slug" type="text" disabled
style="padding:8px; border:1px solid var(--border); border-radius:6px;
opacity:0.6;">
<span style="font-size:11px; color:var(--text-secondary);">
Slug is permanent — used in /catalog/r/&lt;slug&gt; URLs.
</span>
</label>
<label style="display:flex; flex-direction:column; gap:4px;">
<span style="font-size:12px; color:var(--text-muted);">Description</span>
<textarea id="ercp-desc" rows="2"
style="padding:8px; border:1px solid var(--border); border-radius:6px;
font-family:inherit; resize:vertical;"></textarea>
</label>
<label style="display:flex; flex-direction:column; gap:4px;">
<span style="font-size:12px; color:var(--text-muted);">SQL template</span>
<textarea id="ercp-sql" rows="7"
style="padding:8px; border:1px solid var(--border); border-radius:6px;
font-family:var(--font-mono); font-size:12px; resize:vertical;"></textarea>
</label>
<label style="display:flex; flex-direction:column; gap:4px;">
<span style="font-size:12px; color:var(--text-muted);">Related table ids</span>
<input id="ercp-related" type="text"
placeholder="Comma-separated table_registry ids"
style="padding:8px; border:1px solid var(--border); border-radius:6px;">
</label>
<div style="display:flex; gap:12px;">
<label style="flex:1; display:flex; flex-direction:column; gap:4px;">
<span style="font-size:12px; color:var(--text-muted);">Color</span>
<div class="cf-palette-row" data-target="ercp-color"></div>
<input id="ercp-color" type="color"
style="padding:2px; border:1px solid var(--border); border-radius:6px;
height:32px; cursor:pointer;">
</label>
<label style="flex:1; display:flex; flex-direction:column; gap:4px;">
<span style="font-size:12px; color:var(--text-muted);">Status</span>
<select id="ercp-status"
style="padding:8px; border:1px solid var(--border); border-radius:6px; height:38px;">
<option value="prod">Prod</option>
<option value="poc">POC</option>
<option value="coming-soon">Coming soon</option>
<option value="draft">Draft (admin-only)</option>
</select>
</label>
</div>
{# v55 Recipes RBAC matrix — same lazy-hydrate + diff-on-save pattern
as Edit Memory Domain. Hidden until the admin expands it; loads
groups + grants on first toggle, diffs against the original on
submit, and POSTs/DELETEs only the deltas. #}
<details id="ercp-rbac-details"
style="border:1px solid var(--border); border-radius:8px; padding:8px 12px; margin-top:4px;">
<summary style="cursor:pointer; font-weight:600; font-size:13px; user-select:none;">
Group access
<span style="color:var(--text-secondary); font-weight:normal; font-size:12px;">— mark required / available per group</span>
</summary>
<p style="margin:8px 0; color:var(--text-secondary); font-size:12px;">
<em>required</em> pins the recipe to the group's stack;
<em>available</em> surfaces it on their Recipes tab;
<em>(no grant)</em> hides it entirely. Changes apply when you
click <strong>Save</strong>.
</p>
<div id="ercp-rbac-rows"
style="display:flex; flex-direction:column; gap:6px; max-height:30vh; overflow-y:auto;">
<div class="loading" style="padding:6px; color:var(--text-secondary); font-size:12px;">
Click to load groups…
</div>
</div>
</details>
</div>
<div style="display:flex; gap:8px; justify-content:flex-end; margin-top:18px;">
<button class="btn" type="button" onclick="closeEditRecipeModal()">Cancel</button>
<button class="btn btn-primary" type="button" id="ercp-submit-btn"
onclick="submitEditRecipe()">Save</button>
</div>
</div>
</div>
{% endif %}
{# Toast for ephemeral feedback (Add/Remove success/failure). #}
<div id="stack-toast" role="status" aria-live="polite" hidden
style="position:fixed; bottom:24px; right:24px; padding:12px 18px;
background:#202124; color:#fff; border-radius:8px;
box-shadow:0 6px 20px rgba(0,0,0,.2); font-size:13px; z-index:1000;"></div>
</div>
<script>
'use strict';
// v53: server-injected admin flag — read by _renderRecipeCard to decide
// whether to show inline Edit / Delete buttons on each card. Sub-second
// branching only; the actual privilege check still happens server-side
// on every PUT/DELETE.
window.IS_ADMIN = {{ (user.is_admin if user else False) | tojson }};
// Card subscribe/unsubscribe wiring + tab + filter state.
// Vanilla, no framework — runs on /catalog and /memory (the only divergence
// is data-resource-type which the macro doesn't care about).
(function() {
const root = document.getElementById('catalog-page');
if (!root) return;
const resourceType = root.dataset.resourceType;
const subscribeUrl = root.dataset.subscribeEndpoint;
// CSRF token lives in cookie or page if needed by middleware; FastAPI here
// gates by session JWT cookie — no body CSRF token required.
// ── Toast helper ────────────────────────────────────────────────────────
// FIFO queue (max 3) — the previous overwrite-on-second-call behaviour
// wiped the first toast as soon as the second fired, which lost
// useful feedback when admins added several packages in quick
// succession or when a network failure followed a success.
const toast = document.getElementById('stack-toast');
const _toastQueue = [];
let _toastShowing = false;
function _showNextToast() {
if (_toastShowing) return;
const next = _toastQueue.shift();
if (!next) return;
_toastShowing = true;
toast.textContent = next.msg;
toast.hidden = false;
toast.style.background = next.isError ? '#b91c1c' : '#10b77f';
const dwell = next.isError ? 4000 : 2500;
setTimeout(() => {
toast.hidden = true;
_toastShowing = false;
_showNextToast();
}, dwell);
}
function showToast(msg, isError) {
if (_toastQueue.length >= 3) _toastQueue.shift();
_toastQueue.push({ msg, isError });
_showNextToast();
}
// ── Drill-down navigation on card body click ────────────────────────────
// Buttons (data-action) handle their own click + stopPropagation below.
// v54 mod-click + middle-click open the drilldown in a new tab so the
// card-wide click handler stops fighting browser-native shortcuts
// (Cmd/Ctrl + click and middle-click both used to silently swallow).
document.querySelectorAll('.stack-card').forEach(card => {
const drilldown = card.querySelector('.stack-card__drilldown');
if (!drilldown) return;
card.addEventListener('click', (e) => {
if (e.target.closest('button')) return;
if (e.target === drilldown) return;
if (e.metaKey || e.ctrlKey || e.shiftKey || e.button === 1) {
e.preventDefault();
window.open(drilldown.href, '_blank', 'noopener');
return;
}
window.location.href = drilldown.href;
});
// ``auxclick`` fires on middle-button release; the regular click
// listener also sees it via e.button === 1, but Firefox routes
// middle-button exclusively to auxclick on some versions — wire
// both so the behavior is consistent.
card.addEventListener('auxclick', (e) => {
if (e.button !== 1) return;
if (e.target.closest('button')) return;
e.preventDefault();
window.open(drilldown.href, '_blank', 'noopener');
});
});
// ── Subscribe / Unsubscribe ─────────────────────────────────────────────
async function doSubscribe(id) {
const resp = await fetch(subscribeUrl, {
method: 'POST',
headers: { 'Content-Type': 'application/json' },
credentials: 'same-origin',
body: JSON.stringify({ resource_type: resourceType, resource_id: id }),
});
return resp;
}
async function doUnsubscribe(id) {
const url = '/api/stack/subscription/' + encodeURIComponent(resourceType) +
'/' + encodeURIComponent(id);
const resp = await fetch(url, {
method: 'DELETE',
credentials: 'same-origin',
});
return resp;
}
// Update in-place: flip the card's data-in-stack, swap the button's
// data-action + label, update both tab badge counts. Avoids the
// page-reload roundtrip that flashed the layout and lost scroll
// position when admins added several packages in a row.
function _applyStackChange(card, becameInStack) {
if (!card) return;
card.dataset.inStack = becameInStack ? '1' : '0';
// The card may render under both Browse and My Stack grids when the
// server-side render duplicates it; query by id to update all
// matching instances on the page.
const id = card.dataset.id;
if (!id) return;
document.querySelectorAll('.stack-card[data-id="' + CSS.escape(id) + '"]')
.forEach(c => {
c.dataset.inStack = becameInStack ? '1' : '0';
// Toggle the ``is-in-stack`` class so the border + visual state
// match what the server-side macro would render. Without this
// the button label flipped but the card chrome stayed the same
// — the user-reported "fajfka se zobrazí, ale celé se to
// nezmění" bug.
c.classList.toggle('is-in-stack', becameInStack);
// Top-right "In stack" badge mirrors the macro's elif-in_stack
// branch (see _stack_card.html). Skip when requirement is
// 'required' — that slot is owned by the Required badge which
// the server-rendered DOM keeps in place.
const isRequired = c.dataset.requirement === 'required';
let inStackBadge = c.querySelector('.stack-card__req-badge--instack');
if (becameInStack && !isRequired) {
if (!inStackBadge) {
inStackBadge = document.createElement('div');
inStackBadge.className = 'stack-card__req-badge stack-card__req-badge--instack';
inStackBadge.title = 'In your stack';
inStackBadge.textContent = 'In stack';
c.insertBefore(inStackBadge, c.firstChild);
}
} else if (inStackBadge && !isRequired) {
inStackBadge.remove();
}
const actionBtn = c.querySelector('[data-action]');
if (actionBtn) {
actionBtn.dataset.action = becameInStack ? 'remove' : 'add';
// Mirror the macro's footer text — "Remove" / "+ Add to stack".
actionBtn.textContent = becameInStack ? 'Remove' : '+ Add to stack';
actionBtn.classList.toggle('stack-card__btn--add', !becameInStack);
actionBtn.classList.toggle('stack-card__btn--remove', becameInStack);
actionBtn.disabled = false;
}
});
// Keep both grids in sync with their state. The server-side render
// mirrors any in-stack card into both Browse and My Stack grids; an
// Add from Browse needs to clone the Browse card into My Stack, a
// Remove needs to drop the My Stack copy. Without this the My Stack
// grid was stale until full page reload (regression noted in the
// mockup audit).
const myGrid = document.getElementById('catalog-grid-my');
const browseGrid = document.getElementById('catalog-grid-browse');
if (myGrid) {
const existingInMy = myGrid.querySelector(
'.stack-card[data-id="' + CSS.escape(id) + '"]'
);
if (becameInStack && !existingInMy) {
const sourceCard = browseGrid
? browseGrid.querySelector('.stack-card[data-id="' + CSS.escape(id) + '"]')
: card;
if (sourceCard) {
const clone = sourceCard.cloneNode(true);
clone.dataset.inStack = '1';
clone.classList.add('is-in-stack');
const cloneBtn = clone.querySelector('[data-action]');
if (cloneBtn) {
cloneBtn.dataset.action = 'remove';
cloneBtn.textContent = 'Remove';
cloneBtn.classList.remove('stack-card__btn--add');
cloneBtn.classList.add('stack-card__btn--remove');
cloneBtn.disabled = false;
}
myGrid.appendChild(clone);
// Mirror the Remove-empties-the-tab path: if we previously
// hid the grid + showed the empty-state placeholder, un-hide
// the grid now that it has children again.
myGrid.hidden = false;
}
// Empty-state placeholder hides as soon as the grid has a child.
const emptyEl = document.querySelector('[data-view="my"] .stack-empty');
if (emptyEl) emptyEl.hidden = true;
} else if (!becameInStack && existingInMy) {
existingInMy.remove();
if (!myGrid.children.length) {
// Both the grid and the empty-state are server-rendered;
// swap their visibility instead of injecting DOM that wasn't
// in the initial render. Previously the empty-state was only
// emitted when stack_entries was empty at render time, so
// removing the last card left the tab blank — users read
// that as "Remove didn't work" and reached for refresh.
myGrid.hidden = true;
const emptyEl = document.querySelector('[data-view="my"] .stack-empty');
if (emptyEl) emptyEl.hidden = false;
}
}
}
// Update tab counts. My Stack ticks up on add / down on remove;
// Browse stays as the catalogue total — it doesn't shrink.
const myEl = document.querySelector('.stack-tabs .count[data-count="my"]');
if (myEl) {
const cur = parseInt(myEl.textContent, 10) || 0;
myEl.textContent = String(cur + (becameInStack ? 1 : -1));
}
}
document.addEventListener('click', async (e) => {
const btn = e.target.closest('[data-action]');
if (!btn || !root.contains(btn)) return;
e.preventDefault();
e.stopPropagation();
const action = btn.dataset.action;
const id = btn.dataset.id;
const card = btn.closest('.stack-card');
btn.disabled = true;
try {
let resp;
if (action === 'add') resp = await doSubscribe(id);
else if (action === 'remove') resp = await doUnsubscribe(id);
else return;
if (!resp.ok) {
const detail = await resp.json().catch(() => ({}));
showToast('Failed: ' + (detail.detail || resp.statusText), true);
btn.disabled = false;
return;
}
showToast(action === 'add' ? 'Added to stack' : 'Removed from stack');
_applyStackChange(card, action === 'add');
} catch (err) {
showToast('Network error: ' + err.message, true);
btn.disabled = false;
}
});
// ── Tab switching ──────────────────────────────────────────────────────
document.querySelectorAll('.stack-tabs button').forEach(b => {
b.addEventListener('click', () => {
const tab = b.dataset.tab;
document.querySelectorAll('.stack-tabs button').forEach(x => {
x.classList.toggle('is-active', x === b);
x.setAttribute('aria-selected', x === b ? 'true' : 'false');
});
document.querySelectorAll('[data-view]').forEach(v => {
v.hidden = v.dataset.view !== tab;
});
if (tab === 'recipes') loadRecipesTab();
});
});
// v53 Recipes tab — fetch on first open then cache for the page
// lifetime. Renders compact cards (no Add-to-stack) so users can
// browse query templates the same way they browse packages.
let _recipesLoaded = false;
async function loadRecipesTab(force) {
if (_recipesLoaded && !force) return;
const grid = document.getElementById('catalog-grid-recipes');
if (!grid) return;
grid.innerHTML = '<div class="stack-empty"><span class="icon">📑</span><h3>Loading recipes…</h3></div>';
try {
const r = await fetch('/api/recipes', { credentials: 'same-origin' });
if (!r.ok) throw new Error('HTTP ' + r.status);
const body = await r.json();
const items = (body && body.items) || [];
const badge = document.querySelector('.stack-tabs .count[data-count="recipes"]');
if (badge) badge.textContent = String(items.length);
if (!items.length) {
grid.innerHTML = '<div class="stack-empty"><span class="icon">📑</span>'
+ '<h3>No recipes yet</h3>'
+ '<p>Recipes are admin-curated query templates — copy + adapt.</p></div>';
_recipesLoaded = true;
return;
}
grid.innerHTML = items.map(_renderRecipeCard).join('');
_recipesLoaded = true;
} catch (e) {
grid.innerHTML = '<div class="stack-empty" style="color:var(--error);">Failed to load recipes: ' + e.message + '</div>';
}
}
function _renderRecipeCard(r) {
const esc = (s) => String(s == null ? '' : s).replace(/[<>&"']/g, (c) =>
({ '<': '&lt;', '>': '&gt;', '&': '&amp;', '"': '&quot;', "'": '&#39;' }[c]));
const color = r.color || 'var(--primary)';
const title = esc(r.title);
const desc = esc(r.description);
const parts = (r.title || '?').split(/\s+/);
const initials = (parts.length >= 2
? parts[0][0] + parts[1][0]
: (r.title || '?').slice(0, 2)).toUpperCase();
const nTables = (r.related_table_ids || []).length;
// Admin actions sit on a footer row inside the card. Use <div> wrapper
// (not <a>) when admin so the per-button onclicks don't fight the
// card-wide anchor for the click. Non-admin keeps the cleaner <a>
// because there's no overlay.
const cardOpen = window.IS_ADMIN
? '<div class="stack-card" data-recipe-id="' + esc(r.id) + '" style="cursor:default;">'
: '<a class="stack-card" href="/catalog/r/' + encodeURIComponent(r.slug) + '" '
+ 'style="text-decoration:none; color:inherit;">';
const cardClose = window.IS_ADMIN ? '</div>' : '</a>';
// For admin, the photo + body get their own anchor so the click
// still drills into the recipe — only the footer Edit/Delete buttons
// are non-navigating.
const adminBodyHref = window.IS_ADMIN
? '<a href="/catalog/r/' + encodeURIComponent(r.slug) + '" '
+ 'style="text-decoration:none; color:inherit; display:block;">'
: '';
const adminBodyClose = window.IS_ADMIN ? '</a>' : '';
const adminFooter = window.IS_ADMIN
? '<div style="display:flex; gap:6px; justify-content:flex-end; '
+ 'padding:6px 12px; border-top:1px solid var(--border-light, #f0f0f0);">'
+ '<button class="btn btn-secondary" type="button" '
+ 'style="font-size:11px; padding:3px 10px;" '
+ 'onclick="event.stopPropagation(); openEditRecipeModal(&#39;' + esc(r.id) + '&#39;)">Edit</button>'
+ '<button class="btn" type="button" '
+ 'style="font-size:11px; padding:3px 10px; color:#b91c1c; border-color:#fca5a5;" '
+ 'onclick="event.stopPropagation(); deleteRecipe(&#39;' + esc(r.id) + '&#39;, &#39;' + esc(r.title) + '&#39;)">Delete</button>'
+ '</div>'
: '';
return cardOpen
+ adminBodyHref
+ '<div class="stack-card__photo" style="background:' + color + '; color:#fff; '
+ 'font-weight:700; font-size:22px; letter-spacing:1px;">' + initials + '</div>'
+ '<div class="stack-card__body">'
+ '<h3 class="stack-card__title">' + title + '</h3>'
+ (nTables
? '<div class="stack-card__meta">' + nTables + ' table' + (nTables === 1 ? '' : 's') + '</div>'
: '')
+ (desc ? '<div class="stack-card__desc">' + desc + '</div>' : '')
+ '</div>'
+ adminBodyClose
+ adminFooter
+ cardClose;
}
// ── Filter chips ───────────────────────────────────────────────────────
let activeFilter = 'all';
let activeSourceFilter = null;
// v51 — set of currently-checked status values (multi-select). Empty
// set means no status filter (= show all).
function _activeStatuses() {
const out = new Set();
document.querySelectorAll('#catalog-status-filter input[type="checkbox"]:checked')
.forEach((el) => out.add(el.value));
return out;
}
function applyFilters() {
// Single source of truth — the hero search input. No hidden mirror
// input to fall out of sync.
const heroEl = document.getElementById('catalog-hero-search');
const q = (heroEl && heroEl.value || '').toLowerCase();
const statuses = _activeStatuses();
document.querySelectorAll('.stack-card').forEach(card => {
const req = card.dataset.requirement;
const inStack = card.dataset.inStack === '1';
const status = card.dataset.status || 'prod';
const title = (card.querySelector('.stack-card__title')?.textContent || '').toLowerCase();
const desc = (card.querySelector('.stack-card__desc')?.textContent || '').toLowerCase();
let show = true;
if (activeFilter === 'required' && req !== 'required') show = false;
if (activeFilter === 'available' && req !== 'available') show = false;
if (activeFilter === 'in_stack' && !inStack) show = false;
// Status filter — empty selection = pass-through (show all).
if (statuses.size && !statuses.has(status)) show = false;
if (activeSourceFilter) {
const tags = card.querySelectorAll('.stack-card__tag');
let hit = false;
tags.forEach(t => { if (t.textContent.trim() === activeSourceFilter) hit = true; });
if (!hit) show = false;
}
if (q && !title.includes(q) && !desc.includes(q)) show = false;
card.hidden = !show;
});
}
// Hook the v51 status checkboxes into the same applyFilters pipeline.
document.querySelectorAll('#catalog-status-filter input[type="checkbox"]').forEach((el) => {
el.addEventListener('change', applyFilters);
});
document.querySelectorAll('[data-filter]').forEach(b => {
b.addEventListener('click', () => {
document.querySelectorAll('[data-filter]').forEach(x => x.classList.toggle('is-active', x === b));
activeFilter = b.dataset.filter;
applyFilters();
});
});
document.querySelectorAll('[data-filter-source]').forEach(b => {
b.addEventListener('click', () => {
const wasActive = b.classList.contains('is-active');
document.querySelectorAll('[data-filter-source]').forEach(x => x.classList.remove('is-active'));
if (!wasActive) {
b.classList.add('is-active');
activeSourceFilter = b.dataset.filterSource;
} else {
activeSourceFilter = null;
}
applyFilters();
});
});
// Single hero search input drives the filter pipeline directly.
var heroSearch = document.getElementById('catalog-hero-search');
if (heroSearch) {
heroSearch.addEventListener('input', applyFilters);
}
// Explicit Search button — visual parity with /marketplace. The
// input already filters live; the button just re-applies and
// returns focus to the input.
var heroSearchBtn = document.getElementById('catalog-search-btn');
if (heroSearchBtn && heroSearch) {
heroSearchBtn.addEventListener('click', function () {
applyFilters();
heroSearch.focus();
});
}
// ── v53 Create Recipe modal (admin-only) ──────────────────────────
// Exposed on window so the inline button onclicks reach it (we're
// inside an IIFE). Close/cancel reset the form so the next open
// starts clean. After create: close, reload Recipes tab.
function _slugifyTitle(s) {
return (s || '').toLowerCase()
.replace(/[^a-z0-9]+/g, '-').replace(/^-|-$/g, '');
}
window.openCreateRecipeModal = function () {
const el = document.getElementById('createRecipeModal');
if (!el) return;
['rcp-title','rcp-slug','rcp-desc','rcp-sql','rcp-related'].forEach(id => {
const i = document.getElementById(id);
if (i) i.value = '';
});
const status = document.getElementById('rcp-status');
if (status) status.value = 'prod';
const color = document.getElementById('rcp-color');
if (color) color.value = 'var(--primary)';
// Collapse + reset the RBAC matrix so reopen doesn't show last
// recipe's group selections.
const det = document.getElementById('rcp-rbac-details');
if (det) det.open = false;
_rcpRbacLoaded = false;
const rowsEl = document.getElementById('rcp-rbac-rows');
if (rowsEl) rowsEl.innerHTML = '<div class="loading" style="padding:6px; color:var(--text-secondary); font-size:12px;">Click to load groups…</div>';
el.style.display = 'block';
};
window.closeCreateRecipeModal = function () {
const el = document.getElementById('createRecipeModal');
if (el) el.style.display = 'none';
const det = document.getElementById('rcp-rbac-details');
if (det) det.open = false;
_rcpRbacLoaded = false;
};
// ── Create Recipe RBAC matrix (lazy hydrate + write-only on save) ──
// Mirror of admin_corporate_memory.html's _cmdHydrateRbacMatrix /
// _submitCmdGrantsInline. Create flow only POSTs grants — there is
// no original to diff against because the recipe doesn't exist yet.
let _rcpRbacLoaded = false;
async function _rcpHydrateRbacMatrix() {
if (_rcpRbacLoaded) return;
const rowsEl = document.getElementById('rcp-rbac-rows');
rowsEl.innerHTML = '<div class="loading" style="padding:6px; color:var(--text-secondary); font-size:12px;">Loading groups…</div>';
try {
const r = await fetch('/api/admin/groups', { credentials: 'same-origin' });
if (!r.ok) throw new Error('HTTP ' + r.status);
const body = await r.json();
const groups = Array.isArray(body) ? body : (body.groups || []);
if (!groups.length) {
rowsEl.innerHTML = '<div style="padding:8px; color:var(--text-secondary); font-size:12px;">No groups defined yet. Create groups in <a href="/admin/access">Resource access</a> first.</div>';
return;
}
const esc = s => String(s == null ? '' : s).replace(/[&<>"']/g, c =>
({'&':'&amp;','<':'&lt;','>':'&gt;','"':'&quot;',"'":'&#39;'}[c]));
rowsEl.innerHTML = groups.map(g => {
const gid = String(g.id || g.name || '');
const gname = String(g.name || gid);
return (
'<div data-group-id="' + esc(gid) + '" '
+ 'style="display:flex; gap:8px; align-items:center; '
+ 'padding:6px; border:1px solid var(--border); border-radius:6px;">'
+ '<span style="flex:1;">' + esc(gname) + '</span>'
+ '<select class="rcp-rbac-req" style="padding:4px; border:1px solid var(--border); border-radius:4px;">'
+ '<option value="" selected>(no grant)</option>'
+ '<option value="available">available</option>'
+ '<option value="required">required</option>'
+ '</select>'
+ '</div>'
);
}).join('');
_rcpRbacLoaded = true;
} catch (e) {
rowsEl.innerHTML = '<div style="padding:8px; color:var(--error); font-size:12px;">Failed to load: '
+ (e.message ? e.message.replace(/[<>&]/g, '') : 'unknown') + '</div>';
}
}
document.addEventListener('toggle', (e) => {
if (e.target && e.target.id === 'rcp-rbac-details' && e.target.open) {
_rcpHydrateRbacMatrix();
}
}, true);
async function _rcpSubmitGrantsInline(recipeId) {
if (!_rcpRbacLoaded) return 0;
const rows = document.querySelectorAll('#rcp-rbac-rows [data-group-id]');
const calls = [];
rows.forEach(row => {
const gid = row.getAttribute('data-group-id');
const sel = row.querySelector('.rcp-rbac-req');
const req = sel && sel.value;
if (!req) return;
calls.push(fetch('/api/admin/grants', {
method: 'POST',
headers: { 'Content-Type': 'application/json' },
credentials: 'same-origin',
body: JSON.stringify({
group_id: gid,
resource_type: 'recipe',
resource_id: recipeId,
requirement: req,
}),
}));
});
if (!calls.length) return 0;
const results = await Promise.allSettled(calls);
return results.filter(
r => r.status === 'rejected' || (r.value && !r.value.ok)
).length;
}
window.openEditRecipeModal = async function (recipeId) {
try {
const r = await fetch('/api/admin/recipes/' + encodeURIComponent(recipeId),
{ credentials: 'same-origin' });
if (!r.ok) throw new Error('HTTP ' + r.status);
const rec = await r.json();
document.getElementById('ercp-id').value = rec.id;
document.getElementById('ercp-title').value = rec.title || '';
document.getElementById('ercp-slug').value = rec.slug || '';
document.getElementById('ercp-desc').value = rec.description || '';
document.getElementById('ercp-sql').value = rec.sql_template || '';
document.getElementById('ercp-related').value =
(rec.related_table_ids || []).join(',');
document.getElementById('ercp-color').value = rec.color || 'var(--primary)';
document.getElementById('ercp-status').value = rec.status || 'prod';
// Reset the RBAC matrix; lazy-rehydrates next time the admin
// expands the <details>, so the panel always reflects the recipe
// the modal is currently editing.
const det = document.getElementById('ercp-rbac-details');
if (det) det.open = false;
_ercpRbacLoaded = false;
_ercpRbacOriginal = {};
document.getElementById('editRecipeModal').style.display = 'block';
} catch (e) {
alert('Failed to load recipe: ' + e.message);
}
};
window.closeEditRecipeModal = function () {
const el = document.getElementById('editRecipeModal');
if (el) el.style.display = 'none';
const det = document.getElementById('ercp-rbac-details');
if (det) det.open = false;
_ercpRbacLoaded = false;
_ercpRbacOriginal = {};
};
// ── Edit Recipe RBAC matrix (lazy hydrate + diff on save) ──
// Mirror of admin_corporate_memory.html's _emdHydrateRbacMatrix /
// _emdDiffApplyGrants. resource_type is 'recipe' — wire shape is
// identical (groups + grants list, requirement enum, POST/DELETE
// delta against /api/admin/grants).
let _ercpRbacLoaded = false;
let _ercpRbacOriginal = {};
async function _ercpHydrateRbacMatrix() {
if (_ercpRbacLoaded) return;
const recipeId = document.getElementById('ercp-id').value;
const rowsEl = document.getElementById('ercp-rbac-rows');
rowsEl.innerHTML = '<div class="loading" style="padding:6px; color:var(--text-secondary); font-size:12px;">Loading groups + grants…</div>';
try {
const [gResp, grResp] = await Promise.all([
fetch('/api/admin/groups', { credentials: 'same-origin' }),
fetch('/api/admin/grants?resource_type=recipe',
{ credentials: 'same-origin' }),
]);
if (!gResp.ok) throw new Error('groups HTTP ' + gResp.status);
if (!grResp.ok) throw new Error('grants HTTP ' + grResp.status);
const gBody = await gResp.json();
const groups = Array.isArray(gBody) ? gBody : (gBody.groups || []);
const grants = await grResp.json();
const current = {};
(grants || []).forEach(g => {
if (g.resource_id !== recipeId) return;
current[g.group_id] = g.requirement;
});
_ercpRbacOriginal = Object.assign({}, current);
if (!groups.length) {
rowsEl.innerHTML = '<div style="padding:8px; color:var(--text-secondary); font-size:12px;">No groups defined yet. Create groups in <a href="/admin/access">Resource access</a> first.</div>';
return;
}
const esc = s => String(s == null ? '' : s).replace(/[&<>"']/g, c =>
({'&':'&amp;','<':'&lt;','>':'&gt;','"':'&quot;',"'":'&#39;'}[c]));
rowsEl.innerHTML = groups.map(g => {
const gid = String(g.id || g.name || '');
const gname = String(g.name || gid);
const cur = current[gid] || '';
const opt = (v, label) =>
'<option value="' + esc(v) + '"' + (cur === v ? ' selected' : '') + '>' + esc(label) + '</option>';
return (
'<div data-group-id="' + esc(gid) + '" '
+ 'style="display:flex; gap:8px; align-items:center; '
+ 'padding:6px; border:1px solid var(--border); border-radius:6px;">'
+ '<span style="flex:1;">' + esc(gname) + '</span>'
+ '<select class="ercp-rbac-req" style="padding:4px; border:1px solid var(--border); border-radius:4px;">'
+ opt('', '(no grant)')
+ opt('available', 'available')
+ opt('required', 'required')
+ '</select>'
+ '</div>'
);
}).join('');
_ercpRbacLoaded = true;
} catch (e) {
rowsEl.innerHTML = '<div style="padding:8px; color:var(--error); font-size:12px;">Failed to load: '
+ (e.message ? e.message.replace(/[<>&]/g, '') : 'unknown') + '</div>';
}
}
document.addEventListener('toggle', (e) => {
if (e.target && e.target.id === 'ercp-rbac-details' && e.target.open) {
_ercpHydrateRbacMatrix();
}
}, true);
async function _ercpDiffApplyGrants(recipeId) {
if (!_ercpRbacLoaded) return 0;
const rows = document.querySelectorAll('#ercp-rbac-rows [data-group-id]');
const wantDelete = [];
const wantWrite = [];
rows.forEach(row => {
const gid = row.getAttribute('data-group-id');
const sel = row.querySelector('.ercp-rbac-req');
const cur = (sel && sel.value) || '';
const orig = _ercpRbacOriginal[gid] || '';
if (cur === orig) return;
if (!cur) wantDelete.push(gid);
else {
if (orig) wantDelete.push(gid);
wantWrite.push({ group_id: gid, requirement: cur });
}
});
if (!wantDelete.length && !wantWrite.length) return 0;
let grantIdByGroup = {};
if (wantDelete.length) {
const lr = await fetch('/api/admin/grants?resource_type=recipe',
{ credentials: 'same-origin' });
if (lr.ok) {
const arr = await lr.json();
arr.forEach(g => {
if (g.resource_id !== recipeId) return;
grantIdByGroup[g.group_id] = g.id;
});
}
}
// Sequential DELETE → POST to avoid the UNIQUE-constraint race on
// (group_id, resource_type, resource_id). See the matching note in
// admin_tables.html _edpDiffApplyGrants.
const deleteResults = await Promise.allSettled(
wantDelete
.map(gid => grantIdByGroup[gid])
.filter(Boolean)
.map(gid => fetch('/api/admin/grants/' + encodeURIComponent(gid),
{ method: 'DELETE', credentials: 'same-origin' }))
);
const writeResults = await Promise.allSettled(
wantWrite.map(w => fetch('/api/admin/grants', {
method: 'POST',
headers: { 'Content-Type': 'application/json' },
credentials: 'same-origin',
body: JSON.stringify({
group_id: w.group_id,
resource_type: 'recipe',
resource_id: recipeId,
requirement: w.requirement,
}),
}))
);
const results = deleteResults.concat(writeResults);
return results.filter(
r => r.status === 'rejected' || (r.value && !r.value.ok)
).length;
}
window.submitEditRecipe = async function () {
const btn = document.getElementById('ercp-submit-btn');
const id = document.getElementById('ercp-id').value;
const title = document.getElementById('ercp-title').value.trim();
if (!id || !title) { alert('Title is required.'); return; }
const related = document.getElementById('ercp-related').value
.split(',').map(s => s.trim()).filter(Boolean);
const body = {
title: title,
description: document.getElementById('ercp-desc').value.trim() || null,
sql_template: document.getElementById('ercp-sql').value || null,
related_table_ids: related,
color: document.getElementById('ercp-color').value || null,
status: document.getElementById('ercp-status').value || 'prod',
};
btn.disabled = true;
try {
const r = await fetch('/api/admin/recipes/' + encodeURIComponent(id), {
method: 'PUT',
headers: { 'Content-Type': 'application/json' },
credentials: 'same-origin',
body: JSON.stringify(body),
});
if (!r.ok) {
const d = await r.json().catch(() => ({}));
let msg = d.detail || r.statusText;
if (Array.isArray(msg)) msg = msg.map(x => x.msg).join('; ');
alert('Save failed: ' + msg);
return;
}
// Apply any RBAC matrix deltas after the metadata PUT — the
// grants endpoint is independent of the recipes PUT, so a partial
// failure here gets surfaced as a toast without blocking the save.
const rbacFails = await _ercpDiffApplyGrants(id);
if (rbacFails > 0 && typeof showToast === 'function') {
showToast(rbacFails + ' group access change(s) failed', 'error');
}
window.closeEditRecipeModal();
if (typeof showToast === 'function') {
showToast('Recipe "' + title + '" saved');
}
_recipesLoaded = false;
loadRecipesTab(true);
} catch (e) {
alert('Network error: ' + e.message);
} finally {
btn.disabled = false;
}
};
window.deleteRecipe = async function (recipeId, title) {
// v54: soft delete + undo toast. No confirm() — the Undo button on
// the toast is the recovery affordance; a confirm + undo together
// is friction without payoff.
try {
const r = await fetch('/api/admin/recipes/' + encodeURIComponent(recipeId),
{ method: 'DELETE', credentials: 'same-origin' });
if (!r.ok && r.status !== 204) {
const d = await r.json().catch(() => ({}));
alert('Delete failed: ' + (d.detail || r.statusText));
return;
}
_recipesLoaded = false;
loadRecipesTab(true);
if (typeof window.showUndoToast === 'function') {
window.showUndoToast(
'Recipe "' + title + '" deleted.',
'/api/admin/recipes/' + encodeURIComponent(recipeId) + '/restore',
() => { _recipesLoaded = false; loadRecipesTab(true); },
);
}
} catch (e) {
alert('Network error: ' + e.message);
}
};
window.submitCreateRecipe = async function () {
const btn = document.getElementById('rcp-submit-btn');
const title = document.getElementById('rcp-title').value.trim();
if (!title) { alert('Title is required.'); return; }
let slug = document.getElementById('rcp-slug').value.trim();
if (!slug) slug = _slugifyTitle(title);
const related = document.getElementById('rcp-related').value
.split(',').map(s => s.trim()).filter(Boolean);
const body = {
slug: slug,
title: title,
description: document.getElementById('rcp-desc').value.trim() || null,
sql_template: document.getElementById('rcp-sql').value || null,
related_table_ids: related,
color: document.getElementById('rcp-color').value || null,
status: document.getElementById('rcp-status').value || 'prod',
};
btn.disabled = true;
try {
const r = await fetch('/api/admin/recipes', {
method: 'POST',
headers: { 'Content-Type': 'application/json' },
credentials: 'same-origin',
body: JSON.stringify(body),
});
if (!r.ok) {
const d = await r.json().catch(() => ({}));
let msg = d.detail || r.statusText;
if (Array.isArray(msg)) msg = msg.map(x => x.msg).join('; ');
alert('Create failed: ' + msg);
return;
}
const respBody = await r.json().catch(() => ({}));
const newRecipeId = respBody.id;
// Apply optional inline RBAC matrix on success — same write-only
// pattern as Create Memory Domain. Failures bubble up as a toast
// without rolling back the recipe.
let grantFails = 0;
if (newRecipeId) {
grantFails = await _rcpSubmitGrantsInline(newRecipeId);
}
window.closeCreateRecipeModal();
if (typeof showToast === 'function') {
const base = 'Recipe "' + title + '" created';
if (grantFails > 0) {
showToast(base + ' — ' + grantFails + ' grant(s) failed', 'error');
} else {
showToast(base);
}
}
// Force-refresh the Recipes tab so the new row shows.
_recipesLoaded = false;
loadRecipesTab(true);
} catch (e) {
alert('Network error: ' + e.message);
} finally {
btn.disabled = false;
}
};
})();
</script>
{% endblock %}
Reference in a new issue View git blame Copy permalink