Chore: [AEA-5673] - Vector clock removal

[originalphil]

Summary

• Routine Change

Details

Replace vectorClock attribute with inDatastore attribute to indicate existence of an item in the datastore.

[github-actions]

This PR is linked to a ticket in an NHS Digital JIRA Project. Here's a handy link to the ticket:

AEA-5673

[Copilot]

Pull request overview

This PR removes the legacy vectorClock attribute from update/logging flows and replaces it with an inDatastore boolean intended to represent whether a record already exists in the datastore, aligning interactions and tests with the new flag.

Changes:

• Replaced vectorClock with inDatastore across interaction logging and record/document “to store” payloads.
• Updated DynamoDB datastore record-return shape to include inDatastore: True instead of a placeholder vector clock.
• Updated unit tests to assert against the new inDatastore field.

Reviewed changes

Copilot reviewed 6 out of 6 changed files in this pull request and generated 6 comments.

Show a summary per file

File	Description
tests/interactions/updates_test.py	Updates smart-update tests to pass inDatastore instead of vectorClock.
tests/common/dynamodb_datastore_test.py	Adjusts expected returned-record shape to include inDatastore.
src/eps_spine_shared/interactions/updates.py	Updates EPS0126a/EPS0127a log payloads to emit inDatastore.
src/eps_spine_shared/interactions/create_prescription.py	Updates EPS0139 log payload to emit inDatastore.
src/eps_spine_shared/interactions/common.py	Replaces vectorClock usage with inDatastore for store-prep and chooses blind vs smart update using inDatastore.
src/eps_spine_shared/common/dynamodb_datastore.py	Returns records with inDatastore: True instead of a synthetic vector clock.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.