Recovery and lifecycle
Preserve the evidence before changing the state.
Start from the observed symptom. Placement, discovery, invocation, helper execution, research quality, and publication are different failure boundaries.
Skill is not discoverable
Confirm that SKILL.md is at the imported directory root, the complete directory was imported, the host lists omnara-deep-research, and the session began after installation. If the host requires a plugin manifest, use Nova + MIND or the host's supported packaging path. Plain chat can use the copy/paste fallback.
Campaign initialization refuses the destination
The initializer will not overwrite a nonempty directory. Inspect the existing location and choose a new path or deliberately move the old campaign. Do not delete it until you know whether it contains evidence worth preserving.
Validation reports state or counter errors
Correct the canonical ledger or campaign state, not merely the displayed counter. A deeply-read state requires a substantive source note. Excluded, duplicate, or inaccessible terminal states cannot also masquerade as opened, deeply read, or cited.
Search, access, or budget fails
Checkpoint the verbatim inquiry, coverage map, queries, evidence already earned, counts, blockers, lost assurance, and exact resume point. Label unexecuted work explicitly. A budget or access stop is not completion.
Update
- Checkpoint and back up active campaigns.
- Record the current release or commit.
- Replace the exact skill through the host; do not merge versions file by file.
- Start a fresh session and repeat discovery and invocation.
- Validate an existing campaign before resuming.
Integrated Nova + MIND installations must use the Nova upgrade guide.
Remove and clean up
Disable and remove only omnara-deep-research through the host, then verify it is no longer discoverable in a fresh session. This does not remove campaign directories, reports, downloaded ZIPs, caches, browser history, provider logs, backups, or Nova + MIND data. Review exact campaign paths before using a recoverable trash operation.
Get help or contribute
Open a GitHub issue with release or commit, host, OS, Python version when relevant, exact command or prompt, expected and observed results, and complete error. Remove secrets and private sources. Security reports follow the private-reporting policy.