Add an "Add to Bluesky list" action with a list picker #29

Queued: the loop will work on this version of the issue.

loop:queued cid=bafyreibrthhuedcffqqcjrln4b2q3gl3vu7lswtb2rboyicl2tz7zcptaa

Working on this, attempt 1.

loop:claim run=contribute-20261026-160610-3my32gopg6n22 branch=loop/3my32gopg6n22 attempt=1

The session found the issue too big for one run, and proposes a split.

chore(actions): defer "Add to Bluesky list" to its split issues #40 and #41

I stopped without changing any code, because this issue has already been split into two child issues, listed under its "Split into" section. If I built the whole action and picker here, it would duplicate those two issues and the reviews would collide. No commits were made on the branch.

Why I stopped #

• The issue lists its split: #40 "Add an 'Add to list' action" and #41 "List picker for the 'Add to list' action".
• Neither is done on main at 1908205: lib/actions/ and app/islands/action-editors/ have no add-to-list action, and nothing in app/ or lib/ builds app.bsky.graph.listitem records except the generic record action and tests.
• Doing both parts in one branch is the larger scope that the split was meant to avoid.

Acceptance criteria #

• A dedicated action that adds a DID to one of the signed-in user's Bluesky lists, picked from a dropdown, instead of hand-building an app.bsky.graph.listitem record. (Not done here. It is covered by #40, the action, then #41, the picker.)

What the owner needs to decide #

• Mark #40 ready first, since the picker in #41 depends on the action it fills in, and treat this issue as the parent that tracks them (close it when both merge).
• Or, if you want one branch for both after all, remove the split from this issue and run it again. I would then build the action and the picker together.

loop:awaiting-owner run=contribute-20261026-160610-3my32gopg6n22

I marked #40 and #41 as ready

Working on this, attempt 1.

loop:claim run=contribute-20261026-161010-3my32gopg6n22 branch=loop/3my32gopg6n22 attempt=1

The session found the issue too big for one run, and proposes a split.

chore(automations): do not work the umbrella "Add to Bluesky list" issue directly

I stopped without changing anything. This issue is already split into #40 ("Add an "Add to list" action") and #41 ("List picker for the "Add to list" action"), and the owner's comment says those two are the ones marked ready. If I built the whole feature on this branch, it would duplicate their work and conflict with any contributor already working on them.

What I checked #

• The issue's "Split into" section names #40 and #41. The only comment, from the owner, says "I marked #40 and #41 as ready".
• main (1f9d889) has no "Add to list" action yet. I grepped app/ and lib/ for listitem and addToList and found only unrelated matches, so none of the split work has landed.

Checklist #

• #40: Add an "Add to list" action (its own run)
• #41: List picker for the "Add to list" action (its own run, after #40)

What the owner needs to decide #

• Take this issue off "ready", or close it as tracked by #40 and #41, so the loop does not pick it up again.
• If you do want everything delivered in one branch from this issue, say so and close #40 and #41 instead. I would then start with the action itself (#40), then add the picker (#41).

loop:awaiting-owner run=contribute-20261026-161010-3my32gopg6n22

Closing in favor of #40 and #41