Gabeujin Workspace Reconcile Safety
Use this skill when an existing repository or an older workspace-init-mcp output must be upgraded without losing governed work.
Safety Rules
- Prefer a dry run first. Review planned writes, merges, legacy imports, and manual-review items before applying.
- Treat runtime, dashboard, and readiness JSON as merge candidates, not disposable files.
- Archive replaced managed files so restore is possible through reconcile backups.
- If a git repository exists, prefer a clean checkpoint before applying reconcile.
- Preserve custom skills and agents by importing them into canonical
.githubpaths instead of deleting older IDE-specific copies.
Recommended Flow
- Analyze the workspace and confirm the inferred project type, domains, and IDE targets.
- Run a dry reconcile plan and inspect the migration report.
- Review any manual-review items and custom generated-file drift.
- Apply reconcile only after the plan looks safe.
- Validate the workspace and refresh the dashboard afterward.
- If needed, restore managed files from the reconcile backup report.
Output Expectations
- A clear list of planned or applied writes
- Explicit warnings about git, missing backups, or manual-review items
- Durable migration artifacts under
docs/ai-harness/migrations/ - A restore path when managed files were refreshed