Help me understand and prepare the license for my plugin before I publish it on Tone Picnic. I may not know legal or programming terms.

Inspect the project I have provided. Look for LICENSE/COPYING files, notices, source headers, package metadata, dependencies, SDKs, borrowed code, samples and other bundled assets. Report the existing license name and version with the actual file paths. Do not replace it simply because another license is easier. Check which third-party terms affect distributing this particular build and its source; keep required notices and source obligations intact. Say when something needs a closer review instead of claiming certainty.

Explain in a few plain-language sentences:
- What listeners may do with the plugin.
- Whether other people may share, modify or sell copies of the code/plugin.
- What notices, permissions or source files I must provide when distributing it.
- Whether bundled samples/assets have separate conditions.
Make clear that a free download price and an open-source license are different choices, and that selecting a label on Tone Picnic does not add the actual license to my ZIP.

If the project has no clear license, ask me about my intended permissions: do I want people to use the plugin while keeping the code private, freely reuse/change/share the code, or share changes under the same license? Also check whether I own or have permission to license the relevant code. Do not choose or apply a license on my behalf without explaining the effect and getting my decision. “All rights reserved” by itself does not specify a complete end-user permission to use a plugin. Never invent a custom legal agreement and present it as reviewed legal advice.

After I decide, help prepare the appropriate LICENSE/NOTICE files and include them in each applicable release ZIP, preserving the project's existing third-party terms and desktop builds. For a standard license, use its official text and the correct owner/year; do not silently alter it. For custom/commercial terms, identify what is missing and recommend appropriate review rather than guessing.

Return:
1. A short explanation I can understand.
2. Which Tone Picnic choice to pick: “Free to use, code stays private”, “Open source, no strings” (MIT), “Open source, changes stay open” (GPL-3.0), or “It already has a license” with the exact license name and version (up to 80 characters).
3. Where the license and notices are included in my release files, and any source-distribution obligations still to complete.
4. An updated patchwork-upload.json if it already exists.
If the choice or permissions are unresolved, keep license as "Not decided yet" and tell me what is needed. Tone Picnic can save the private draft, but it will ask me to choose the actual license before publishing. Do not publish, upload, spend money or change rights without my approval.