Release/1.5.0

CHANGELOG.md

@@ -4,6 +4,40 @@ All notable changes to this project are documented in this file. Format follows
 
 For narrative release notes written for operators and product owners, see [RELEASE_NOTES.md](RELEASE_NOTES.md).
 
+## [1.5.0] - 2026-07-13
+
+Model-catalog and MCP-admin expansion, plus UI polish. Admins can now discover the tools behind OAuth-gated MCP servers (e.g. the GitHub remote MCP server) using their own vaulted 3LO token, two new curated model cards land (Claude Sonnet 5, GPT-5.4), and the max-output-tokens field goes optional so reasoning/Responses-API models without a fixed cap can be added. Alongside: sticky admin/settings sidebars, a redesigned 404 page, chat-scroll and sticky-nav fixes, a vitest flake fix, and a Docker curl security patch. No CDK deploy, no data migration, no breaking changes — ships via the backend and frontend pipelines.
+
+### 🚀 Added
+
+- Admin tool "Discover" now works against OAuth-gated MCP servers: pass the OAuth provider id and discovery connects with the admin's own vaulted 3LO token (fetched via AgentCore Identity `get_token_for_user`, injected as a bearer), validating the admin's connection and listing the tools their token can see. Previously OAuth-gated servers were refused outright (400) or connected unauthenticated and 401'd. `requires_consent` → 409; unknown provider / forward-auth conflict / oauth2-without-provider → 400 (#639)
+- Two curated model catalog cards: **Claude Sonnet 5** (Bedrock, `global.anthropic.claude-sonnet-5`, 1M context, effort-based reasoning, caching on) and **GPT-5.4** (Mantle, `openai.gpt-5.4`, Responses API). Bedrock Claude cards now order most-capable-first and the "Bedrock Mantle" tab sits next to "Bedrock" (#641)
+
+### ✨ Improved
+
+- Max output tokens is now optional on the admin model form — reasoning / Responses-API models (GPT-5.x, adaptive-thinking Claude) that share output with reasoning budget have no fixed cap to enter. `max_output_tokens` is `Optional[int]` end to end; it was only ever a ceiling for the admin-configured `max_tokens` param and is never sent to the provider, so leaving it unset is safe (#643, #644)
+- Admin and user-settings sidebar navs are now sticky on desktop, staying in view as the content column scrolls (#632, #638)
+- The 404 page was redesigned to match the auth/first-boot screens (frosted glass, animated blobs, graph-paper grid) (#633)
+- Chat scroll space is now sized to the pending response and adapts to the shell scroll container, so the last turn spaces correctly (#637)
+
+### 🐛 Fixed
+
+- Mantle `google.gemma-4-*` models 401'd with `access_denied` because Gemma 4 is served only on Mantle's `/openai/v1` path but the Strands SDK routed it to `/v1`. The SDK's OpenAI-path prefix table is now extended with `google.gemma-4-` at build time (lazy, idempotent, guarded); Gemma 3 stays on `/v1` (#641)
+- The admin/settings sticky sidebars needed a real shell scroll container to anchor against — the app shell now scrolls on the correct element so `position: sticky` engages (#634)
+- Vitest runs now guarantee the Angular JIT compiler is present, stopping the intermittent `PlatformLocation` provider flake in the SPA unit suite (#636)
+
+### 🔒 Security
+
+- Dockerfiles pin curl to `+deb13u*` instead of an exact point release, so the security patch floats with Debian's mirror (which purges superseded point versions on each CVE update) and builds don't break; the digest-pinned base image still provides reproducibility (#645)
+
+### 🔧 CI/CD
+
+- `scripts/common/sync-version.sh` is now portable across GNU and BSD userlands (macOS `sed`/`grep`), so the version bump runs outside the dev container (#631)
+
+### 📚 Docs
+
+- Added the quota cooldown-windows + platform-ceiling spec and committee one-pager (`docs/specs/`) (#635); added a design note proposing `mantleEndpointPath` as a live admin setting (#641)
+
 ## [1.4.0] - 2026-07-10
 
 Opt-in MCP user-identity forwarding, plus an admin OAuth-provider repair. A new Cognito Pre-Token-Generation Lambda can copy configured user-pool attributes into namespaced claims on the access token — the only token forwarded end-to-end to MCP servers — so personalized MCP tools can identify the caller. It ships disabled by default (a fork that configures nothing gets zero resources). Also fixes a 502 when adding the first admin OAuth provider. A platform (CDK) deploy is required for the OAuth-provider IAM fix.

README.md

@@ -8,7 +8,7 @@
 **An open-source, production-ready Generative AI platform for institutions**
 *Built by Boise State University, designed for everyone.*
 
-[![Release](https://img.shields.io/badge/Release-v1.4.0-6366f1?style=flat&logo=github&logoColor=white)](RELEASE_NOTES.md)
+[![Release](https://img.shields.io/badge/Release-v1.5.0-6366f1?style=flat&logo=github&logoColor=white)](RELEASE_NOTES.md)
 [![Nightly](https://github.com/Boise-State-Development/agentcore-public-stack/actions/workflows/nightly.yml/badge.svg)](https://github.com/Boise-State-Development/agentcore-public-stack/actions/workflows/nightly.yml)
 
 ![Python](https://img.shields.io/badge/Python-3.13+-3776AB?style=flat&logo=python&logoColor=white)
@@ -296,7 +296,7 @@ agentcore-public-stack/
 
 See [RELEASE_NOTES.md](RELEASE_NOTES.md) for the full changelog, including new features, bug fixes, platform upgrades, and deployment notes for each release.
 
-**Current release:** v1.4.0
+**Current release:** v1.5.0
 
 ---
 

RELEASE_NOTES.md

@@ -1,3 +1,72 @@
+# Release Notes — v1.5.0
+
+**Release Date:** July 13, 2026
+**Previous Release:** v1.4.0 (July 10, 2026)
+
+---
+
+> ✅ **No platform (CDK) deploy required.** This release is application code and frontend only — it ships through the `backend.yml` (app-api / inference-api image rebuild) and `frontend-deploy.yml` pipelines. No new AWS resources, no IAM changes, no data migration, no breaking changes.
+
+---
+
+## Highlights
+
+v1.5.0 expands the **model catalog** and the **MCP admin** surface, then rounds out the UI. Admins can now run tool **Discovery against OAuth-gated MCP servers** — such as the GitHub remote MCP server — using their own vaulted 3LO token, rather than being refused outright. Two curated model cards land — **Claude Sonnet 5** and **GPT-5.4** — and the **max-output-tokens** field becomes optional so reasoning / Responses-API models that have no fixed output cap can be added at all. The remainder is polish and hardening: sticky admin/settings sidebars, a redesigned 404 page, chat-scroll and sticky-nav fixes, a vitest flake fix, a Mantle Gemma-4 routing fix, and a Docker curl security patch.
+
+## Discover OAuth-gated MCP servers with the admin's token
+
+Admins configuring a tool couldn't see what an OAuth-gated MCP server actually offered: the "Discover" flow refused `auth_type=oauth2` outright (400) or connected unauthenticated and got a 401 (wrapped to a 400), so servers like the GitHub remote MCP server (`api.githubcopilot.com/mcp/`) were undiscoverable. Discovery now connects with the admin's *own* vaulted token for the provider and lists the tools that token can see.
+
+### Backend
+
+- **Provider-aware discovery (#639)** — `MCPDiscoverRequest` gains `requires_oauth_provider` (alias `requiresOauthProvider`). The handler loads the provider, fetches the admin's vaulted 3LO token via AgentCore Identity (`get_token_for_user`) and injects it as `oauth_token` into `create_external_mcp_client` — mirroring how the agent loop attaches the end-user's provider token at runtime, and reusing the exact path `connector_status` already uses. It fetches the **admin's own** token only; it cannot mint an arbitrary end-user's token. Providers such as GitHub scope-filter the tool list to the token's grants, so the result reflects what the admin's connection can actually reach. `requires_consent` → 409; unknown provider / conflict with `forward_auth` / oauth2-without-provider → 400.
+
+### Frontend
+
+- The discover payload now sends `requiresOauthProvider` (the form control already existed) and the `OAuth2CallbackUrl` header (bare `/oauth-complete`, no query string) so the backend can resolve the admin's token.
+
+### Test Coverage
+
+5 backend tests for the OAuth-provider discovery path; 2 SPA specs for the discover payload.
+
+## Model catalog — Sonnet 5, GPT-5.4, and optional output caps
+
+Two new curated cards and one form change together let admins add the current generation of frontier models with a single click.
+
+### Frontend
+
+- **New curated cards (#641)** — **Claude Sonnet 5** (`global.anthropic.claude-sonnet-5`, 1M context, effort-based reasoning, caching on) and **GPT-5.4** (Mantle, `openai.gpt-5.4`, Responses API surface — its `openai.gpt-5.*` id matches the SDK's `/openai/v1` routing prefixes so one-click create routes correctly). The Bedrock Claude list now orders most-capable-first (Opus 4.7, Sonnet 5, Sonnet 4.6, Haiku 4.5), GPT-5.4 sits ahead of Qwen in the Mantle list, and the "Bedrock Mantle" tab moves next to "Bedrock" in the catalog selector.
+- **Optional max output tokens (#643, #644)** — newer reasoning / Responses-API models don't publish a discrete max-output-tokens value (output shares the context budget with reasoning tokens), so the admin form field is now optional. `max_output_tokens` becomes `Optional[int]` across `ManagedModelCreate` / `ManagedModel` and the SPA interfaces (`number | null`); the DynamoDB write omits it when absent, the form drops `Validators.required`, and the catalog card null-guards to show "— out". It was only ever a ceiling for the admin-configured `max_tokens` param and is never sent to the provider, so an unset value is safe at inference time.
+
+## 🐛 Bug fixes
+
+- **Mantle Gemma 4 models returned `access_denied` (#641).** Gemma 4 is served only on Mantle's `/openai/v1` path (per its AWS model card), but the Strands SDK's `_OPENAI_PATH_MODEL_PREFIXES` shipped only `openai.gpt-5.`, so `google.gemma-4-*` fell through to `/v1` and inference 401'd. The SDK's prefix table is now extended with `google.gemma-4-` at build time (`_ensure_gemma4_openai_v1_routing`: lazy, idempotent, guarded) until it lands upstream — scoped to the 4.x family so Gemma 3 stays on `/v1`. Covered by guard tests.
+- **Sticky sidebars didn't engage (#634).** The redesigned admin/settings sticky sidebars need a real scroll container to anchor against; the app shell now scrolls on the correct element so `position: sticky` takes effect and the chat scroll space sizes to the pending response (#637).
+- **Intermittent SPA unit-test flake (#636).** Vitest runs now guarantee the Angular JIT compiler is present, eliminating the sporadic `PlatformLocation` provider error in the unit suite.
+
+## 🔒 Security
+
+- **Docker curl patch floats with the mirror (#645).** Debian removes the superseded point version of curl from the trixie mirror on each security update, so an exact `+deb13uN` pin broke every build once the next CVE landed. Both Dockerfiles now pin `+deb13u*` — tracking the live security patch while keeping the minor version fixed. The digest-pinned base image is what actually provides reproducibility.
+
+## ✨ UI polish
+
+- **Sticky navigation (#632, #638)** — the admin and user-settings sidebar navs stay in view on desktop as the content column scrolls.
+- **Redesigned 404 page (#633)** — the not-found page now matches the auth / first-boot screens (frosted glass, animated blobs, graph-paper grid in Boise blue).
+
+## 🔧 CI/CD
+
+- **Portable version sync (#631)** — `scripts/common/sync-version.sh` now runs across GNU and BSD userlands (macOS `sed`/`grep`), so the release bump works outside the dev container.
+
+## 📚 Docs
+
+- Added the quota cooldown-windows + platform-ceiling spec and committee one-pager under `docs/specs/` (#635), and a design note proposing `mantleEndpointPath` as a live admin setting as the durable alternative to patching the SDK's hardcoded routing table (#641).
+
+## 🚀 Deployment notes
+
+- **No special steps.** No CDK deploy, no IAM changes, no data migration, no breaking changes. The backend changes (Mantle Gemma-4 routing, optional `max_output_tokens`, Docker curl pin) ship on the next `backend.yml` image rebuild; the SPA changes ship via `frontend-deploy.yml`.
+
+---
+
 # Release Notes — v1.4.0
 
 **Release Date:** July 10, 2026

VERSION

@@ -1 +1 @@
-1.4.0
+1.5.0

backend/Dockerfile.app-api

@@ -39,7 +39,7 @@ WORKDIR /app
 
 # Install runtime dependencies (curl required for HEALTHCHECK)
 RUN apt-get update && apt-get install -y \
-    curl=8.14.1-2+deb13u3 \
+    curl=8.14.1-2+deb13u* \
     && rm -rf /var/lib/apt/lists/*
 
 # Copy the virtual environment from builder

backend/Dockerfile.inference-api

@@ -39,7 +39,7 @@ WORKDIR /app
 
 # Install runtime dependencies (curl required for HEALTHCHECK)
 RUN apt-get update && apt-get install -y \
-    curl=8.14.1-2+deb13u3 \
+    curl=8.14.1-2+deb13u* \
     && rm -rf /var/lib/apt/lists/*
 
 # Copy the virtual environment from builder

backend/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "agentcore-stack"
-version = "1.4.0"
+version = "1.5.0"
 requires-python = ">=3.10"
 description = "Multi-agent conversational AI system with AWS Bedrock AgentCore"
 readme = "README.md"

backend/src/apis/app_api/admin/tools/routes.py

@@ -9,6 +9,16 @@
 from fastapi import APIRouter, Depends, HTTPException, Query
 
 from apis.shared.auth import User, require_admin
+from apis.shared.oauth.agentcore_identity import (
+    CallbackUrlUnavailableError,
+    WorkloadTokenUnavailableError,
+    custom_parameters_for,
+    get_agentcore_identity_client,
+)
+from apis.shared.oauth.provider_repository import (
+    OAuthProviderRepository,
+    get_provider_repository,
+)
 from apis.app_api.tools.service import get_tool_catalog_service
 from apis.app_api.tools.discovery import discover_tools_for_saved_tool
 from apis.shared.tools.gateway_target_service import (
@@ -358,6 +368,7 @@ def _discovery_failure_detail(status: int) -> str:
 async def admin_discover_mcp_tools(
     request: MCPDiscoverRequest,
     admin: User = Depends(require_admin),
+    provider_repo: OAuthProviderRepository = Depends(get_provider_repository),
 ):
     """Connect to an MCP server with the given config and return its tool list.
 
@@ -385,11 +396,55 @@ async def admin_discover_mcp_tools(
         create_external_mcp_client,
     )
 
-    if request.auth_type in (MCPAuthType.OAUTH2.value, MCPAuthType.OAUTH2):
+    # An OAuth (3LO) gated server is discovered using the admin's *own* vaulted
+    # token for the named provider — mirroring how the agent loop attaches the
+    # end-user's provider token at runtime. This validates the admin's own
+    # connection and returns the tools their token can see (providers such as
+    # GitHub scope-filter the tool list to the token's grants). It fetches the
+    # admin's token only; it can't mint an arbitrary end-user's token, so the
+    # discovered list reflects the admin's connection, not every user's.
+    oauth_token: Optional[str] = None
+    if request.requires_oauth_provider:
+        if request.forward_auth_token:
+            raise HTTPException(
+                status_code=400,
+                detail="Choose either an OAuth provider or forwarded-auth "
+                "discovery, not both.",
+            )
+        provider = await provider_repo.get_provider(request.requires_oauth_provider)
+        if provider is None:
+            raise HTTPException(
+                status_code=400,
+                detail=f"Unknown OAuth provider "
+                f"'{request.requires_oauth_provider}'.",
+            )
+        identity = get_agentcore_identity_client()
+        try:
+            result = await identity.get_token_for_user(
+                provider_name=provider.provider_id,
+                scopes=provider.scopes,
+                user_id=admin.user_id,
+                # Match the customParameters used at consent time — AgentCore
+                # factors them into the vault key, so omitting them would
+                # falsely report consent-required for a vaulted token.
+                custom_parameters=custom_parameters_for(provider.custom_parameters),
+            )
+        except (WorkloadTokenUnavailableError, CallbackUrlUnavailableError) as err:
+            logger.warning("OAuth discovery token unavailable: %s", err)
+            raise HTTPException(status_code=503, detail=str(err))
+        if result.requires_consent or not result.access_token:
+            raise HTTPException(
+                status_code=409,
+                detail=f"You haven't connected '{provider.display_name}' yet. "
+                "Connect it in your connector settings, then retry discovery.",
+            )
+        oauth_token = result.access_token
+
+    elif request.auth_type in (MCPAuthType.OAUTH2.value, MCPAuthType.OAUTH2):
         raise HTTPException(
             status_code=400,
-            detail="OAuth-gated MCP servers can't be discovered server-side; "
-            "list the tool names manually.",
+            detail="Select the OAuth provider for this server to discover its "
+            "tools, or list the tool names manually.",
         )
 
     # Forward-auth servers (same-team MCP that validates a forwarded JWT, behind
@@ -400,8 +455,7 @@ async def admin_discover_mcp_tools(
     # trust-boundary note above); forwarding their own session token to that URL
     # is a strictly lower bar than the end-user token forwarding they're
     # configuring for the tool.
-    oauth_token: Optional[str] = None
-    if request.forward_auth_token:
+    elif request.forward_auth_token:
         if not admin.raw_token:
             raise HTTPException(
                 status_code=400,

backend/src/apis/shared/models/managed_models.py

@@ -265,7 +265,6 @@ async def _create_managed_model_cloud(model_data: ManagedModelCreate, table_name
         'inputModalities': model_data.input_modalities,
         'outputModalities': model_data.output_modalities,
         'maxInputTokens': model_data.max_input_tokens,
-        'maxOutputTokens': model_data.max_output_tokens,
         'allowedAppRoles': model_data.allowed_app_roles,
         'availableToRoles': model_data.available_to_roles,
         'enabled': model_data.enabled,
@@ -278,6 +277,8 @@ async def _create_managed_model_cloud(model_data: ManagedModelCreate, table_name
     }
 
     # Add optional fields
+    if model_data.max_output_tokens is not None:
+        item['maxOutputTokens'] = model_data.max_output_tokens
     if model_data.cache_write_price_per_million_tokens is not None:
         item['cacheWritePricePerMillionTokens'] = model_data.cache_write_price_per_million_tokens
     if model_data.cache_read_price_per_million_tokens is not None:

backend/src/apis/shared/models/mantle.py

@@ -64,6 +64,29 @@ def param_map_for(api_mode: MantleApiMode) -> Dict[str, str]:
     )
 
 
+def _ensure_gemma4_openai_v1_routing() -> None:
+    """Teach the Strands SDK to route ``google.gemma-4-*`` to ``/openai/v1``.
+
+    Per its AWS model card, Gemma 4 is served *only* on the Mantle
+    ``/openai/v1`` base path — "different from the ``v1`` path used by other
+    models." But the SDK's ``_OPENAI_PATH_MODEL_PREFIXES`` only lists
+    ``openai.gpt-5.``, so ``google.gemma-4-*`` falls through to ``/v1`` and the
+    endpoint 401s ("... is not enabled for this account"). Append the family
+    prefix at build time until it lands upstream (strands-agents/sdk-python).
+
+    ``google.gemma-4-`` specifically — NOT ``google.gemma-``: Gemma 3 is served
+    on ``/v1`` and must not be rerouted. Idempotent; safe to call on every build.
+    """
+    from strands.models import _openai_bedrock as _sdk
+
+    prefix = "google.gemma-4-"
+    if prefix not in _sdk._OPENAI_PATH_MODEL_PREFIXES:
+        _sdk._OPENAI_PATH_MODEL_PREFIXES = (
+            *_sdk._OPENAI_PATH_MODEL_PREFIXES,
+            prefix,
+        )
+
+
 def build_mantle_model(
     model_id: str,
     api_mode: MantleApiMode,
@@ -88,6 +111,9 @@ def build_mantle_model(
     from strands.models import OpenAIResponsesModel
     from strands.models.openai import OpenAIModel
 
+    # Bridge until google.gemma-4- lands in the SDK's base-path prefix table.
+    _ensure_gemma4_openai_v1_routing()
+
     bedrock_mantle_config: Dict[str, Any] = {}
     if region:
         bedrock_mantle_config["region"] = region