Update to Riqor

{
  "description": "Use when an AI coding agent needs to diagnose Riqor installation, package integrity, shell integration, plugin state, or managed-session failures.",
  "included_files": [],
  "name": "riqor-diagnostics",
  "skill_md_contents": "---\nname: riqor-diagnostics\ndescription: Use when an AI coding agent needs to diagnose Riqor installation, package integrity, shell integration, plugin state, or managed-session failures.\n---\n\n# Riqor Diagnostics\n\nDiagnose from the narrowest boundary outward and preserve the original failure evidence\n\n## First checks\n\n```bash\nriqor version --json\nriqor status --json\nriqor doctor --json\n```\n\nUse `riqor doctor --package-only --json` when testing the npm payload without requiring Codex\n\n## Classify the failure\n\n- Package metadata or provenance: inspect the installed versioned payload and provenance result\n- Executable ownership: verify `riqor`, `codex-harness`, and `cxh` are Riqor-managed before replacing anything\n- Shell integration: inspect managed markers and XDG paths; malformed markers must fail closed\n- Codex plugin: use an isolated `CODEX_HOME` for reproduction and do not reuse personal auth state in fixtures\n- Activator: confirm the session was launched by `riqor codex --activator` and inspect timing boundaries\n- Evidence state: distinguish a real verification-pending transition from stale or malformed state\n\n## Recovery rules\n\n- Preserve foreign files and executables\n- Never follow a symlink and overwrite its target during repair\n- Back up user shell configuration before a managed rewrite\n- Prefer idempotent repair followed by a fresh doctor run\n- Do not delete repository run records merely to make diagnostics green\n\nAfter a repair, rerun the exact failing check and then the relevant package or repository regression suite\n"
}