דילוג לתוכן
מרכז התיעוד
לאתר LinkNodes Energy
LinkNodesENERGYתיעוד

טוענים את החיפוש…

    חיפוש גם בתוך המאמרים ↑ ↓ לניווט Esc לסגירה

    לאתר החברה

    שחרורים ואימות

    אימות ארכיטקטורה ונתונים

    בדיקות הקטלוגים, המילון והספריות במועד השחרור.

    בעמוד הזה

    Verified 2026-11-08 (Asia/Jerusalem). This is foundation evidence, not a production readiness certificate.

    Database#

    The user selected existing Supabase project dxeijkkmueuhvynvsgch (ev1, organization digitalops, Singapore). Both public and private application schemas were empty before applying the existing reviewed SQL files.

    Local migrationApplied cloud versionCloud migration name
    0001_ev1.sql20261107223903legacy_driver_foundation
    20261107211048_platform_foundation.sql20261107223913platform_foundation

    All 23 application tables have RLS enabled. The security advisor returned five INFO findings for private tables with RLS and no policies. These deliberately deny direct client access; SQL privilege checks also confirmed no SELECT/INSERT grants to anon/authenticated on those five tables. Authenticated clients cannot directly insert invoices, payments or charging sessions. No other project was modified.

    The isolated PostgreSQL suite passed 26 checks, including tenant isolation and role restrictions. These locally injected claims are separate from real cloud JWT verification.

    Identity#

    The existing Clerk app now has a production instance for product.linknodesenergy.com. DNS, TLS and sending-domain verification all report complete. Session tokens include role=authenticated. Native Clerk organization selection and generic Clerk billing are disabled because membership lives in the application database and a payment provider has not been selected. Google sign-in is disabled in production until production OAuth credentials are configured.

    The initial Supabase integration used the product hostname instead of the Clerk issuer hostname and returned HTTP 401 / PGRST301. The user corrected it to clerk.product.linknodesenergy.com. A subsequent real production sign-in passed 18 checks across two users: matching identity/role/issuer, tenant creation and own-tenant reads, cross-tenant read isolation, cross-tenant insert denial, and denial of forged invoices. The deployed product then passed 30 checks with real sessions, including server context, tenant creation through the app API, authenticated onboarding UI, own-workspace reads, cross-tenant API denial and direct database restrictions. Unauthenticated app context returns 401.

    Production-only Clerk and public Supabase configuration is deployed to the product project after the successful JWT checks. The demonstration flows remain explicitly labelled and separate. Privileged invitation acceptance still requires a server-only Supabase secret. Do not bypass JWT verification or RLS to unblock that step.

    Code and browser checks#

    • 90 unit tests passed, including 10 new schema/catalog/contract checks.
    • ESLint and the production Next.js build passed.
    • Nine distinct browser tests passed across the Engineering and Product System libraries. A test initially expected 11 vehicle columns; the migration has 10, and the corrected test passed.
    • Desktop and 390px screenshots were inspected; automated checks also cover 320px layouts, search, filters, deep links, relationship navigation, JSON downloads and contract validation.
    • CI regenerates versioned catalogs and handbooks and rejects source/export drift.

    Repeatable cloud verification#

    scripts/check-cloud-identity.mjs is opt-in and targets this project's production identity and database. It requires exactly two explicitly prepared temporary Clerk user IDs and creates QA tenants only. Run with private files outside the repository:

    LNE_QA_CONFIG=/private/clerk-config.json \
    LNE_QA_USERS=/private/qa-user-ids.json \
    LNE_QA_FIXTURES=/private/qa-tenant-fixtures.json \
    node scripts/check-cloud-identity.mjs
    

    The config contains secret and publishable; the users file is an array of two IDs. Neither credentials, sign-in tickets nor JWTs are logged. Fixture IDs accumulate across runs so failures cannot lose the cleanup inventory. Set LNE_QA_API=1 only after app identity is enabled to also test server context and cross-tenant API denial. Explicit cleanup of recorded QA tenants and test users is required even after failures.

    Remaining release gates#

    Invitation onboarding and live revocation lifecycle checks; charging-network and payment-provider selection and sandbox adapters; durable processing and reconciliation; real financial ledger; analytics backed by reconciled facts; monitoring, rate limiting, backup restore exercise and approved operational targets. The public libraries distinguish implemented foundations from these planned capabilities.

    Temporary fixture cleanup#

    Two temporary Clerk users were deleted after revoking seven active test sessions. All four temporary QA tenants, their policies, memberships and audit rows were removed. The first transactional cleanup attempt rolled back because the database disallows session_replication_role; no permissions were expanded. A scoped operational migration then removed the fixtures by their verified names and creation window, under an exclusive tenant-table lock. It temporarily suppressed only the tenant deletion audit trigger (which would recreate a foreign-key reference to the deleted fixture), re-enabled it before commit, and retained all foreign-key and RLS checks. Post-cleanup verification confirmed zero QA tenants, the audit trigger enabled, and RLS on all 23 tables. This operation is in cloud migration history as cleanup_temporary_identity_verification; it introduces no persistent schema change and is not a schema migration to replay in new environments.

    Production browser checks exposed Vercel overriding suggested download filenames; explicit Content-Disposition headers now make the exported filenames consistent. The mobile test now scopes its heading to the loaded library rather than matching the temporary Next.js loading heading.

    Final release#

    Runtime source 3ad255b is deployed as [operational-id-redacted] on https://product.linknodesenergy.com. Vercel reports READY and successful domain assignment. The six passing production browser cases plus all three corrected reruns give nine distinct passing cases on the deployed product; the affected system unit suite also passed again (10/10). Desktop sign-in rendered without script errors. HTTPS checks without bypassing certificate validation returned 200 for both new libraries, 401 for unsigned platform context, and 404 for library paths on the company website and admin domains. The final download responses carry the intended branded filenames.

    The cloud-only fixture cleanup history version is 20261107231143. Database audit trigger verification returned O (enabled); no QA tenants remain.

    The final sign-in form was also verified on the live product at 390px and 320px: visible controls, no horizontal overflow, no script errors. The grid and Clerk card widths were corrected after this check exposed the initial fixed-width layout.