kartman-dev 1.0.0-dev.0

package/dist/claude-config/worktrees/valiant-sparking-hare/.claude/skills/doc-drift-check/references/severity-guide.md

@@ -0,0 +1,174 @@
+# Severity Classification Guide
+
+Detailed guide for categorizing doc drift findings by severity level. Use this when analyzing mismatches between code changes and documentation.
+
+## 🔴 Critical — Would Cause Wrong Assumptions
+
+These mismatches would cause someone to build against incorrect assumptions or make wrong decisions.
+
+### Model/Schema Changes
+
+- Code adds a new model but the Notion module page doesn't list it
+- Code removes or renames a model field, but the module documentation still references the old field
+- Relationship between models changed (e.g., ForeignKey → ManyToMany) but not reflected in docs
+- New required field added to a model but not documented in the module's models section
+
+**Example:**
+> Code adds `AccessKey` model to `andgate_crypto` module, but the Crypto module page in Notion under Platform's Product Development doesn't mention it.
+
+### API/Endpoint Changes
+
+- New endpoint added without documentation
+- Endpoint removed but still listed in docs
+- Request/response format changed but docs show old format
+- Authentication requirements changed
+
+### Environment & Configuration
+
+- New environment variable required but not in CLAUDE.md or deployment docs
+- Configuration option removed but still documented
+- Default value changed for existing config
+
+### Architecture Changes
+
+- New module/app created without corresponding Notion documentation
+- Service dependencies changed (module A now depends on module B, but docs don't show this)
+- Database migration adds/removes tables not reflected in schema docs
+
+---
+
+## 🟡 Moderate — Would Miss Important Capabilities
+
+These mismatches would cause someone to miss important features or follow outdated procedures.
+
+### Service Changes
+
+- New service class added to a module but module page doesn't list it in the services section
+- Service method signature changed (different params) but process docs reference old signature
+- Service now calls a different external provider but process diagrams show old flow
+
+**Example:**
+> Code adds `AccessKeyService` to handle crypto signing, but the Crypto module page doesn't list it under Services.
+
+### Process Flow Changes
+
+- Steps in a business process reordered or modified
+- New step added to a process (e.g., new validation step in onboarding)
+- Conditional logic changed (e.g., different handling for B2B vs B2C)
+- Process now has prerequisites that aren't documented
+
+**Example:**
+> Customer onboarding now requires provider-specific KYC before account creation, but the process page still shows a single KYC step.
+
+### Feature Documentation Gaps
+
+- New feature implemented but no feature document exists
+- Feature behavior changed significantly but feature docs describe old behavior
+- Feature flag added without documentation in relevant places
+
+### Workflow Changes
+
+- Webhook handling changed but webhook documentation outdated
+- Background task behavior modified but not reflected in process docs
+- Error handling strategy changed for a module
+
+---
+
+## 🟢 Light — Brief Confusion Only
+
+These mismatches would cause someone brief confusion but wouldn't lead to incorrect work.
+
+### Naming/Renaming
+
+- Service or utility class renamed but docs use old name
+- File moved to different directory but docs reference old path
+- Variable or constant renamed
+
+**Example:**
+> `CryptoSigningService` renamed to `AccessKeyService` in code but Notion module page still says `CryptoSigningService`.
+
+### Outdated Examples
+
+- Code example in docs uses old import path
+- Example shows deprecated API usage but functionally equivalent
+- Test examples reference old fixtures
+
+### Minor Wording
+
+- Documentation says "will be implemented" for already-implemented features
+- Status markers (TODO, WIP) left in docs for completed work
+- Comments in code reference old Notion page names
+
+---
+
+## Per-Source Analysis Guide
+
+### Notion Module Pages
+
+Module pages describe models and services for each module. When checking:
+
+1. **Models section** — Compare listed models against actual Django models in the code
+2. **Services section** — Compare listed services against actual service classes
+3. **API section** — Compare listed endpoints against actual URL configs
+4. **Shared models** — Verify cross-module dependencies are still accurate
+5. **Dependency graph** — Check if module interdependencies changed
+
+### Notion Processes Database
+
+Process pages describe business workflows. When checking:
+
+1. **Process steps** — Do the documented steps match the actual code flow?
+2. **Prerequisites** — Are process prerequisites still accurate?
+3. **Provider interactions** — Do provider-specific flows match current implementation?
+4. **Status transitions** — Do documented state machines match code?
+5. **Related modules** — Is the "Модули" relation still correct?
+
+### Repository docs/ Directory
+
+Local documentation files. When checking:
+
+1. **Architecture docs** — Do they reflect current module structure?
+2. **API docs** — Do endpoint descriptions match implementations?
+3. **Setup/deployment docs** — Are instructions still accurate?
+
+### CLAUDE.md
+
+Project-level documentation. When checking:
+
+1. **Environment variables table** — All required vars listed?
+2. **Project structure** — Does the tree match actual directory layout?
+3. **Technology stack** — Any new dependencies or tools?
+4. **Key documentation links** — Do referenced docs still exist?
+
+### Database Schema
+
+Schema documentation. When checking:
+
+1. **Table definitions** — Do they match current migrations?
+2. **Relationships** — Are FK/M2M relations documented correctly?
+3. **Indexes** — Any new indexes not mentioned in schema docs?
+4. **New tables** — Any new migrations creating tables not in schema docs?
+
+---
+
+## Edge Cases
+
+### When NOT to Flag
+
+- Code comments that are slightly outdated (not worth a Linear comment)
+- Test file documentation being slightly behind (tests are self-documenting)
+- Third-party library version bumps with no behavior change
+- Formatting-only changes to documentation files
+- Internal refactoring that doesn't change public interfaces or behavior
+
+### When to Escalate to Critical
+
+Even if a change seems small, escalate if:
+- It affects an external-facing API that developers build against
+- It changes model fields that other services query
+- It modifies environment variables needed for deployment
+- It alters the behavior described in a process that operations follows
+
+### Multiple Small Issues
+
+If there are many Light issues (5+) concentrated in one documentation area, consider grouping them and elevating to a single Moderate finding with a suggestion to do a documentation review for that area.

package/dist/claude-config/worktrees/valiant-sparking-hare/.github/workflows/claude-code-review.yml

@@ -0,0 +1,32 @@
+name: Claude Code Review
+
+on:
+  pull_request:
+    types: [opened, synchronize, ready_for_review, reopened]
+
+jobs:
+  claude-review:
+    runs-on: ubuntu-latest
+    permissions:
+      contents: write
+      pull-requests: write
+      issues: write
+      id-token: write
+
+    steps:
+      - name: Checkout repository
+        uses: actions/checkout@v4
+        with:
+          fetch-depth: 1
+
+      - name: Run Claude Code Review
+        id: claude-review
+        uses: anthropics/claude-code-action@v1
+        with:
+          claude_code_oauth_token: ${{ secrets.CLAUDE_CODE_OAUTH_TOKEN }}
+          plugin_marketplaces: 'https://github.com/anthropics/claude-code.git'
+          plugins: 'code-review@claude-code-plugins'
+          prompt: '/code-review:code-review ${{ github.repository }}/pull/${{ github.event.pull_request.number }}'
+          # See https://github.com/anthropics/claude-code-action/blob/main/docs/usage.md
+          # or https://code.claude.com/docs/en/cli-reference for available options
+

package/dist/claude-config/worktrees/valiant-sparking-hare/.github/workflows/claude.yml

@@ -0,0 +1,37 @@
+name: Claude Code
+
+on:
+  issue_comment:
+    types: [created]
+  pull_request_review_comment:
+    types: [created]
+  issues:
+    types: [opened, assigned]
+  pull_request_review:
+    types: [submitted]
+
+jobs:
+  claude:
+    if: |
+      (github.event_name == 'issue_comment' && contains(github.event.comment.body, '@claude')) ||
+      (github.event_name == 'pull_request_review_comment' && contains(github.event.comment.body, '@claude')) ||
+      (github.event_name == 'pull_request_review' && contains(github.event.review.body, '@claude')) ||
+      (github.event_name == 'issues' && (contains(github.event.issue.body, '@claude') || contains(github.event.issue.title, '@claude')))
+    runs-on: ubuntu-latest
+    permissions:
+      contents: write
+      pull-requests: write
+      issues: write
+      id-token: write
+      actions: read # Required for Claude to read CI results on PRs
+    steps:
+      - name: Checkout repository
+        uses: actions/checkout@v4
+        with:
+          fetch-depth: 1
+
+      - name: Run Claude Code
+        id: claude
+        uses: anthropics/claude-code-action@v1
+        with:
+          claude_code_oauth_token: ${{ secrets.CLAUDE_CODE_OAUTH_TOKEN }}

package/dist/claude-config/worktrees/valiant-sparking-hare/.nvmrc

@@ -0,0 +1 @@
+v22.18.0

package/dist/claude-config/worktrees/valiant-sparking-hare/.prettierignore

@@ -0,0 +1,11 @@
+*.yml
+*.yaml
+*.d.ts
+node_modules
+coverage
+.nuxt
+.output
+.npmrc
+.nvmrc
+dist
+public

package/dist/index.d.ts

@@ -0,0 +1,2 @@
+
+export {  }