Update stacklok/toolhive-registry-server to v1.4.10

[renovate]

This PR contains the following updates:

Package	Update	Change
stacklok/toolhive-registry-server	patch	v1.4.9 → v1.4.10

After this PR opens, .github/workflows/upstream-release-docs.yml adds source-verified content edits for the new release. For stacklok/toolhive, the same workflow also syncs reference assets (CLI help, Swagger) and regenerates the CRD MDX pages.

---

Release Notes

stacklok/toolhive-registry-server (stacklok/toolhive-registry-server)

v1.4.10

Compare Source

What's Changed

• Render audit log level as AUDIT not INFO+2 by @​rdimitrov in #​828
• Release v1.4.10 by @​toolhive-release-app[bot] in #​829

Full Changelog: stacklok/toolhive-registry-server@v1.4.9...v1.4.10

---

Configuration

📅 Schedule: (in timezone America/New_York)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Never, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

---

Docs update for toolhive-registry-server v1.4.10

At a glance

Upstream	stacklok/toolhive-registry-server v1.4.9 → v1.4.10
Hand-written changes	2 commit(s)
Reference assets	unchanged
Gaps	0
Release contributors	1 auto-assigned (see sidebar)
Action required	Spot-check skill-authored prose for accuracy

Summary of changes

• Updated audit log level note in docs/toolhive/guides-registry/audit-logging.mdx: removed the standalone INFO+2 known-issue admonition (fixed by stacklok/toolhive-registry-server#828) and folded a brief mention of the older v1.4.9-and-earlier behavior into the existing audit-level note for readers on older versions.

Run cost

Session	Turns	Cost (USD)
Generation	36	$1.6520
Editorial review	25	$1.5052
Total	61	$3.1572

How this PR was built

Two Claude Opus sessions run per release: a generation pass
(upstream-release-docs skill, 6 phases) followed by a fresh-
context editorial pass (docs-review). Prettier/ESLint
auto-fixes are applied after.

Auto-synced paths — do not hand-edit these in review:

• docs/toolhive/reference/cli/
• docs/toolhive/reference/crds/
• static/api-specs/

If a "Gaps needing human context" section is present above,
each entry includes a paste-ready Helper prompt for local
Claude a reviewer can use to resolve the gap.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
docs-website	Ready	Preview, Comment	Jun 24, 2026 5:59pm

[claude]

Claude finished @renovate[bot]'s task in 2m 47s —— View job

---

Upstream release docs: toolhive-registry-server v1.4.9 → v1.4.10

• Phase 1: Discovery
• Phase 2: Deep-dive (verified internal/audit/logger.go at v1.4.10)
• Phase 3: Audit (impact map below)
• Phase 4: Implement source-verified edit
• Phase 5: Format/lint clean
• Phase 6: Wrote SUMMARY.md, committed, and pushed

Release contents

The only user-facing change in v1.4.10 is stacklok/toolhive-registry-server#828 (closes #826): the audit log JSON level field now serializes as "AUDIT" instead of "INFO+2". The other listed PR is the release-bot commit, with no user-facing impact.

Impact map

File	Change
docs/toolhive/guides-registry/audit-logging.mdx	Removed the standalone INFO+2 known-issue admonition (the bug it tracked was fixed in #828). Folded a brief sentence about v1.4.9-and-earlier behavior into the existing audit-level note so readers running older versions still know what to filter on.

No new fields, flags, env vars, or API routes shipped in v1.4.10, so no other documentation needed updates. Auto-generated reference (CLI, swagger, CRDs) is unaffected.

Verification

• Confirmed the new ReplaceAttr hook at internal/audit/logger.go:47-54 in the local clone at v1.4.10 rewrites audit.LevelAudit → "AUDIT".
• Grepped for INFO+2 and #826 across the full docs tree — only audit-logging.mdx referenced them; both references are now inside the single consolidated note.
• npm run prettier:fix and npm run eslint:fix reported no changes after the edit.
  · Branch

[claude]

Claude finished @renovate[bot]'s task in 2m 54s —— View job

---

Editorial review: toolhive-registry-server v1.4.10 doc update

• Identify changed files and read them
• Run /docs-review skill on the edits
• Verify factual claim against upstream v1.4.10 clone (internal/audit/logger.go:47-54)
• Apply actionable fixes
• Run prettier:fix and eslint:fix (both clean — no changes)
• Commit and push (d5cab25)

Findings

Verified the new prose against the upstream source — the ReplaceAttr hook at internal/audit/logger.go:47-54 rewrites the level to "AUDIT" in v1.4.10, so the "v1.4.9 and earlier" framing is correct.

Two small editorial nits in the folded paragraph, both applied:

1. Ambiguous antecedent. "Registry Server v1.4.9 and earlier serialize this field as ..." — "this field" is the level field, but it's three sentences and a paragraph break away. Named it explicitly.
2. Non-parallel filter examples. The first paragraph tells readers to match on level = "AUDIT" or msg = "audit_event" (field-qualified). The new paragraph dropped the field names. Matched the structure so both halves of the note read as a single pattern, and removed the trailing "instead" (the contrast is already clear from "those versions").

-Registry Server v1.4.9 and earlier serialize this field as `"INFO+2"` instead of
-`"AUDIT"`. If you're filtering logs from older versions, match on `"INFO+2"` or
-`"audit_event"` instead.
+Registry Server v1.4.9 and earlier serialize the `level` field as `"INFO+2"`
+instead of `"AUDIT"`. When filtering logs from those versions, match on
+`level = "INFO+2"` or `msg = "audit_event"`.

Nothing else flagged — placement, scope, "Next steps", admonition structure, and front matter all check out. SUMMARY.md left untouched per workflow instructions.
· Branch