Merge branch 'localization' into develop

# Conflicts:
#	package-lock.json
#	src/components/Header.astro
#	src/content/docs/android/adapty-cursor-android.mdx
#	src/content/docs/capacitor/adapty-cursor-capacitor.mdx
#	src/content/docs/developer-cli/developer-cli-authentication.mdx
#	src/content/docs/developer-cli/developer-cli-quickstart.mdx
#	src/content/docs/developer-cli/developer-cli-reference.mdx
#	src/content/docs/developer-cli/developer-cli.mdx
#	src/content/docs/flutter/adapty-cursor-flutter.mdx
#	src/content/docs/ios/adapty-cursor.mdx
#	src/content/docs/kmp/adapty-cursor-kmp.mdx
#	src/content/docs/react-native/adapty-cursor-react-native.mdx
#	src/content/docs/unity/adapty-cursor-unity.mdx

Author: eandreeva-twr

.claude/skills/editor/SKILL.md

@@ -115,6 +115,8 @@ See `references/simplified-technical-english.md` → Voice Guidelines + Verb Ten
 
 Check for: non-parallel heading structure at same level, inconsistent list punctuation, dashes instead of colons after bold labels (`**Label**:` not `**Label** -`), inline lists where bullet lists would be clearer.
 
+**Exception — UI/product names**: If a heading uses the exact name of a product feature or UI element, do not flag it for breaking parallelism. Feature names take precedence over grammatical consistency. Example: `## Sharing paid access between user accounts` is the name of the feature in the UI — do not rewrite it to fix parallel structure.
+
 See `references/article-structure.md` → Parallel Heading Structure + List Formatting
 
 ### 7. Instruction Pattern (Location → Action)
@@ -124,6 +126,8 @@ Instructions must follow: Goal → Location → Action
 ✅ "To create a paywall, in the Paywalls section, click **Create paywall**"
 ❌ "Click **Create paywall** to create a paywall in the Paywalls section"
 
+**Do not over-granularize**: A short inline instruction (2–3 steps expressible in one clear sentence) should stay inline. Breaking it into a numbered list introduces unnecessary friction. Use numbered steps only when: (a) the sequence has 4+ distinct actions, (b) each step requires separate verification, or (c) the sentence becomes unreadably long. Conciseness takes priority — do not flag a clear one-sentence instruction as a problem.
+
 See `references/simplified-technical-english.md` → Instruction Pattern
 
 ### 8. Article Structure
@@ -134,9 +138,21 @@ See `references/article-structure.md`
 
 ### 9. Links and Images
 
-**Diff reviews** (check only added items): existing pages, correct relative paths, anchor slugs lowercase-hyphenated, image files exist, `@assets/` not `@asset/`, descriptive alt text.
+Run the link checker in diff mode to validate links automatically:
+
+```bash
+npm run check-links-diff
+```
+
+This checks outgoing links from changed files AND incoming links to changed files (catches breakage from renamed files or removed headings). Reports are written to `_temp/link-report.md` and `_temp/link-report.html`.
 
-**Full article reviews**: validate ALL links and images.
+After the script finishes, read `_temp/link-report.md` and include a summary in your review output. Report only **broken links** (errors) and **stale links** (warnings) — skip the "manual check" category. If issues were found, tell the user they can open the full HTML report:
+
+```
+open _temp/link-report.html
+```
+
+Additionally check images manually: image files exist, `@assets/` not `@asset/`, descriptive alt text.
 
 See `references/astro-patterns.md`
 
@@ -168,6 +184,24 @@ For each issue: quote the text (with line number) → explain why → provide sp
 
 See `references/output-templates.md` for annotated feedback example.
 
+### Interactive Review Flow
+
+After completing all checks, follow this flow:
+
+1. **Number every finding** sequentially across all categories (Critical, Important, Suggestions). Assign a single global number to each, not per-category numbers.
+
+2. **Present the full numbered list** as a concise "whole picture" — one line per finding, format: `**N.** [article if multiple] brief description → proposed fix`
+
+3. **Ask before proceeding**: *"Here are all [N] findings. Would you like to go through them interactively, deciding which to accept?"* — wait for the answer.
+
+4. **If yes — use `AskUserQuestion`**, 4 suggestions at a time:
+   - Question label (header, max 12 chars): `#N Topic`
+   - Question text: `#N — filename line X: [quoted text] → [proposed rewrite]`
+   - Options: **Accept** (describe what changes), **Skip** (leave as-is). "Other" is always available for custom comments.
+   - Handle user comments: if the user types a custom note, incorporate it before applying the fix.
+
+5. **Apply only accepted changes** after all answers are collected. Do not edit anything until the full quiz is complete.
+
 ## Special Considerations
 
 ### Diff Reviews

.claude/skills/product-manager/SKILL.md

@@ -146,6 +146,24 @@ Start every review with **Persona Usage Analysis**, then:
 
 See [`feedback-example.md`](references/feedback-example.md) for a complete annotated example.
 
+### Interactive Review Flow
+
+When both editor and product-manager reviews are combined in one session, a single shared numbered list is produced. When used alone, follow the same flow:
+
+1. **Number every actionable finding** sequentially across all categories. Each finding gets one global number.
+
+2. **Present the full numbered list** as a concise "whole picture" — one line per finding, format: `**N.** [article if multiple] brief description → proposed fix`
+
+3. **Ask before proceeding**: *"Here are all [N] findings. Would you like to go through them interactively, deciding which to accept?"* — wait for the answer.
+
+4. **If yes — use `AskUserQuestion`**, 4 suggestions at a time:
+   - Question label (header, max 12 chars): `#N Topic`
+   - Question text: `#N — filename: [quoted text] → [proposed fix or action]`
+   - Options: **Accept** (describe what changes), **Skip** (leave as-is). "Other" is always available for custom comments.
+   - Handle user comments: if the user types a custom note, incorporate it before applying.
+
+5. **Apply only accepted changes** after all answers are collected. Do not edit anything until the full quiz is complete.
+
 ## Feedback Guidelines
 
 - Quote the problematic section

.github/workflows/check-links.yml

@@ -1,30 +1,48 @@
 name: Check documentation links
 
 on:
-  push:
-    branches: [main, develop]
   pull_request:
-    branches: [main, develop]
+    branches: [main]
+  workflow_dispatch:
+    inputs:
+      check-type:
+        description: 'Which links to check'
+        required: true
+        default: 'all'
+        type: choice
+        options:
+          - all
+          - internal-only
+          - external-only
 
 jobs:
   internal-links:
     name: Check internal links
     runs-on: ubuntu-latest
+    if: >-
+      github.event_name != 'workflow_dispatch' ||
+      github.event.inputs.check-type == 'all' ||
+      github.event.inputs.check-type == 'internal-only'
     steps:
       - uses: actions/checkout@v4
       - uses: actions/setup-node@v4
         with:
           node-version: 20
+      - run: npm install github-slugger puppeteer
       - run: node scripts/check-links/index.mjs --internal-only
 
   external-links:
     name: Check external links
     runs-on: ubuntu-latest
-    if: github.ref == 'refs/heads/main'
+    if: >-
+      github.event_name == 'workflow_dispatch' &&
+      (github.event.inputs.check-type == 'all' ||
+       github.event.inputs.check-type == 'external-only')
     continue-on-error: true
     steps:
       - uses: actions/checkout@v4
       - uses: actions/setup-node@v4
         with:
           node-version: 20
+      - run: npm install github-slugger puppeteer
       - run: node scripts/check-links/index.mjs --external-only

.github/workflows/s3-deploy-development.yml

@@ -4,7 +4,19 @@ on:
     branches:
       - develop
 jobs:
