A complete walkthrough of the auth.coditect.ai portal as deployed on March 14, 2026 — frontend v1.34.0-wpp-header running on GKE. Includes 15 annotated screenshots, architecture documentation (ADR/SDD/TDD-261), and the development timeline across concurrent work sessions.
15
Screenshots
3
Architecture Docs
3
Dev Sessions
ADR-261
Design Decision
Production Status — 2026-03-14
Backend API — v1.43.1 · 4/4 pods
Auth Portal — v1.34.0-wpp-header · 2/2 pods
Landing Page — Cloudflare Pages · live
Migrations — 4 applied · complete
Dashboard Gallery
15 screenshots from auth.coditect.ai captured on 2026-03-14 during the v1.34.0-wpp-header deployment walkthrough. Click any image to view full size.
ADR-261v1.4.0 · 2026-03-14Accepted
Landing Page to Auth Portal Full Integration
The coditect.ai landing page, auth.coditect.ai portal, and api.coditect.ai backend were three isolated systems. This ADR establishes the end-to-end pipeline connecting survey submission to automatic user registration, welcome communications, magic-link login, and a personalized dashboard backed by real project and payment data.
Decision Summary
Prior to this decision, three production systems operated independently with no integration between them. The disconnection created three failure modes: a broken conversion funnel, no real project data in the dashboard, and silent Stripe payments that never activated user projects.
The decision implements an end-to-end pipeline that closes all three gaps with the minimum set of additions to the existing Django + React stack.
Core Decision
Description
1. Unified Survey-Register
Single public endpoint creates User + Tenant, links Lead, generates 48-hour magic link token, returns JWTs. Idempotent on email.
2. Magic Link Auth
Passwordless first-login via single-use token. Sets email_verified=True. Redirects to /home.
3. Lead-to-User FK
Nullable FK enables dashboard to query real LeadProject records. SET_NULL on delete preserves history.
4. Staged Communications
Welcome email + SMS created as LeadActivity records, delivered out-of-band. Keeps response <500ms.
5. Client-Side Personalization
localStorage-based engine. No server round-trip. Hero/CTA variants for returning visitors.
6. Token Auto-Login
Auth portal checks ?token= on load. Auto-verifies and redirects without user interaction.
The auth portal Layout component must implement the WPP-standard header and sidebar pattern derived from wpp-viewer/viewer.jsx and wpp-viewer/components/Sidebar.jsx.
Header Element (left → right)
Implementation
Sidebar toggle
PanelLeftClose / PanelLeft icon — keyboard: Cmd+B
Category expand/collapse all
Folder / ChevronsUpDown — visible only when sidebar is open
Logo + title + subtitle
h-9 w-9 rounded-lg logo · "CODITECT" · "AI Infrastructure Platform"
Right side
Search (/, Ctrl+K), Pricing, Cart, Dark mode toggle, Auth controls
UUID-Based Dashboard URLs design decision + Frontend v1.30–v1.31 update record
v1.1.0
2026-03-14
Deployment Record — GKE topology, operational issues, E2E verification
SDD-261v1.5.0 · 2026-03-14Accepted
Software Design Document — Landing Page to Auth Portal Integration
System design covering component architecture, data flow, sequence diagrams for the three primary flows (survey-register, magic-link login, post-payment activation), security model, data model changes, and the WPP-Standard Layout component specification.
The Layout component at src/components/layout.tsx implements the WPP-standard pattern. Pattern source: wpp-viewer/viewer.jsx + wpp-viewer/components/Sidebar.jsx.
Deployed: v1.34.0-wpp-header, commit 3dbf0cd. ADR-261 D-8 design decision documents this pattern as the required standard for all CODITECT portal UIs.
TDD-261v1.5.0 · 2026-03-14Accepted
Technical Design Document — Landing Page to Auth Portal Integration
API contracts for all new and modified endpoints, migration execution order, rollback strategy, 20-section test plan, deployment sequence, error handling, and performance budgets.
Test Plan Overview
The test plan covers 20 named test sections (4.1–4.20), organized across functional areas:
Section
Area
Goal
4.1
E2E Pipeline
Survey form → authenticated dashboard with real project data
4.2
Migration Safety
Staging database migration run — 3 migrations in strict order
4.3
Stripe Webhook
checkout.session.completed → LeadProject pilot activation
4.4
Idempotency
Duplicate email submission does not create duplicate user
4.5
Personalization
localStorage state persists across sessions; hero/CTA variants
Use django (not django-backend), celery (not celery-worker)
Docker builds on Apple Silicon produce arm64
ImagePullBackOff on GKE amd64 nodes
Always use docker buildx --platform linux/amd64
PascalCase imports vs kebab-case filenames
Vite build fails on Linux (case-sensitive fs)
Fixed 63 source files + Dockerfile symlink script
Stripe checkout → LeadProject activation
Not yet E2E tested with real Stripe
Pending C.18.4.2
Session Log2026-03-14Complete
Session Log — 2026-03-14
Machine: d3d3a316-09c6-8f41-4a3f-d93e422d199c — 11 entries across concurrent sessions ec231c2b, a774f233, and e3b63d81 covering the full ADR-261 deployment pipeline, CLI skill creation, and WPP-standard layout implementation.
00:37 UTC
ADR-261 TRACK Subtask Completeness Audit + Gap Closure
Audited all TRACK files for ADR-261 subtask completeness. Found 15 missing subtasks covering backend deployment to GKE, E2E verification, and architecture documentation. Created C.18 (8 subtasks), F.14 (3 subtasks — all complete), and B.19.2 (1 subtask). All implementation code complete; C.18 deployment tasks are the remaining work.
Created /coditect-register skill (v2.0) with 8-step interactive flow — name/email collection, consent summary, API registration, and Playwright --dashboard browser automation. Created /license-activate skill (v1.0). Updated install mechanism analysis to v2.0. Six architecture documents updated. Live-tested and found Path("") truthy bug in cloud_registration.py — fixed. Registration API call reaches api.coditect.ai but returns 404 (endpoint not yet deployed).
a774f233C.19N.12
03:28 UTC
C.18 Deployment Pipeline Complete: Backend v1.43.1 + Frontend v1.29.0 Live on GKE
Deployed ADR-261 integration to GKE production. Applied 4 Django migrations via kubectl exec. Fixed TenantMembership ImportError CrashLoopBackOff (wrong module) → rebuilt as v1.43.1. Fixed 63 PascalCase import mismatches. First Docker image was arm64 → rebuilt with --platform linux/amd64. E2E verification passed: survey-register creates user + JWT + magic link, idempotency confirmed. Both frontend pods 1/1 Ready.
ec231c2bC.18.1–4B.19.2
03:45 UTC
ADR/SDD/TDD-261 Updated with Deployment Record + TRACK Tasks Completed
Updated all three architecture documents to reflect actual deployment state: corrected topology from Cloud Run to GKE, added deployment record with 4 operational issues and workarounds. Marked 7/8 TRACK-C C.18 tasks complete.
ec231c2bC.18F.14
03:51 UTC
Session Overlap Analysis: Two Active 2026-03-14 Sessions
Analyzed overlap between concurrent sessions. a774f233 focused on CLI skills and architecture docs. e3b63d81 focused on UI/frontend unification. Low overlap — complementary scopes across different layers (CLI vs frontend). No file lock conflicts.
a774f233C.19
04:01 UTC
Registration Endpoint Live but Returns 500
Backend v1.43.1 unblocked the /coditect-register endpoint (was 404, now 500). Three likely causes: Tenant.slug uniqueness conflict, missing Installation model migration columns, or send_mail config. Plan: kubectl exec into backend pod to step through registration logic in Django shell.
Full /coditect-register flow working end-to-end. Registration returns 201, installation ID 68c07b5a, user created. Django email silently failed — sent welcome email via Google Workspace MCP instead. Login token saved to registration.json. Auto-fills email + login_token in Playwright for seamless dashboard access. Each user gets unique URL at auth.coditect.ai/installations/{uuid}. Cross-session coordination pattern proven.
a774f233C.19
04:41 UTC
Multi-Account Design Gap + ADR/SDD/TDD Email+AutoLogin Updates
Identified multi-account design gap — registration.json is single-account (last-write-wins). Proposed per-email files at licensing/registrations/{email}.json with active-account.json pointer. Updated ADR-261 (Django SMTP + MCP workaround), SDD-261 Section 7 (registration.json schema, --dashboard auto-login flow), TDD-261 (revised 4.10, new 4.10a, 4.10b).
Replaced the auth portal's non-standard flat nav sidebar with the WPP-standard layout pattern. PanelLeftClose/PanelLeft toggle in header. Folder/ChevronsUpDown expand/collapse all. Collapsible category tree with ChevronRight/ChevronDown headers. Mobile overlay with backdrop dismiss. Keyboard shortcuts: Cmd+B, /, Ctrl+K. Frontend v1.34.0-wpp-header deployed (commit 3dbf0cd). ADR/SDD/TDD-261 updated with D-8, component spec, and test plan section 4.20.
e3b63d81B.20v1.34.0-wpp-header
Session ec231c2b2026-03-12 – 2026-03-14Active
Working Session — ec231c2b-b0d0-4f26-bad5-99f212d66294
Primary deployment session for ADR-261. Started 2026-03-12T14:41Z. Covered TRACK audit, full GKE deployment pipeline, architecture doc updates, ADR-262 implementation, and WPP layout migration.
Completed Tasks
Fix /installations* route guard redirect bug — deployed in v1.34.0
Fix header/sidebar regression — v1.34.0-wpp-header (commit 3dbf0cd). Replaced flat nav with WPP-standard layout: PanelLeftClose/PanelLeft toggle, Folder/ChevronsUpDown expand/collapse, collapsible category tree with ChevronRight/ChevronDown, mobile overlay, Cmd+B / Ctrl+K shortcuts. ADR/SDD/TDD-261 updated with D-8.
Path("") truthy bypassed get_user_data_dir() fallback — fixed in cloud_registration.py
Synced to protected install
coditect-core 6a326023, rollout-master 26e33c5e
Cross-session coordination pattern: Sessions ec231c2b and a774f233 coordinated across working-session.md notes. a774f233 identified blockers (404→500), wrote to ec231c2b's working session file, ec231c2b fixed and wrote back, a774f233 verified and completed the flow. 12+ round-trips proved the pattern production-grade.
Remaining Items
Verify browser-screenshot-on-error.py PostToolUse hook no longer errors
Consider adding session-start hook that validates ~/.coditect symlink integrity
About CODITECT
AI Infrastructure Platform — building the connective tissue for AI-assisted software development.
What Is CODITECT?
CODITECT is an AI infrastructure platform built by AZ1.AI INC. It provides a structured environment for AI-assisted software development through a framework of agents, commands, skills, scripts, and hooks — installed locally and connected to a cloud control plane.
The platform is distributed as a CLI tool installable on macOS, Linux, and Docker/Linux environments. After installation, users register at auth.coditect.ai to access their project dashboard, manage installations, and track development progress.
Platform Components
URL
Purpose
Technology
coditect.ai
Marketing landing page with 8-step qualification survey
This site is a standalone WPP-style documentation and gallery site built to showcase the auth.coditect.ai portal as deployed on March 14, 2026. It uses the same WPP-standard layout pattern (D-8 from ADR-261) applied in the auth portal itself — collapsible category sidebar, PanelLeft toggle, dark/light mode, keyboard navigation.
Detail
Value
Build date
2026-03-14
Portal version captured
v1.34.0-wpp-header (commit 3dbf0cd)
Screenshots
15 × PNG, auth.coditect.ai, 2026-03-14 01:54–02:26 UTC