@knowcode/doc-builder 1.8.2 → 1.8.3

package/html/private/supabase-auth-integration-plan.html

@@ -98,8 +98,8 @@
     "name": "Knowcode Ltd",
     "url": "https://knowcode.tech"
   },
-  "datePublished": "2025-07-26T10:38:42.032Z",
-  "dateModified": "2025-07-26T10:38:42.032Z",
+  "datePublished": "2025-07-26T11:11:45.927Z",
+  "dateModified": "2025-07-26T11:11:45.927Z",
   "mainEntityOfPage": {
     "@type": "WebPage",
     "@id": "https://doc-builder-delta.vercel.app/private/supabase-auth-integration-plan.html"
@@ -138,7 +138,7 @@
             
             <div class="header-actions">
                 <div class="deployment-info">
-                    <span class="deployment-date" title="Built with doc-builder v1.8.1">Last updated: Jul 26, 2025, 10:38 AM UTC</span>
+                    <span class="deployment-date" title="Built with doc-builder v1.8.2">Last updated: Jul 26, 2025, 11:11 AM UTC</span>
                 </div>
                 
                 
@@ -287,77 +287,40 @@
     style RLS fill:#f87171</div>
     </div>
 <h2>Database Schema</h2>
-<h3>Core Tables</h3>
-<pre><code class="language-sql">-- Organizations table
-CREATE TABLE organizations (
-    id UUID PRIMARY KEY DEFAULT gen_random_uuid(),
-    name TEXT NOT NULL,
-    slug TEXT UNIQUE NOT NULL,
-    created_at TIMESTAMPTZ DEFAULT NOW(),
-    settings JSONB DEFAULT &#39;{}&#39;::jsonb
-);
-
--- Documentation sites table
-CREATE TABLE doc_sites (
-    id UUID PRIMARY KEY DEFAULT gen_random_uuid(),
-    org_id UUID REFERENCES organizations(id),
-    name TEXT NOT NULL,
-    domain TEXT UNIQUE NOT NULL,
-    config JSONB DEFAULT &#39;{}&#39;::jsonb,
+<h3>Simplified Domain-Based Design</h3>
+<pre><code class="language-sql">-- Single table for user access control
+CREATE TABLE docbuilder_access (
+    user_id UUID REFERENCES auth.users(id) ON DELETE CASCADE,
+    domain TEXT NOT NULL,
     created_at TIMESTAMPTZ DEFAULT NOW(),
-    is_active BOOLEAN DEFAULT true
+    PRIMARY KEY (user_id, domain)
 );
 
--- User access table (many-to-many)
-CREATE TABLE user_site_access (
-    user_id UUID REFERENCES auth.users(id),
-    site_id UUID REFERENCES doc_sites(id),
-    role TEXT NOT NULL DEFAULT &#39;viewer&#39;,
-    granted_at TIMESTAMPTZ DEFAULT NOW(),
-    granted_by UUID REFERENCES auth.users(id),
-    expires_at TIMESTAMPTZ,
-    PRIMARY KEY (user_id, site_id)
-);
+-- Create index for faster lookups
+CREATE INDEX idx_docbuilder_access_domain ON docbuilder_access(domain);
 
--- Access logs for audit trail
+-- Optional: Access logs for audit trail
 CREATE TABLE access_logs (
     id UUID PRIMARY KEY DEFAULT gen_random_uuid(),
     user_id UUID REFERENCES auth.users(id),
-    site_id UUID REFERENCES doc_sites(id),
+    domain TEXT NOT NULL,
     action TEXT NOT NULL,
     metadata JSONB DEFAULT &#39;{}&#39;::jsonb,
     ip_address INET,
     user_agent TEXT,
     created_at TIMESTAMPTZ DEFAULT NOW()
 );
-
--- Invitation links
-CREATE TABLE invitations (
-    id UUID PRIMARY KEY DEFAULT gen_random_uuid(),
-    site_id UUID REFERENCES doc_sites(id),
-    email TEXT NOT NULL,
-    role TEXT NOT NULL DEFAULT &#39;viewer&#39;,
-    token TEXT UNIQUE NOT NULL,
-    created_by UUID REFERENCES auth.users(id),
-    created_at TIMESTAMPTZ DEFAULT NOW(),
-    expires_at TIMESTAMPTZ NOT NULL,
-    claimed_at TIMESTAMPTZ,
-    claimed_by UUID REFERENCES auth.users(id)
-);
 </code></pre>
 <h3>Row Level Security Policies</h3>
-<pre><code class="language-sql">-- Users can only see sites they have access to
-CREATE POLICY &quot;Users can view accessible sites&quot; ON doc_sites
-    FOR SELECT USING (
-        EXISTS (
-            SELECT 1 FROM user_site_access
-            WHERE site_id = doc_sites.id
-            AND user_id = auth.uid()
-            AND (expires_at IS NULL OR expires_at &gt; NOW())
-        )
-    );
+<pre><code class="language-sql">-- Enable RLS on tables
+ALTER TABLE docbuilder_access ENABLE ROW LEVEL SECURITY;
+ALTER TABLE access_logs ENABLE ROW LEVEL SECURITY;
 
--- Access logs are append-only
+-- Users can only see their own access records
+CREATE POLICY &quot;Users see own access&quot; ON docbuilder_access
+    FOR SELECT USING (user_id = auth.uid());
+
+-- Access logs are append-only by authenticated users
 CREATE POLICY &quot;Insert access logs&quot; ON access_logs
     FOR INSERT WITH CHECK (user_id = auth.uid());
 
@@ -416,18 +379,20 @@ class SupabaseAuthManager {
         }
       }
     );
