Series, links, tags and four careful agent tools

What was asked

The exact prompts for this stretch of work aren't in this report. See Open questions.

What happened

Over one afternoon, six steps landed on the editor-and-layers branch:

1. Series. A report can belong to one series, a project's timeline. Series are private until shared, and sharing a series never shares its reports. Agents send the repo's identifier, and a new report from the same repo goes to the series that repo used last.
2. Links and tags. A report can continue from one earlier report and be related to others. Tags are the owner's own labels and are never shown to visitors. Visitors only see linked reports they're allowed to open.
3. Video. Cards show a video's first frame, videos load only metadata until played, and GIFs can be up to 25 MB.
4. Four tools. create, edit, get and list reports now do everything the nine earlier tools did. Every write is checked first: secrets, broken layer order, contradictions, loops and duplicate series are refused, and nothing is saved.
5. Gap fixes. Tags are added and removed one by one so a tag added on the website isn't lost. A conflict is found before upload slots are reserved. More fields are scanned for secrets. If the text saves but tags or links fail, the agent is told it was saved, so it doesn't send it twice.
6. A live agent test. A fresh Claude Code agent used all four tools end to end and made ten deliberate mistakes. The tools behaved, but the test showed Claude Code keeps only about 2,000 characters of a server's instructions and of each tool description. Labnotes' were 7,222, so the rules about series, layers and safety never reached the agent. Everything was rewritten to fit, and a test keeps it that way.

A screenshot of an agent's write being refused, with its reason and "Nothing was saved"

Result

78 files changed (about 12,100 lines added, 800 removed) across nine commits on the branch. The verdict is yours to set.

The branch also carries the in-place editor and layered sharing: