test: kitchen sink workflow validation v2

This PR validates the translation workflow after config-driven refactoring:

Changes:
- Add new test file: test-workflow-validation.mdx
- Modify existing file: introduction.mdx
- Update docs.json navigation

Tests:
- New file translation (add workflow)
- Existing file translation (update workflow)
- Navigation sync across languages
- Config-driven language codes (zh/ja instead of cn/jp)
- Source language abstraction (no hardcoded "English")

Expected workflow behavior:
1. Detect changes in en/ directory
2. Translate new file to zh and ja
3. Update modified file translations
4. Sync docs.json for all language sections
5. Commit translated files automatically

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>

docs.json

@@ -36,7 +36,8 @@
                           "pages": [
                             "en/use-dify/getting-started/introduction",
                             "en/use-dify/getting-started/quick-start",
-                            "en/use-dify/getting-started/key-concepts"
+                            "en/use-dify/getting-started/key-concepts",
+                            "en/use-dify/getting-started/test-workflow-validation"
                           ]
                         },
                         {

en/use-dify/getting-started/introduction.mdx

@@ -30,5 +30,5 @@ Dify is an open-source platform for building agentic workflows. It lets you defi
 </CardGroup>
 
 <Info>
-  The name Dify comes from **D**o **I**t **F**or **Y**ou.
+  The name Dify comes from **D**o **I**t **F**or **Y**ou. This platform empowers developers to build sophisticated AI applications without needing deep machine learning expertise.
 </Info>

en/use-dify/getting-started/test-workflow-validation.mdx

@@ -0,0 +1,45 @@
+---
+title: "Test Workflow Validation"
+description: "Test file to validate the translation workflow after config-driven refactoring"
+---
+
+# Test Workflow Validation
+
+This is a test file created to validate that the translation workflow works correctly after refactoring the codebase to be fully config-driven.
+
+## Purpose
+
+This file tests:
+- **New file addition**: Translation workflow should detect this file and create zh/ja versions
+- **Config-driven language codes**: All hardcoded `cn`/`jp` references replaced with `zh`/`ja` from config.json
+- **Source language abstraction**: System now uses "source language" instead of hardcoded "English"
+
+## Expected Behavior
+
+When this PR is created, the GitHub Actions workflow should:
+
+1. Detect this new file in `en/use-dify/getting-started/`
+2. Translate it to Chinese (zh) and Japanese (ja) using the Dify API
+3. Add the translated files to the corresponding locations
+4. Update docs.json for all language sections
+
+## Test Coverage
+
+This kitchen sink PR includes:
+- ✅ New file addition (this file)
+- ✅ File modification (introduction.mdx)
+- ✅ docs.json navigation update
+
+## Verification Steps
+
+After the workflow completes:
+1. Check for `zh/use-dify/getting-started/test-workflow-validation.mdx`
+2. Check for `ja/use-dify/getting-started/test-workflow-validation.mdx`
+3. Verify docs.json has been updated for all language sections
+4. Confirm translations are accurate and include AI notice
+
+---
+
+**Test Date**: November 27, 2025
+**Refactoring**: Config-driven language system
+**Branch**: test/kitchen-sink-workflow-validation-v2