v1.0.37

a16z-infra/JungleGymv1.0.37Aug 10, 2026by GargantuaX

AI Summary

This package update improves the `@pilio/gemini-watermark-remover` by restoring full-strength alpha removal for specific 96px watermarks and preferring full-strength candidates when localized evidence is strong. It maintains safety guards to prevent artifacts on dark content.

Key Highlights

  • Restores full-strength alpha removal for positively signed exact 96px watermarks.
  • Prefers full-strength candidates when localized source evidence is stronger.
  • Preserves inverse-polarity guard for unsupported dark-polarity inputs.
  • Five of six reporter samples were visually clean in review.

New Features

  • Enhanced watermark removal robustness for specific formats
  • Improved candidate selection logic

Full Release Notes

## Package/SDK release

This release updates `@pilio/gemini-watermark-remover` with the issue #101 residual-removal improvement from PR #133.

### Watermark removal

- Restores full-strength alpha removal for positively signed exact 96px/R192 `20260520` watermarks.
- Prefers the full-strength candidate when localized positive source evidence is stronger than circular self-template ranking.
- Preserves the issue #123 inverse-polarity guard so unsupported dark-polarity inputs remain conservative instead of risking a black-hole artifact.

Across the six latest issue #101 reporter samples, five positive-source samples selected full-strength alpha and were visually clean in review. The inverse-polarity sample remained conservatively limited.

### Verification

- Full serial suite: 1685 total, 1653 passed, 32 skipped, 0 failed.
- SDK package smoke: 8 passed, 0 failed.
- Production build, pull-request CI, and post-merge `main` CI passed.
- Package tarball SHA-256: `049f1df67a36a4ddb142ac28fe8d8743a6c4422232d900d4cf9f84d4426b22d0`.

### Release scope

This is a package/SDK-only release. It does not publish new userscript or Chrome extension artifacts; those browser release surfaces remain at v1.0.35. The public website is a separate deployment surface and must be upgraded to this SDK version independently.