Public API support for creating and managing Views

We need public/API-key support for creating and managing Views.

Current problem:

• Views are a core organizational surface in Plane.
• They are how teams encode saved filters, work slices, operating cadences, and repeatable working contexts.
• But from an automation and integration perspective, Views appear to be missing from the supported public/API-key surface.

Requested capability:

1. List views for a project.
2. Create views via API.
3. Update views via API.
4. Delete or archive views via API.
5. Manage filters, grouping, sorting, visible fields, and layout/display settings through the API.
6. Support stable IDs/external IDs so automations can upsert views instead of duplicating them.

Why this matters:

• repo -> Plane automation often needs to create the working surface, not just the underlying work items
• company ops automations need recurring inbox, waiting-on, planning, or review views
• integrations need to keep views aligned with tags, states, modules, and workflow rules
• without API support, the data can be automated but the usable surface still has to be built manually in the UI

Real-world impact:
We were able to automate work items because the API-key surface supports them reliably, but views are still a manual gap. That means the structure exists in Plane, but the actual saved working contexts still require hand setup.

This would pair especially well with broader API coverage for Pages and other project surfaces. For many teams, automating Plane successfully means not only creating records, but also creating the views people actually work from.

Start at Plane's public/API-key surface for project Views and trace how existing API-supported work items are exposed. Define the scope for listing, creating, updating, deleting or archiving Views, including filters, grouping, sorting, display settings, and stable IDs. Done means these operations are available through the API and covered by appropriate tests.