fix(metadata): clarify Tessl summary

[martinfrancois]

Summary

• Problem: the Tessl summary was generic and didn't explain the concrete user benefit.
• Why it matters: the registry listing should quickly explain that the skill helps agents use Optional well in new code and cleanups.
• What changed: updated the Tessl plugin description and summary to use the cleanup/antipattern wording.
• What did not change: skill behavior, eval scenarios, CI, or release automation.

Change Type

• Skill behavior
• Evals or scoring
• Documentation
• CI, release, or dependency automation
• Repository metadata or contribution process
• Other maintenance

Linked Issue

• Related #

User-Visible Behavior

The Tessl registry summary will say: “Help AI coding agents use Java Optional well in new code and cleanups, without replacing one antipattern with another.”

Bug Fix Details

• Root cause: previous metadata described the category, not the practical problem solved.
• Test, eval, or guardrail added: plugin lint and publish dry-run cover metadata validity.
• If no test or eval was added, why not: this changes metadata text only.

Validation

Checks most contributors can run:

• python3 scripts/validate_skill.py skills/java-optionals
• python3 scripts/validate_eval_criteria.py evals evals-reference
• tessl plugin lint .
• markdownlint, if Markdown changed
• Manual rendered-doc or example review, if docs or examples changed

Tessl-authenticated checks:

• bash scripts/check_publish_dry_run.sh .
• tessl skill review --threshold 100 skills/java-optionals/SKILL.md, if skill text or references changed
• tessl eval run --variant with-context --variant without-context ., if skill behavior,
  evals, or benchmark claims changed

Details:

Publish dry-run reached the registry; next patch version 0.1.23 is available.

Human Verification

Checked the plugin metadata text and durable agent note. The wording uses “cleanups” and “antipattern” as requested.

Review Checklist

• Docs updated, or N/A
• Evals updated, or N/A
• PR title or squash title uses Conventional Commits
• Redaction checked: no Tessl tokens, GitHub tokens, package manager tokens, private repository
  links, private eval artifacts, private registry/workspace links, local host paths, or
  proprietary Java source

AI Assistance (if used)

• AI-assisted PR
• I confirm I understand and reviewed the change

AI prompts / session logs (optional)

Asked to use the cleanups description and keep “antipattern” in the Tessl summary.