resync

[theg1239]

spent a lot of water and tokens to review your slop

Greptile Summary

This PR declares the project under GPL version 3 only. The main changes are:

• Adds the full GPLv3 license text.
• Adds a GPLv3 badge to the README.
• Adds copyright and license details to the README.

Confidence Score: 4/5

The npm distribution needs to match the new GPL declaration before merging.

npm metadata continues to identify the package as unlicensed. The published npm package omits the new license file and notice. The added GPL text and repository README agree with each other.

README.md and the npm package metadata and file list.

T-Rex Logs

What T-Rex did

• T-Rex reproduced the packaging process to verify the published package remains unlicensed by running npm pack on the head checkout and inspecting the tarball contents and license fields.
• T-Rex validated that after updating the README local license references, the license markers point to the LICENSE file and the GPLv3 notices are present, with the build and help checks completing successfully and exit codes indicating success.

_{Ran code and verified through T-Rex}

Important Files Changed

Filename	Overview
LICENSE	Adds the standard GNU General Public License version 3 text.
README.md	Adds the GPLv3 badge and GPL-3.0-only declaration, which conflicts with the existing npm publishing metadata.

_{Reviews (1): Last reviewed commit: "docs: clarify GPLv3 licensing" | Re-trigger Greptile}

Greptile also left 1 inline comment on this PR.

[greptile-apps]

Published Package Remains Unlicensed

The repository now declares GPL-3.0-only, but the npm publishing path still exposes "license": "UNLICENSED", substitutes a README with no license notice, and omits LICENSE from the package files. npm consumers and compliance scanners therefore receive contradictory terms and can reject or misclassify the package; align the package metadata and published contents with this declaration.

Artifacts

Repro: executable npm pack and tarball inspection harness

• Contains supporting evidence from the run (text/x-shellscript; charset=utf-8).

Repro: complete packaging execution output with command, working directory, exit code, manifest license, file listing, README inspection, and restoration check

• Keeps the command output available without making the summary code-heavy.

Repro: machine-readable tarball inspection report

• Contains supporting evidence from the run (application/json; charset=utf-8).

Repro: npm pack JSON result

• Contains supporting evidence from the run (application/json; charset=utf-8).

Repro: generated npm package tarball

• Contains supporting evidence from the run (text/plain; charset=utf-8).

_{Ran code and verified through T-Rex}