Repository navigation
Conversation
* chore: remediate dependency advisories and set Firebase project - next / eslint-config-next 16.2.12 -> 16.3.8 (3 critical + 1 high advisory) - vitest / @vitest/coverage-v8 ^3.1.1 -> ^4.1.12 (drops vulnerable tinypool 1.x; no patched 1.x exists); migrate removed poolOptions.forks.singleFork in backend/vitest.config.ts to maxWorkers: 1, isolate: false - lockfile-only, in-range fixes: sharp, nanoid, source-map-js, js-yaml, brace-expansion, proxy-addr, @fastify/busboy, @grpc/grpc-js - scoped override @firebase/firestore>@grpc/grpc-js ^1.14.5 (Firebase pins ~1.9.0, which has no patched release) - ignore only GHSA-vfj7-8cjw-p6xm (braces: no patched version exists; lint-time path only), documented in README with a removal condition - commit the real Firebase project ID in .firebaserc - frontend/AGENTS.md: block regenerated by next 16.3 `next dev` * chore: make postcss override comment version-independent
Establishes the Firestore foundation for the SafeCall Incident Evidence & Action Log feature. - Add Incident and ActionLog models, owner-scoped queries and Zod validation. - Enforce verified-owner access and append-only action history through Firestore security rules. - Add composite index definitions and 71 Firestore emulator tests. - Harden authentication, session synchronisation and sign-out handling. - Add authentication and component regression tests. - Update documentation, patch Vite and correct pre-commit whitespace validation. Verification: 81 frontend, 5 backend and 71 Firestore security tests passed. GitHub CI passed. The incident seed script, dashboard, detail screen and deployment remain for subsequent phases.
Author
|
Opened against the upstream boilerplate repository by mistake. Closing and recreating against the correct project repository. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Implements Phase 3 of the SafeCall Incident Evidence & Action Log feature: controlled, administrator-only seeding of 50 fictional incidents.
Implementation
INC-001–INC-050) with 50 unique device IDs.Verification
Emulator smoke test
Safety and scope
Next phase
Phase 4 will implement the incident dashboard using the existing Incident schema and seeded dataset.