-  run:
+  check-internal-links:
+    name: Check internal links
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-node@v4
+        with:
+          node-version: 20
+      - run: npm install github-slugger
+      - run: node scripts/check-links/index.mjs --internal-only
+
+  deploy:
+    needs: check-internal-links
     runs-on: ubuntu-latest
     environment: development
     env:
@@ -30,4 +42,4 @@ jobs:
           delete-removed: true
           # no-cache: true
           private: true
-          # files-to-include: '{.*/**,**}'Add comment
+          # files-to-include: '{.*/**,**}'

.github/workflows/s3-deploy-production.yml

@@ -4,7 +4,19 @@ on:
     branches:
       - main
 jobs:
-  run:
+  check-internal-links:
+    name: Check internal links
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-node@v4
+        with:
+          node-version: 20
+      - run: npm install github-slugger
+      - run: node scripts/check-links/index.mjs --internal-only
+
+  deploy:
+    needs: check-internal-links
     runs-on: ubuntu-latest
     environment: production
     env:

.github/workflows/translate.yml

@@ -17,9 +17,12 @@ jobs:
 
     steps:
       - uses: actions/checkout@v4
+        with:
+          # Need parent commit to compute the diff
+          fetch-depth: 2
 
       # Hashes are gitignored but must persist between runs so --incremental
-      # only re-translates files that actually changed since the last run.
+      # only re-translates sections that actually changed within a file.
       # The key includes the commit SHA so each push creates a new entry;
       # restore-keys fetches the most recent previous entry as a fallback.
       - name: Restore translation hash cache
@@ -37,10 +40,46 @@ jobs:
       - name: Install dependencies
         run: npm ci
 
+      # Split the diff into added/modified files (to translate) and deleted files (to clean up).
+      - name: Get changed translatable files
+        id: diff
+        run: |
+          CHANGED=$(git diff --name-only --diff-filter=AMR HEAD^1 HEAD \
+            | grep -E '^(src/content/docs/.+\.mdx|src/data/sidebars/.+\.json|src/api-reference/specs/[^./]+\.yaml)$' \
+            | tr '\n' ',' | sed 's/,$//')
+          DELETED=$(git diff --name-only --diff-filter=D HEAD^1 HEAD \
+            | grep -E '^(src/content/docs/.+\.mdx|src/api-reference/specs/[^./]+\.yaml)$' \
+            | tr '\n' ',' | sed 's/,$//')
+          echo "files=$CHANGED" >> $GITHUB_OUTPUT
+          echo "deleted=$DELETED" >> $GITHUB_OUTPUT
+
       - name: Translate changed files
+        if: steps.diff.outputs.files != ''
         env:
           ANTHROPIC_API_KEY: ${{ secrets.ANTHROPIC_API_KEY }}
