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/operations/deployment.md

@@ -0,0 +1,39 @@
+---
+name: deployment-basics
+description: Deployment documentation, environment setup, runbook, and rollback basics.
+tags: ['operations', 'deployment']
+---
+
+# Deployment Basics
+
+## Purpose
+Standardize deployment operations: environment documentation, runbook creation, rollback procedures.
+
+## When to Use
+- Before any production deployment
+- When setting up a new environment
+- After a release for handoff
+- When rollback is needed
+
+## Procedure: Environment Setup
+1. Document required variable names from safe sources only (`.env.example`, docs, schemas, compose placeholders, Coolify redacted status). Do not read live `.env`, runtime env dumps, credential stores, shell history, or logs to discover secret values.
+2. Document required system dependencies
+3. Document required network access (ports, domains)
+4. Create env.example file with placeholders
+
+## Procedure: Runbook
+1. Pre-deploy: verify env, run tests, backup current state
+2. Deploy: step-by-step commands with expected output
+3. Post-deploy: health check, optional public reachability test, bounded error-log review
+4. Rollback: revert steps, restore backup, verify
+
+## Procedure: Rollback
+1. Identify the last known good state
+2. Revert code (git checkout <tag>)
+3. Restore database (if schema changed)
+4. Verify health and public reachability tests; skip authenticated tests unless user-provided test account exists for this task
+5. Document rollback reason in worklog
+
+## See Also
+- Tool: `deployment_runner` (if available in plugin)
+- Help: `operations/runtime.md`

help/operations/git.md

@@ -0,0 +1,32 @@
+---
+name: git-workflow
+description: Git discipline for plugin development - branch, commit after logical blocks, no main push without approval.
+tags: ['operations', 'git']
+---
+
+# Git Workflow
+
+## Purpose
+Enforce git discipline: branch, commit after logical blocks, no push to main without explicit user approval.
+
+## When to Use
+After each implementation block or when project state files are updated.
+
+## When Not to Use
+When git is not available or the project is not yet a git repository.
+
+## Procedure
+1. Check git availability (`which git`)
+2. Ensure working on feature branch (`git branch --show-current`)
+3. Stage changed files (`git add <files>`)
+4. Write descriptive commit message (docs:, feat:, test:, deploy:)
+5. Commit changes (`git commit -m "..."`)
+6. Do NOT push to main without explicit user approval
+7. Update .a0/worklog.md with commit reference
+
+## Quality Gates
+Commit after logical blocks, no main push without approval, descriptive messages.
+
+## See Also
+- Tool: `git` (core Agent Zero tool)
+- Skill: `git-workflow` (global)

help/operations/runtime.md

@@ -0,0 +1,36 @@
+---
+name: runtime-verification
+description: Start app, bounded error-log review and healthcheck workflow for the runtime_devops_engineer. Browser/UI checks are opt-in and public-only by default.
+tags: ['operations', 'runtime', 'verification']
+---
+
+# Runtime Verification
+
+## Purpose
+Verify the application actually starts, responds to health checks, and behaves correctly before declaring a build successful.
+
+## When to Use
+- After implementation completes
+- Before declaring a build successful
+- After deployment for health/reachability testing
+- During debugging of startup issues
+
+## Procedure
+1. Discover start command (package.json scripts, Makefile, docker-compose)
+2. Start the app in background or as a service
+3. Wait for startup completion (configurable timeout)
+4. Check health endpoint (GET /health, /api/health, etc.)
+5. Capture bounded runtime error output only; never search logs for credentials, cookies, tokens, session data or login material
+6. Optional public browser reachability check only after explicit user approval; do not attempt login or authenticated access
+7. Stop the app gracefully
+8. Return structured handoff
+
+## Quality Gates
+- App starts without errors (no ImportError, no 500)
+- Health endpoint returns 200
+- Bounded error output shows no critical errors
+- Public reachability test passes (if applicable); authenticated UI tests are skipped unless the user provides a test account in the current task
+
+## See Also
+- Tool: `browser` (optional public reachability only; never for credential discovery or login attempts)
+- Help: `operations/deployment.md`