Remaining tasks
Engineering work that is not done, in priority order, with next steps and dependencies.
Last updated: 2026-11-13. Items that wait on something outside the repository are in blockers. IDs match the tracker.
P0: before production traffic
| ID | Task | Next steps | Depends on |
|---|---|---|---|
| SEC-07 | Apply runtime-role timeouts | Applied automatically by OpenTofu on each environment's first deploy; confirm SHOW statement_timeout as lynkoria_app | Database access |
| SEC-02 | Confirm the client-IP header cannot be spoofed | On staging, send a request with a fake DO-Connecting-IP; the console sign-in audit row must show the real IP | Staging |
| LOAD-01, OPS-01 | Staging load, restore and rollback drills | See blockers | Staging |
P1: launch quality
| ID | Task | Next steps | Depends on |
|---|---|---|---|
| SEC-06 | Confirm the scanner image passes the CI Trivy gate | Push; fix any fixable high/critical findings in the scanner base like the API's zlib pin | CI |
| TEST-01 | Clean-project installs | Install each npm package, the Maven artifacts and the Swift package into fresh sample projects and run the quickstart | Built artifacts |
| NAT-01..03 | Native SDKs | Compile and test once toolchains exist; add Android instrumentation tests and React Native native-module tests | Blockers |
| Docs | Keep docs current | Update this tracker, platform status and the changelog with every change | none |
P2: improvements
| ID | Task | Next steps | Depends on |
|---|---|---|---|
| SEC-08 | Pin the ClamAV image digest | Review clamav/clamav:1.4, record its digest in both Compose files | Operator review |
| SEC-11 | Tighten console CSP | Template connect-src with the API origin at build time or per Pages project | none |
| FEAT-01 | Waiting rooms | If a product needs admission control: add a waiting participant state, a host approval endpoint and a socket event; until then, product backends gate join-token issuance | Product requirement |
| FEAT-02 | Offline send queue | Persist unsent messages in the client SDK (IndexedDB / platform storage) and replay on reconnect with the same clientMessageId | Product requirement |
| ARCH-02 | HLS/CDN for large audiences | Egress HLS to the bucket, short-lived signed CDN URLs, viewer analytics | REC-01 |
| DEP-01 | Single-host Compose deployment | Production-shaped Compose (API, migrate job, scanner, clamd, Caddy) for hosts outside DigitalOcean, with external PostgreSQL/Redis/S3/LiveKit; validate with docker compose config and a TLS staging run | Decision that a second deployment target is supported |
| TEST-02 | Local Egress test | Add livekit/egress to the local Compose profile and an integration test that records a short room into local storage | none |
| Load | More scenarios | Presence churn, group-call media, network interruption, scanner and push throughput (load testing) | Staging for meaningful numbers |
AR effects
Filters, masks and beauty effects are client-side processing of the local camera track before it is published; the server only forwards tracks. The supported approach (ADR 017): web apps attach a LiveKit track processor (@livekit/track-processors for background blur/replacement, or a MediaPipe-based processor for face effects) to the camera track from session.room.localParticipant; native apps use the platform equivalents in the LiveKit Android/iOS SDKs. Lynkoria adds no server component, and effects work with E2EE. A first-class session.setVideoProcessor() wrapper is worth adding only when a product commits to effects.