Part of #1706: emit typed a11y primitives from CRUD scaffold codegen

[madmax983]

Part of #1706.

Before / After

Before: the CRUD scaffold could generate a submit button or a nav/action link with no accessible name, and the generated app compiled fine — the missing accessible name only surfaced (if ever) at runtime or in an audit.

After: generated submit buttons and static-text nav/action links emit typed primitives — autumn_web::a11y::Button::new(name) and Link::new(href, text) — so a nameless generated control fails to compile in the generated app. Accessibility is enforced by construction. The rendered HTML is byte-identical to before and runtime behavior is unchanged; this is purely a codegen-shape change.

How

Generator-only change in autumn-cli/src/generate/scaffold.rs. The codegen paths that now route through the typed primitives:

• Submit buttons in the live-validation path emit Button::new(...).
• Nav + action links in the index / show / search / data_table paths emit Link::new(href, text).
• The Show-column link emits Link::new(...).

Composition is preserved across every existing scaffold axis: FTS/search, sort-filter allowlisting, policy, submit-tokens, typed paths, and the #1867 zero-JS multipart uploads. Freshly-generated sample projects still cargo check clean (proven by the generated-project cargo-check tests, see Testing).

Scope / follow-on

Being honest about what this slice does not cover:

• Raw form-field inputs are mostly left as-is. The standard field path already routes through form::* helpers that require a label, so those are already accessible. The escape-hatch raw-markup fields carry class + aria-invalid/aria-describedby + inline-error + validation-constraint wiring that the current TextField typestate cannot express. Full TextField field adoption needs the primitive extended first — that is the named follow-on.
• The destructive Delete button (with its confirm() guard) is left as-is.
• Dynamic-text links (where the link text is computed at runtime) are left as-is.

Testing

Post-rebase onto latest trunk-dev (which now includes #1867 uploads and the #1845 a11y verify scanner):

• cargo fmt --all -- --check — clean
• cargo clippy --workspace --all-targets -- -D warnings — clean
• cargo test -p autumn-cli — green (unittests 3678, cli_tests 175, generate 177; 0 failed)
• Generated-project cargo-check proofs (ignored, slow): generated_form_for_scaffold_cargo_checks, generated_attachment_scaffold_cargo_checks (composition with Scaffold: persist file uploads on plain multipart submit (zero JS) #1867 uploads), and the base generated_scaffold_cargo_checks all pass — the generated sample projects compile with the typed primitives in place.

Part of #1706.

---

Generated by Claude Code

[gemini-code-assist]

Code Review

This pull request updates the scaffold generator in autumn-cli to use typed accessibility primitives (autumn_web::a11y::Button and autumn_web::a11y::Link) instead of raw HTML elements for buttons and links. This ensures that generated applications have accessible names and avoids compilation errors. There are no review comments, and I have no feedback to provide.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.