@djangocfg/layouts 2.1.227 → 2.1.228

package/src/layouts/AuthLayout/types.ts

@@ -1,12 +1,13 @@
 /**
  * Auth Layout Types
  *
- * Re-exports from @djangocfg/api/auth for convenience.
- * Single source of truth is in @djangocfg/api/auth/types.
+ * - Pure auth logic types re-exported from @djangocfg/api/auth
+ * - UI/layout types defined here — api package has no business knowing about them
  */
 
+import type React from 'react';
+
 export type {
-  AuthChannel,
   AuthStep,
   AuthFormState,
   AuthFormStateHandlers,
@@ -15,8 +16,60 @@ export type {
   AuthFormAutoSubmit,
   AuthFormReturn,
   UseAuthFormOptions,
-  AuthLayoutConfig,
-  AuthFormContextType,
-  AuthLayoutProps,
-  AuthHelpProps,
 } from '@djangocfg/api/auth';
+
+import type { AuthFormReturn } from '@djangocfg/api/auth';
+
+// ─────────────────────────────────────────────────────────────────────────────
+// Layout Config — UI-specific configuration for AuthLayout
+// ─────────────────────────────────────────────────────────────────────────────
+
+export interface AuthLayoutConfig {
+  /** Support page URL */
+  supportUrl?: string;
+  /** Terms of service URL */
+  termsUrl?: string;
+  /** Privacy policy URL */
+  privacyUrl?: string;
+  /** Source URL for tracking */
+  sourceUrl: string;
+  /** Enable GitHub OAuth button */
+  enableGithubAuth?: boolean;
+  /** Logo URL for success screen (SVG recommended) */
+  logoUrl?: string;
+  /** URL to redirect after successful auth (default: /dashboard) */
+  redirectUrl?: string;
+  /**
+   * Enable 2FA setup prompt after successful authentication.
+   * @default true
+   */
+  enable2FASetup?: boolean;
+}
+
+// ─────────────────────────────────────────────────────────────────────────────
+// Context — form state + layout config merged for step components
+// ─────────────────────────────────────────────────────────────────────────────
+
+export interface AuthFormContextType extends AuthFormReturn, AuthLayoutConfig {}
+
+// ─────────────────────────────────────────────────────────────────────────────
+// Component Props
+// ─────────────────────────────────────────────────────────────────────────────
+
+export interface AuthLayoutProps extends AuthLayoutConfig {
+  children?: React.ReactNode;
+  className?: string;
+  /** Callback when identifier step succeeds */
+  onIdentifierSuccess?: (identifier: string) => void;
+  /** Callback when OTP verification succeeds */
+  onOTPSuccess?: () => void;
+  /** Callback when OAuth succeeds */
+  onOAuthSuccess?: (user: any, isNewUser: boolean, provider: string) => void;
+  /** Callback on any error */
+  onError?: (message: string) => void;
+}
+
+export interface AuthHelpProps {
+  className?: string;
+  variant?: 'default' | 'compact';
+}

package/src/layouts/ProfileLayout/.claude/.sidecar/activity.jsonl

@@ -0,0 +1,2 @@
+{"ts":"2026-03-15T05:27:58.550593Z","action":"update_check","tokens":0,"model":"deepseek/deepseek-v3.2","details":{}}
+{"ts":"2026-03-15T05:28:21.054276Z","action":"review","tokens":1533,"model":"deepseek/deepseek-v3.2","details":{"items_found":5}}

package/src/layouts/ProfileLayout/.claude/.sidecar/history/2026-03-15.md

@@ -0,0 +1,35 @@
+# Sidecar Review -- 2026-03-15T05:28:21.052657+00:00
+
+## Staleness
+
+- [?] Cannot assess staleness because documentation contents are unavailable. However, given the high commit activity (20 commits in 2 days), any documentation older than 30 days is almost certainly stale and contradictory to the current codebase state (e.g., new 'debuger', 'monitor', and OTP features).
+  Files: Documentation referenced in file list
+  Action: Provide documentation content to check modification dates against commit history. Update all documentation to reflect recent changes like the debug panel, monitoring integration, and OTP brute-force protection.
+  (id: 46040dd3aace)
+
+## Contradictions
+
+- [~] The commit 'updaded rq' (2026-03-14) has a typo and inconsistent formatting compared to other commits (e.g., 'chore(deps): bump django-rq version to 4.0.0'). This suggests poor documentation practices in commit messages, which can lead to confusion about project changes.
+  Files: Commit history analysis
+  Action: Enforce a commit message convention (e.g., Conventional Commits) and consider amending the 'updaded rq' commit for clarity. Ensure future commits are consistently formatted.
+  (id: 6e3e54dfac9f)
+
+## Missing Documentation
+
+- [!] No documentation content was provided for analysis. The provided metadata lists documentation files but their contents are unavailable, making it impossible to verify accuracy, check for staleness, or identify contradictions with the codebase.
+  Files: All documentation files
+  Action: Provide the actual content of the documentation files listed in the metadata (e.g., README.md, API docs, configuration guides) to enable a proper analysis for staleness, contradictions, and gaps.
+  (id: fb1ef89d45a4)
+
+- [?] The top-level source directories '__tests__' and 'components' have no associated documentation content provided. Recent commits mention features like 'debuger', 'monitor', 'accounts', and 'otp', which likely reside in these directories, but their documentation cannot be verified.
+  Files: __tests__, components
+  Action: Review and provide documentation for the '__tests__' and 'components' directories, ensuring it covers the features mentioned in recent commits (e.g., debug panel, OTP brute-force protection, monitoring integration).
+  (id: d538d5624ebb)
+
+- [!] No dependencies were detected, but recent git commits show active dependency management (e.g., 'bump django-cfg version to 1.7.77', 'bump django-rq version to 4.0.0'). This indicates a contradiction between the reported state and project activity, and documentation for these key dependencies is missing.
+  Files: Dependency files (e.g., pyproject.toml, requirements.txt)
+  Action: Provide the actual dependency files (pyproject.toml, package.json, or requirements.txt) to check for contradictions with documentation and ensure all critical packages like 'django-cfg' and 'django-rq' are documented.
+  (id: fe7c9fa20e8b)
+
+---
+Model: deepseek/deepseek-v3.2 | Tokens: 1533

package/src/layouts/ProfileLayout/.claude/.sidecar/review.md

@@ -0,0 +1,35 @@
+# Sidecar Review -- 2026-03-15T05:28:21.052657+00:00
+
+## Staleness
+
+- [?] Cannot assess staleness because documentation contents are unavailable. However, given the high commit activity (20 commits in 2 days), any documentation older than 30 days is almost certainly stale and contradictory to the current codebase state (e.g., new 'debuger', 'monitor', and OTP features).
+  Files: Documentation referenced in file list
+  Action: Provide documentation content to check modification dates against commit history. Update all documentation to reflect recent changes like the debug panel, monitoring integration, and OTP brute-force protection.
+  (id: 46040dd3aace)
+
+## Contradictions
+
+- [~] The commit 'updaded rq' (2026-03-14) has a typo and inconsistent formatting compared to other commits (e.g., 'chore(deps): bump django-rq version to 4.0.0'). This suggests poor documentation practices in commit messages, which can lead to confusion about project changes.
+  Files: Commit history analysis
+  Action: Enforce a commit message convention (e.g., Conventional Commits) and consider amending the 'updaded rq' commit for clarity. Ensure future commits are consistently formatted.
+  (id: 6e3e54dfac9f)
+
+## Missing Documentation
+
+- [!] No documentation content was provided for analysis. The provided metadata lists documentation files but their contents are unavailable, making it impossible to verify accuracy, check for staleness, or identify contradictions with the codebase.
+  Files: All documentation files
+  Action: Provide the actual content of the documentation files listed in the metadata (e.g., README.md, API docs, configuration guides) to enable a proper analysis for staleness, contradictions, and gaps.
+  (id: fb1ef89d45a4)
+
+- [?] The top-level source directories '__tests__' and 'components' have no associated documentation content provided. Recent commits mention features like 'debuger', 'monitor', 'accounts', and 'otp', which likely reside in these directories, but their documentation cannot be verified.
+  Files: __tests__, components
+  Action: Review and provide documentation for the '__tests__' and 'components' directories, ensuring it covers the features mentioned in recent commits (e.g., debug panel, OTP brute-force protection, monitoring integration).
+  (id: d538d5624ebb)
+
+- [!] No dependencies were detected, but recent git commits show active dependency management (e.g., 'bump django-cfg version to 1.7.77', 'bump django-rq version to 4.0.0'). This indicates a contradiction between the reported state and project activity, and documentation for these key dependencies is missing.
+  Files: Dependency files (e.g., pyproject.toml, requirements.txt)
+  Action: Provide the actual dependency files (pyproject.toml, package.json, or requirements.txt) to check for contradictions with documentation and ensure all critical packages like 'django-cfg' and 'django-rq' are documented.
+  (id: fe7c9fa20e8b)
+
+---
+Model: deepseek/deepseek-v3.2 | Tokens: 1533

package/src/layouts/ProfileLayout/.claude/.sidecar/scan.log

@@ -0,0 +1,3 @@
+Review generated: 5 items found
+Tokens used: 1533 (deepseek/deepseek-v3.2)
+Converted 5 items to tasks

package/src/layouts/ProfileLayout/.claude/.sidecar/tasks/T-001.md

@@ -0,0 +1,18 @@
+---
+context_files:
+- All documentation files
+created_at: '2026-03-15T05:28:21.056182Z'
+id: T-001
+priority: high
+source: sidecar_review
+source_item_id: fb1ef89d45a4
+status: pending
+title: '[gap] No documentation content was provided for analysis. The provided metadata
+  lists'
+---
+
+No documentation content was provided for analysis. The provided metadata lists documentation files but their contents are unavailable, making it impossible to verify accuracy, check for staleness, or identify contradictions with the codebase.
+
+**Files:** All documentation files
+
+**Action:** Provide the actual content of the documentation files listed in the metadata (e.g., README.md, API docs, configuration guides) to enable a proper analysis for staleness, contradictions, and gaps.

package/src/layouts/ProfileLayout/.claude/.sidecar/tasks/T-002.md

@@ -0,0 +1,19 @@
+---
+context_files:
+- __tests__
+- components
+created_at: '2026-03-15T05:28:21.057118Z'
+id: T-002
+priority: medium
+source: sidecar_review
+source_item_id: d538d5624ebb
+status: pending
+title: '[gap] The top-level source directories ''__tests__'' and ''components'' have
+  no associated'
+---
+
+The top-level source directories '__tests__' and 'components' have no associated documentation content provided. Recent commits mention features like 'debuger', 'monitor', 'accounts', and 'otp', which likely reside in these directories, but their documentation cannot be verified.
+
+**Files:** __tests__, components
+
+**Action:** Review and provide documentation for the '__tests__' and 'components' directories, ensuring it covers the features mentioned in recent commits (e.g., debug panel, OTP brute-force protection, monitoring integration).

package/src/layouts/ProfileLayout/.claude/.sidecar/tasks/T-003.md

@@ -0,0 +1,18 @@
+---
+context_files:
+- Dependency files (e.g., pyproject.toml, requirements.txt)
+created_at: '2026-03-15T05:28:21.057738Z'
+id: T-003
+priority: high
+source: sidecar_review
+source_item_id: fe7c9fa20e8b
+status: pending
+title: '[gap] No dependencies were detected, but recent git commits show active dependency
+  man'
+---
+
+No dependencies were detected, but recent git commits show active dependency management (e.g., 'bump django-cfg version to 1.7.77', 'bump django-rq version to 4.0.0'). This indicates a contradiction between the reported state and project activity, and documentation for these key dependencies is missing.
+
+**Files:** Dependency files (e.g., pyproject.toml, requirements.txt)
+
+**Action:** Provide the actual dependency files (pyproject.toml, package.json, or requirements.txt) to check for contradictions with documentation and ensure all critical packages like 'django-cfg' and 'django-rq' are documented.

package/src/layouts/ProfileLayout/.claude/.sidecar/tasks/T-004.md

@@ -0,0 +1,18 @@
+---
+context_files:
+- Documentation referenced in file list
+created_at: '2026-03-15T05:28:21.058352Z'
+id: T-004
+priority: medium
+source: sidecar_review
+source_item_id: 46040dd3aace
+status: pending
+title: '[staleness] Cannot assess staleness because documentation contents are unavailable.
+  However,'
+---
+
+Cannot assess staleness because documentation contents are unavailable. However, given the high commit activity (20 commits in 2 days), any documentation older than 30 days is almost certainly stale and contradictory to the current codebase state (e.g., new 'debuger', 'monitor', and OTP features).
+
+**Files:** Documentation referenced in file list
+
+**Action:** Provide documentation content to check modification dates against commit history. Update all documentation to reflect recent changes like the debug panel, monitoring integration, and OTP brute-force protection.

package/src/layouts/ProfileLayout/.claude/.sidecar/tasks/T-005.md

@@ -0,0 +1,18 @@
+---
+context_files:
+- Commit history analysis
+created_at: '2026-03-15T05:28:21.059002Z'
+id: T-005
+priority: low
+source: sidecar_review
+source_item_id: 6e3e54dfac9f
+status: pending
+title: '[contradiction] The commit ''updaded rq'' (2026-03-14) has a typo and inconsistent
+  formatting comp'
+---
+
+The commit 'updaded rq' (2026-03-14) has a typo and inconsistent formatting compared to other commits (e.g., 'chore(deps): bump django-rq version to 4.0.0'). This suggests poor documentation practices in commit messages, which can lead to confusion about project changes.
+
+**Files:** Commit history analysis
+
+**Action:** Enforce a commit message convention (e.g., Conventional Commits) and consider amending the 'updaded rq' commit for clarity. Ensure future commits are consistently formatted.

package/src/layouts/ProfileLayout/.claude/.sidecar/usage.json

@@ -0,0 +1,5 @@
+{
+  "date": "2026-03-15",
+  "tokens": 1533,
+  "calls": 1
+}