[wedamija]

We're moving the notebook tables (Investigation*) into a new sentry.notebooks app, separate from the hypothesis engine that writes them, so other Seer producers like Autofix and triage can write notebooks too.

Notebook create, details, and block writes become public so Seer producers can call them through Code Mode. They accept only notebookVersion, and the response types are fully documented.

[cursor]

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

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

^{Reviewed by Cursor Bugbot for commit 2013c59. Configure here.}

[billyvg]

🤖 Publishing writes that a read-only org:read token can perform

NotebookPermission (notebooks/endpoints/base.py, outside this diff) maps POST/PUT/DELETE to org:read. That lets members write in open-membership orgs. Once these methods are public, though, the published contract says a user token minted with only org:read, which people treat as read-only, can do all of the following:

• create notebooks
• overwrite producer blocks by key, including reviving deleted ones
• reorder blocks
• delete blocks

Runtime behaviour doesn't change: private endpoints already accepted tokens. What changes is that the public docs advertise it, and tightening the scope later would break public clients. Is org:read the scope you want to commit to for public notebook writes? A member-held write scope such as event:write might fit better. If you do want org:read, it may be worth a sentence in the tag description.

_{Written by an AI agent and included in this review by its author.}