chore(release): 0.92.0

[padak]

Release PR for v0.92.0. Batches every PR merged since v0.91.0; no behavior of its own beyond the version bump, the changelog entry and the resolved version gates.

Scope — 7 PRs since v0.91.0

PR	Issue	What shipped
#719	#714	kbagent flow triggers — cron schedules and table triggers in one call, with an honest negative for what it cannot see
#717	#711	A 401 is no longer automatically blamed on the token; the metastore's master-token gate is diagnosed; exceptionId surfaced on 401/403/404
#722	#704	/kbagent:setup can finish in chat — an attended agent drives device-code login; the skill covers setup/logout for clients without slash commands
#718	#716	kbagent --conversation-id ID global flag
#706	—	223 stale version gates retired at a 0.80.0 floor, no content removed
#702	—	Release process enforced rather than remembered (vnext-resolve, heading rule, release-scope-check)
#721	—	Docstring fix: get_flow_detail never returned schedule info

make release-scope-check confirms all 7 are referenced by the changelog entry.

Checklist

• 2. pyproject.toml → 0.92.0
• 3. Changelog entry — 8 bullets, one logical change each, every headline under the 160-char cap
• 4. make vnext-resolve VERSION=0.92.0 → 11 placeholders resolved; make vnext-check clean (338 gates / 65 versions)
• 5. make version-sync → plugin.json, marketplace.json, uv.lock
• 6. make skill-gen → no diff (no command-tree change since feat(flow): add flow triggers -- table triggers, not just cron (#714) #719's own run)
• 7. whatsnew.ts → one curated item (see below)
• 8-11. Manual review of the silent-drift surfaces (see below)
• 12. make check
• 15. make release-scope-check

What's-new entry

No web/frontend code changed this release, but #717's error rework is UI-visible: the Semantic Layer page renders API error messages verbatim, so a user with a valid non-master token was being told their token had expired. One curated item covers exactly that.

Plugin files touched (reviewers: this is where CI cannot help)

Listed so the second line of defence knows where to look:

• plugins/kbagent/agents/keboola-expert.md
• plugins/kbagent/skills/kbagent/references/gotchas.md
• plugins/kbagent/skills/kbagent/references/commands-reference.md
• plugins/kbagent/skills/kbagent/references/semantic-layer-workflow.md
• plugins/kbagent/.claude-plugin/plugin.json (auto-synced)
• .claude-plugin/marketplace.json (auto-synced shim)

Most of these changes are the mechanical vNEXT → v0.92.0 resolution; anything beyond that is called out in the commits.

After merge

Tag the merge commit — the tag push is the release. Then merge the chore(kbagent): publish v0.92.0 PR the pipeline opens against keboola/ai-kit, or plugin users keep getting 0.91.0.