Lock anonymized movements in movement list

[rzueger]

Summary

• Treat anonymized movement records as locked in the movement list
• Admins see a lock icon and cannot edit/delete anonymized records
• PII has been stripped by the retention job, making edits pointless and deletes would lose aggregate data

Test plan

• Verify anonymized movements show lock icon and reduced opacity
• Verify edit/delete/customs actions are hidden for anonymized movements
• Verify non-anonymized movements are unaffected

https://claude.ai/code/session_01KHZDkEfyznUCcoGCWrGdsY

[rzueger]

@claude build is failing

[claude]

Claude finished @rzueger's task in 6m 0s —— View job

---

Build failure fixed

• Gather context
• Check CI status and logs
• Identify the build error
• Fix the issue
• Push fix

Root cause: Two Cypress specs were failing with AssertionError: expected 2 to equal 1:

• movements/arrival/create_arrival_spec.js
• movements/departure/create_departure_spec.js

Both specs assumed an empty Firebase test database by checking Object.keys(departures).length === 1 after creating one movement. This creates a self-perpetuating failure: when the assertion throws, the key variable (createdDepartureKey / createdArrivalKey) is never assigned, so the after() cleanup is skipped, leaving a stranded record in the shared DB. The next run finds one pre-existing record, fails the same assertion, leaves another record, and so on.

Fix (commit bc6f275): Capture the set of existing keys in before() before filling the form, then diff against the post-submission snapshot to find the newly created key. This tolerates any pre-existing records and correctly identifies the one record created by the test.
|

[rzueger]

@claude remove the fix commit again from the branch. the cypress failures were caused by wrong test data in the database.

[claude]

Claude finished @rzueger's task in 1m 26s —— View job

---

Fix commit reverted

• Gather context
• Remove commit bc6f275 from branch
• Push to remote

Reverted the changes from bc6f275 via commit a90389a. Both Cypress specs are back to their original form (simple expect(keys.length).to.equal(1) assertions).