-    this.siteId = config.siteId;
   }
 
   async checkAccess() {
     const { data: { user } } = await this.supabase.auth.getUser();
     if (!user) return false;
 
+    // Use current domain for access check
+    const domain = window.location.host;
+    
     const { data, error } = await this.supabase
-      .from(&#39;user_site_access&#39;)
-      .select(&#39;role, expires_at&#39;)
+      .from(&#39;docbuilder_access&#39;)
+      .select(&#39;created_at&#39;)
       .eq(&#39;user_id&#39;, user.id)
-      .eq(&#39;site_id&#39;, this.siteId)
+      .eq(&#39;domain&#39;, domain)
       .single();
 
     if (error || !data) return false;
@@ -470,7 +435,7 @@ class SupabaseAuthManager {
 
   async logAccess(action, metadata = {}) {
     await this.supabase.from(&#39;access_logs&#39;).insert({
-      site_id: this.siteId,
+      domain: window.location.host,
       action,
       metadata,
       ip_address: await this.getClientIP(),
@@ -486,8 +451,8 @@ async function buildWithSupabaseAuth(config) {
     // Inject Supabase configuration
     const supabaseConfig = {
       supabaseUrl: config.auth.supabaseUrl,
-      supabaseAnonKey: config.auth.supabaseAnonKey,
-      siteId: config.auth.siteId
+      supabaseAnonKey: config.auth.supabaseAnonKey
+      // Domain is detected automatically from window.location.host
     };
 
     // Create enhanced auth.js with Supabase integration
@@ -521,8 +486,8 @@ async function buildWithSupabaseAuth(config) {
   auth: {
     // Supabase configuration
     supabaseUrl: process.env.SUPABASE_URL,
-    supabaseAnonKey: process.env.SUPABASE_ANON_KEY,
-    siteId: process.env.DOC_SITE_ID,
+    supabaseAnonKey: process.env.SUPABASE_ANON_KEY
+    // Domain-based authentication - no siteId needed
     
     // Optional: Custom login page styling
     loginTheme: {

package/html/private/supabase-auth-setup-guide.html

@@ -98,8 +98,8 @@
     "name": "Knowcode Ltd",
     "url": "https://knowcode.tech"
   },
-  "datePublished": "2025-07-26T10:38:42.034Z",
-  "dateModified": "2025-07-26T10:38:42.034Z",
+  "datePublished": "2025-07-26T11:11:45.929Z",
+  "dateModified": "2025-07-26T11:11:45.929Z",
   "mainEntityOfPage": {
     "@type": "WebPage",
     "@id": "https://doc-builder-delta.vercel.app/private/supabase-auth-setup-guide.html"
@@ -138,7 +138,7 @@
             
             <div class="header-actions">
                 <div class="deployment-info">
-                    <span class="deployment-date" title="Built with doc-builder v1.8.1">Last updated: Jul 26, 2025, 10:38 AM UTC</span>
+                    <span class="deployment-date" title="Built with doc-builder v1.8.2">Last updated: Jul 26, 2025, 11:11 AM UTC</span>
                 </div>
                 
                 
@@ -249,10 +249,11 @@
 <p>@knowcode/doc-builder supports enterprise-grade authentication through Supabase. This provides:</p>
 <ul>
 <li><strong>Secure authentication</strong> with industry-standard security practices</li>
-<li><strong>Multi-site support</strong> - one account can access multiple documentation sites</li>
+<li><strong>Domain-based access</strong> - automatic authentication based on site domain</li>
 <li><strong>User management</strong> through CLI commands</li>
 <li><strong>Password reset</strong> functionality built-in</li>
 <li><strong>Enterprise features</strong> like audit logging and access control</li>
+<li><strong>Zero configuration</strong> - built-in credentials (v1.8.2+)</li>
 </ul>
 <h2>Prerequisites</h2>
 <ol>
@@ -272,41 +273,30 @@
 <p>Wait for the project to be created (usually 1-2 minutes).</p>
 <h2>Step 2: Create Database Tables</h2>
 <p>In your Supabase dashboard, go to <strong>SQL Editor</strong> and run this SQL:</p>
-<pre><code class="language-sql">-- Table 1: Documentation sites
-CREATE TABLE docbuilder_sites (
-    id UUID PRIMARY KEY DEFAULT gen_random_uuid(),
-    domain TEXT UNIQUE NOT NULL,
-    name TEXT NOT NULL,
-    created_at TIMESTAMPTZ DEFAULT NOW()
-);
-
--- Table 2: User access mapping
+<pre><code class="language-sql">-- Single table for user access control (simplified!)
 CREATE TABLE docbuilder_access (
     user_id UUID REFERENCES auth.users(id) ON DELETE CASCADE,
-    site_id UUID REFERENCES docbuilder_sites(id) ON DELETE CASCADE,
+    domain TEXT NOT NULL,
     created_at TIMESTAMPTZ DEFAULT NOW(),
-    PRIMARY KEY (user_id, site_id)
+    PRIMARY KEY (user_id, domain)
 );
 
+-- Create index for faster lookups
+CREATE INDEX idx_docbuilder_access_domain ON docbuilder_access(domain);
+
 -- Enable Row Level Security
-ALTER TABLE docbuilder_sites ENABLE ROW LEVEL SECURITY;
 ALTER TABLE docbuilder_access ENABLE ROW LEVEL SECURITY;
 
--- RLS Policy: Users can only see sites they have access to
-CREATE POLICY &quot;Users see accessible sites&quot; ON docbuilder_sites
-    FOR SELECT USING (
-        EXISTS (
-            SELECT 1 FROM docbuilder_access
-            WHERE site_id = docbuilder_sites.id
-            AND user_id = auth.uid()
-        )
-    );
-
--- RLS Policy: Users can see their own access
+-- RLS Policy: Users can only see their own access
 CREATE POLICY &quot;Users see own access&quot; ON docbuilder_access
     FOR SELECT USING (user_id = auth.uid());
 </code></pre>
-<h2>Step 3: Get Supabase Credentials</h2>
+<h2>Step 3: Configure Authentication (Automatic in v1.8.2+)</h2>
+<p>As of version 1.8.2, Supabase credentials are automatically configured! You have two options:</p>
+<h3>Option 1: Use Built-in Credentials (Recommended)</h3>
+<p>Simply create a <code>docs/private/</code> directory or set <code>authentication: &#39;supabase&#39;</code> in your config. The system will automatically use the shared authentication database.</p>
+<h3>Option 2: Use Custom Supabase Project</h3>
+<p>If you want to use your own Supabase project:</p>
 <ol>
 <li>In your Supabase dashboard, go to <strong>Settings</strong> → <strong>API</strong></li>
 <li>Copy these values:<ul>
@@ -317,16 +307,20 @@ CREATE POLICY &quot;Users see own access&quot; ON docbuilder_access
 </ol>
 <p><i class="ph ph-warning-circle" aria-label="warning"></i> <strong>Never share your service role key</strong> - only use the anon/public key for doc-builder.</p>
 <h2>Step 4: Initialize Authentication</h2>
-<p>Run the initialization command in your documentation project:</p>
-<pre><code class="language-bash">npx @knowcode/doc-builder auth:init
+<h3>Option 1: Automatic Setup (v1.8.2+)</h3>
+<p>Just create a config file or use the <code>--preset</code> flag:</p>
+<pre><code class="language-javascript">// doc-builder.config.js
+module.exports = {
+  siteName: &#39;My Documentation&#39;,
+  
+  features: {
+    authentication: &#39;supabase&#39;
+  }
+  // No auth config needed - uses built-in credentials!
+};
 </code></pre>
-<p>This will prompt you for:</p>
-<ul>
-<li>Your Supabase project URL</li>
-<li>Your Supabase anonymous key  </li>
-<li>A name for your documentation site</li>
-</ul>
-<p>It creates a <code>doc-builder.config.js</code> file like this:</p>
+<h3>Option 2: Custom Supabase Project</h3>
+<p>If using your own Supabase project:</p>
 <pre><code class="language-javascript">module.exports = {
   siteName: &#39;My Documentation&#39;,
   
@@ -336,24 +330,13 @@ CREATE POLICY &quot;Users see own access&quot; ON docbuilder_access
   
   auth: {
     supabaseUrl: &#39;https://xxx.supabase.co&#39;,
-    supabaseAnonKey: &#39;eyJ...&#39;,
-    siteId: &#39;&#39;  // Will be set in next step
+    supabaseAnonKey: &#39;eyJ...&#39;
+    // No siteId needed - uses domain automatically!
   }
 };
 </code></pre>
-<h2>Step 5: Add Your Site to Database</h2>
-<h3>Option A: Using SQL (Recommended)</h3>
-<p>In Supabase SQL Editor, run:</p>
-<pre><code class="language-sql">INSERT INTO docbuilder_sites (domain, name) 
-VALUES (&#39;docs.yourcompany.com&#39;, &#39;Company Documentation&#39;)
-RETURNING id;
-</code></pre>
-<p>Copy the returned ID and update your config file&#39;s <code>siteId</code> field.</p>
-<h3>Option B: Using CLI (Coming Soon)</h3>
-<pre><code class="language-bash">npx @knowcode/doc-builder auth:add-site \
-  --domain docs.yourcompany.com \
-  --name &quot;Company Documentation&quot;
-</code></pre>
+<h2>Step 5: No Site Registration Needed!</h2>
+<p>The new domain-based system eliminates the need for site registration. The system automatically uses the current domain (e.g., <code>docs.example.com</code>) as the access key. Just grant users access to your domain in the next step.</p>
 <h2>Step 6: Create Your First User</h2>
 <h3>Method 1: Through Supabase Dashboard</h3>
 <ol>
@@ -367,14 +350,23 @@ RETURNING id;
 <p>Users can sign up when they visit your documentation site and try to log in.</p>
 <h2>Step 7: Grant User Access</h2>
 <h3>Using SQL:</h3>
-<pre><code class="language-sql">-- Replace with actual user ID and site ID
-INSERT INTO docbuilder_access (user_id, site_id)
-VALUES (&#39;user-uuid-here&#39;, &#39;site-uuid-here&#39;);
+<pre><code class="language-sql">-- Grant access by domain (no site ID needed!)
+INSERT INTO docbuilder_access (user_id, domain)
+VALUES (
+  (SELECT id FROM auth.users WHERE email = &#39;user@example.com&#39;),
+  &#39;docs.yourcompany.com&#39;
+);
+
+-- Grant access to multiple domains
+INSERT INTO docbuilder_access (user_id, domain) VALUES
+  ((SELECT id FROM auth.users WHERE email = &#39;user@example.com&#39;), &#39;docs.yourcompany.com&#39;),
+  ((SELECT id FROM auth.users WHERE email = &#39;user@example.com&#39;), &#39;staging-docs.yourcompany.com&#39;),
+  ((SELECT id FROM auth.users WHERE email = &#39;user@example.com&#39;), &#39;localhost:3000&#39;);
 </code></pre>
 <h3>Using CLI (Coming Soon):</h3>
 <pre><code class="language-bash">npx @knowcode/doc-builder auth:grant \
   --email user@example.com \
-  --site-id your-site-uuid
+  --domain docs.yourcompany.com
 </code></pre>
 <h2>Step 8: Build and Deploy</h2>
 <pre><code class="language-bash"># Build with Supabase authentication
@@ -386,55 +378,52 @@ npx @knowcode/doc-builder deploy
 <p>Your documentation site now has secure authentication! <i class="ph ph-confetti" aria-label="party"></i></p>
 <h2>User Management</h2>
 <h3>List Users with Access</h3>
-<pre><code class="language-sql">SELECT u.email, da.created_at as granted_at
+<pre><code class="language-sql">-- List all users for a specific domain
+SELECT u.email, da.created_at as granted_at
 FROM docbuilder_access da
 JOIN auth.users u ON u.id = da.user_id
-WHERE da.site_id = &#39;your-site-id&#39;;
+WHERE da.domain = &#39;docs.yourcompany.com&#39;;
 </code></pre>
 <h3>Revoke Access</h3>
-<pre><code class="language-sql">DELETE FROM docbuilder_access 
+<pre><code class="language-sql">-- Remove access for a specific domain
+DELETE FROM docbuilder_access 
 WHERE user_id = (SELECT id FROM auth.users WHERE email = &#39;user@example.com&#39;)
-AND site_id = &#39;your-site-id&#39;;
+AND domain = &#39;docs.yourcompany.com&#39;;
 </code></pre>
 <h3>Reset User Password</h3>
 <p>Users can reset their own passwords through the login page &quot;Forgot Password&quot; link.</p>
 <h2>Environment Variables (Optional)</h2>
-<p>For better security, use environment variables:</p>
+<p>For better security with custom Supabase projects, use environment variables:</p>
 <pre><code class="language-bash"># .env
 SUPABASE_URL=https://xxx.supabase.co
 SUPABASE_ANON_KEY=eyJ...
-DOC_SITE_ID=your-site-uuid
 </code></pre>
 <p>Update your config:</p>
 <pre><code class="language-javascript">module.exports = {
   auth: {
     supabaseUrl: process.env.SUPABASE_URL,
-    supabaseAnonKey: process.env.SUPABASE_ANON_KEY,
-    siteId: process.env.DOC_SITE_ID
+    supabaseAnonKey: process.env.SUPABASE_ANON_KEY
+    // No siteId needed - uses domain automatically!
   }
 };
 </code></pre>
 <h2>Multi-Site Setup</h2>
-<p>To use one Supabase project for multiple documentation sites:</p>
+<p>The domain-based system makes multi-site setup incredibly simple:</p>
 <ol>
-<li>Add each site to the database:</li>
-</ol>
-<pre><code class="language-sql">INSERT INTO docbuilder_sites (domain, name) VALUES
-(&#39;docs.product1.com&#39;, &#39;Product 1 Docs&#39;),
-(&#39;internal.company.com&#39;, &#39;Internal Docs&#39;),
-(&#39;api.company.com&#39;, &#39;API Documentation&#39;);
-</code></pre>
-<ol start="2">
-<li><p>Create separate config files for each site with different <code>siteId</code> values</p>
+<li><p><strong>No site registration needed</strong> - Each domain is automatically recognized</p>
 </li>
-<li><p>Grant users access to specific sites:</p>
+<li><p><strong>Grant users access to multiple domains</strong>:</p>
 </li>
 </ol>
-<pre><code class="language-sql">-- User can access both Product 1 and Internal docs
-INSERT INTO docbuilder_access (user_id, site_id) VALUES
-(&#39;user-uuid&#39;, &#39;product1-site-uuid&#39;),
-(&#39;user-uuid&#39;, &#39;internal-site-uuid&#39;);
+<pre><code class="language-sql">-- User can access multiple documentation sites
+INSERT INTO docbuilder_access (user_id, domain) VALUES
+  ((SELECT id FROM auth.users WHERE email = &#39;user@example.com&#39;), &#39;docs.product1.com&#39;),
+  ((SELECT id FROM auth.users WHERE email = &#39;user@example.com&#39;), &#39;internal.company.com&#39;),
+  ((SELECT id FROM auth.users WHERE email = &#39;user@example.com&#39;), &#39;api.company.com&#39;);
 </code></pre>
+<ol start="3">
+<li><strong>Same configuration for all sites</strong> - Just deploy to different domains!</li>
+</ol>
 <h2>Security Features</h2>
 <h3>What Supabase Provides</h3>
 <ul>
@@ -449,8 +438,8 @@ INSERT INTO docbuilder_access (user_id, site_id) VALUES
 <h3>Row Level Security</h3>
 <p>All data access is protected by RLS policies:</p>
 <ul>
-<li>Users can only see sites they have access to</li>
 <li>Users can only see their own access records</li>
+<li>Domain-based access is automatically enforced</li>
 <li>No way to access other users&#39; data</li>
 </ul>
 <h2>Troubleshooting</h2>
@@ -463,8 +452,8 @@ INSERT INTO docbuilder_access (user_id, site_id) VALUES
 <h3>Users Can&#39;t Access Site</h3>
 <ul>
 <li>Verify the user exists in <code>auth.users</code> table</li>
-<li>Check that user has access in <code>docbuilder_access</code> table  </li>
-<li>Confirm the <code>site_id</code> matches your config</li>
+<li>Check that user has access in <code>docbuilder_access</code> table for the correct domain</li>
+<li>Confirm the domain in the database matches your deployment URL</li>
 </ul>
 <h3>Login Page Not Working</h3>
 <ul>

package/html/private/test-private-doc.html

@@ -98,8 +98,8 @@
     "name": "Knowcode Ltd",
     "url": "https://knowcode.tech"
   },
-  "datePublished": "2025-07-26T10:38:42.036Z",
-  "dateModified": "2025-07-26T10:38:42.036Z",
+  "datePublished": "2025-07-26T11:11:45.930Z",
+  "dateModified": "2025-07-26T11:11:45.930Z",
   "mainEntityOfPage": {
     "@type": "WebPage",
     "@id": "https://doc-builder-delta.vercel.app/private/test-private-doc.html"
@@ -138,7 +138,7 @@
             
             <div class="header-actions">
                 <div class="deployment-info">
-                    <span class="deployment-date" title="Built with doc-builder v1.8.1">Last updated: Jul 26, 2025, 10:38 AM UTC</span>
+                    <span class="deployment-date" title="Built with doc-builder v1.8.2">Last updated: Jul 26, 2025, 11:11 AM UTC</span>
                 </div>
                 
                 

package/html/private/user-management-tooling.html

@@ -98,8 +98,8 @@
     "name": "Knowcode Ltd",
     "url": "https://knowcode.tech"
   },
-  "datePublished": "2025-07-26T10:38:42.038Z",
-  "dateModified": "2025-07-26T10:38:42.038Z",
+  "datePublished": "2025-07-26T11:11:45.932Z",
+  "dateModified": "2025-07-26T11:11:45.932Z",
   "mainEntityOfPage": {
     "@type": "WebPage",
     "@id": "https://doc-builder-delta.vercel.app/private/user-management-tooling.html"
@@ -138,7 +138,7 @@
             
             <div class="header-actions">
                 <div class="deployment-info">
-                    <span class="deployment-date" title="Built with doc-builder v1.8.1">Last updated: Jul 26, 2025, 10:38 AM UTC</span>
+                    <span class="deployment-date" title="Built with doc-builder v1.8.2">Last updated: Jul 26, 2025, 11:11 AM UTC</span>
                 </div>
                 
                 
@@ -273,21 +273,15 @@
 </li>
 </ol>
 <h3>Database Schema</h3>
-<p>The system works with two main tables:</p>
-<p><strong>docbuilder_sites</strong></p>
-<ul>
-<li><code>id</code> (UUID) - Primary key</li>
-<li><code>domain</code> (TEXT) - Site URL without https://</li>
-<li><code>name</code> (TEXT) - Display name</li>
-<li><code>created_at</code> (TIMESTAMP)</li>
-</ul>
+<p>The system now uses a simplified single-table design:</p>
 <p><strong>docbuilder_access</strong></p>
 <ul>
 <li><code>user_id</code> (UUID) - References auth.users</li>
-<li><code>site_id</code> (UUID) - References docbuilder_sites</li>
+<li><code>domain</code> (TEXT) - Site domain (e.g., docs.example.com)</li>
 <li><code>created_at</code> (TIMESTAMP)</li>
-<li>Composite primary key on (user_id, site_id)</li>
+<li>Primary key on (user_id, domain)</li>
 </ul>
+<p>No more site registration needed! The system automatically uses the current domain.</p>
 <h2>Implementation Details</h2>
 <h3>User Creation Methods</h3>
 <p>Due to Supabase CLI limitations (no direct user creation commands), the system offers three methods:</p>