[Joyyyb]

Summary

Frontend: analytics annotations, data-quality queue, and offline pet availability

What was solved

#1138 — [Frontend] Add analytics chart annotations for policy changes

Add a frontend analytics chart annotation feature for admins to mark deployment/policy changes on time series, with backend-owned authorization/consent gating visibility, plus focused tests covering primary, empty/denied, and boundary/failure flows with accessible keyboard and screen-reader support.

Addressed:

• Changed: README.md
• Implement annotation capability in the appropriate petChain-Frontend route, component, hook, or client layer
• Allow admins to annotate a time series with deployment or policy change markers
• Show annotations only to authorized viewers, with authorization and consent decisions owned by the backend

#1139 — [Frontend] Add data-quality queue for incomplete records

Add a role-filtered data-quality queue in petChain-Frontend that surfaces records missing required fields and lets users navigate directly to the relevant correction form, with backend-owned authorization/consent, focused tests for primary/empty/denied/boundary flows, and accessible keyboard/screen-reader interaction.

Addressed:

• Changed: README.md
• Implement the data-quality queue in the appropriate petChain-Frontend route, component, hook, or client layer.
• Queue must be role-filtered and list records missing required fields.
• Users must be able to navigate directly from a queue item to the relevant correction form.

#1140 — [Frontend] Add user-managed offline availability for selected pets

Add a frontend feature that lets users pin selected pet summaries and recent records for offline availability, displays estimated storage cost, and allows clearing a single pet's cache without affecting other accounts. Implement in the petChain-Frontend layer (hook/component/client), keep authorization/consent decisions backend-owned, add focused tests for primary flow, empty/denied states, and boundary/failure cases, and ensure privacy-by-default plus keyboard and screen-reader accessibility.

Addressed:

• Changed: frontend/src/hooks/useOfflinePets.ts, frontend/src/components/OfflinePetsManager.tsx, frontend/src/lib/offlineCache.ts, frontend/src/hooks/tests/useOfflinePets.test.ts
• Implement offline availability for selected pets in the appropriate petChain-Frontend route, component, hook, or client layer
• Allow users to pin selected pet summaries and recent records for offline use
• Show the estimated storage cost of pinned offline data

Changes

• frontend/src/hooks/useOfflinePets.ts (create)
• frontend/src/lib/offlineCache.ts (create)
• README.md (modify)
• frontend/src/components/OfflinePetsManager.tsx (create)
• frontend/src/hooks/__tests__/useOfflinePets.test.ts (create)

Approach

1. [Frontend] Add analytics chart annotations for policy changes #1138 — [Frontend] Add analytics chart annotations for policy changes (Changed: README.md)
2. [Frontend] Add data-quality queue for incomplete records #1139 — [Frontend] Add data-quality queue for incomplete records (Changed: README.md)
3. [Frontend] Add user-managed offline availability for selected pets #1140 — [Frontend] Add user-managed offline availability for selected pets (Changed: frontend/src/hooks/useOfflinePets.ts, frontend/src/components/OfflinePetsManager.tsx, frontend/src/lib/offlineCache.ts, frontend/src/hooks/tests/useOfflinePets.test.ts)

Issues

Closes #1138
Closes #1139
Closes #1140

[drips-wave]

@Joyyyb Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits.

You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀

Learn more about application limits