Update stacklok/toolhive-studio to v0.36.5

[renovate]

This PR contains the following updates:

Package	Update	Change
stacklok/toolhive-studio	patch	v0.36.4 → v0.36.5

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-studio (stacklok/toolhive-studio)

v0.36.5

Compare Source

What's Changed

• fix(cli): parse commit-hash version strings from dev builds by @​reyortiz3 in #​2334

Full Changelog: stacklok/toolhive-studio@v0.36.4...v0.36.5

---

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-studio v0.36.5

Note

Skill reported no doc-relevant changes for this release.
This PR only bumps the version pin and any pin_files edits.

At a glance

Upstream	stacklok/toolhive-studio v0.36.4 → v0.36.5
Hand-written changes	0 commit(s)
Reference assets	unchanged
Gaps	0
Release contributors	1 auto-assigned (see sidebar)
Action required	—

Run cost

Session	Turns	Cost (USD)
Generation	20	$1.3867
Editorial review	5	$0.4627
Total	25	$1.8494

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:

• static/api-specs/
• docs/toolhive/reference/cli/ (toolhive only)

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 28, 2026 12:11am

[claude]

Claude finished @renovate[bot]'s task in 1m 23s —— View job

---

Upstream release docs sync: toolhive-studio v0.36.4 → v0.36.5

No hand-edited documentation changes required for this release.

• Phase 1: Discovery — single change: fix(cli): parse commit-hash version strings from dev builds toolhive-studio#2334 fix(cli): parse commit-hash version strings from dev builds
• Phase 2: Deep dive — verified against source at v0.36.5 (main/src/cli/cli-detection.ts:23): parseVersionOutput regex relaxed from \d+\.\d+\.\d+ to [\w.-]+ so the Settings page shows the actual version (instead of "Unknown") when the externally installed thv binary is a dev/CI build stamped with a commit hash. No new public surface — no new CLI flags, env vars, config keys, API routes, or struct fields
• Phase 3: Docs audit — grepped docs for parseVersionOutput, commit-hash, THV_VERSION, binary version, Settings page. Only related text is docs/toolhive/guides-ui/install.mdx:123 ("Displays the Desktop UI version and ToolHive binary version") — generic claim that the fix improves but does not falsify. Impact map empty
• Phase 4: Implementation — none needed
• Phase 5: Validation — n/a
• Phase 6: Handoff — wrote NO_CHANGES.md at repo root for the workflow to surface

Why no edits

stacklok/toolhive-studio#2334 is an internal display bug fix in the desktop app's CLI detection logic. It affects which version string the Settings page can parse from thv version output, not user-facing workflows, configuration, or APIs. The docs make no claim about how the version is parsed that this release could break.
· Branch

[claude]

Claude finished @renovate[bot]'s task in 24s —— View job

---

Editorial review: toolhive-studio v0.36.4 → v0.36.5

• Identify files changed in the previous commit
• Run editorial review on docs changes
• Apply fixes and format

Result

No documentation files were changed by the prior session — the only change in HEAD is the renovate version bump in .github/upstream-projects.yaml, and a NO_CHANGES.md signal file at the repo root (which I'm instructed not to touch). The prior session correctly determined this is an internal display bug fix in the desktop app's CLI version-parsing logic with no user-facing surface to document.

Nothing to review or format.
· Branch