update docs for jriver and kick

[aw-was-here]

Summary by Sourcery

Update the project's documentation for Jriver and KickBot and adapt CI workflows to use the new documentation build script.

Enhancements:

• Use a dedicated CI documentation build script for GitHub Pages workflows

Build:

• Rename docs build command in ghpages-main and ghpages-test workflows to use build-ci-website.sh

CI:

• Update GitHub Actions workflows to call build-ci-website.sh instead of build-website.sh for docs deployment

Documentation:

• Refresh Jriver input documentation
• Refresh KickBot output documentation

[sourcery-ai]

Reviewer's Guide

Replaces the GitHub Actions website build script with the new build-ci-website.sh and refreshes documentation for the JRiver input and Kick output plugins, including an updated Kick UI resource file.

File-Level Changes

Change	Details	Files
Switch GitHub Actions site build to new CI script.	Replace build-website.sh with build-ci-website.sh in ghpages-main.yaml Replace build-website.sh with build-ci-website.sh in ghpages-test.yaml	.github/workflows/ghpages-main.yaml .github/workflows/ghpages-test.yaml
Refresh JRiver input plugin documentation.	Revise plugin overview and setup steps Update code examples and option descriptions	docs/input/jriver.rst
Refresh Kick output plugin documentation.	Revise integration guide Update configuration parameters	docs/output/kickbot.rst
Update Kick UI resource file.	Refresh UI layout definitions Adjust resource identifiers	nowplaying/resources/kick_ui.ui

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

Hey @aw-was-here - I've reviewed your changes and they look great!

Prompt for AI Agents

Please address the comments from this code review:
## Individual Comments

### Comment 1
<location> `docs/input/jriver.rst:45` </location>
<code_context>

-#. Note the **Port** number (default is 52199)
+.. image:: images/jriver-advanced-port.png
+   :target: images/jjriver-advanced-port.png
+   :alt: JRiver Advanced drop down showing the port
+
</code_context>

<issue_to_address>
Typo in image path: 'jjriver' should be 'jriver'.

Please update the target path to 'jriver-advanced-port.png' to match the correct image name.
</issue_to_address>

<suggested_fix>
<<<<<<< SEARCH
.. image:: images/jriver-advanced-port.png
   :target: images/jjriver-advanced-port.png
   :alt: JRiver Advanced drop down showing the port
=======
.. image:: images/jriver-advanced-port.png
   :target: images/jriver-advanced-port.png
   :alt: JRiver Advanced drop down showing the port
>>>>>>> REPLACE

</suggested_fix>

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[sourcery-ai]

issue (typo): Typo in image path: 'jjriver' should be 'jriver'.

Please update the target path to 'jriver-advanced-port.png' to match the correct image name.

Suggested change

	.. image:: images/jriver-advanced-port.png
	:target: images/jjriver-advanced-port.png
	:alt: JRiver Advanced drop down showing the port
	.. image:: images/jriver-advanced-port.png
	:target: images/jriver-advanced-port.png
	:alt: JRiver Advanced drop down showing the port

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 66.38%. Comparing base (92aee8b) to head (e1d4f62).

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #1206      +/-   ##
==========================================
+ Coverage   66.35%   66.38%   +0.02%     
==========================================
  Files          63       63              
  Lines       10741    10741              
==========================================
+ Hits         7127     7130       +3     
+ Misses       3614     3611       -3     

Flag	Coverage Δ
unittests	66.38% <ø> (+0.02%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

see 2 files with indirect coverage changes

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.