-        run: node scripts/translate.mjs --incremental
+        run: node scripts/translate.mjs --incremental --only-files "${{ steps.diff.outputs.files }}"
+
+      # Remove translated files and hash caches for deleted source content.
+      # Sidebars are intentionally excluded: deleting a sidebar JSON is rare and
+      # rebuildSidebarLabels will naturally omit it on the next sidebar update.
+      - name: Clean up deleted translations
+        if: steps.diff.outputs.deleted != ''
+        run: |
+          for SRC_PATH in $(echo "${{ steps.diff.outputs.deleted }}" | tr ',' '\n'); do
+            BASENAME=$(basename "$SRC_PATH")
+            EXT="${BASENAME##*.}"
+            NAME="${BASENAME%.*}"
+            for LOCALE_DIR in src/locales/*/; do
+              if [ "$EXT" = "mdx" ]; then
+                rm -f "${LOCALE_DIR}${NAME}.mdx"
+                rm -f "${LOCALE_DIR}.hashes/${NAME}.json"
+              elif [ "$EXT" = "yaml" ]; then
+                # Remove all localized variants: adapty-api.zh.yaml, etc.
+                rm -f src/api-reference/specs/${NAME}.*.yaml
+                rm -f "${LOCALE_DIR}.hashes/api-specs/${NAME}.json"
+              fi
+            done
+          done
 
       # Commit any new or updated locale files back to main.
       # This push triggers s3-deploy-production.yml, so the deploy that follows

.gitignore

@@ -24,8 +24,12 @@ yarn-error.log*
 /.idea
 /static/*
 !/static/api/
+/.claude/projects
 
 /_temp
+/docs/superpowers
+/.superpowers
+.impeccable.md
 
 # Translation
 .translate-batch-id
@@ -227,3 +231,4 @@ src/locales/zh/.hashes/
 /versioned_docs/version-3.0/sdk-installation-capacitor.md
 
 .worktrees/
+_temp/

CLAUDE.md

@@ -164,3 +164,27 @@ These are layout/interactive components in `src/components/`, not imported by ar
 ## Reference
 
 Comprehensive component examples and writing guidelines: `TECH_WRITERS_README.md`
+
+## Design Context
+
+### Users
+Mobile developers (iOS, Android, React Native, Flutter, Unity, KMP, Capacitor) integrating Adapty's in-app purchase and subscription SDK. Technical, time-conscious, task-focused — they arrive to find an answer and get unblocked.
+
+### Brand Personality
+**Reliable, clean, developer-first.** Direct and precise. No marketing fluff. Trust is earned by making the right answer obvious and getting out of the developer's way.
+
+### Emotional Goals
+Developers should feel **confident** (know exactly what to do), **fast** (find things without hunting), and **welcomed** (smooth onboarding, low barrier to entry).
+
+### Reference
+**Stripe Docs** — authoritative, information-dense but scannable, strong typographic hierarchy, no decoration for decoration's sake.
+
+### Anti-References
+No heavy animations, neon gradients, or glassmorphism. No generic corporate feel. No cluttered sidebars or competing CTAs. No playful/toy-like UI — this is a technical reference.
+
+### Design Principles
+1. **Clarity over cleverness** — every decision serves comprehension, nothing else
+2. **Scannability first** — headers, code blocks, callouts, and step numbers are navigation anchors
+3. **Trust through restraint** — one brand color (`#6720ff`), subtle shadows, consistent spacing
+4. **Code is first-class** — code blocks, syntax highlighting, copy buttons must be beautiful in both themes
+5. **Dark mode is equal, not secondary** — full design target, no contrast or legibility compromises

TECH_WRITERS_README.md

@@ -116,13 +116,17 @@ Display images with click-to-zoom functionality. Automatically resolves images f
 - `width` (optional): Image width, default: "700px"
 - `alt` (optional): Alt text, defaults to filename
 - `className` (optional): Additional CSS classes
+- `href` (optional): URL to link the image to. Disables zoom — the image becomes a clickable link instead.
 
 **Usage:**
 
 ```mdx
 import ZoomImage from '@site/src/components/ZoomImage.astro';
 
 <ZoomImage id="screenshot.png" width="700px" alt="Dashboard screenshot" />
+
+{/* Image as a link (no zoom) */}
+<ZoomImage id="banner.webp" href="https://example.com" alt="Click to visit" />
 ```
 
 **Image resolution:**

astro.config.mjs

@@ -27,7 +27,20 @@ export default defineConfig({
     inlineStylesheets: 'never',
   },
   vite: {
-    plugins: [tailwindcss()],
+    plugins: [
+      tailwindcss(),
+    ],
+    server: {
+      watch: {
+        ignored: [
+          '**/.DS_Store',
+          '**/.Spotlight-V100/**',
+          '**/.DocumentRevisions-V100/**',
+          '**/.astro/content-modules.mjs',
+          '**/src/assets/**',
+        ],
+      },
+    },
     define: {
       global: 'window',
       'process.env': '{}',