gsadmin/sencho
1
0
Fork 0
mirror of https://github.com/Studio-Saelix/sencho.git synced 2026-08-19 06:46:23 +00:00
Code Issues Packages Projects Releases Wiki Activity

docs: relicense Sencho to AGPLv3 and reframe Community positioning (#1623)

Browse Source 
* docs: relicense Sencho to AGPLv3 and reframe Community positioning

Replace BSL with AGPLv3 for the public Community product, update contributor
and licensing copy for Community-focused contributions, and surface source
and license links in Settings About.

* docs: clarify CLA scope and Community contribution framing

* fix(ui): split About link constants and harden AboutSection test selectors
This commit is contained in:
Anso
2026-07-13 03:49:29 -04:00
committed by GitHub
parent c01f2479b9
commit 9b3f5c5a90
31 changed files with 852 additions and 140 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/features/node-compatibility.mdx
+1 -1
View File
@@ -99,4 +99,4 @@ Some features need both an Admiral license **and** node capability support. The
1. The license gate is checked first. On the wrong tier, the feature's entry point (sidebar item, top-nav button, settings section) is hidden entirely, so you never reach the panel.
2. If you are on the right tier but the active node does not advertise the capability, the entry point is visible but the panel is replaced by the capability lock card.
The practical effect is that you only see the lock card for features your license already covers, so it is always actionable: upgrading the node will unlock the feature.
The practical effect is that you only see the lock card for features your plan already covers, so it is always actionable: upgrading the node restores access to that feature.