Changelog
Dated platform milestones. SDK release notes come from Changesets.
2026-11-16: optional Cloudflare Access
- Infrastructure:
enable_access(defaulttrue; GitHub variableENABLE_ACCESS) turns the console's Cloudflare Access application and policy on or off. Off, OpenTofu sets neitherCF_ACCESS_TEAM_DOMAINnorCF_ACCESS_AUD, and the team domain and allowed emails are not required; with it on, a precondition requires both. Plan tests cover both cases. Access stays recommended: the console has no MFA of its own. - Docs: the manual deployment page is production-first, with staging optional, and explains the Access decision; the Cloudflare token table names the exact permissions.
2026-11-16: infrastructure as code with OpenTofu
- Infrastructure:
infra/opentofu/describes the whole deployment. Theplatformstack (one state per environment) creates the VPC, PostgreSQL (database, roles, pool, trusted sources, grants), Valkey (noeviction), the Spaces bucket (CORS, lifecycle, bucket-scoped key), the media Droplet (LiveKit, Caddy layer4 and Redis via cloud-init, replacing the interactive LiveKit generator), the scanner Droplet (cloud-init, private CA and certificate generated and renewed by OpenTofu), the App Platform app (API, migration job, owner bootstrap job, optional metrics worker, alerts), Cloudflare DNS, Access and Pages projects. Thezonestack holds zone-wide Cloudflare settings, per-environment origin-lock secrets and rules, the API cache bypass, thewwwredirect, DMARC and CAA. Every application secret is generated by OpenTofu; state and plans are encrypted and encryption is enforced. - CI/CD:
deploy.ymlbuilds and scans the API image (and the scanner image only when its sources change), runstofu applywith the digests, smoke-tests readiness and the origin lock, and publishes the console (now withVITE_DOCS_URL) and docs. Rollback is a Deploy run withapi_image_digest. Newinfra.ymlplans on pull requests and applies the zone stack. CI runspnpm infra:tofu(format, validate, mocked plan test). - Removed:
infra/digitalocean/(provision.sh,app.yaml,deploy.env.example, CORS and lifecycle JSON),infra/livekit/,infra/monitoring/{app-worker.yaml,prometheus.yml},scripts/{render-app-spec,rollback-app-spec}.mjsandscripts/provision.test.mjs.database-grants.sqlmoved toinfra/opentofu/platform/files/. - Docs: the deployment handbook is rewritten around OpenTofu: one-time bootstrap, configuration, GitHub environments, zone apply, first deploy, first sign-in, production, operations (changes, rollback, rotation, local runs, imports) and monitoring.
- Not verified: the stacks pass
tofu validateand a mocked plan test, but have not been applied to real DigitalOcean or Cloudflare accounts.
2026-11-16: step-by-step deployment handbook
- Docs:
docs/deployment/is now a numbered handbook for DigitalOcean Singapore and Cloudflare: architecture overview, twelve steps from workstation to CI/CD, production recommendations and status and gaps.deployment-guide.mdis replaced by the step pages; links are updated. Prerequisites gains a domain plan, tool install and a secrets worksheet; troubleshooting gains a deployment-problems table; the production checklist gains infrastructure checks. - Fixed: the checklist probed the scanner over plain HTTP; the scanner serves HTTPS only.
- Documented gaps:
provision.shdoes not create the scanner Droplet and firewall, a reserved IP, the Valkeynoevictionpolicy or VPC rules for the metrics ports; the spec renderer requires Access, origin lock and scanner values; the console CSP hard-codes thelynkoria.comAPI hosts;deploy.ymldoes not setVITE_DOCS_URL. No application code changed. - Not verified: commands were checked against the repository and
doctlhelp, not run against live accounts.
2026-11-16: docs site builds with Turbopack
- Docs site:
apps/docsdevandbuildno longer pass--webpack. Turbopack now resolves Tailwind's native dependencies on the current Node/pnpm toolchain, and the fumadocs-mdx webpack cache warnings are gone. The static export check still verifies 116 pages.
2026-11-14: lynkoria.com behind Cloudflare
- Security: the API supports an origin lock. With
CF_ORIGIN_SECRETset, every route except/health/*, and every socket upgrade, requires thex-lynkoria-origin-secretheader that a Cloudflare Transform Rule adds. Requests to the App Platform hostname that skip the edge get403. In production the API refuses to start if it trustscf-connecting-ipwithout the secret. - Breaking for operators: the App Platform template now uses
CLIENT_IP_HEADER=cf-connecting-ipand needs theCF_ORIGIN_SECRETsecret plus the matching Cloudflare rule (Cloudflare zone). - Infrastructure: staging hosts in
deploy.env.exampleare*-staging.lynkoria.com. The console CSPconnect-srcallows only the production and staging API origins. A new Cloudflare zone page covers the host map, Full (strict) TLS, cache bypass, WAF, Access, Email Routing, SPF/DMARC, CAA and DNSSEC. - Docs site: canonical URLs,
sitemap.xml,robots.txt(origin fromNEXT_PUBLIC_SITE_URL, defaulthttps://lynkoria.com, the apex that serves the landing page and docs) and/.well-known/security.txt.wwwredirects to the apex. - Not verified: no DNS records exist yet. INFRA-01 stays blocked until the zone is applied and the post-DNS checks pass.
2026-11-14: example apps redesign and dev scripts
- Examples:
apps/example-nextjsandapps/example-tanstack-startuse Tailwind CSS on the@lynkoria/brandtokens and component layer, like the console and playground. Both show connection status with a reconnect banner, room switching, chat with history, typing indicators and loading, empty and error states. The Next.js example adds a call panel with participant tiles, microphone, camera and screen-share controls and remote audio; the TanStack Start example adds a landing page, route pending and error components and a not-found page. No SDK changes. - Development:
pnpm devno longer starts the example apps. Start them withpnpm dev:example(Next.js on:3100, TanStack Start on:3200) next topnpm dev. - Tests: the Next.js Playwright suite reads message bodies instead of plain-text rows and checks that a published camera renders for the other participant. Not run locally in this change: the e2e harness could not start against the local test database (
role "realtime" does not exist); CI runs both suites.
2026-11-14: documentation and console upgrade
- Console: Overview dashboard (live activity, 30-day usage, activity chart, projects), Analytics page and project Analytics tab (hourly and daily ranges, comparison, local/UTC labels, chart/table, per-project totals), project Calls tab (live state, quota meter, calls and livestreams, participants, End call, Remove participant), webhook delivery history with backlog, Account page (own sessions and sign-in history), audit-log filters kept in the URL, team activity per organization. Every number links to its definition in the metrics catalog.
- API (additive):
/v1/admin/usage,/v1/admin/live,/v1/admin/projects/{id}/calls(+ detail, end, remove participant),/projects/{id}/live,/projects/{id}/webhook-events,/projects/{id}/usage/export,/v1/admin/me/sessions,/v1/admin/me/activity, audit-log filters; console roles and key scopes documented in OpenAPI. - Security: audit events are append-only in the database; refused console changes, sign-ins, exports and session ends are audited; usage exports are built and audited on the server. Light-theme contrast now meets WCAG AA.
- Data: hourly usage rollup (kept 35 days); migrations
0002–0005(audit triggers, console indexes, hourly table, index ordering). - Docs: generated HTTP and JavaScript SDK references, glossary and metrics catalog; environment variables checked against the config schemas; every guide code block type-checked (12 broken examples fixed); Mermaid diagrams and labelled support-status badges.
- Tests: console end-to-end and axe accessibility tests in CI; console API authorization, isolation and analytics tests.
2026-11-14: Android models ready for 1.0
- Breaking (Android, unpublished): public
lynkoria-coremodels are no longer data classes. They keep value equality andtoString, butcopy()and destructuring are gone, so later releases can add fields without breaking apps compiled against an earlier version. Use the constructor with named arguments instead ofcopy().
2026-11-14: TLS between the API and the scanner
- Security: the scanner serves HTTPS (TLS 1.3) with a certificate from a private CA, and the API trusts only that CA for scanner connections (
SCANNER_CA_CERT), so the scanner token and files no longer cross the VPC in clear text and an impostor cannot return verdicts. Production refuses a plain-HTTP scanner URL off-host.scripts/scanner-pki.shissues the CA and certificates; renewal reloads onSIGHUP. See ADR 023. - Upgrade: issue a certificate, set
SCANNER_TLS_DIRon the scanner host andSCANNER_URL=https://…plusSCANNER_CA_CERTon the API (deployment guide).
2026-11-14: release preparation (program phase 6)
- Release process: versioning policy and release checklist in package publishing; a clean-install check in CI installs the packed npm packages into a fresh project (ESM,
require(), TypeScript 5 strict types, server rendering, no zod in the client bundle). - Docs: Node.js 22.12+ for backends; stale native build statements corrected.
2026-11-14: cross-cutting tests (program phase 5)
- Reliability: restarting PostgreSQL no longer crashes the API (an idle pooled connection's termination was an unhandled error); database and network outages return a retryable 503 with
Retry-Afterinstead of 500. - Tests: browser network-drop recovery, fan-out across two API instances (100% delivery up to 999 receivers) and dependency failure drills, all recorded in load testing.
2026-11-14: native SDKs (program phase 4)
- Android: opt-in foreground service keeps calls running in the background (
OngoingCallNotification);lynkoria-corebinary-compatibility check. - iOS: Swift 6 language mode; acknowledgement timeouts now fire (they could hang); CallKit-answered calls keep LiveKit audio off until the session is activated.
- React Native: Expo config plugin.
- CI: Kotlin and Swift core integration tests run against a real API.
2026-11-13: JavaScript SDKs (program phase 3)
- Packages:
require()works on Node.js 22.12+; client bundles no longer include zod (messaging client about 17 KB gzip);@lynkoria/reactkeeps one connection under Strict Mode and is marked"use client";@lynkoria/serveradds notifications, recordings and retries for idempotent calls. - Frameworks: tested Next.js and TanStack examples with Playwright, a capability matrix and ADR 022.
2026-11-13: service boundaries (program phase 2)
- Services: new services page: responsibilities, data ownership, interfaces, authentication, timeouts and failure behavior per service.
- Reliability: webhook retries are jittered; Spaces requests have connect and inactivity timeouts; a test proves messaging keeps working while LiveKit is unreachable.
- Scanner: a consumer can hold several tokens, so its token rotates without downtime.
2026-11-13: infrastructure fixes (program phase 1)
Details in program status.
- Scanner: the production Compose
clamdnow starts under its hardened profile, and a one-shot signature update runs before clamd so it never serves the image's stale database;docker compose up --waitwaits for a scanner that can scan. - API: readiness probes time out after 2 s per dependency and report not ready while shutting down. Attachment scans carry the API request id into scanner logs (
@lynkoria/scanner-clientrequestId). - Monitoring: realtime connection-success metric, alerts for unreachable API/LiveKit/node targets, failing scans and rejected LiveKit webhooks, and runbooks for every alert.
- CI: automatic staging deploys skip with a notice until staging is provisioned.
- Shutdown:
SHUTDOWN_DRAIN_SECONDSkeeps an instance serving but not ready before it closes; App Platform's drain and grace periods are set explicitly. - Scaling: the API can run several instances; Socket.IO fan-out and disconnects cross instances through the Redis Streams adapter (ADR 021).
2026-11-13: dependency update (program phase 0)
Baseline, upgrades and validation are recorded in program status.
- Native builds: the Android SDK and sample compile for the first time (JitPack for LiveKit's
audioswitch, compileSdk 37, root plugin declarations so AGP uses Kotlin 2.4.21). The full Swift package, including LiveKit, builds for macOS after a type ambiguity fix; tools version 6.0. - Dependencies: Hono and its Node server (security fixes), AWS SDK, livekit-client 2.24.0, JUnit 6, Node 26.13.1 images, ClamAV 1.4.6 by digest (multi-arch image locally), Swift 6.4.2 CI image. Shared npm versions use a pnpm catalog.
pnpm auditis clean (SEC-09). - Found: the production scanner Compose
clamddoes not start under its capability limits; tracked as P1-01 in program status.
2026-11-13: platform audit
Full audit of code, security, documentation, deployment and styling (report).
- Security: attachments now upload to a quarantine key and only scanned bytes are served (SEC-01); the client IP comes from a single configured ingress header (
CLIENT_IP_HEADER, SEC-02); password hashing concurrency is capped (SEC-03); API CSP; HSTS and docs CSP on the static sites; the scanner image is scanned in CI; runtime-role statement timeouts in the grants script. - SDK: call sessions expose typed participants, connection quality and device selection;
useCallParticipantsin@lynkoria/react. - Styling: Tailwind v4 across console, playground and docs with a shared brand theme; about 1,800 lines of CSS removed (CSS audit).
- Docs: reorganized into architecture, security, deployment, operations, decisions, implementation and reviews; complete environment reference; prerequisites, production and security checklists; findings register.
- Breaking for operators:
/docs/platform/*URLs moved. SetCLIENT_IP_HEADERif your ingress is not App Platform. Attachment uploads in flight during the deploy must be retried.
2026-11-13: platform extension
Native Android and iOS SDK cores and media layers (preview), React Native SDK, push delivery (FCM/APNs) and incoming-call support, recording lifecycle through LiveKit Egress (preview), independent ClamAV malware scanner with attachment gating, console password sign-in with CLI-provisioned accounts, an Operations view in the console, and API, fan-out and livestream load tests. Console users now need password accounts (pnpm admin:user create); Cloudflare Access became an optional extra layer.
2026-11-12: v1 implementation review
v1 control plane, messaging, presence, calls, livestreams, webhooks, console and deployment tooling reviewed against the implementation plan. Fixes included organization-scoped administration, PATCH contracts that no longer reset omitted settings, token and session revalidation, non-cacheable secret responses, HTTPS-only approved webhook destinations, fail-closed rate limits, messaging locking and pagination fixes, retention tombstones, presence lease races, idempotent call lifecycle and usage, SDK reconnect and replay fixes, separate database roles, and explicit OpenTelemetry instrumentation (review).