Files
Oleg Isonen 0a4e3a48dd docs: Explain Form capabilities with focused screenshots (#6591)
## Summary

Explain what the Form component can do, with short chapters for actions,
email, uploads, search and filters, submission feedback, and Preview
testing.

- Replace the old guide with the reviewed text.
- Add five tightly cropped screenshots, each in light and dark themes.
- Update links from the Variables and Webhook Form guides to the new
sections.

## Checklist

- [x] Update the Form documentation and review its behavior claims
against the implementation.
- [x] Add five matching light/dark screenshot pairs with descriptive alt
text.
- [x] Verify 21 local links and anchors, all 10 image references,
formatting, and the final diff.
- [x] Fix the CI database port conflict in browser shard 2.
- [x] Re-run the shard 3 email tests locally with the CI build and
schema artifacts: 4/4 passed in 61 seconds.
- [x] Use sanitized CI diagnostics to investigate the MCP submit
failures, then remove all temporary diagnostic code.
- [x] Pin the MCP test fixture to installed Playwright Chromium and run
E2E shards with two workers.
- [x] Review documentation impact of CI changes: no additional docs are
needed.
- [x] Confirm required CI checks pass.

The CI follow-up keeps test setup stable: Docker assigns free PostgreSQL
and PostgREST host ports, the MCP test fixture uses the installed
Playwright Chromium, and each E2E shard uses two workers. Local startup
passed with port 55434 occupied; the focused email tests passed 4/4. The
final clean CI run passed all ten E2E shards, Main, Visual regression,
Lint PR, and Check submodules. Temporary diagnostics have been removed.
The exact cause of the earlier browser startup failures was not proven.
These CI changes do not change Form behavior.
2026-10-24 15:01:02 +02:00
..