Add wet-glue to CLI section

[Noob-stupid]

Adding wet-glue under CLI.

What it does: two comment lines (// glue:begin / // glue:end) mark a code region you're undecided about — for example a lookup that might be a red-black tree or a B+ tree. You register alternative implementations, swap between them (source-level text replacement, no runtime indirection), run your own benchmark via glue verify, and finally glue seal the winner, which removes the markers and welds it as plain code.

Why it fits the criteria:

• Java primary target — implemented in Java 17 and operates on Java source; also works on C#/Kotlin/Go/TS and any //-comment language.
• Unique niche — as far as I know nothing else models a lifecycle for experimental code regions: experimental → candidate → sealed (↔ unseal), with an audit log (swappable.lock) and "is the glue drying" nudges.
• Zero runtime overhead — swapping happens at edit time; sealed code is plain code, strictly equivalent to handwritten.
• English docs + MIT license — both present.

Validation on real code: the tool was exercised end-to-end on NanoHTTPD (5k+ stars) — registering a thread-pool candidate against the classic thread-per-connection model and benchmarking both; case study.

This is self-promotion (I'm the author); disclosing that up front. Happy to adjust wording or placement to match house style.

---

Summary by cubic

Adds wet-glue to the CLI section of the README. It lets developers mark undecided code regions with // glue:begin/// glue:end, swap in alternative implementations, benchmark them, and seal the winner as plain code. Note: this is the author's own project.

^{Written for commit 3fe262e. Summary will update on new commits.}

[cubic-dev-ai]

No issues found across 1 file

_{Re-trigger cubic}