Test helpdesk sheet sync

[ashley314]

Description

After #20 get's merged I want to run through a series of tests live to make sure of the following:

• 1) No charges in the GCP service account](https://console.cloud.google.com/iam-admin/serviceaccounts?project=jcsda-helpdesk)
• 2) GitHub Actions cost stays cheap
• 3) Accurate sheet syncing
• 4) Sheet edit permissions locked to service account and Phil
• 5) Auto-assignment by requesting org
• 6) Triage label application
• 7) Notes column preserved across re-syncs
• 8) Concurrency control under rapid edits
• 9) Demonstration for managers

Requirements

None

Acceptance Criteria (Definition of Done)

Satisfied there are not bugs and the spreadsheet tracking is working.

Dependencies

#20

[ashley314]

Live Test Plan: helpdesk-sheet-sync Feature

1. No charges in the GCP service account
   How to test: Open GCP Console > IAM & Admin > Service Accounts > jcsda-helpdesk-sheets. Confirm it has no project-level IAM roles — only the Sheet itself is shared with it. After running live tests, check GCP Billing > Reports filtered to the project and confirm $0.00 usage. The drive.file scope means it can only touch one explicitly shared file, not browse Drive broadly.

2. GitHub Actions cost stays cheap
   How to test: After running ~10 test issues, go to the repo's Settings > Actions > Usage. The sync workflow only fires on issue events (not pushes or PRs) and should complete in under 30 seconds each. Confirm total minutes consumed are trivial. Note: label and weekly-stats workflows add some minutes — check all three.

3. Accurate sheet syncing
   How to test: Open a test issue with every field filled in. Verify the Sheet row contains correct values for all columns across all four sections (Ticket Info, Requester, Work Tracking, Maintainer Notes). Then:
   Edit the issue body — confirm the row updates
   Close the issue — confirm status, closed_at, and time_to_close_days update
   Reopen it — confirm status reverts and closed_at clears
   Add/remove labels — confirm the labels column reflects the change

4. Sheet edit permissions locked to service account and Phil
   How to test: Open the Sheet as a non-privileged account (e.g., a personal Gmail). Attempt to edit a data cell and a header cell — both should be blocked. Confirm the Sheet sharing dialog shows only the service account email and Phil's account as editors; all others are view-only. Also confirm the frozen header rows (rows 1–2) are protected even for editors.

5. Auto-assignment by requesting org
   How to test: Open issues selecting different organizations from the dropdown (e.g., CADRE, NASA, MMM). Verify each issue gets automatically assigned to the correct liaison from org_assignee_map.json. Test the "Other" and empty-org fallback — both should assign to gibbsp. Confirm the assignees column in the Sheet matches.

6. Triage label application
   How to test: After opening an issue, have a maintainer fill in the "Maintainer classification" and "Root cause" fields via an edit. Confirm the triage: and root: labels are automatically applied. Then change those fields — confirm the old labels are removed and new ones added (no label accumulation).

7. Notes column preserved across re-syncs
   How to test: Manually type something in the notes column of a Sheet row. Then trigger a re-sync by editing the corresponding GitHub issue. Confirm the notes column value is unchanged after the sync (the script is explicitly designed to preserve this column).

8. Concurrency control under rapid edits
   How to test: Make several quick edits to the same issue in succession (e.g., change the title 3 times fast). Check the Actions run history — earlier runs should show as cancelled, with only the latest completing. Verify the Sheet reflects the final state, not an intermediate one.

9. Demonstration for managers
   How to test: Walk through the full lifecycle of one representative ticket in real time: submit → auto-assign → maintainer triages (fills classification fields) → labels appear → ticket closes → Sheet row finalizes with time-to-close. Have the Sheet visible on screen so stakeholders can see sync happen live. Focus on the Sheet's read-only view for non-editors as the primary interface managers will use.