docs: clarify licensing boundaries

[solankydev]

Summary

• keep the project source and documentation under the standard MIT License
• reserve Openza names, logos, and official app icons as brand assets
• replace stale Astro/Starlight notices with the current WinUI dependency inventory
• add consistent package licensing and attribution metadata

Validation

• GitHub API detects the branch root LICENSE as MIT
• MSBuild evaluates PackageLicenseExpression as MIT
• dependency licenses checked against exact NuGet package metadata
• git diff --check
• gitleaks detect --source . --verbose

Summary by CodeRabbit

• Documentation

  • Added licensing guidance covering project content and reserved brand assets.
  • Clarified README licensing information, including brand asset restrictions and third-party license notices.
  • Expanded third-party notices with categorized dependency and project asset details.
  • Updated copyright attribution to include project contributors.

• Chores

  • Added package and distribution metadata, including authorship, product, repository, and license information.

[coderabbitai]

Warning

Review limit reached

@solankydev, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 17 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 190bae3d-773e-4ec1-a99d-a6f1215346ab

📥 Commits

Reviewing files that changed from the base of the PR and between 8c5d39c and 26afd5f.

📒 Files selected for processing (1)

• THIRD-PARTY-NOTICES.md

📝 Walkthrough

Walkthrough

The changes add reserved-brand licensing terms, update MIT attribution and README licensing text, add package distribution metadata, and restructure third-party dependency notices into categorized tables.

Changes

Licensing and distribution metadata

Layer / File(s)	Summary
License and brand terms BRAND.md, LICENSE, README.md	Reserved Openza brand assets and usage restrictions are documented, contributor attribution is expanded, and the README license notice includes brand and dependency licensing details.
Package and dependency metadata Directory.Build.props, THIRD-PARTY-NOTICES.md	Project package properties are expanded, and third-party notices are reorganized into runtime, test, and project-owned asset sections with license metadata.

Estimated code review effort: 1 (Trivial) | ~5 minutes

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately summarizes the main change: clarifying licensing boundaries and brand asset restrictions.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch docs/license-boundaries

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[coderabbitai]

Actionable comments posted: 1

🧹 Nitpick comments (1)

THIRD-PARTY-NOTICES.md (1)

7-19: 🔒 Security & Privacy | 🔵 Trivial | ⚡ Quick win

Record the exact license artifact for each dependency.

The Package license file value is too generic for an auditable notice. NuGet exposes different metadata forms across these packages—for example, Apache-2.0 for xUnit and MIT for coverlet, while Microsoft.WindowsAppSDK exposes a separate license-info entry. Record the exact SPDX expression or license/NOTICE file path and verify each row against the project’s package references. (nuget.org)

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@THIRD-PARTY-NOTICES.md` around lines 7 - 19, Update the dependency table in
THIRD-PARTY-NOTICES.md so every row records the exact SPDX expression or
license/NOTICE artifact path exposed by its corresponding package metadata,
replacing the generic Microsoft.WindowsAppSDK “Package license file” entry with
its specific license-info artifact. Verify all entries, including
CommunityToolkit.Mvvm, Microsoft.WindowsAppSDK, xUnit.net, the Visual Studio
runner, Microsoft.NET.Test.Sdk, and coverlet.collector, against the project’s
package references and NuGet metadata.

Source: MCP tools

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@LICENSE`:
- Around line 1-3: Add a brief note to LICENSE referencing BRAND.md and
clarifying that the Openza name, logos, and app icons are excluded from the MIT
license grant. Preserve the existing MIT license text and copyright notice
unchanged.

---

Nitpick comments:
In `@THIRD-PARTY-NOTICES.md`:
- Around line 7-19: Update the dependency table in THIRD-PARTY-NOTICES.md so
every row records the exact SPDX expression or license/NOTICE artifact path
exposed by its corresponding package metadata, replacing the generic
Microsoft.WindowsAppSDK “Package license file” entry with its specific
license-info artifact. Verify all entries, including CommunityToolkit.Mvvm,
Microsoft.WindowsAppSDK, xUnit.net, the Visual Studio runner,
Microsoft.NET.Test.Sdk, and coverlet.collector, against the project’s package
references and NuGet metadata.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 4d121ae6-2c37-4ea3-8ef9-7c1396248c02

📥 Commits

Reviewing files that changed from the base of the PR and between bfa9041 and 8c5d39c.

📒 Files selected for processing (5)

• BRAND.md
• Directory.Build.props
• LICENSE
• README.md
• THIRD-PARTY-NOTICES.md