Add visible fields to project views (#2988)

* Add visible fields to project views

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>

Copilot-Session: 1421a5d5-fdce-4c0e-9528-56d555ec30d4

* Fail fast and surface orphaned views on project view writes

Reject roadmap layouts before enumerating project fields in both the
create and update paths, and verify view ownership before resolving
visible fields on update, so rejected requests no longer pay for a
paginated field listing.

Skip the follow-up filter mutation when the filter is explicitly null,
since a new view has no filter to clear, and include the created view ID
when cleanup after a failed filter mutation also fails so the caller can
recover the orphaned view.

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>

---------

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Copilot-Session: 1421a5d5-fdce-4c0e-9528-56d555ec30d4

Author: zwick

README.md

@@ -1141,8 +1141,8 @@ The following sets of tools are available:
   - `title`: The project title. Required for 'create_project' method. (string, optional)
   - `updated_field`: The field/value to apply, using {"id": 123, "value": ...} or {"name": "Status", "value": ...}; null clears the field. Required for 'update_project_item' and 'update_project_items', where one top-level field/value applies to every item in a batch. For 'update_project_item' SINGLE_SELECT fields, the name form accepts option names; the ID form expects an option ID. (object, optional)
   - `view_id`: Project view node ID for update or delete; must belong to owner/project_number. (string, optional)
-  - `visible_field_names`: Field names for table or board creation; mutually exclusive with visible_fields. (string[], optional)
-  - `visible_fields`: Field database IDs for table or board creation; mutually exclusive with visible_field_names. (string[], optional)
+  - `visible_field_names`: Ordered project field names to show on create or replace on update; omit on update to preserve, or pass [] to reset. Mutually exclusive with visible_fields. Roadmap accepts only []. (string[], optional)
+  - `visible_fields`: Ordered project field database IDs to show on create or replace on update; omit on update to preserve, or pass [] to reset. Mutually exclusive with visible_field_names. Roadmap accepts only []. (string[], optional)
 
 </details>
 

pkg/github/__toolsnaps__/projects_write.snap

@@ -257,14 +257,14 @@
         "type": "string"
       },
       "visible_field_names": {
-        "description": "Field names for table or board creation; mutually exclusive with visible_fields.",
+        "description": "Ordered project field names to show on create or replace on update; omit on update to preserve, or pass [] to reset. Mutually exclusive with visible_fields. Roadmap accepts only [].",
         "items": {
           "type": "string"
         },
         "type": "array"
       },
       "visible_fields": {
-        "description": "Field database IDs for table or board creation; mutually exclusive with visible_field_names.",
+        "description": "Ordered project field database IDs to show on create or replace on update; omit on update to preserve, or pass [] to reset. Mutually exclusive with visible_field_names. Roadmap accepts only [].",
         "items": {
           "type": "string"
         },

pkg/github/minimal_types.go

@@ -439,7 +439,7 @@ type MinimalProjectView struct {
 	Name          string  `json:"name"`
 	Layout        string  `json:"layout"`
 	Filter        string  `json:"filter"`
-	VisibleFields []int64 `json:"visible_fields,omitempty"`
+	VisibleFields []int64 `json:"visible_fields"`
 }
 
 type MinimalProjectItem struct {