[ReenigneArcher]

Description

Announce the planned migration of seven repositories into SunshineStream, Themerr, and KokoStreamTV, explaining the project identities under the LizardByte umbrella.

• List the destination organizations, repositories, and planned *.lizardbyte.dev project websites.
• Keep current repository links usable while the moves are prepared; explain the planned landing-page forwards and the updated Themerr release needed for the new ThemerrDB address.
• Include awesome-sunshine with Sunshine in the SunshineStream organization.
• State that Koko remains under development and the two archived Themerr integrations remain archived.
• Use the existing blog layout, author metadata, announcement tags, and an aligned Markdown table.

Screenshot

Issues Fixed or Closed

Roadmap Issues

Testing

• Parsed the YAML front matter and checked required blog fields, all seven moving repository names, the three destination organizations, and aligned table pipes.
• Verified current repository ownership, archived status, and project descriptions against live GitHub sources.
• No application code changes or new regression tests: this PR adds one Markdown announcement.
• Hosted Jekyll CI passed. Inspected the built HTML artifact: the migration table renders with all three organizations, all seven repositories, the planned hostnames, and the archive/upgrade guidance.
• All non-skipped PR checks passed, including common lint, Node CI, CodeQL, SonarCloud, and Codecov.

Type of Change

• feat: New feature (non-breaking change which adds functionality)
• fix: Bug fix (non-breaking change which fixes an issue)
• docs: Documentation only changes
• style: Changes that do not affect the meaning of the code (white-space, formatting, missing semicolons, etc.)
• refactor: Code change that neither fixes a bug nor adds a feature
• perf: Code change that improves performance
• test: Adding missing tests or correcting existing tests
• build: Changes that affect the build system or external dependencies
• ci: Changes to CI configuration files and scripts
• chore: Other changes that don't modify src or test files
• revert: Reverts a previous commit
• BREAKING CHANGE: Introduces a breaking change (can be combined with any type above)

Checklist

• Code follows the style guidelines of this project
• Code has been self-reviewed
• Code has been commented, particularly in hard-to-understand areas
• Code docstring/documentation-blocks for new or existing methods/components have been added or updated
• Tests have been added or updated for new or modified functionality, including regression tests for bug fixes

AI Usage

See our AI usage policy.

• AI tools were used while preparing this PR

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 100.00%. Comparing base (f0a26ca) to head (aa20837).
✅ All tests successful. No failed tests found.

Additional details and impacted files

@@            Coverage Diff            @@
##            master      #517   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           10        10           
  Lines          999       999           
  Branches       131       131           
=========================================
  Hits           999       999           

---

Continue to review full report in Codecov by Harness.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update f0a26ca...aa20837. Read the comment docs.

🚀 New features to boost your workflow:

• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud