ccdeck 3.22.1 → 3.22.4

package/LICENSING.md

@@ -5,34 +5,108 @@ ccdeck is licensed under the **GNU Affero General Public License v3.0 only**
 
 Copyright © 2026 Bargan Constantin.
 
-## What changed, and when
-
-Everything up to and including **3.21.4** was published under the MIT licence,
-under all three npm names (`ccdeck`, `agents-deck`, `agent-dag`). The AGPL
-applies from **3.22.0** onward, which is the first release cut under it.
-
-## The old releases are still MIT
-
-This is the part worth being exact about, because relicensing is often
-described sloppily.
-
-- **Versions already published under MIT stay MIT.** 3.21.4 and everything
-  before it were distributed under the MIT licence, and they remain available
-  on those terms. Changing the licence in this repository does not reach
-  backwards into copies that are already out in the world.
-- **Rights already granted are not revoked.** If you received ccdeck under
-  MIT, you keep the MIT permissions you were given for that copy — including
-  the right to use, modify, redistribute and sublicense it, and to build
-  closed-source work on it. Nothing here takes that away.
-- **Old tags and releases stay up.** Git tags up to `v3.21.4`, the GitHub
-  releases and the npm versions are not being deleted or rewritten. The MIT
-  licence text that shipped inside each of those artifacts is still the licence
-  for that artifact.
-- **The new licence is not retroactive.** Do not read this change as "ccdeck
-  is now AGPL, therefore the old copies are too." It is not, and they are not.
-
-What the change does affect is the code in this repository going forward, and
-any release built from it after the relicensing commit.
+## The current licence covers the whole codebase
+
+The **complete current ccdeck-owned codebase** is offered under
+`AGPL-3.0-only`. Not merely the commits made after the change — the whole
+work, as the project distributes it today.
+
+This is worth stating plainly because relicensing is often misread as applying
+only to what came after it. It does not. The code implementing the canvas, the
+session clusters, the tool-call timeline, the quota and usage panels, the LAN
+sync, the installer and the hook was written before the licence changed, and
+it is part of the current work. When that code ships in a current release, the
+licence the project offers it under is the AGPL.
+
+A licence applies to software — to the code — rather than to a feature as an
+idea. So the accurate statement is not "the features are AGPL" but: the
+complete current ccdeck-owned codebase, including the code implementing
+features that existed before the relicensing, is distributed by the project
+under `AGPL-3.0-only`.
+
+The copyright holder is relicensing the complete current work, which is
+something a sole copyright holder may do with their own code. That some of
+this code also appeared in older MIT releases does **not** mean the project
+offers the current repository or the current release under MIT.
+
+## The version boundary
+
+```text
+v3.22.0 and later:
+    Distributed by the project under AGPL-3.0-only — the complete current
+    ccdeck-owned codebase, including the code implementing features that
+    existed before the relicensing.
+
+v3.21.4 and earlier:
+    Historically distributed under the MIT License. Previously granted MIT
+    rights in the material distributed in those releases remain valid.
+```
+
+3.22.0 is the first release the project distributes under the AGPL.
+
+## ccdeck is not offered as "MIT OR AGPL"
+
+The project does **not** currently offer ccdeck under a choice of licences.
+There is no MIT option and no MIT fallback on what the project distributes
+today: obtain the current release from the project, and the licence it is
+offered to you under is `AGPL-3.0-only`.
+
+That is a statement about what the project offers now. It is not a statement
+about rights somebody was already granted — see
+[Historical releases](#historical-releases) for those.
+
+## Historical releases
+
+Before the AGPL relicensing, certain ccdeck releases were distributed under the
+MIT License.
+
+Those historical copies retain the rights granted under the license under which
+they were originally distributed. Those previously granted rights cannot be
+retroactively revoked.
+
+This does not mean that the project dual-licenses ccdeck, or offers part of the
+current work under MIT. The current ccdeck-owned codebase and current releases
+are offered by the project exclusively under `AGPL-3.0-only`.
+
+Concretely, and without overstating it:
+
+- **Old releases stay usable on their old terms.** Somebody who lawfully
+  obtained ccdeck 3.21.4 or earlier under MIT keeps the MIT rights they were
+  granted in the material distributed in those releases — including the right
+  to use, modify, redistribute and build closed-source work on it. Those
+  rights are theirs already, and this change does not touch them.
+- **The old artifacts stay up.** Git tags through `v3.21.4`, the GitHub
+  releases and the npm versions are not being deleted, unpublished or
+  rewritten. The MIT text that shipped inside each of those artifacts is still
+  the licence for that artifact. Removing them would not withdraw anything
+  anyway.
+- **Nothing became AGPL retroactively.** A copy distributed under MIT was
+  distributed under MIT and stays that way. Do not read this page as saying
+  the old releases are now AGPL, because they are not.
+
+## What the historical MIT grants do and do not cover
+
+Two things are true at once, and both matter:
+
+- **The current ccdeck release, as distributed by the project, is licensed
+  under `AGPL-3.0-only`.** That is the licence on offer for what you obtain
+  from the project today.
+- **Previously granted MIT rights in material distributed in historical MIT
+  releases remain valid.** They were granted, they cannot be retroactively
+  revoked, and they do not disappear merely because identical or substantially
+  identical code also appears in a later AGPL release.
+
+What those historical grants do **not** do is reach forward. They do not cover
+new code, or modifications, first distributed under the AGPL. A later release
+is not placed under MIT because it contains material that also appeared in an
+MIT release: the new and changed code in it is offered by the project under
+the AGPL only.
+
+Where the line falls between material already distributed under MIT and code
+first distributed under the AGPL is a question about specific code, and this
+page does not try to settle it for any particular file. What the project can
+state is what it offers, and what it offers for the current release is
+`AGPL-3.0-only`.
 
 ## Why AGPL
 
@@ -41,13 +115,13 @@ functionality. The AGPL is chosen so that modifications to the covered software
 stay open — including modified versions that users interact with over a
 network, which is the case an ordinary GPL does not cover.
 
-The intent is to keep ccdeck open source while making it harder for a modified
-version to be run as a closed-source competing hosted service. Precisely: the
-AGPL requires whoever runs a modified version to make the corresponding source
-available **to the users interacting with that modified version over a
-network**. It does not require anyone to send changes to this repository, open
-a pull request, or contribute anything upstream — there is no obligation to
-this project, only to those users.
+The intent is to keep ccdeck open source and ensure that users of modified
+network-hosted versions can also access the corresponding source code.
+Precisely: the AGPL requires whoever runs a modified version to make the
+corresponding source available **to the users interacting with that modified
+version over a network**. It does not require anyone to send changes to this
+repository, open a pull request, or contribute anything upstream — there is no
+obligation to this project, only to those users.
 
 ## What this means if you use ccdeck
 
@@ -73,6 +147,10 @@ Their copyright and permission notices are preserved in
 [THIRD_PARTY_NOTICES.md](./THIRD_PARTY_NOTICES.md) and must travel with any
 copy of ccdeck.
 
+Those MIT and ISC notices describe **dependencies**, not ccdeck. They are not a
+second licence on ccdeck's own code, and their presence in the tree does not
+put ccdeck's own code under MIT.
+
 ccdeck claims copyright only over its own code, not over that third-party code.
 
 ## Contributing

package/README.md

@@ -459,24 +459,17 @@ and starts again when you log in. `ccdeck --stop` ends it.
 
 ## License
 
-ccdeck is licensed under the GNU Affero General Public License v3.0 only
-(AGPL-3.0-only).
+ccdeck is licensed under the **GNU Affero General Public License v3.0 only (AGPL-3.0-only)**.
 
-Copyright © 2026 [Bargan Constantin](https://github.com/BarganConstantin).
-
-See [LICENSE](./LICENSE) for the full text.
+The current release, as distributed by the project, is offered under the AGPL
+in full: the complete current ccdeck-owned codebase, including the code
+implementing features that existed before the relicensing.
 
-Running the deck imposes nothing on you. The AGPL's obligations attach to
-distributing ccdeck or offering a **modified** version to users over a network
-— and what they require is that those users be offered the corresponding
-source of that modified version, not that anyone contribute changes back to
-this repository.
+Copyright © 2026 [Bargan Constantin](https://github.com/BarganConstantin).
 
-Releases up to and including **3.21.4** were published under the MIT licence
-and remain available under MIT — this change is not retroactive and revokes
-nothing already granted. [LICENSING.md](./LICENSING.md) explains what applies
-to which version.
+See [LICENSE](./LICENSE) for the full license text and
+[LICENSING.md](./LICENSING.md) for licensing history and additional details.
 
 ccdeck bundles third-party code under permissive licences (MIT, ISC,
-BSD-3-Clause); their notices are preserved in
-[THIRD_PARTY_NOTICES.md](./THIRD_PARTY_NOTICES.md).
+BSD-3-Clause). Those licences are theirs, not ccdeck's, and their notices are
+preserved in [THIRD_PARTY_NOTICES.md](./THIRD_PARTY_NOTICES.md).