v0.2: collections — multiple slideshows under one shareable page

[ericelizes]

Why

v0.1 caps slideshows at 20 slides / 100 MB (commit bb97fda). Anything past that is the run trying to be something it isn't — a tour, a portfolio piece, a multi-step demo. Those use cases are real, but they're not "one slideshow with 50 slides," they're "several focused slideshows grouped together."

This issue tracks the v0.2 direction: collections — N slideshows under one shareable page.

The shape

A collection is an ordered list of slideshows that lives at a single shareable URL. Two killer use cases:

• Recruiter portfolio. "Here are the last five QA runs I shipped." One URL pasted in a cold message; the recipient sees five clip thumbnails with summaries on a single page, clicks any of them to see the full slideshow.
• Multi-step demos. "Walking through our checkout flow" might be three slideshows: signup, cart, payment. A reader scans summaries, drills into whichever section matters.

API sketch

Method	Path	Auth	What
POST /api/v1/collection/	none	create a collection; returns share_url + write_token
POST /api/v1/collection/<id>/items/	write_token	append a slideshow to the collection (by share_token)
DELETE /api/v1/collection/<id>/items/<position>/	edit_token	remove without renumbering remaining
PATCH /api/v1/collection/<id>/	write_token	rename, set bio, reorder

Web shape

/c/<share_token> — collection viewer page. Renders the collection title + bio + an ordered grid of slideshow cards (cover image, title, summary, slide count). Each card links to the existing /s/<share_token> viewer.

The home gallery (is_gallery=True slideshows) doesn't change — collections are a parallel surface.

What this lets us NOT do

The cleaner reason to ship collections is what it lets us not do in the per-slideshow product:

• Don't expand the 20-slide cap. The cap is correct for v0.1 and stays correct in v0.2. A long story is N slideshows in a collection, not one slideshow with 50 slides.
• Don't add chapters within a slideshow. The narrative arc framing in the SKILL holds — every slideshow has a single spine. Multi-spine artifacts use a collection.
• Don't add per-user accounts. Collections can stay token-authed like slideshows.

Out of scope for this issue

• Comments / reactions on collections
• Collection-level analytics
• Auto-curation from the gallery feed

Pinned by

• 20-slide / 100 MB caps shipped in bb97fda explicitly defer the "longer runs" story to this work.
• The v0.1 README and the bundled SKILL.md both frame AgentClip as "short, focused walkthroughs." Collections is what makes that framing scalable instead of limiting.