Add Library power-user features for large collections

[zachyzissou]

Problem

A real library with 250+ shows needs more than raw scrolling. The Library should help users scan, segment, and act on large collections efficiently.

Candidate features

• Saved filters or quick scopes for active, stale, unplayed, in-progress, downloaded, and recently updated shows.
• Bulk actions for sync, unsubscribe, download cleanup, and mark played where appropriate.
• Better show metadata signals: update status, last episode date, unplayed/in-progress counts.
• Faster jump/search affordances tuned for one-handed use.

Acceptance criteria

• Define and ship the first focused set of high-value Library power-user controls.
• Preserve compact Tuner/OLED visual language.
• Keep scrolling smooth with 250+ shows.
• Add tests or fixtures for large-library behavior.

Agent execution contract

Readiness: agent:needs-spec
Lane: Library product features

Start in these files:

• OffScript/LibraryView.swift
• OffScript/PodcastServices.swift
• OffScriptTests/OffScriptTests.swift

Required verification:

• xcodebuild test -project OffScript.xcodeproj -scheme OffScript -destination 'platform=iOS Simulator,OS=latest,name=iPhone 17 Pro' -only-testing:OffScriptTests CODE_SIGNING_ALLOWED=NO

Non-goals / guardrails:

• Do not ship broad bulk actions without a narrowed safety spec.
• Do not trade scrolling performance for feature density.

PR expectation: Needs first-slice spec before implementation; use one feature per PR.

Low-thinking agents must follow docs/AGENT_EXECUTION_RUNBOOK.md. If the touched code falls outside the files above, stop and tighten the issue or ask for senior review before continuing.

[zachyzissou]

Status: parked, needs scope cut

This is currently labeled or implied as ready for low-thinking work, but the acceptance criteria are list-of-features rather than a single shippable slice. To unblock:

• Pick one specific feature/failure mode from the candidate list.
• Define what "done" looks like for that one slice (UI test? unit test? real-device pass?).

Until then this can't be picked up autonomously without guessing what to build. Suggest moving to a "Needs Spec" status until a slice is named.

Discovered while reviewing the kanban post-session 2026-04-30.