feat(lists): open/closed issue filter, smart row headline, tap-to-edit, and GitHub schema

[Adron]

Summary

Improves how GitHub-backed lists are browsed and edited, and how list rows render generally. GitHub-backed lists now default to showing open issues with a segmented Open/Closed filter at the top. Rows headline the most meaningful field (not the first column), tapping a row opens view/edit, and GitHub lists get a working dynamic add/edit form now that the schema is available. Pairs with the backend fix that returns the synthetic GitHub schema on GET /api/lists/:id.

What's included

• Open/Closed issue filter — a segmented control at the top of GitHub-backed list detail filters rows by issue state, defaulting to Open so closed issues are hidden until requested. The filtered-empty case gets its own "No Open/Closed Issues" copy, distinct from the "nothing synced yet" state; local (non-GitHub) lists are unaffected.
• Smart row headline — DynamicItemRow uses ListPropertyDef.primaryDisplayField(from:) to pick a title/name/subject-like field (else the first editable text field), instead of the first column. For GitHub that was the issue #; with an empty schema it fell back to the alphabetically-first raw field — an assignee (the user) or created_at (a date), exactly the reported symptom. Improved nil fallback prefers title-like values.
• Tap-to-view/edit — the whole row opens the edit sheet on tap; the inline toggle and expand chevron still capture their own taps; swipe Edit/Close/Delete remain.
• GitHub list schema — GET /api/lists/:id returned empty properties for GitHub lists (no stored columns), which disabled the add button (.disabled(schema.isEmpty)) and blanked the dynamic add/edit form. The backend now returns the synthetic issue schema (deployed on main); iOS keeps ListPropertyDef.gitHubIssueSchema() as a fallback only when the fetched schema is empty (older/undeployed backend).

Root cause (row/schema symptoms)

getListById (backend) reads properties from the DB, but GitHub lists have no stored listProperty rows — their columns are synthetic issue fields. So iOS received an empty schema, which cascaded into all three symptoms. The durable fix is server-side (now returning the schema); the client fallback is defense-in-depth.

Testing

• xcodebuild build (iPhone 16 simulator) — BUILD SUCCEEDED
• xcodebuild test on ListPropertyDefHelpersTests + APIClientListsTests — 34 passed, 0 failures (7 model + 27 API)
• New coverage: model tests for the synthetic schema shape + primaryDisplayField heuristic, and an API test decoding the real server GitHub property payload (id: \"gh_<key>\", listId, visibilityCondition, validationRules.options, isReadOnly). The Open/Closed filter is view-layer logic verified by the build.

Caveats / follow-ups

• Live GitHub flow (add/close/edit real issues, the Open/Closed toggle against real data, tap-to-edit feel) still warrants an on-device pass with a GitHub-linked account — the simulator can't reach a GitHub-backed list.
• The client gitHubIssueSchema() fallback is intentionally retained as an inert safety net; it can be removed once we're confident every environment runs the updated backend.

🤖 Generated with Claude Code