WIP: add nanobind leak detector

[trevor-e]

No description provided.

[codecov]

Codecov Report

Attention: Patch coverage is 77.77778% with 8 lines in your changes missing coverage. Please review.

Project coverage is 75.94%. Comparing base (4457ff4) to head (ed53935).
Report is 2 commits behind head on main.

Files with missing lines	Patch %	Lines
tests/conftest.py	75.00%	5 Missing and 3 partials ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #204      +/-   ##
==========================================
+ Coverage   75.70%   75.94%   +0.24%     
==========================================
  Files         125      127       +2     
  Lines        9713     9846     +133     
  Branches     1096     1105       +9     
==========================================
+ Hits         7353     7478     +125     
- Misses       1959     1964       +5     
- Partials      401      404       +3     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[graphite-app]

This appears to be test code that intentionally triggers the nanobind leak detector by printing a fake leak message to stderr. These debug print statements should be removed before merging as they will cause the test to fail with a false positive leak detection. If this was added to verify the detector's functionality, consider moving it to a dedicated test case for the detector itself rather than leaving it in an unrelated test.

Suggested change

	import sys
	print("DEBUG: About to write to stderr", file=sys.stdout)
	print("nanobind: leaked telkins", file=sys.stderr)
	print("DEBUG: Just wrote to stderr", file=sys.stdout)
	import sys

Spotted by Diamond

Is this helpful? React 👍 or 👎 to let us know.