feat(litellm): 1.99.1 update coverage, trove agent, nginx /ui /docs fixes #75

2026-09-11T19:33:27Z

kagentz-bot commented

2026-09-11 19:33:27 +00:00

What changed

Makes the fleet update contracts genuinely cover the CT 116 inference stack after the 1.99.1 upgrade, and removes assertions that no longer match live state.

litellm-self-heal \u2014 container count 11 -> 12; add trove-agent-docker to the container inventory; correct the /ui/ /docs checks (now 301 -> /litellm/... -> 200, added 2026-09-11).
litellm-health \u2014 same container-count and /ui/ /docs corrections.
infrastructure-control \u2014 12 containers on CT 116; add trove-agent-docker row; remove the dead 192.168.68.24:9401 router scrape target (probed unreachable, code=000).
infrastructure-update \u2014 add CT 116 trove agent to the Wave 3 table; add version-pin awareness so a pinned tag is not a silent compose pull no-op; version 1.3.0 -> 1.4.0.
contract-registry.yaml \u2014 bump infrastructure-update and litellm-self-heal to 1.1.0; refresh last_updated.

Why the pin stays

Registry digests: main-stable == latest == 1.100.1 (sha256:a3715fa7...), while CT 116 runs the pinned 1.99.1 (sha256:a53a7d3f...). Reverting to a floating tag would silently jump to the bleeding-edge release that was explicitly declined on 2026-09-11.

Verification

scripts/prose-lint.sh -> LINT PASSED (12 pre-existing warnings).
No Grafana nginx route regression; no stale CT IDs.
0 secret-shaped lines introduced by this commit.

## What changed Makes the fleet update contracts genuinely cover the CT 116 inference stack after the 1.99.1 upgrade, and removes assertions that no longer match live state. - **litellm-self-heal** \u2014 container count 11 -> 12; add `trove-agent-docker` to the container inventory; correct the `/ui/` `/docs` checks (now `301 -> /litellm/... -> 200`, added 2026-09-11). - **litellm-health** \u2014 same container-count and `/ui/` `/docs` corrections. - **infrastructure-control** \u2014 12 containers on CT 116; add `trove-agent-docker` row; remove the dead `192.168.68.24:9401` router scrape target (probed unreachable, code=000). - **infrastructure-update** \u2014 add CT 116 trove agent to the Wave 3 table; add version-pin awareness so a pinned tag is not a silent `compose pull` no-op; version 1.3.0 -> 1.4.0. - **contract-registry.yaml** \u2014 bump `infrastructure-update` and `litellm-self-heal` to 1.1.0; refresh `last_updated`. ## Why the pin stays Registry digests: `main-stable` == `latest` == **1.100.1** (`sha256:a3715fa7...`), while CT 116 runs the pinned **1.99.1** (`sha256:a53a7d3f...`). Reverting to a floating tag would silently jump to the bleeding-edge release that was explicitly declined on 2026-09-11. ## Verification - `scripts/prose-lint.sh` -> **LINT PASSED** (12 pre-existing warnings). - No Grafana nginx route regression; no stale CT IDs. - 0 secret-shaped lines introduced by this commit.

kagentz-bot added 1 commit 2026-09-11 19:33:27 +00:00

feat(litellm): 1.99.1 update coverage, trove agent, nginx /ui /docs path fixes

PR Pipeline — Authorize → Validate → Review → Merge / auth (pull_request) Successful in 2s

Details

PR Pipeline — Authorize → Validate → Review → Merge / validate (pull_request) Successful in 3s

Details

PR Pipeline — Authorize → Validate → Review → Merge / lint (pull_request) Successful in 1s

Details

PR Pipeline — Authorize → Validate → Review → Merge / ai-review (pull_request) Successful in 3s

Details

PR Pipeline — Authorize → Validate → Review → Merge / gate (pull_request) Successful in 2s

Details

7730cc7c03

kagentz-bot merged commit b326a8944a into master

2026-09-11 19:34:23 +00:00

kagentz-bot deleted branch update/litellm-1991-trove-20260911

2026-09-11 19:34:26 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: SyslogSolution/prose-contracts#75