Initial commit: a0_software_orchestrator v1.0

- Auto-Registration-Bug behoben (register_project/get_project_id/resolve_project Trennung)
- 25 Tests gruen (Pytest)
- block_compactor-Tool refactored (Option B: Soft-Check statt Hard-Block)
- 4 Restbaustellen gefixt
- DB-Schema: plugin_settings-Tabelle hinzugefuegt
- 3 Schattenprojekte aus DB geloescht
- Plan v3 + Refactor-Plan + Worklog dokumentiert

help/management/errors.md

@@ -0,0 +1,38 @@
+---
+name: error-tracking
+description: Known errors lifecycle management and recovery for the orchestrator agent.
+tags: ['management', 'errors', 'tracking']
+---
+
+# Error Tracking
+
+## Purpose
+Track known errors across sessions, document their root cause and solution, and reuse the knowledge for future occurrences.
+
+## When to Use
+- When a tool or subordinate returns a persistent error
+- When a code block fails compilation or tests
+- When the agent encounters an unknown error
+- After resolution to log the solution
+
+## When Not to Use
+- For transient network blips (retry once, then log)
+- For user input errors (request clarification instead)
+
+## Procedure: Error Logging
+1. Capture full error output (stack trace, message, context)
+2. Search the library for similar past errors (use library-query)
+3. If a similar error exists, apply the documented solution
+4. If new error, document: title, symptom, cause, fix, tags, project_id
+5. Extract to library (use library-extractor) for future reference
+
+## Procedure: Resolution
+1. Apply minimal targeted fix
+2. Run tests to verify
+3. Commit the fix
+4. Update error entry with resolution status
+
+## See Also
+- Help: `library/extract.md`
+- Help: `library/query.md`
+- Tool: `error_handler` (if available in plugin)