# Changelog All notable changes to Agnes AI Data Analyst. Format: [Keep a Changelog](https://keepachangelog.com/en/1.1.0/). Versions follow [Semantic Versioning](https://semver.org/spec/v2.0.0.html), pre-1.0 — public surface (CLI flags, REST endpoints, `instance.yaml` schema, `extract.duckdb` contract) may shift between minor versions; breaking changes called out under **Changed** or **Removed** with the **BREAKING** marker. CalVer image tags (`stable-YYYY.MM.N`, `dev-YYYY.MM.N`) are produced for every CI build; semver tags (`v0.X.Y`) are cut at release boundaries and reference the same commit as a `stable-*` tag from the same day. --- ## [Unreleased] ### Added - `instance.custom_scripts`: operator-injected HTML/JS blocks rendered into every page that extends `base.html`. Each entry takes `name`, `enabled`, `placement` (`head_start` | `head_end` | `body_end`), and `html`. Use for feedback widgets (Marker.io), analytics (GTM, PostHog), error capture (Sentry). Admin-only; rendered with `| safe` — same trust boundary as `instance.logo_svg` / `instance.overview`. Empty default keeps the OSS vendor-neutral. Resolved by `app/instance_config.py::get_custom_scripts()`; surfaced in `/admin/server-config` via `_KNOWN_FIELDS["instance"]`. Example Marker.io block in `config/instance.yaml.example`. - New `marketplace.curators_url` config item (editable via `/admin/server-config` → **Marketplace** section). Drives the "See all curators →" link on the `/marketplace` curated-tab info block; when empty the link is hidden (matches today's behaviour). SSRF-guarded on save (private-IP allowlist, same posture as `data_source.keboola.stack_url`). - `/home` now opens with a value-first intro hero — eyebrow greeting, one-line product framing, **Set up in ~15 min** / **Just browse** CTAs, and a four-pillar row (Data packages · Plugins · Skills · Memory) — so analysts understand *what* the instance is before any install step. - New **Your first session** narrative on `/home` walks through the five beats of a real session (launch → pick project → memory loads → ask → close) with mock terminal frames so the visual rhythm is obvious before the user copies their first command. - Setup wizard inside the install-hero now carries a progress chip (`Step 1 of N · ~15 min · One-time · Reversible`), a thin progress bar, and per-step number badges next to each install block. - `/home` welcome hero gains a *footnotes* row beneath the four pillars: a hairline-separated block rendering operator-authored HTML from `instance.overview` (`AGNES_INSTANCE_OVERVIEW` env override). This is the same `| safe`-filtered body that used to drive the standalone Overview section between the walkthrough and surfaces grid — the rendering contract is unchanged, only the location and styling moved. Empty yaml → footnotes absent (OSS stays vendor-neutral). Renders for both onboarded and not-onboarded users. - Welcome hero's *"AI Chief of Staff"* lede gains a trailing sentence ("*You run all your projects inside and it learns from it.*") so the workspace-folder framing lands before the reader scrolls past. - Default `instance.theme` flipped from `navy` to `blue`. The brand-blue palette is now the out-of-the-box look; `navy` (dark hero + mint-green CTAs) is the opt-in via `AGNES_INSTANCE_THEME` / `instance.theme` / admin server-config. Existing instances that explicitly set `navy` are unaffected; instances relying on the implicit default will switch to blue. - `/home` palette shifted from blue to green/navy: brand accent is now `#2ea877` (mint green) on light surfaces, hero card is navy `#0f1b3a`, code panels are near-black `#0c1224` with warm-yellow `#ffd866` accents. The existing `--hp-primary` token alias is reused so all downstream rules pick up the new green automatically; instance theme overrides via `config.theme_overrides()` still win. - VS Code surface tile on `/home` carries a **Recommended** pill so new analysts default to the editor flow. - "Want to look around first?" section renamed to **Explore your workspace**, with an `id="look-around"` anchor wired to the new hero's secondary CTA. - `/home` setup wizard restructured to match the published design spec section by section: header (eyebrow + heading + lede) floats above the card, install hero is a plain bordered surface (no accent strip), per-step labels drop the `Step N —` prefix, and the closing strip is a single flex row with the `agnes pull` waiting status on the left and the *Already set up? Mark me as onboarded →* fallback link on the right. - VS Code surface tile on `/home` now renders the recommended-layout screenshot (served from `/static/img/vscode-layout.png`) and opens a full-page lightbox on click. Falls back to the labeled EXPLORER/TERMINAL panel when the image is missing. - Workspace install path moved to `~/Desktop/{workspace_dir}` across every step, surface card, and shortcut command. The Step 2 recommendation callout acknowledges home-folder placement as a valid fallback. - Step 1 verify text in the install hero reintroduces the Enterprise plan as the Finance and Legal option alongside Pro / Max 5× / Max 20×. - Step 6 shortcut installs a shell *function* (not an alias) so arguments pass through with `"$@"` (unix) and `@args` (Windows), and offers an end-user **Auto / YOLO** permission toggle — `--permission-mode auto` by default, `--dangerously-skip-permissions` for the YOLO variant. - Step 5 *Or paste manually* fallback `
` is now inline on the copy-script button row (right-aligned when closed, full-width preview when opened); the description above the row reads at the standard step-lede size instead of the previous 13px chip. ### Fixed - Google Workspace connector prompt's Step 8 verify no longer asks Claude to parse a row count out of `gws drive files list` / `gws chat spaces list` JSON. Claude would improvise a `python3 -c 'f"… {len(d.get(\"files\",[]))}…"'` snippet that fails two ways: f-string expressions reject backslashes in Python <3.12 (`SyntaxError`), and `gws` can emit a banner before the JSON body (`json.JSONDecodeError`). Step 8 now treats exit code 0 as success, drops the ` drive file(s), chat space(s) visible` counts, and explicitly warns against both anti-patterns. The summary-grep prefix (`✅ Google Workspace ready —`) is preserved. - Install-script Step 2 + Step 9 restart cue + post-install `/home` hero now reference `~/Desktop/` to match the `/home` "Step 2 — pick a folder" recommendation users actually run (`mkdir -p ~/Desktop/`). Previously the pasted setup script checked `pwd` against `$HOME/` and would warn "Foundry AI is normally installed in ~/FoundryAI" even though the /home page had just sent the user to `~/Desktop/FoundryAI`. - Pre-login pages (`/login`, magic-link screens, first-time `/setup`) now honour the configured `instance.theme`. `base_login.html` sets `` from `instance_theme`, additionally loads `design-tokens.css` so the `.btn-primary` Google SSO button gets its `--ds-primary` green fill (previously rendered as invisible white text on a white card because the `--ds-*` tokens weren't defined), and the navy variant flips the `.login-features` hero panel from brand-blue `--primary` to the deep-navy gradient — eliminating the jarring blue → navy flip after sign-in on navy-configured instances. - Skill / agent detail pages nested inside a Flea Market plugin rendered the parent plugin's title on the hero instead of the skill/agent name. The frontend fallback chain branched on `source === 'curated'` and so flea-inner items fell through to `d.plugin_name`, which the inner-detail API populates with the parent entity name. Branch now keys on the presence of an inner segment in the URL so inner items use `d.name || innerName` (the actual skill/agent name) and standalone flea plugins keep their `d.plugin_name`. - `/activity-center` audit-log hero rendered as half-width because `_page_hero.html` was nested inside `
`, a flex row that pinned the time-range + auto-refresh controls beside it. The hero is now a sibling rendered before the `
` so it spans the full container width like every other admin page; the controls keep their original flex row underneath. - Same flex-row squeeze applied to `/admin/users`, `/admin/access`, `/admin/groups`, `/admin/marketplaces`, `/admin/server-config`, `/admin/welcome`, `/admin/workspace-prompt`, `/admin/sessions`, `/admin/sessions/`, `/admin/usage`. Each had `_page_hero.html` nested inside a `display: flex; justify-content: space-between` toolbar that pinned the page filter/search controls next to the hero. Hero now renders outside the toolbar so it spans the full container width; toolbar continues to hold only the controls. - Page-shell canonicalised — `.container` in `style-custom.css` now sets the canonical `1280px` max-width and `16px 32px 48px` padding so every page (admin, marketplace, catalog, profile, /home, /setup-advanced) inherits the same nav-to-hero gap and side gutters. Per-page `.container:has(.) { max-width: none }` + `.-page { max-width: 1400px }` overrides removed from `admin_users`, `admin_access`, `admin_groups`, `admin_marketplaces`, `admin_welcome`, `admin_workspace_prompt`. `.page-header--hero` no longer self-constrains via `max-width: var(--width-app)`; the container provides the width so the hero sits flush with the toolbar / table beneath it. - `_page_chrome.html` trimmed to just the page-background tint for the redesign scopes (`/home`, `/store`, `/setup-advanced`); the duplicate `.container` + `.container > main` rules it carried are redundant with the new canonical container. - Marketplace hero unified with the canonical `.page-header--hero` box. The bespoke `.mp-hero` rule duplicated padding, radius, gradient, shadow, and font sizes that already lived on `.page-header--hero`; markup is now `
` so the shared box drives dimensions + colour, and `.mp-hero` only adds the right-anchored cover image. Inner text uses the `.page-header__eyebrow / __title / __subtitle` classes the rest of the app already uses. Same width, same height, same shadow tint as every other page-hero on the app. - `/admin/tables`, `/admin/tokens`, `/install`, `/profile`, `/store/upload`, `/setup-advanced`, `/catalog`, `/corporate-memory` page heroes now all share the canonical `.page-header--hero` dimensions (padding, border-radius, max-width, shadow tint). Each page either migrated to the shared `_page_hero.html` include (`admin_tables`, `profile`) or kept its bespoke wrapper with the canonical class added (`admin_tokens`, `install`, `store_upload`) so per-page extras (counts chips, version pills) live as children inside the canonical box. `.stack-hero` (catalog + memory search hero) and `.advanced-mock .ad-hero` (setup-advanced) now reference the same gradient + dimensions so widths line up across the app. - `.page-header--hero` shadow tint follows the brand blue (`rgba(0, 115, 209, 0.2)`) instead of the legacy green (`rgba(46, 168, 119, 0.2)`) — the gradient is blue everywhere outside the `/home` redesign, so the depth highlight now matches. - Setup-section heading on `/home` no longer right-aligns. The inherited `header { display: flex; justify-content: space-between }` rule from the legacy stylesheet was kicking in on the new section header; the wrapper is now a `
` so the eyebrow / heading / lede stack normally on the left. - `/home` (onboarded view) and `/setup-advanced` hero gradients picked up the new green palette — both pages still carried the retired blue (`#0056A3`) endpoint as a per-template override, reading visibly out of sync with the rest of the app. Both pages now reference `var(--primary-dark)` so any future palette shift cascades automatically. - `/setup-advanced` YOLO snippet was the old `alias yolo="claude --dangerously-skip-permissions"` form (no `cd`, no arg forwarding). Replaced with the shell function variant that matches `/home` Step 6 — drops into `~/Desktop/{workspace_dir}` and forwards `"$@"` (unix) / `@args` (Windows). - `/setup-advanced` workspace path references migrated from `~/{workspace_dir}` to `~/Desktop/{workspace_dir}` so the install story is consistent between `/home` and `/setup-advanced`. - "Setup a new Claude Code" CTA button on `/dashboard` is now labelled **Copy install script to clipboard**, matching `/home` and the canonical action wording now documented inside `_claude_setup_cta.jinja`. - Global brand colour reverted to blue (`--primary: #0073D1`). Login, dashboard, catalog, marketplace, admin, profile, etc. read blue again. The `/home` redesign green palette is now an opt-in via the local `.home-mock` / `.advanced-mock` scopes (explicit green hex set in-scope, not via `var(--primary)`), so the green only applies on the redesigned pages. ### Internal - New `app/web/static/css/design-tokens.css` declares the `--ds-*` design-system token set (green/navy palette, system font stack, callout vocabularies, navy-tinted elevation shadows) globally on `:root`. Loaded by `base.html` alongside `style-custom.css`. - `.home-mock` and `.advanced-mock` scopes in `home_not_onboarded`, `home_onboarded`, and `setup_advanced` reference `var(--ds-*)` so the values live in one place. Local `--hp-*` declarations removed from all three templates (~330 token declarations deduped to a single source). Tokens stay opt-in: pages without one of those scope classes don't pick up any `--ds-*`-driven styling and keep reading the legacy `--primary` family. - New `app/web/static/css/components.css` carries the first set of shared design-system components, free of any scope prefix and reusable on any page: `.callout-rec` (amber lightbulb), `.callout-hint` (blue info), `.code-output` (dashed "what you should see" block), `.lightbox` (image enlarge overlay), `.setup-section-header` (eyebrow + heading + lede wizard header). Loaded by `base.html`. - `/home` install hero migrated to the shared classes — markup renamed (`class="rec"` → `class="callout-rec"`, `class="hint"` → `class="callout-hint"`, `class="expected-output"` → `class="code-output"`). Local `.home-mock .install-block .rec`, `.hint`, `.expected-output`, `.setup-section-header`, and `.lightbox` CSS rules removed from `home_not_onboarded.html` — they now live in `components.css` and any page can pick them up by adding the class. Wizard-specific patterns (`.install-cmd`, `.os-tabs`, `.mode-tabs`, `.terminal-frame`) stay scoped to the template for now; future PR work can lift them once a second consumer needs them. ### Removed - Collapsed-by-default *Getting Started* `
` block at the top of `/home` (the in-page anchor it carried — *Setup Agnes in your Claude Code* / *Go deeper into your AI workspace* — duplicated links already reachable from the install hero and `/setup-advanced`). - Operator-owned *Overview* `
` on `/home` no longer renders as a standalone block between the first-session walkthrough and the surfaces grid. The same operator-authored HTML body (`instance.overview` / `AGNES_INSTANCE_OVERVIEW`) now renders inside the welcome hero footnotes instead (see *Changed* above) — the rendering contract is unchanged, only the location and styling moved, so existing instances that set the yaml field get the same content in the new home. ### Removed ### Internal ## [0.55.6] - 2026-05-20 ### Fixed - `agnes query --remote`: SQL using only a full backtick BQ path (`` `..` ``) no longer fails with `Parser Error: syntax error at or near "``"`. The rewriter now detects backtick-quoted paths and wraps them in `bigquery_query()` before passing to DuckDB, instead of sending the BQ-native backtick syntax to the local DuckDB parser. (#363) ## [0.55.5] — 2026-05-19 ### Fixed - `agnes init` now runs `_chmod_workspace_hooks(workspace)` for OVERRIDE mode too (Initial Workspace Template seed-repo flow), not just the DEFAULT path. Override-mode workspaces seeded from an admin's template repo were leaving hooks like `.claude/hooks/skill-nudge/nudge.sh` and `.claude/hooks/prompt-history/log-prompt.sh` non-executable when the seed repo's git checkout didn't preserve the +x bit (`core.filemode=false`, archive extractions, FUSE/NFS mounts), and every SessionStart fired `Permission denied`. The chmod helper already recurses (`rglob`) so subdir-scoped hook layouts were covered — the bug was that the call site sat inside the `if not override_active:` block. Moved out to a common step before the first pull so every init path runs it. - Inline `` chips inside the blue install-hero on `/home` (both not-onboarded install steps + onboarded welcome paragraph) now render as amber-on-dark-navy with a subtle amber border instead of the previous `rgba(255,255,255,0.12)` faint-white-on-blue pill with inherited white text. The previous combination was ≈2:1 contrast (fails WCAG AA) and the chip silhouette merged into the hero gradient, so `claude --version`, `~/Agnes`, `/agnes-private`, `~/.claude/settings.local.json`, etc. looked like a muddy blob rather than a readable code chip. New rule lands at ≈9:1 contrast and matches the existing `.install-cmd` copy-button-box palette. Two inline `style="background: rgba(255,255,255,0.12);..."` overrides in the lead paragraphs of both home templates dropped so the CSS rule wins; styling now lives in one place per hero scope (`.install-hero code` / `.hero code`). ## [0.55.4] — 2026-05-19 ### Security - Bumped `idna` from 3.11 to 3.15 (Dependabot, #357). 3.14 closed a bypass of the CVE-2024-3651 mitigation by rejecting oversize inputs up-front (**CVE-2026-45409**); 3.15 hardens further by enforcing the DNS-length cap on individual labels early in `check_label`. Transitive dependency of `requests` / `httpx` — bumped via `uv.lock` only, no surface-area change. ## [0.55.3] — 2026-05-19 ### Changed - **BREAKING:** `src/rbac.can_access_table` + `get_accessible_tables` now route through Data Package stack membership instead of per-table `resource_grants`. Per-table grants no longer surface a table to analysts on their own — admins must wrap tables in a Data Package and grant the package (Required or in the user's stack). `manifest.direct_tables` is always `[]` (key kept for older-CLI destructuring). Internal tables (`agnes_sessions/telemetry/audit`) + admin god-mode keep their carve-outs. Standardised 403 detail across every CLI gate (`/api/data/*`, `/api/query`, `/api/v2/sample`, `/api/v2/scan`, `/api/v2/schema`): *"Table 'X' is not in your stack. Ask an admin to add it to a Data Package you have access to (Required or in your stack), then run `agnes pull` to refresh."* New shared test helper `tests.conftest.grant_table_via_package` replaces the legacy `resource_grants(table)` pattern across 8 test files. Closes #356 / #333 follow-up. - `agnes diagnose` is now role-aware. A fresh analyst install no longer reports `Overall: degraded` just because the server has operator-side warnings (stale tables, session-pipeline cadence, BQ billing-project config) that the analyst can't act on. Server (`/api/health/detailed`) tags every check with `audience: "analyst" | "operator"` plus a top-level `caller_role` derived from `user.is_admin` and an `overall_analyst` aggregation. Client excludes operator checks from the headline for analyst callers, surfaces operator warning count on a secondary line so they stay visible, auto-promotes admin/operator callers to the full aggregation, and lets analysts opt in via `--include-operator-checks`. Legacy servers (no `caller_role`) keep the pre-#345-B full aggregation — no silent regression. Closes #345 B. ### Added - `AGNES_MARKETPLACE_URL` env override for `agnes refresh-marketplace --bootstrap`. Pre-fix the marketplace endpoint was hardcoded to `{server_host}/marketplace.git/`, which broke deployments that serve the marketplace from a different host than the API (reverse-proxy split, CDN-fronted marketplace). When set, the env var is parsed via `urlparse`; missing scheme or host fails fast with a clear error (operator misconfiguration surfaces immediately). The PAT injection / strip behavior is preserved on the override path. Default behavior unchanged when the env var is empty / unset. Closes #345 A. ### Added - `agnes query --json` is now a shortcut for `--format json` — paste-prompts and LLM-assisted analysts routinely reach for `--json` first, and the typer "Did you mean `--stdin`?" suggestion the missing flag previously produced was actively misleading. `--json --format ` is rejected as mutually exclusive (`--json --format json` is redundantly allowed). Closes #345 D. ### Internal - Added explicit 5xx-path regression test alongside the existing 4xx case for `agnes query --remote` to lock in the `raise typer.Exit(1)` rc=1 contract for any non-2xx response (`tests/test_cli_query.py::test_remote_query_5xx_exits_nonzero`). No code change — the existing exit-code logic already does the right thing; the test guards against future regression. Closes #345 C. ### Fixed - **UI consistency pass** (I-UI-01..05): radio-card selected state on `/admin/tables` (14 cards get blue border + light bg highlight via `.sync-option-card:has(input:checked)`); promoted `.label-qualifier` / `.optional` to global rule (drops local duplicate); inline `` migrated to design tokens with bg + border; `.btn-google` hover hardcoded swatches replaced with vars; `.code-block code` border + radius reset for dark containers; `.form-textarea` promoted to global. Plus #340 follow-up: removed leftover Phase F2 `{% if data_source_type == 'keboola' %}` guard around edit-modal JS so handlers ship to every instance type (Discover button onclick call sites still respect the guard). Closes #347 (credit @MonikaFeigler). - `agnes refresh-marketplace` (non-bootstrap path) now re-applies `chmod +x` to every `.sh` under `~/.agnes/marketplace` after each `git reset --hard FETCH_HEAD`, not just on the initial bootstrap clone. `git reset --hard` rewrites the working tree from the tree object — if the upstream tree stores a hook script as non- executable (or on `core.filemode=false` setups), every refresh silently re-strips the +x bit and the previously-fixed hooks fire with "Permission denied" again on the next `SessionStart`. Extracted `_chmod_clone_sh_files()` helper, called from both `_bootstrap_clone` and `_git_fetch_and_reset`. Best-effort, no-op on Windows NTFS. Closes the coverage gap Devin Review flagged on PR #350. - Stripped six stale unresolved merge-conflict markers (`<<<<<<<` / `=======` / `>>>>>>>`) from the `[0.55.1]` section of `CHANGELOG.md` that landed on `main` via PR #350's release-cut commit. Markers were rendering as raw conflict text on GitHub and in any tooling that parses the changelog; the HEAD-side content inside each pair is what was kept (the incoming side held superseded intermediate-commit duplicates). ### Fixed - **First-demo UX polish on /catalog** (2026-05-19): Browse grid now groups **Required** packages first instead of by `created_at` so the most-relevant adopt-immediately items lead. `.stack-card__desc` line clamp bumped 2 → 4 lines so card descriptions get more room. `/catalog/t/` table-detail page dropped four editorial sections (Sample questions / What's inside / Things to know / Pairs well with) — hero (name + description + parent packages) only. Same Browse-order treatment applied to `/corporate-memory`. ## [0.55.2] — 2026-05-19 ### Fixed - **Customer-instance Terraform module pre-creates `/data/uploads`** (`infra/modules/customer-instance/startup-script.sh.tpl`). v50/0.55.0 added a marketplace cover-image upload directory mounted under `${DATA_DIR}/uploads`; `app/main.py` eagerly mkdirs it at boot for the `StaticFiles` mount. On host-bind deploys where `/data` root is root-owned, the container's non-root `agnes` user (UID 999) can't create the directory and the app crashloops with `PermissionError: '/data/uploads'`. The startup script now pre-creates `uploads` alongside `state/analytics/extracts` under the existing `chown -R 999:999`. Fresh VMs provisioned at `infra-v1.9.0`+ get the dir at first boot; for existing instances bump the module pin + `terraform apply` (which rewrites the instance startup-script metadata) and reboot the VM so the refreshed mkdir/chown block replays. As a one-off without rebooting, run `sudo mkdir -p /data/uploads && sudo chown 999:999 /data/uploads` on the host. ## [0.55.1] — 2026-05-19 ### Added - `/home` install-hero lead now includes a short "What leaves your machine" privacy callout: explains that prompts / tool-calls / tool-responses travel back to the central catalog while raw data rows stay local, and points at `/agnes-private` as the per-session opt-out. - `agnes init` now accepts `--token-file ` and `AGNES_TOKEN` env-var fallback alongside `--token`. Precedence: `--token` > `--token-file` > `AGNES_TOKEN`. The file-/env-var paths dodge Claude Code's auto-classifier, which sometimes flags a long bearer token in an `--token "eyJ..."` command line as a credential-exfil pattern. The pasted setup script now uses `--token-file ~/.agnes/token` (token written via single-quoted heredoc, umask 077) for the same reason. ### Changed - `/home` onboarding install-hero reordered: folder creation is now Step 2 (was Step 3) and starting Claude with `claude --dangerously-skip-permissions` is the new Step 3, rendered with the same `.install-cmd` + copy-button affordance as the other steps. Step 4 paste runs ~20 shell commands that auto-accept-edits would not cover (Bash still prompts), so the YOLO flag is the default recommendation (session-scoped, drops on next plain `claude`). Shift + Tab → auto-accept-edits kept as the strict- review fallback; persistent YOLO allowlist link to `/setup-advanced#yolo` opens in a new tab so users don't lose their `/home` install context. Setup script's "Verify cwd" warning copy refreshed to reference "/home Step 2". - `agnes init` adds `Bash(agnes *)` to the default `permissions.allow` list in the seeded `.claude/settings.json`. Without it, Claude Code was blocking subsequent `agnes ` invocations (`agnes catalog`, `agnes pull`, …) inside the workspace it had just bootstrapped. - `agnes init` and `agnes refresh-marketplace --bootstrap` now `chmod +x` every `.sh` they land on disk (`/.claude/hooks/*.sh` after init; every `.sh` under `~/.agnes/marketplace` after a clone/pull). Git checkout doesn't always preserve the file-mode bit (filemode=false repos, ZIP extractions), so hooks were firing with "Permission denied" — silent `SessionStart` / `PreToolUse` breakage. Best-effort: no-op on Windows NTFS. - Setup script step 3 now uses `--token-file ~/.agnes/token` plus a single-quoted heredoc for the token write, and includes an explicit note about the `!` prefix fallback when Claude Code's classifier blocks an `agnes ` invocation (e.g. `! agnes init …`). - Setup script step 1 (no-CA install path) now emits a robust `grep -qF + ||` snippet for the optional `~/.local/bin` PATH persistence so re-runs don't append a duplicate entry to the user's rc file (fixed-string match + short-circuit per the dedup bug report). ## [0.55.0] — 2026-05-19 ### Added - **Extended Data Packages content (v56 schema)** backing the rewritten `/catalog/p/` package detail page per the extended-descriptions admin extended-descriptions spec. Eight new schema fields, validated API, per-section template rendering, Browse-grid card augmentation: * **`data_packages`** gains owner_name + owner_team (rendered as "Owned by X · Team" line on hero + Browse card), tags (JSON list of category strings), long_description (markdown body for the "What it is" section), when_to_use + when_not_to_use (paired "Use it when / Skip it when" panels), example_questions (package- level flagship list as a one-click prompt panel). * **`table_registry`** gains grain, platforms, partition_col, history, gotchas — structured per-table documentation surfaced in the collapsible per-table row on the package detail page. First `gotcha` with `key=true` renders as a distinct "Key gotcha" block. * **Virtual badges** (`curated` / `new`) derived render-time from creator Admin-group membership + 30-day created_at window — no extra DB column needed. Surfaced on Browse-grid cards (`data-badge="…"` hooks) + the detail-page hero. - **`PUT/POST /api/admin/data-packages`** and **`PATCH /api/admin/registry/{id}/docs`** accept the new fields with per-field validation matching the extended-descriptions admin spec checklist (tags ≤8 × ≤30 chars, long_description ≤4000, bullets ≤8 × ≤200, example_questions ≤12, gotchas ≤8). PATCH echoes the fresh state for round-trip rendering. - **CI guard `test_data_packages_no_vendor_content.py`** scans `app/` + `src/` + `cli/` + `config/` + `scripts/` for vendor-specific tokens from the colleague's spec MD; fails CI if any leak into OSS surfaces. Vendor content stays in the private infra repo's admin- import flow. - **`+ New Memory Item`** button on `/admin/corporate-memory` for admin-seeded items (rules, playbooks, decisions). Modal chains POST `/api/memory` → optional PATCH `domain_ids` → POST `/admin/batch?action=approve|mandate`, so admin-created items land directly as Approved (or Mandatory if the Required checkbox is ticked) without going through Pending review. - **`domains: list[str]`** field on every memory-item API response. The bulk + single-item hydration paths now emit the full slug list, in addition to the legacy `domain` single-slug surface kept for back-compat. The admin queue renders all chips with a `+N` overflow past three. - **GET `/api/memory/admin/{id}`** — single-item fetch for admin. Powers the `#item-` deep link from `/memory/d/`'s Edit affordance: the page now fetches the row directly (no pagination racing) and injects it into `_itemsById` so the edit modal opens reliably even when the item is beyond page 1 of All Items. - **PATCH /api/memory/admin/{id}** accepts a new `domain_ids: list[str]` field that atomically replaces the item's full memory-domain membership via `knowledge_item_domains`. The admin item-edit modal now sends this on save so chip-input domain selections actually persist — previously the chip-input was decorative (legacy single-domain `` removed.** The chip-input is now the canonical domain control on `/admin/corporate-memory`; PATCH writes `domain_ids` (list) to the junction. The hidden `` to native `` swatch picker. Server now validates the hex format too (`^#[0-9a-fA-F]{6}$`) — admins can no longer save malformed values like `#ff5733#e0f2fe` that broke the card layout downstream. ### Fixed - **Memory admin modals were dead — duplicate `let _cmdNewDomainId`** in `admin_corporate_memory.html`. The deprecated step-2 RBAC modal left stub `let` declarations that collided with the live state vars declared earlier in the same `