feat(lists): per-column validation and help text, an Add Row form, and the GitHub repo tag

[Adron]

Summary

Closes #50 — three of its four items. Item 3 is upstream-blocked and is not built; evidence below.

Item 1 — validation and help text (was blocked on P2-G)

work-consolidation.md P2-G listed the schema DSL's validation encoding as API-unconfirmed, which is what blocked this. It is confirmed, and it turned out not to be DSL syntax at all — these are first-class fields the server has stored since the schema routes shipped and no client ever wrote:

validationRules { min, max, minLength, maxLength, pattern }
helpText · placeholder · isRequired · isVisible · displayOrder

The schema editor gains them behind a per-column Details disclosure, so the common case — name a column, pick its type — stays one line.

The controls are type-dependent. Length rules only for the text family, range rules only for number. A "Min length" on a checkbox would be a control that cannot do anything, and sending the rule would put a constraint on the server that nothing enforces.

The editor also stops re-deriving a column's key from its label. They are separate on the server, and a web-authored column can be keyed year under a label of "Publication Year" — rewriting the key on a macOS save would orphan every stored cell in that column.

Item 2 — the Add Row form, which had to exist first

Validation and help text needed somewhere to be used, and there was nowhere: macOS had no add-row form. addRow() created an empty row and left the user to fill it in through the inspector.

AddRowSheetView carries the two behaviours the help page is explicit about:

• "Add another after saving" persists across lists and visits, empties the form, counts up, and returns focus to the first field — bulk entry never needs the mouse between rows.
• A rejected save clears nothing. A session that loses a typed row to a validation error is worse than one that never offered the form, so the failure path deliberately does not touch the values. There is a test asserting the two interact correctly: staying open must not be confused with clearing.

Local validation refuses a row before the service call. The rules are the server's and it would reject the same row, so spending a round-trip to be told what we already know costs the user time and tells them less — a 400 cannot say which column was wrong. Every failure is reported at once, against the field that caused it.

pattern is deliberately never evaluated locally. It is a server-side regular expression; compiling it here would let this client refuse a value the server accepts whenever the two engines disagree on syntax. A round-trip is the correct cost for the one rule we cannot faithfully reproduce. There is a test pinning that as a decision rather than an omission.

Item 4 — the repository link and Private-repo tag

githubRepo and githubRepoPrivate have been on the wire since the list routes shipped, and OwnedListMappers hard-coded gitHubSource: nil past them — so a GitHub-backed list looked like a plain one and the private-repository warning had nothing to render from.

The tag is not decoration: a link to a private repository sends a visitor to a GitHub sign-in or a "not found" page, and the help page is explicit that the list should say so before they follow it. Absent — rather than shown as "public" — when the server did not say.

Item 3 — From Template: no such route exists

Searched all 233 paths in the live spec:

/api/documents/templates        GET
/api/documents/from-template    POST
/api/documents/templates/seed-defaults  POST

There is no list equivalent, and no ListTemplate schema in components.schemas. The web documents a From Template tab; the API this client can reach serves nothing behind it.

Not half-built. It needs a backend ask — the shape of a pre-defined list schema catalogue — and that belongs on #58.

Verification

• xcodebuild build → ** BUILD SUCCEEDED **
• xcodebuild test (App) → Executed 1002 tests, with 0 failures · ** TEST SUCCEEDED **
• swift test InterlinedDomain → Executed 1017 tests, with 0 failures
• swift test InterlinedKit --skip ContractTests → Executed 485 tests, with 0 failures
• swift test InterlinedPersistence → Executed 140 tests, with 0 failures
• Decision 0003 (anchored) → zero hits

New tests: AddRowViewModelTests (11), RowValueValidatorTests (14).

Stacking

Branches from #87 (fix/lists-detail-envelope), which is where the schema object, the key/label split and the per-column metadata come from — this is unbuildable without it. Also merges #99 (Xcode 27 Document disambiguation), without which the App target does not compile at all.

Review order: #99 → #87 → this.

🤖 Generated with Claude Code