Docs

• Docs/09-extending/
• Docs/10-testing/
• Docs/12-config-wizard/
• Docs/appendix/
• Docs/examples/
• Docs/user-manual/

Also update the top-level Docs/README.md in Batch 2.

Instructions for each Agent

Each agent receives this task:

Read every .md file in your assigned directory. For each file:

1. Identify all references to code files, classes, methods, configuration keys, CLI commands, enums, or interfaces.
2. Find and read the referenced source code in the codebase to verify accuracy.
3. Update the documentation so it matches the current code. This includes:
   • Class/method/property names and signatures
   • Configuration keys and their types/defaults
   • Enum values and their numeric codes
   • CLI command names, options, and descriptions
   • Code examples and snippets
   • File paths and project references
4. Preserve the existing structure, tone, and formatting of each document.
5. Do NOT modify any source code files - only update .md files under Docs/.
6. Remove dead documentation: If a documented class, method, enum, configuration key, CLI option, or feature no longer exists in the codebase, remove the corresponding section, table row, list item, or code example entirely. Do not leave stubs, "removed" notes, or placeholders. If removing a section leaves a parent section empty, remove the parent too.
7. Document undocumented code: After verifying existing content, search the codebase for classes, methods, enums, configuration keys, CLI commands, and public APIs that fall within the scope of this document but are not yet documented. Add them in the appropriate location within the document, matching the existing style and level of detail. Scope is determined by the document's topic - e.g., a database-layer doc should cover all DAL classes, a CLI-reference doc should cover all registered commands.

Phase 2 - Consolidation

After all Phase 1 agents complete, launch a single general-purpose Agent to:

Read ALL .md files under ./Docs/. Check for:

1. Contradictions: Same concept described differently in multiple files (e.g., different default values, conflicting enum names). Fix by aligning with the source code.
2. Duplications: Identical content repeated across files. Consolidate into one authoritative location and cross-reference from others.
3. Missing cross-references: Where one doc mentions a concept explained in detail elsewhere, add a See [link](path) reference.
4. Consistency: Ensure terminology is uniform (e.g., always "target group" not sometimes "target-group" and sometimes "TargetGroup" in prose).
5. If consolidation leaves a section empty or redundant, remove it.
6. Only modify .md files under Docs/.

Phase 3 - Link Validation

After Phase 2 completes, launch a single general-purpose Agent to:

Check ALL internal markdown links in files under ./Docs/:

1. For every [text](relative/path) link, verify the target file exists at that relative path.
2. For every [text](path#anchor) link, verify both the file exists AND the anchor heading exists in the target file.
3. Check links in CLAUDE.md that point to Docs/ as well.
4. Fix any broken links:
   • Correct the path if the file was moved/renamed
   • Remove the entire link and surrounding sentence/item if the target no longer exists and the content is obsolete
   • Fix anchor references to match actual heading text
5. Only modify .md files.
6. Report a summary of all fixes made.

Final Summary

After all 3 phases complete, provide a summary to the user:

• Number of files updated per phase
• Key changes made (new sections, removed outdated info, fixed links)
• Any issues that need manual review