DOC-6763 investigate automating binder notebook creation

[andy-stark-redis]

Note: not finished - this is to get Bugbot feedback, etc.

---

Note

Medium Risk
New automation touches external binder-launchers clones, Docker execution, and CI gates; kernel-name fixes affect all regenerated Node/Go notebooks. Work is marked WIP but correctness of sync/verify behavior matters for published Binder environments.

Overview
Extends jupyterize into an end-to-end path from docs examples to binder-launchers branches: ship notebooks (demo.ipynb) plus assert-bearing test notebooks (demo.test.ipynb), with local and CI verification before deploy.

Generation & parsing: New --with-tests keeps REMOVE blocks as cells tagged test (nested REMOVE handled by depth). Notebooks get deterministic cell{i} ids. Kernel names in config.py align with real Binder images: Node jslab, Go gonb.

Unwrapping: Orphan trailing } from class/method wrappers split across cells are stripped via brace-aware logic (strings/comments ignored), with new tests.

New tooling: verify.py runs a generated test notebook in the pinned base image (Redis + kernel or Python script mode). sync_notebook.py reads BINDER_ID, jupyterizes both notebooks into the matching branch, runs verify.py as a pre-check, upgrades verify-gated GitHub workflow / .dockerignore, and optionally commits/pushes. Documents Node/Go kernel limitations in js-notebook-findings.md.

Examples: Adds redis-py doctest sources for time series (python-dt-timeseries) and vector sets (python-dt-vector-set) with step markers and asserts for the pipeline.

^{Reviewed by Cursor Bugbot for commit 49c9bde. Bugbot is set up for automated code reviews on this repo. Configure here.}

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[github-actions]

DOC-6763

[jit-ci]

🛡️ Jit Security Scan Results

✅ No security findings were detected in this PR

---

^{Security scan by Jit}

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, have a team admin enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 49c9bde. Configure here.}

[cursor]

Vecset example missing assert coverage

Low Severity

The new vecset example’s add_quant REMOVE block only asserts res31, and the final add_reduce step has no REMOVE block at all. demo.test.ipynb verification can pass while vemb results or dimension-reduction behavior are wrong.

 

^{Reviewed by Cursor Bugbot for commit 49c9bde. Configure here.}