Update stacklok/toolhive to v0.47.1

[renovate]

This PR contains the following updates:

Package	Update	Change
stacklok/toolhive	patch	v0.47.0 → v0.47.1

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

v0.47.1

Compare Source

What's Changed

• Run short CI jobs on the standard runner by @​rdimitrov in #​6541
• Run operator E2E on one Kubernetes version per PR by @​rdimitrov in #​6540
• Release v0.47.1 by @​toolhive-release-app[bot] in #​6554

Full Changelog: stacklok/toolhive@v0.47.0...v0.47.1

---

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 v0.47.1

At a glance

Upstream	stacklok/toolhive v0.47.0 → v0.47.1
Hand-written changes	1 commit(s)
Reference assets	refreshed (separate commit)
Gaps	0
Owner	@rdimitrov - identified from merged release PR stacklok/toolhive#6554
Release contributors	2 review requested (see sidebar)
Action required	Spot-check skill-authored prose for accuracy

Who does what

@rdimitrov cut this release and owns this PR: review your own changes, chase the remaining approvals, and merge once they're in. You don't need to wait on a review from anyone listed as having no docs impact below.

Everyone with a review request: the target is a review and approval within 2 business days.

Summary of changes

• Updated the list-operation filtering section in docs/toolhive/reference/authz-policy-reference.mdx to add resources/templates/list alongside the other filtered list methods, including a new per-item check row, and to note that filtered resource template responses are served with Cache-Control: private, no-store.
• Updated the parallel list-operations section in docs/toolhive/concepts/cedar-policies.mdx to include resources/templates/list in the automatically filtered methods.

Notes for the reviewer

• The release ships two CI-only PRs (stacklok/toolhive#6540, stacklok/toolhive#6541) and a permission-profile deep-clone hardening fix (pkg/runner/config_builder.go); none of these change user-visible behavior, so no docs edits were needed for them.
• The user-visible change is a security fix delivered as a "Merge commit from fork" (embargoed): resources/templates/list responses were previously authorized as a list operation but passed through unfiltered. As of v0.47.1 they are filtered with the same read_resource per-item check used for resources/list. The middleware also fails closed for any protected list method with no registered response filter, and JSON parsing now rejects duplicate or case-aliased fields in the template list result. These last two are internal hardening and not surfaced to policy authors, so they are intentionally not documented.
• Pre-existing accuracy point (not introduced by this release, no edit made): the Cedar authorizer's authorizeResourceRead uses the raw resource URI as the entity ID (see pkg/authz/authorizers/cedar/core.go), while the "Resource URI sanitization" section still describes character-replacement sanitization. That reads stale but is unchanged in v0.47.1 and is out of scope for this PR.

Run cost

Session	Turns	Cost (USD)
Generation	86	$6.9629
Editorial review	21	$1.4014
Total	107	$8.3643

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)
• docs/toolhive/reference/crds/

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
docs-website	Ready	Preview	Sep 9, 2026 10:50am UTC

[claude]

Claude finished @renovate[bot]'s task in 8m 53s —— View job

---

ToolHive v0.47.1 documentation sync

• Phase 1: Gather release context
• Phase 2: Classify contributors and read source
• Phase 3: Identify doc-worthy changes
• Phase 4: Apply doc edits
• Phase 5: Format and lint
• Phase 6: Write artifacts and commit

Summary of changes

Docs updated (committed as 7dd8b60):

• docs/toolhive/reference/authz-policy-reference.mdx — Added resources/templates/list to the filtered list-operations paragraph and to the per-item check table, and noted that filtered resource template responses are served with Cache-Control: private, no-store.
• docs/toolhive/concepts/cedar-policies.mdx — Added a resources/templates/list bullet to the parallel list-operations section.

Why: the release ships two CI-only PRs (stacklok/toolhive#6540, stacklok/toolhive#6541) and an internal permission-profile deep-clone fix, none of which are user-visible. The user-visible change is an embargoed security fix delivered as merge-from-fork commits: resources/templates/list responses were previously authorized as a list operation but passed through the response filter unfiltered. As of v0.47.1 they are filtered with the same read_resource per-item check used for resources/list. The middleware also fails closed for protected list methods with no registered filter, and template-list JSON parsing now rejects duplicate or case-aliased fields — internal hardening not surfaced to policy authors, so it is intentionally not documented.

Artifacts: REVIEWERS.json (Chris Burns docs-facing, Radoslav Dimitrov non-docs-facing) and SUMMARY.md written for the workflow to splice into the PR body.

Note for reviewer: the pre-existing "Resource URI sanitization" section in the policy reference describes character-replacement sanitization, but the current Cedar authorizer's authorizeResourceRead uses the raw URI as the entity ID. This is unchanged in v0.47.1 and out of scope for this PR, but worth an issue for a future release.
· Branch

[claude]

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

---

Docs review for toolhive v0.47.1

• Identify files changed in the release commit
• Review docs/toolhive/concepts/cedar-policies.mdx
• Review docs/toolhive/reference/authz-policy-reference.mdx
• Verify claims against upstream source
• No actionable fixes needed
• Run prettier/eslint (both clean)

Summary

Editorial pass on the two docs modified by the release commit (concepts/cedar-policies.mdx and reference/authz-policy-reference.mdx). Both additions describe the new resources/templates/list response filtering.

Verified against upstream at pkg/authz/response_filter.go and pkg/authz/middleware.go:

• resources/templates/list is registered as a list-filtered method (middleware.go:49).
• Per-item check uses read_resource with the RFC 6570 URI template treated as the resource identifier (response_filter.go:880-899).
• The Cache-Control: private, no-store header is applied specifically when the filter is responseFilterResourceTemplates (response_filter.go:181-185), matching the doc's scoping to "filtered resource template responses."
• The bullet-list phrasing in the concepts page ("whose URI template the user can read") accurately captures the URI-template-as-identifier nuance the reference table spells out.

Both npm run prettier:fix and npm run eslint:fix reported no changes. No edits made.
• Branch: renovate/stacklok-toolhive-0.x