Design editor.md integration with lecturer automated fixes

[dcasota]

Task Description

Design how to integrate photonos-docs-lecturer automated fixes into editor droid.

Design Decisions Needed

1. Fix Categories to Enable:

   • Deterministic (FIX_ID 2,3,7,8) - always?
   • LLM-assisted (FIX_ID 9,10,11) - optional?
   • Special (FIX_ID 13,14) - default disabled?

2. LLM Configuration:

   • Require GEMINI_API_KEY?
   • Fallback without LLM?
   • Alternative: XAI_API_KEY?

3. Selective Fixing:

   • By category (critical, branding, formatting)?
   • By FIX_ID?
   • All at once?

4. Validation Strategy:

   • Automatic rollback on failure?
   • Run installer.sh after fixes?
   • Quality metric comparison?

5. Integration Method:

   • Use lecturer's run command?
   • Disable PR creation (editor handles)?
   • Custom fix application?

Deliverables

• Updated editor.md specification
• Fix workflow design
• Rollback strategy

Acceptance Criteria

• ✅ Fix strategy decided
• ✅ editor.md specification updated
• ✅ Validation approach defined
• ✅ Ready to implement

Related

• Integration Analysis: EDITOR Enhancement section
• Integration Analysis: Medium-term Actions fix(installer): ensure menu configuration is always added to config.toml #9

Labels

lecturer-integration, editor, design, medium